Page 1 of 3

Re: ESP Easy development status

Posted: 28 Jan 2017, 22:10
by JayJay
Martinus, ik hoop dat het weer goed komt met je! Sterkte man, en enorm veel dank voor het prachtige werk wat je geleverd hebt.

Het gaat je goed.

Jan

Re: ESP Easy development status

Posted: 02 Feb 2017, 16:19
by beic
I think our friend got a lifetime offer in the same branch! ;)

But that is the life path I think!

Kind regards,
Viktor

Re: ESP Easy development status

Posted: 02 Feb 2017, 18:14
by JR01
What if we all pay an amnt per ESPEasy install - and ask Martinus to keep going where we pay per install to carry on?

Re: ESP Easy development status

Posted: 02 Feb 2017, 20:04
by NietGiftig
beic wrote:I think our friend got a lifetime offer in the same branch! ;)
And that would be quite right, but not our business, mind you
The complete code is on github, anybody who want to continue with the project is free to fork it

Re: ESP Easy development status

Posted: 03 Feb 2017, 08:02
by beic
NietGiftig wrote: And that would be quite right, but not our business, mind you
I'm not mind at all, but little bit sad... :(
NietGiftig wrote: The complete code is on github, anybody who want to continue with the project is free to fork it
Unfortunately, after 1 month past, there is no one to continue his work/steps, and I'm afraid that this beautiful project is abandoned! :(

Kind regards,
Viktor

Re: ESP Easy development status

Posted: 03 Feb 2017, 14:45
by DeNB3rt
maybe, it is already quite complete the latest build :)

Re: ESP Easy development status

Posted: 03 Feb 2017, 15:51
by NietGiftig
DeNB3rt wrote:maybe, it is already quite complete the latest build :)
Thatś what I was thinking.
And those people who think that they can enhance it, please fork it, and tell us about it.
Waiting in anticipation.

Re: ESP Easy development status

Posted: 03 Feb 2017, 17:09
by Alexs
NietGiftig wrote: The complete code is on github, anybody who want to continue with the project is free to fork it
Exactly right, you can fork it, or as Martinus said you can join the github project and contribute to the core.
beic wrote: Unfortunately, after 1 month past, there is no one to continue his work/steps, and I'm afraid that this beautiful project is abandoned! :(
I have just joined the community, and the github project :)

Re: ESP Easy development status

Posted: 03 Feb 2017, 19:52
by mrwee
Personally I'd ruin ESPeasy if I was to contribute with coding, but I'd be happy to donate money if it could ensure the project's future.

Re: ESP Easy development status

Posted: 13 Feb 2017, 18:57
by psy0rz
Awww..too bad...I just discovered the project a few weeks ago.

Thanks for the great work martinus!

If we just have someone that could merge all the pull requests, the project might continue on.

Since the software architecture is quite nice, i'm willing to try it.

Edwin

Re: ESP Easy development status

Posted: 13 Feb 2017, 20:19
by NietGiftig
psy0rz wrote: If we just have someone that could merge all the pull requests, the project might continue on.
Since the software architecture is quite nice, i'm willing to try it.
You do not merge without good knowledge of the complete system.
So a "someone" to merge ?
Merging is not so difficult, but how to guaranty the quality?

Better to fork the existing project and merge the things you like.

Re: ESP Easy development status

Posted: 13 Feb 2017, 20:26
by ayasystems
A lot of fork is the best way to kill the project ... some one should take the main code

Re: ESP Easy development status

Posted: 13 Feb 2017, 20:33
by NietGiftig
ayasystems wrote:A lot of fork is the best way to kill the project ... some one should take the main code
If your fork is reliable people can choose.

Re: ESP Easy development status

Posted: 13 Feb 2017, 20:57
by psy0rz
Forking isn't the correct solution for this situation: The original project is stalled, we need someone to continue the project.

I've already reviewed a lot of the pull requests that are open and responded to them. Some of those pull requests can be merged with little knowledge of the rest of the project. (since they are simple bugfixes/features)

