Serial in eepe/eepskye
Posted: Wed May 14, 2014 2:58 pm
First of all I would like to start by saying THANK YOU to 2 members of this forum for this feature. Mike and Mbanzi. It started as a crazy idea when reading about the simulator in eepe/companion. some people wanted the bars going one way, some others wanted them going the other way because it was more correct, etc..
I just thought. if we could see what was happening on the model itself, all that argument would be irrelevant. But obviously all that required a lot of programming knowledge that I don't have, both for an arduino and companion.. Then I decided to do what I do best.. To nag people
No, not really. I think I even opened a thread about this, at the time I think I requested it for opentx and companion, but I think there wasn't much interest on this feature. One evening I was chatting with mbanzi, a member from this forum and I mentioned this.. He thought it was a great idea and he started to spend some hours of his time. he got some working code on an arduino, and also a modified version of companion. Here is a video showing it working:
https://www.youtube.com/watch?v=KwqIogHXirM
Then we asked Mike for some help, which he did. But companion needed far too many changes and we were not sure that the opentx team was going to implement this on companion, so the project went a bit quiet. We all have life to deal with as well. But Mike kept making some changes in eepe/eepskye that would make this possible in the future. Well, the latest change included the serial output and it was the last step to have some working serial sent by eepskye.
But enough of history now
We have serial between ersky and eepskye working over bluetooth on the 9XR-Pro, 9x radios with skyboard, and Taranis, but that would leave out the people that use the 9x radio with er9x, and the ones that don't have a bluetooth module installed in the tx. So, there is some code for an arduino board to allow those to use the feature. I use the arduino pro mini 16Mhz 5V with atmega328 via a FTDI adapter connected to the computer via USB, to allow it to receive the serial data from eepskye and output a PPM stream. But other arduino boards may also work.. I will try a nano board next.
Until now eepskye only sent 8 channels over serial but now with the new Frsky "X" modules and receivers it is possible to have up to 16 channels per module using the known S-Bus protocol. So, why not make eepskye (and eepe) output 16 channels over serial? So Mike decided it was a good idea and implemented 16 channel output on eepskye. It was working more or less ok over bluetooth but not with the arduino code that Mike was also changing to support the 16 channels.. there was a lot of latency and the servos moved in steps.
So, after some testing and fiddling with the arduino code, Mike decided to dump the actual serial code in eepskye and use the much better and faster S-Bus protocol on eepskye to send the 16 Channels, as ersky9x already uses this protocol as well anyway.. He also wrote some code for the arduino board that receives the S-Bus data and outputs two PPM streams on pins 9 and 10.
Chennels 1 to 8 on pin 10, and channels 9 to 16 on pin 9.
I don't have to say that this is working very well. Thanks Mike
The arduino also provides a full S-BUS (inverted at 100000) output on Pin 11. This is driven by hardware (timer 2), but otherwise like a software serial port.
You can find the eepskye file here:
viewtopic.php?f=7&t=4676
The one from the 9th of October or later. Just extract it to your eepe directory.. Backup the old one first. At the moment only eepskye has this feature but I think Mike will also implement it in eepe soon.
You will also need to update ersky9x on your radios to the latest test versions from 9th of October so it can receive S-Bus as trainer over Bluetooth.
So what does this do and what can we do with this?
Well, you can make changes to your model, program a new model, etc, by programming the model in eepskye. Use the bluetooth dongle installed on your radio or plug the FTDI and arduino to a USB port on your computer, start eepskye, open/create a model, start the simulator, select the correct COM port, Click on the "Send (SBus)" button, power the model, and see your model's controls move as you move the virtual sticks in eepskye. Cool, right??
Make changes on the editor, and see them happening in real time on the model itself. you don't even need to close the editor or stop the serial connection when you edit the model. No more need to guess which way each aileron is going by looking at the bars. You can see it happening.
RULE NUMBER 1
PLEASE REMOVE THE PROPS WHEN USING THIS FEATURE. ALWAYS. THAT IS A MUST.
We shouldn't have props on when working on the models anyway.
How can we connect things up?
There are a couple options.
1 - Ersky9x radios (includes the 9XR-PRO, 9X with Skyboard installed, and Taranis with ersky9x installed). Bluetooth if the radio has a module installed. In this case a model for the serial must be created. Model file is attached to this post.
2 - with arduino via a FTDI adapter, using a RF module (or two if you want to use the 16 channels) and a receiver bound to it.
The arduino outputs two PPM streams on pins 10 and 9.
Pin 8 of the arduino also goes low (off) when serial link is lost. that means that with some additional circuit, maybe a FET transistor or a relay, we can power the RF module OFF when the serial is lost therefore allowing the receiver to failsafe and keep throttle channel at minimum. This is a safety feature. (Will work on this next and provide a circuit to power the RF module(s) )
You can also use eepskye to help program your model's failsafe.. much easier than using the tx itself.
Always set failsafe
[BBvideo 425,350]https://www.youtube.com/watch?v=Yqt-Yn1187o[/BBvideo]
3 - With arduino via FTDI, and the PPM output connected to your tx's trainer input.
You must then create a model (Attached to this post) on the tx only for this feature, configure the trainer input for the first 4 channels and/or make some mixes with the PPMn inputs as source in the mixes, and set the weight to 80%. Set the limits on the limits menu to -125 to 125. Here are my settings.. at the moment I set it only for the first 4 channels so I'm using only the trainer input menu on the radio.. You can set it for the full 16 channels by using the PPMn (n = PPM input 1 to 16) as source in the mixer.
on the trainer menu:
RUD := 80% ch1 Switch RUD
ELE := 80% ch2 Switch RUD
THR := 80% ch3 Switch RUD
AIL := 80% ch4 Switch RUD
We will have to calibrate the trainer to the PPM signal from eepskye. just make sure throttle stick is at center in eepskye, the same procedure we use to calibrate another Trainer TX.
Or if you're using the PPMn sources directly in the mixer, you could use something like this:
CH1 80% PPM1 Switch RUD
CH2 80% PPM2 Switch RUD
CH3 -100% FULL
. . R 80% PPM3 Switch RUD
CH4 80% PPM4 Switch RUD
CH5 80% PPM5..... etc, etc,..
As I said before a "Model file" is attached at the end of the post
Note that on channel 3 (my throttle channel) I force the output to -100 when the Trainer/Serial is disabled.
In er9x/ersky9x if a valid PPM signal is not present on the trainer port the trainer will disable itself automatically and give control to the teacher. That includes the PPM sources in the mixer. in this case if the serial is lost, the control will return to the radio and throttle will be forced to minimum.
Limits menu:
All 16 channels at -125 to +125
Here is a little video showing how to connect it this way:
https://www.youtube.com/watch?v=lmvIIV9OyLU
4 - In case you don't have a rx available, or don't want to use the tx or an RF module, there is another possibility And this is my favorite method when programming a new model. No RF involved, so no draining of the radio battery. We might need it charged in case we need to go to the field if the Sun comes out, or if it stops raining
This is a project that converts PPM to PWM using a 4017 IC. All details here:
viewtopic.php?f=84&t=5067
You just connect this converter to the arduino's PPM output on pin 10 and/or pin 9, and use it as if it was a receiver.. For 16 Channels use two of them as the 4017 supports only 8 channels.
Power this little board and the servos using a 4 cell NiMh receiver pack, a BEC, or another suitable power supply.
We can also power it using a circuit connected to pin 8 of the arduino (yet to be designed and the same for the RF module from option 2 above) to trigger the failsafe and stop pulses. Normally ESCs will not run the motor if pulses are lost but as said before, Always remove the props
My favorite setup to learn to work with the tx and try new setups.
I hope you enjoy this feature as much as I will and a big thank you again to Mike and Mbanzi
Mike please feel free to comment or correct any inaccuracy And I do apologise for my English. You all know how bad it is
I will be updating this post as we get new ways to connect eepskye to your model
João
P.S. - Ahh, one last warning.
Do not use this to fly your model...
Doing it could be very bad to your( or someone else's) health or property
[hr]
[hr]
Arduino as an SBUS Decoder and Outputting 16 Servo Channels with Failsafe on all Channels
Above we saw How we can connect an arduino to eepskye via serial and output 2 PPM streams, that you can feed directly to a TX's trainer port or to an RF module.
Thanks To Mike eepskye now sends out a SBUS signal with 16 channel information through USB and we can decode it using an arduino.. In my case I'm using an Arduino pro mini 16Mhz 5V with an FTDI adapter.. Some other arduino like the Nano for example, that already has the FTDI chip built in can be used.
The project I'm sharing now can decode the SBUS signal from eepskye and also the normal SBUS signal from other devices, and will detect them automatically.. Eepskye outputs the signal at a lower baudrate, 57600 baud and the normal SBUS signal is 100000 Baud and inverted.
According to what Mike said (the bit I understood ) the PC has trouble to send the signal at 100000 baud. But anyway, the artduino can decode both but I'm only able to test the code with eepskye as I don't own any SBUS equipment. Mike is also working on a version that will use an arduino running at 8Mhz 3.3V. This could probably allow it to be used on a model without the possibility of the arduino having a brown out due to the servos loading the battery too much causing the voltage to drop and a consequent reboot..Not good.. The 3.3v arduino will solve that problem..
So, After a lot of programming work from Mike (Thank You so Much) and some testing we seem to have some working code for this project.. I did design a little stripboard for the project. as you can see on the pictures from mine below, the pins are too close to the arduino and I have changed the design so you don't have to sand your arduino so it fits in between them, like I had to do to mine
Here are some pictures.
Option 1 - A board with the arduino and all the components to add the capability to also use an external SBUS source from a frsky receiver for example.. This could be also used to install in your aircraft together with a frsky "X" series receiver and have the extra channels up to 16.
Mike is developing a version of the code that uses an arduino at 8Mhz and 3.3V to avoid brown outs when using a 4 cell NiMh battery pack to power the servos. They could cause the voltage to drop beyond the arduino's working voltage.. Will attach the code to this post when is ready.
You can find all these pictures and also the arduino code inside the .Zip file attached to this post.
Option 2 - This version is for use with eepskye only in case you just want to program your models from the PC and see what is happening on your model in real time.
It doesn't use the extra components for the external SBUS source and it is much easier to build. On this version the arduino is powered only from the FTDI, so no need for the little jumper to power it from the servo battery. Servos are, of course powered by an external battery or BEC. If you use a ESC with BEC in your aircraft just connect it normally to your throttle channel and it will also power the servos. In this case an external battery for the servos is not needed
Ahh, no need to say.. again... REMOVE THE PROPS OR ROTORS
THE ARDUINO CODE USED ON THIS VERSION IS THE SAME AS FOR THE OTHER VERSION WITH THE TRANSISTOR AND RESISTOR, AND IT IS IN THE ZIP FILE ATTACHED TO THIS POST
How to connect to eepskye
To connect the eepskye, please download the latest test version (not released yet) from here
viewtopic.php?f=7&t=4676&p=65894#p65894
And copy it to your eepe installation folder overwriting the existing one.. But please before backup the old one or just rename it..
Connect the arduino (assuming that you already flashed it with the code ) using the FTDI adapter.
Open eepskye and create a new model. You can program some basic mixes like you would do when programming a new model on your radio.
Start the simulator on eepskye. At the top you can select the correct COM port for your FTDI adapter. When done, hit the "Send SBus" button.
Assuming that you already connected all the servos Power the Servos by connecting a Battery / BEC to the power pins. You should now be able to control your servos from eepskye.
Please pay attention to the voltage you connect to your servos. Most accept voltages of around 5V. Some until 6V.
How to set Failsafe
Well, if you are reading this post from the beginning you should know by now that is not a good idea to have any type of propellers, rotors, knives, shovels, etc, attached to your model's motors. So please remove them.
The failsafe in this case is more to avoid your servos getting damaged in case some unexpected problem happens, like computer or eepskye (or both ) crash, that could move the servos to one side damaging them. The failsafe will kick in if serial is lost and your servos will go to the position you've previously programmed.. Of course THROTTLE SHOULD ALWAYS BE SET AT MINIMUM.. This is basic knowledge
To set fasilsafe on all 16 channels, or just the ones you are using, use eepskye to put the channels where you want them to be. You can use those buttons (hold x, hold y, fix x, etc...) above the sticks so they don't return to center and stay where you put them. Wouldn't you want to have this on the radio as well sometimes??
After you put the channels where you want them, just press the failsafe button on the board.. Done. The channel positions are now saved on the arduino's eeprom. You can test it by stopping the serial on eepskye.
Ok, I think i didn't forget anything, but I will read all this again later..
Please enjoy it and even if you're not using er9x or ersky9x you can just install eepe and eepskye on your PC and play with this toy. You don't even have to own a radio. AND IT'S FREE
It is very easy to program a model from scratch this way. Actually I have a dummy model that I'm using to test new mixing and learn a bit more. And it is fun..
Once again a big thanks to mbanzi for starting this project, and a special THANK YOU to Mike that made all this possible
João
I just thought. if we could see what was happening on the model itself, all that argument would be irrelevant. But obviously all that required a lot of programming knowledge that I don't have, both for an arduino and companion.. Then I decided to do what I do best.. To nag people
No, not really. I think I even opened a thread about this, at the time I think I requested it for opentx and companion, but I think there wasn't much interest on this feature. One evening I was chatting with mbanzi, a member from this forum and I mentioned this.. He thought it was a great idea and he started to spend some hours of his time. he got some working code on an arduino, and also a modified version of companion. Here is a video showing it working:
https://www.youtube.com/watch?v=KwqIogHXirM
Then we asked Mike for some help, which he did. But companion needed far too many changes and we were not sure that the opentx team was going to implement this on companion, so the project went a bit quiet. We all have life to deal with as well. But Mike kept making some changes in eepe/eepskye that would make this possible in the future. Well, the latest change included the serial output and it was the last step to have some working serial sent by eepskye.
But enough of history now
We have serial between ersky and eepskye working over bluetooth on the 9XR-Pro, 9x radios with skyboard, and Taranis, but that would leave out the people that use the 9x radio with er9x, and the ones that don't have a bluetooth module installed in the tx. So, there is some code for an arduino board to allow those to use the feature. I use the arduino pro mini 16Mhz 5V with atmega328 via a FTDI adapter connected to the computer via USB, to allow it to receive the serial data from eepskye and output a PPM stream. But other arduino boards may also work.. I will try a nano board next.
Until now eepskye only sent 8 channels over serial but now with the new Frsky "X" modules and receivers it is possible to have up to 16 channels per module using the known S-Bus protocol. So, why not make eepskye (and eepe) output 16 channels over serial? So Mike decided it was a good idea and implemented 16 channel output on eepskye. It was working more or less ok over bluetooth but not with the arduino code that Mike was also changing to support the 16 channels.. there was a lot of latency and the servos moved in steps.
So, after some testing and fiddling with the arduino code, Mike decided to dump the actual serial code in eepskye and use the much better and faster S-Bus protocol on eepskye to send the 16 Channels, as ersky9x already uses this protocol as well anyway.. He also wrote some code for the arduino board that receives the S-Bus data and outputs two PPM streams on pins 9 and 10.
Chennels 1 to 8 on pin 10, and channels 9 to 16 on pin 9.
I don't have to say that this is working very well. Thanks Mike
The arduino also provides a full S-BUS (inverted at 100000) output on Pin 11. This is driven by hardware (timer 2), but otherwise like a software serial port.
You can find the eepskye file here:
viewtopic.php?f=7&t=4676
The one from the 9th of October or later. Just extract it to your eepe directory.. Backup the old one first. At the moment only eepskye has this feature but I think Mike will also implement it in eepe soon.
You will also need to update ersky9x on your radios to the latest test versions from 9th of October so it can receive S-Bus as trainer over Bluetooth.
So what does this do and what can we do with this?
Well, you can make changes to your model, program a new model, etc, by programming the model in eepskye. Use the bluetooth dongle installed on your radio or plug the FTDI and arduino to a USB port on your computer, start eepskye, open/create a model, start the simulator, select the correct COM port, Click on the "Send (SBus)" button, power the model, and see your model's controls move as you move the virtual sticks in eepskye. Cool, right??
Make changes on the editor, and see them happening in real time on the model itself. you don't even need to close the editor or stop the serial connection when you edit the model. No more need to guess which way each aileron is going by looking at the bars. You can see it happening.
RULE NUMBER 1
PLEASE REMOVE THE PROPS WHEN USING THIS FEATURE. ALWAYS. THAT IS A MUST.
We shouldn't have props on when working on the models anyway.
How can we connect things up?
There are a couple options.
1 - Ersky9x radios (includes the 9XR-PRO, 9X with Skyboard installed, and Taranis with ersky9x installed). Bluetooth if the radio has a module installed. In this case a model for the serial must be created. Model file is attached to this post.
2 - with arduino via a FTDI adapter, using a RF module (or two if you want to use the 16 channels) and a receiver bound to it.
The arduino outputs two PPM streams on pins 10 and 9.
Pin 8 of the arduino also goes low (off) when serial link is lost. that means that with some additional circuit, maybe a FET transistor or a relay, we can power the RF module OFF when the serial is lost therefore allowing the receiver to failsafe and keep throttle channel at minimum. This is a safety feature. (Will work on this next and provide a circuit to power the RF module(s) )
You can also use eepskye to help program your model's failsafe.. much easier than using the tx itself.
Always set failsafe
[BBvideo 425,350]https://www.youtube.com/watch?v=Yqt-Yn1187o[/BBvideo]
3 - With arduino via FTDI, and the PPM output connected to your tx's trainer input.
You must then create a model (Attached to this post) on the tx only for this feature, configure the trainer input for the first 4 channels and/or make some mixes with the PPMn inputs as source in the mixes, and set the weight to 80%. Set the limits on the limits menu to -125 to 125. Here are my settings.. at the moment I set it only for the first 4 channels so I'm using only the trainer input menu on the radio.. You can set it for the full 16 channels by using the PPMn (n = PPM input 1 to 16) as source in the mixer.
on the trainer menu:
RUD := 80% ch1 Switch RUD
ELE := 80% ch2 Switch RUD
THR := 80% ch3 Switch RUD
AIL := 80% ch4 Switch RUD
We will have to calibrate the trainer to the PPM signal from eepskye. just make sure throttle stick is at center in eepskye, the same procedure we use to calibrate another Trainer TX.
Or if you're using the PPMn sources directly in the mixer, you could use something like this:
CH1 80% PPM1 Switch RUD
CH2 80% PPM2 Switch RUD
CH3 -100% FULL
. . R 80% PPM3 Switch RUD
CH4 80% PPM4 Switch RUD
CH5 80% PPM5..... etc, etc,..
As I said before a "Model file" is attached at the end of the post
Note that on channel 3 (my throttle channel) I force the output to -100 when the Trainer/Serial is disabled.
In er9x/ersky9x if a valid PPM signal is not present on the trainer port the trainer will disable itself automatically and give control to the teacher. That includes the PPM sources in the mixer. in this case if the serial is lost, the control will return to the radio and throttle will be forced to minimum.
Limits menu:
All 16 channels at -125 to +125
Here is a little video showing how to connect it this way:
https://www.youtube.com/watch?v=lmvIIV9OyLU
4 - In case you don't have a rx available, or don't want to use the tx or an RF module, there is another possibility And this is my favorite method when programming a new model. No RF involved, so no draining of the radio battery. We might need it charged in case we need to go to the field if the Sun comes out, or if it stops raining
This is a project that converts PPM to PWM using a 4017 IC. All details here:
viewtopic.php?f=84&t=5067
You just connect this converter to the arduino's PPM output on pin 10 and/or pin 9, and use it as if it was a receiver.. For 16 Channels use two of them as the 4017 supports only 8 channels.
Power this little board and the servos using a 4 cell NiMh receiver pack, a BEC, or another suitable power supply.
We can also power it using a circuit connected to pin 8 of the arduino (yet to be designed and the same for the RF module from option 2 above) to trigger the failsafe and stop pulses. Normally ESCs will not run the motor if pulses are lost but as said before, Always remove the props
My favorite setup to learn to work with the tx and try new setups.
I hope you enjoy this feature as much as I will and a big thank you again to Mike and Mbanzi
Mike please feel free to comment or correct any inaccuracy And I do apologise for my English. You all know how bad it is
I will be updating this post as we get new ways to connect eepskye to your model
João
P.S. - Ahh, one last warning.
Do not use this to fly your model...
Doing it could be very bad to your( or someone else's) health or property
[hr]
[hr]
Arduino as an SBUS Decoder and Outputting 16 Servo Channels with Failsafe on all Channels
Above we saw How we can connect an arduino to eepskye via serial and output 2 PPM streams, that you can feed directly to a TX's trainer port or to an RF module.
Thanks To Mike eepskye now sends out a SBUS signal with 16 channel information through USB and we can decode it using an arduino.. In my case I'm using an Arduino pro mini 16Mhz 5V with an FTDI adapter.. Some other arduino like the Nano for example, that already has the FTDI chip built in can be used.
The project I'm sharing now can decode the SBUS signal from eepskye and also the normal SBUS signal from other devices, and will detect them automatically.. Eepskye outputs the signal at a lower baudrate, 57600 baud and the normal SBUS signal is 100000 Baud and inverted.
According to what Mike said (the bit I understood ) the PC has trouble to send the signal at 100000 baud. But anyway, the artduino can decode both but I'm only able to test the code with eepskye as I don't own any SBUS equipment. Mike is also working on a version that will use an arduino running at 8Mhz 3.3V. This could probably allow it to be used on a model without the possibility of the arduino having a brown out due to the servos loading the battery too much causing the voltage to drop and a consequent reboot..Not good.. The 3.3v arduino will solve that problem..
So, After a lot of programming work from Mike (Thank You so Much) and some testing we seem to have some working code for this project.. I did design a little stripboard for the project. as you can see on the pictures from mine below, the pins are too close to the arduino and I have changed the design so you don't have to sand your arduino so it fits in between them, like I had to do to mine
Here are some pictures.
Option 1 - A board with the arduino and all the components to add the capability to also use an external SBUS source from a frsky receiver for example.. This could be also used to install in your aircraft together with a frsky "X" series receiver and have the extra channels up to 16.
Mike is developing a version of the code that uses an arduino at 8Mhz and 3.3V to avoid brown outs when using a 4 cell NiMh battery pack to power the servos. They could cause the voltage to drop beyond the arduino's working voltage.. Will attach the code to this post when is ready.
You can find all these pictures and also the arduino code inside the .Zip file attached to this post.
Option 2 - This version is for use with eepskye only in case you just want to program your models from the PC and see what is happening on your model in real time.
It doesn't use the extra components for the external SBUS source and it is much easier to build. On this version the arduino is powered only from the FTDI, so no need for the little jumper to power it from the servo battery. Servos are, of course powered by an external battery or BEC. If you use a ESC with BEC in your aircraft just connect it normally to your throttle channel and it will also power the servos. In this case an external battery for the servos is not needed
Ahh, no need to say.. again... REMOVE THE PROPS OR ROTORS
THE ARDUINO CODE USED ON THIS VERSION IS THE SAME AS FOR THE OTHER VERSION WITH THE TRANSISTOR AND RESISTOR, AND IT IS IN THE ZIP FILE ATTACHED TO THIS POST
How to connect to eepskye
To connect the eepskye, please download the latest test version (not released yet) from here
viewtopic.php?f=7&t=4676&p=65894#p65894
And copy it to your eepe installation folder overwriting the existing one.. But please before backup the old one or just rename it..
Connect the arduino (assuming that you already flashed it with the code ) using the FTDI adapter.
Open eepskye and create a new model. You can program some basic mixes like you would do when programming a new model on your radio.
Start the simulator on eepskye. At the top you can select the correct COM port for your FTDI adapter. When done, hit the "Send SBus" button.
Assuming that you already connected all the servos Power the Servos by connecting a Battery / BEC to the power pins. You should now be able to control your servos from eepskye.
Please pay attention to the voltage you connect to your servos. Most accept voltages of around 5V. Some until 6V.
How to set Failsafe
Well, if you are reading this post from the beginning you should know by now that is not a good idea to have any type of propellers, rotors, knives, shovels, etc, attached to your model's motors. So please remove them.
The failsafe in this case is more to avoid your servos getting damaged in case some unexpected problem happens, like computer or eepskye (or both ) crash, that could move the servos to one side damaging them. The failsafe will kick in if serial is lost and your servos will go to the position you've previously programmed.. Of course THROTTLE SHOULD ALWAYS BE SET AT MINIMUM.. This is basic knowledge
To set fasilsafe on all 16 channels, or just the ones you are using, use eepskye to put the channels where you want them to be. You can use those buttons (hold x, hold y, fix x, etc...) above the sticks so they don't return to center and stay where you put them. Wouldn't you want to have this on the radio as well sometimes??
After you put the channels where you want them, just press the failsafe button on the board.. Done. The channel positions are now saved on the arduino's eeprom. You can test it by stopping the serial on eepskye.
Ok, I think i didn't forget anything, but I will read all this again later..
Please enjoy it and even if you're not using er9x or ersky9x you can just install eepe and eepskye on your PC and play with this toy. You don't even have to own a radio. AND IT'S FREE
It is very easy to program a model from scratch this way. Actually I have a dummy model that I'm using to test new mixing and learn a bit more. And it is fun..
Once again a big thanks to mbanzi for starting this project, and a special THANK YOU to Mike that made all this possible
João