I will now start reviewing the rest of the code base and determine if I can handle it.

Maybe we should continue the discussion here: viewtopic.php?f=14&t=2617

I've posted more details there.

Edwin

Re: ESP Easy development status

Posted: 15 Feb 2017, 19:10
by psy0rz
(cross post, for people that only follow this thread)

Ok i've pretty much have things up and running.

Have a look at the README over here to see whats going on: https://github.com/psy0rz/ESPEasy/blob/master/README.md

I've already merged a pull request: https://github.com/letscontrolit/ESPEasy/pull/96

If you guys want to test to see if everything is working like you would expect, that would be great.

Please let me know what you think,
Edwin

Re: ESP Easy development status

Posted: 15 Feb 2017, 19:21
by NietGiftig
I'm glad you forked it, you seem to have some knowledge in this field,
You did exact what I was proposing.
But your actions are not in line with you're statements :o
psy0rz wrote:Forking isn't the correct solution for this situation: The original project is stalled, we need someone to continue the project.
Edwin

Re: ESP Easy development status

Posted: 15 Feb 2017, 20:12
by frank
This is great.
Are you going to pick up the experimental stuf to?

Re: ESP Easy development status

Posted: 15 Feb 2017, 20:33
by psy0rz
We're talking about 2 different kind of forks here, it could either mean:

1. There is some disagreement, or someone wants to go a different direction than the original project. Hence the whole PROJECT is forked, starting a new project. Perhaps a different name and perhaps a new site/wiki/forum. (I have no interest in doing that at all.)

2. Someone on is starting work on a temporary branch (github calls it a fork) to continue the project for practical reasons, but is still working on the same project with the same people.

I'm number 2: As soon as I have access to the main repository I will continue there and merge back my changes to the main repository. (since development there stopped this will be very easy since there are no changes to merge)

I still dont have contact with anyone who can help me with that. (Martinus hasn't responded yet, but it's only been a few days since my first message)

Maybe its better this way: People can see what kind of changes I want to make and determine if they like it, before handing over "the keys" so to speak. :)

Edwin

NietGiftig wrote:I'm glad you forked it, you seem to have some knowledge in this field,
You did exact what I was proposing.
But your actions are not in line with you're statements :o
psy0rz wrote:Forking isn't the correct solution for this situation: The original project is stalled, we need someone to continue the project.
Edwin

Re: ESP Easy development status

Posted: 15 Feb 2017, 20:38
by psy0rz
frank wrote:This is great.
Are you going to pick up the experimental stuf to?
I would love to add all the experimental plugins that do not require changes to the code base. So keep the base stable, but have an option for users to enable a potential unstable plugin from the webgui.

Look here to find out about the different releases that contain these experimental plugins: https://github.com/psy0rz/ESPEasy/blob/ ... management

Re: ESP Easy development status

Posted: 15 Feb 2017, 21:21
by NietGiftig
psy0rz wrote:
Maybe its better this way: People can see what kind of changes I want to make and determine if they like it, before handing over "the keys" so to speak. :)
Edwin
Yes, that's what I intended to say !!

Please make an link in your signature with a short explanation, so people go to the temporary fork

Re: ESP Easy development status

Posted: 15 Feb 2017, 21:46
by psy0rz
NietGiftig wrote:
psy0rz wrote:
Maybe its better this way: People can see what kind of changes I want to make and determine if they like it, before handing over "the keys" so to speak. :)
Edwin
Yes, that's what I intended to say !!

Please make an link in your signature with a short explanation, so people go to the temporary fork
Ok sorry. :) there was a bit of confusion so i wanted to make absolutely clear. (my head is still in coding mode ;)

I added a simple signature as well. thanks.

Re: ESP Easy development status

Posted: 15 Feb 2017, 21:49
by frank
psy0rz wrote:
frank wrote:This is great.
Are you going to pick up the experimental stuf to?
I would love to add all the experimental plugins that do not require changes to the code base. So keep the base stable, but have an option for users to enable a potential unstable plugin from the webgui.

Look here to find out about the different releases that contain these experimental plugins: https://github.com/psy0rz/ESPEasy/blob/ ... management
That is great but wat i ment is the experimental stuf like the arduino easy and the arduino mega stuf

Re: ESP Easy development status

Posted: 15 Feb 2017, 21:57
by psy0rz
No, I will focus purely on the ESPeasy coding. If someone wants to maintain that stuff but needs some initial help with improving the development process I might be able to do that.

I also dont have time to do the many other things: Maintaining forums and wikis and giving general support, but I assume there are already people that are doing a great job with that? (wiki seems pretty nice so far, and i like the direct links from the webgui in esp easy)

If people prefer some pull requests or playground plugins to be handled first let me know, otherwise I will get the long hanging fruit first. (easy merges with minimal impact on code base)

Edwin

Re: ESP Easy development status

Posted: 16 Feb 2017, 11:48
by psy0rz
I have contact with Martinus and access to the main repository. Fortunately he will stay involved with the project, but currently doesn't have the time to do any real coding. So he'll be on the background (for now).

I'll keep you posted.

Re: ESP Easy development status

Posted: 16 Feb 2017, 12:15
by ayasystems
Thanks psy0rz!

Re: ESP Easy development status

Posted: 17 Feb 2017, 19:50
by frank
i am getting verry happy from all this good news :D :D :D :D :D

But it wood be even beter if someone picks up the expirimental stuf :D :D :D :D

I can do testing and assist withthe wiki

Re: ESP Easy development status

Posted: 17 Feb 2017, 20:10
by mrwee
What about the forum? Would be nice if 'we' had multiple sub-groups e.g. per plugin, subjects like 'mqtt', 'openhab','"domoticz', etc.
Also, how to cope with change requests in a structured way?

Re: ESP Easy development status

Posted: 17 Feb 2017, 20:14
by frank
mrwee wrote:What about the forum? Would be nice if 'we' had multiple sub-groups e.g. per plugin, subjects like 'mqtt', 'openhab','"domoticz', etc.
Also, how to cope with change requests in a structured way?
that would be great with a timeline etc.with wat happens when

Re: ESP Easy development status

Posted: 18 Feb 2017, 17:34
by psy0rz
mrwee wrote:What about the forum? Would be nice if 'we' had multiple sub-groups e.g. per plugin, subjects like 'mqtt', 'openhab','"domoticz', etc.
Also, how to cope with change requests in a structured way?
It would be great if the current forum admins can make decisions about changes like this and handle it. Maybe you can ask them via pm or something?

Re: ESP Easy development status

Posted: 21 Feb 2017, 10:43
by DeNB3rt
mrwee wrote:What about the forum? Would be nice if 'we' had multiple sub-groups e.g. per plugin, subjects like 'mqtt', 'openhab','"domoticz', etc.
Also, how to cope with change requests in a structured way?
agree :)

Re: ESP Easy development status

Posted: 21 Feb 2017, 11:57
by psy0rz
Change requests should perhaps go on the issue tracker on github. (https://github.com/letscontrolit/ESPEasy/issues)

Support requests and discussion should stay on the forum.

Re: ESP Easy development status

Posted: 03 Mar 2017, 00:17
by psy0rz
Ok i just finshed a lot of tutorials, explaining everything about platformio and github.

They are at the bottom of this page: http://www.letscontrolit.com/wiki/index ... evelopment

Re: ESP Easy development status

Posted: 03 Mar 2017, 08:14
by krikk
great tutorials, would have saved me a few hours if they where published a few days earlyer :D

Re: ESP Easy development status

Posted: 05 Mar 2017, 10:38
by BertB
@psy0rz
Great tutorial, works out fine, until you write about Smart Code Linter. Perhaps I installed it without knowing what I was doing.
May be this has nothing to do with my current problem, which is that nothing happens (well, Atom seizes to respond) after:

Building the correct version

Press F7 and you will get an overview of possible versions you can build:

I am working on a 64 bit windows 7 pc and could use some help.

Re: ESP Easy development status

Posted: 06 Mar 2017, 08:37
by krikk
smart code linter does not work because we are useing .ino files, it's in the FAQ of platformio... really annoying

Re: ESP Easy development status

Posted: 06 Mar 2017, 13:08
by BertB
@krikk
Okay .. so I removed github and atom completley from my pc and walked through the setup procedures again.
With Linter disabled and Clang (is that safe?) for a later remind.

Still the same problem. When I press F7, i get a pop-up saying that the editor is not reponding ...
Atom.png
Atom.png (255.66 KiB) Viewed 50794 times

Re: ESP Easy development status

Posted: 06 Mar 2017, 19:09
by krikk
did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)

Re: ESP Easy development status

Posted: 06 Mar 2017, 19:43
by BertB
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
Yas, I did.
You have no problems here?

Re: ESP Easy development status

Posted: 06 Mar 2017, 20:15
by BertB
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Atom2.png (176.19 KiB) Viewed 50743 times

Re: ESP Easy development status

Posted: 06 Mar 2017, 23:08
by BertB
BertB wrote: 06 Mar 2017, 20:15
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Somehow I managed to get the choice to select the Wemos D1 mini, but now Atom says it cannot compile because there is nothing in the .../ESPEasy/src folder

Re: ESP Easy development status

Posted: 07 Mar 2017, 14:15
by psy0rz
BertB wrote: 06 Mar 2017, 23:08
BertB wrote: 06 Mar 2017, 20:15
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Somehow I managed to get the choice to select the Wemos D1 mini, but now Atom says it cannot compile because there is nothing in the .../ESPEasy/src folder
Did you open the ESPEasy folder in Atom, or did you open the src folder directly? (you should open the ESPEasy folder)

Re: ESP Easy development status

Posted: 07 Mar 2017, 14:46
by BertB
Hi. Thanks for the reponse. I am desperately trying to get things up and running, cause I have a lot of ideas, however this kind of programming techniques, I am not familiar with. So please forgive me for asking many stupid questions.

Before I first managed to get any reponse to the F7 keystroke, I had to choose a board with the initialize or update button.
My working folder is /Documents/ESPEasy. In it are:
.git
.pioenvs
lib (with only readme.txt)
MiniProExtender
src (with some files starting with a . (dot)
and a lot of 'normal' ESPEasy stuff.

Then, after selecting ESPEasy.ino and the proper board and pressing F7, I got:
[03/07/17 14:41:34] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Collected 23 compatible libraries
Looking for dependencies...
Project does not have dependencies
Error: Nothing to build. Please put your source code files to 'C:\Users\Bert\Documents\ESPEasy\src' folder

[ERROR] Took 1.50 seconds
Environment d1_mini [ERROR]
[ERROR] Took 1.50 seconds

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
Environment nanoatmega328 [SKIP]

So, I moved the 'normal'ESPEasy files to the src folder.
Then, after pressing F7 again:

[03/07/17 14:44:44] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Converting ESPEasy.ino
Collected 23 compatible libraries
Looking for dependencies...
Library Dependency Graph

|-- <Servo(esp8266)> v1.0.2
|-- <Wire> v1.0
|-- <ESP8266WiFi> v1.0
|-- <ESP8266WebServer> v1.0
| |-- <ESP8266WiFi> v1.0
Compiling .pioenvs\d1_mini\src\ESPEasy.ino.o
Archiving .pioenvs\d1_mini\libFrameworkArduinoVariant.a
Compiling .pioenvs\d1_mini\FrameworkArduino\Esp.o
Compiling .pioenvs\d1_mini\FrameworkArduino\FS.o
C:/Users/Bert/Documents/ESPEasy/src/ESPEasy.ino:157:26: fatal error: PubSubClient.h: No such file or directory
#include <PubSubClient.h>
^
compilation terminated.
Compiling .pioenvs\d1_mini\FrameworkArduino\HardwareSerial.o
*** [.pioenvs\d1_mini\src\ESPEasy.ino.o] Error 1

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
[ERROR] Took 3.48 seconds
Environment d1_mini [ERROR]
[ERROR] Took 3.48 seconds
Environment nanoatmega328 [SKIP]

Re: ESP Easy development status

Posted: 07 Mar 2017, 14:53
by BertB
After that, I copied al the downloaded library files to the lib folder.
After hitting F7 again, I got:

[03/07/17 14:50:16] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Converting ESPEasy.ino
Collected 44 compatible libraries
Looking for dependencies...
Library Dependency Graph

|-- <Wire> v1.0
|-- <IRremoteESP8266>
|-- <PubSubClient> v2.6
|-- <Json> v5.6.4
|-- <ESP8266WebServer> v1.0
| |-- <ESP8266wifi-master>
| |-- <ESP8266WiFi> v1.0
|-- <LiquidCrystal_I2C>
| |-- <Wire> v1.0
|-- <ESP8266WiFi> v1.0
|-- <ESP8266wifi-master>
|-- <Servo(esp8266)> v1.0.2
Compiling .pioenvs\d1_mini\src\ESPEasy.ino.o
Archiving .pioenvs\d1_mini\libFrameworkArduinoVariant.a
Compiling .pioenvs\d1_mini\FrameworkArduino\Esp.o
Compiling .pioenvs\d1_mini\FrameworkArduino\FS.o
Compiling .pioenvs\d1_mini\FrameworkArduino\HardwareSerial.o
In file included from C:/Users/Bert/Documents/ESPEasy/src/ESPEasy.ino:153:0:
lib\ESP8266wifi-master/ESP8266WiFi.h:23:26: fatal error: avr/pgmspace.h: No such file or directory
#include <avr/pgmspace.h>
^
compilation terminated.
*** [.pioenvs\d1_mini\src\ESPEasy.ino.o] Error 1

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
Environment nanoatmega328 [SKIP]
[ERROR] Took 4.46 seconds
Environment d1_mini [ERROR]
[ERROR] Took 4.46 seconds

Re: ESP Easy development status

Posted: 07 Mar 2017, 14:57
by BertB
By the way,

I do not get your list after hitting F7, but this:
Atom3.png
Atom3.png (166.39 KiB) Viewed 52410 times

Re: ESP Easy development status

Posted: 07 Mar 2017, 15:01
by psy0rz
BertB wrote: 07 Mar 2017, 14:46 Before I first managed to get any reponse to the F7 keystroke, I had to choose a board with the initialize or update button.
Then something went wrong. You shouldn't need to initialize. (initializing creates or updates your platformio.ini, but we've already created a platformio.ini for you with all the nice options you should see in the F7 list)

Can you remove the ESPEasy directory completely, clone again with Github desktop, and then open it again with Atom and press F7.

If it hangs again when you pressed F7, wait a while (30 seconds or so) and then an error will pop up. Please create a screenshot of that.

Edwin

Re: ESP Easy development status

Posted: 07 Mar 2017, 19:47
by BertB
I did as you suggested.
This is the result.
Atom4.png
Atom4.png (32.59 KiB) Viewed 52376 times

Re: ESP Easy development status

Posted: 15 Mar 2017, 01:53
by psy0rz
In the meanwhile i also fixed building in Arduino IDE again and updated the wiki.

Use at least v2.0.0-dev7 and the changes i made here: https://www.letscontrolit.com/wiki/inde ... are_Upload

Re: ESP Easy development status

Posted: 19 Mar 2017, 18:33
by AndrewJ
Hi, and thanks for all the good work! I really like ESPeasy and have it on several nodemcu modules. I'm now trying to install it on a Sonoff switch.
I'm running Windows 10 and most of my experience is with the Arduino IDE rather than platformio.

A couple of questions about the Arduino IDE tutorial, as it applies on windows 10 ...
- Is it a specific intention to use Arduino IDE v. 1.6.12? When I followed the link to the main software page, it shows 1.8.1 as the current version. I decided to go ahead with that one (I used the Windows installer option). It wanted to uninstall my previous version so I said yes to that.
- It then installed the IDE in c:\Program files (x86) in a folder named simply Arduino. I'm unsure if this is the folder to rename with P230 at the end and create the folder named Portable, or is it somewhere else?
Please could you clarify a bit? Thanks in advance.
Andrew.

Re: ESP Easy development status

Posted: 19 Mar 2017, 19:53
by Shardan
AndrewJ wrote: 19 Mar 2017, 18:33 Hi, and thanks for all the good work! I really like ESPeasy and have it on several nodemcu modules. I'm now trying to install it on a Sonoff switch.
I'm running Windows 10 and most of my experience is with the Arduino IDE rather than platformio.

A couple of questions about the Arduino IDE tutorial, as it applies on windows 10 ...
- Is it a specific intention to use Arduino IDE v. 1.6.12? When I followed the link to the main software page, it shows 1.8.1 as the current version. I decided to go ahead with that one (I used the Windows installer option). It wanted to uninstall my previous version so I said yes to that.
- It then installed the IDE in c:\Program files (x86) in a folder named simply Arduino. I'm unsure if this is the folder to rename with P230 at the end and create the folder named Portable, or is it somewhere else?
Please could you clarify a bit? Thanks in advance.
Andrew.
Well, i'm not an expert and running Win7 but i'll try to answer your questions as good as possible.
At first: If you do a installer based installation you might run into problems when compiling old ESP-Sources (R14x)
or possibly sketches for other platforms - the configurations conflict, even if you make a second "portable" installation.
I've removed all stadard installations and made two independend portable installations, it works.

If you use the win-installer, the Arduino IDE is registered with windows - do not rename the "Arduino" folder, as this will cross the registering.
A regular installation with installer is not portable, the HowTo was written with a portable installation in mind.
i suppose you don't need a "portable" folder with that.
Install the ESP8266 Boards as described in the HowTo.
Download the source zip if you didn't already.
Unpack it to a folder of your choice on your harddisk.
Cupy the libs fromt he source to the "c:\programs(x86)\arduino\libraries" folder.
Rename the "src" folder to "ESPEasy" (Watch capitals!)
Start the IDE and open the "ESPEasy.ino" file.
Scroll down in the source code and make a choice which plugin set should be installed:

Code: Select all

/build all the normal stable plugins
//#define PLUGIN_BUILD_NORMAL

//build all plugins that are in test stadium
#define PLUGIN_BUILD_TESTING

//build all plugins that still are being developed and are broken or incomplete
//#define PLUGIN_BUILD_DEV
I selected the "Testing" built by removing the "//". Just uncomment only one of the choices.
Select your board or ESP-Type with the IDE's board manager.
Set the SPIFFS size as described in the HowTo (1 MB for the NodeMCU with ESP12E)

Now you may start compilation.
Use the "Ctrl + Alt + S" (export compiled binary) to create a bin file.
The .bin file is created in the same folder the ESPEasy.ino is located.
Due to my experience flashing with the Arduino IDE results in failing boot of the ESP.
I've used the esptool from the source files successfully.

Anyways, this discussion should be moved to the ESPMega board of the forum as it is not staff related.

Hope that helps.

Regards
Shardan

Re: ESP Easy development status

Posted: 20 Mar 2017, 08:17
by AndrewJ
Thanks for the clear and comprehensive reply. Now I get it, I should have downloaded the zip file (not used the Windows Installer!).
Tried it the way you said and it's working, compiled and uploaded to my Sonoff Switch.
Thank you!
(and sorry for posting on the wrong board)

Andrew