ERSKY9X Coding

[MikeB]

New revision released.
Display changed limits when AutoLimits is enabled.
Fix flight Mode labels
Protect PPM sync pulse length from becoming too short.
Extend to 32 model memories

Mike.

[kaos]

Yeah! 32 model memory. Thank you! I will load it tomorrow, actually today here.
with 32 model memory, does the current eepskye and C9X still can read, write and backup the eeprom?

[MikeB]

Eepskye is also updated, although there might be a problem with saved files, just been pointed out, I need to check.
C9X may be OK as I think it might read all the EEPROM, not sure.

Mike.

[kaos]

As of now, if I load this version, how would that affect the existing models? Obviously I can't restored the precious 20 models eeprom to the 32 model eeprom for now. or I can copy each model from the 20 model to the 32 model file and resotore them?
for safety sake, what is the address number to back up all 32 models using samba? (for 20 model, that was 0x2A0000 I think, have to look up my notes )

[MikeB]

0x00042000 instead of 0x0002A000.

I have the fix, I hope to commit it later tonight.

Mike.

[kaos]

got it, Mike. I checked my note, I have been putting in 0x2A000 to back up 20 model. the 3 '0's in front of 2A are needed? I may have been doing it wrong all this time.
once you have the eepskye running, it won't matter. Just want to know what is the right way.

[MikeB]

The leading 0s are not needed, just making sure it is an 8-digit (32-bit) value I typed in, your previous post had an extra trailing 0!
Eepskye is now updated fully.

Mike.

[kaos]

great. definitely will give it a test over the wkend. Thx- again.

[kaos]

Mike: I found this phenomenon in expo/DR. the expo/dr supposedly will change both way when stick is in the proximity of center (10% if I remember). I just noticed a thing. I am testing on my micro quad, and this particular qaud (Q-bot micro) needs quite a bit of trim on ele. then I found out it probably put the 'stick' out of the 10% range and I can only change one direction dr/expo when stick is centered.
I wonder if the 10% should be >25% (the triim limit). so it does not matter where the trim is when stick is centered it will change both ways. when only one way change is needed, it is easier to put the stick at that direction closer to the end of that direction any way.
edit: then I check again, actually the out put of ele is not ouside the 10%. may be this only happen to ELE expo/DR, can you confirm this? the weight is the mixer is 70, ele out put is 4.3 when stick is centered. This does not happen to rud or ail.

and yes, I will load the new version (32 model) after I finish testing the Q-bot micro fpv.

[MikeB]

I'll have a look.

Mike.

[kaos]

Mike: i just edit my previous post. take a look.

[MikeB]

Check your stick calibration! Look on the ANA screen to see if your ELE stick gives 0 when centered.
It look like I only have a 2% (yes 2) "deadband" on the EXPO/DR, I'll extend this to 10% anyway.

Mike.

Edit: It was 2.5%, I had changed er9x to 10%, will be 10% in next revision.

[kaos]

OK, thx. as long as I know what is happening. yes, I got the impression of 10% from er9x.

edit:
YES, 32 model.
Just loaded r178 and eeskye r381. 32 model. tried copy a model to a #28 slot, works. Also, eepskye r381 custom splash screen is working now. successfully burned the new fw with custom splash screen.

Great work Mike. LIke many others, still wonder do you ever go to sleep.

[kaos]

Mike: did you change the ele expo/DR setting thing in r178 already? Strangely, after I loaded the r178, I have no problem setting the ele expo/dr for both direction at the same time when stick is at center area on the same model with same trim. I did not change a thing. no recalibrating. If you have not, I wonder if my potentiater may be acting strangely previously.

[MikeB]

No, I haven't changed it yet.

Mike.

[MikeB]

r180 committed.

Add mutex support in OS - preparing for the addition of telemetry logging to the SD card.
Some code saving to match er9x code
Fix FrSky buffer overflow bug
Encoder editing of owner name
Fix mode page editing of modes 6 and 7
Remove memory check warning option
Volume control - per model choose one of P1,P2,P3 or GVAR4-GVAR7 to control the voice volume
PXX support for XJT - includes bind and range check, failsafe not added (yet)
SPort support for XJT - automatically selected when PXX selected
Improve Stick Mode operation - mixes shouldn't change when you change modes
Vario Sink Tones option reversed - makes it read more sensibly
Auto update mix sources when loading old eeprom model - makes the change transparent to users.
Disable trainer if no trainer ppm input

The most serious change is the handling of the stick mode and mix sources. You will get an ALERT every time you select a model from before r804 warning you to check the mixes as they will be changed based on you current stick mode. From then on, the mixes should be independant of stick mode changes.
The other major addition is support for the XJT module and SPort telemetry data from it.

It is recommended that you backup your existing EEPROM BEFORE updating.

Mike.

[cae]

Thank you Mike.

Colin.

[kaos]

Fantasitic!
Don't forget the background music playing function. It would be fun when flying with the rhythm of the music.

any future plan to have the function of storing/retrieving model setup on SD card?

[MikeB]

r181 released:
Quite a few bugs due to the stick mode change now fixed.

List of changes:
Correct sink tones sense
Fix HP vario SPort scaling
Make COM2 work with in SPort mode
Add code towards model backup to SD card
Add channel uS display to limits menu
Fix trainer bug on stick modes
Fix expo/dr bug due to stick modes change
Fix throttle trim bug due to stick modes change
Fix encoder button not changing on/off values
Fix cyclic pitch bug on different stick modes
Scale output bars if extended limits enabled
Increase RPM blade count to 127

Mike.

[RCHH]

Excellent stuff.
One question though - RPM blade count up to 127?

Why so high? Very interesting indeed!

[kaos]

for motor/porp with gear reduction set up. but yes, 127 is way more than enough.

[MikeB]

RCCH: Using a sensor connecting to the brushless motor wires, you typically get up to 7 "blades" needed. Then, as kaos says, if this is on a heli with a gear reduction of (say) 10:1, you need a blade count of 70 to get the rotor RPM figure.
127 is the largest I can easily get.

Mike.

[RCHH]

Ah I see. With my helis it is not something I currently use, as I have optical sensors directly sensing the blades, but having now googled a bit, have found mention of the E-RPM sensor project over at FrSky.
Unfortunately I get a 'not authorised to view' message. Will contact an admin about it.

Ever more useful stuff Mike - wonder if there is anything left that this TX could be enabled to do? Awesome!

[jhsa]

coffee?

[MikeB]

You'll need to use something like 1200 mAH of the capacity of a 3S lipo to heat 200 millilitres water by 50 deg. C!

Mike.

[jhsa]

Can you code that? maybe we can use the openXsensor for meauring the temperature and send it through serial to the receiver.. My guess is that isn't enough flash on stock board :p

João

[Kilrah]

Sounds OK. 2000mAh to make the coffee, the remaining 200 for a couple of flights. Then you need to change battery and start over as you'll need more coffee with those temperatures.

[jhsa]

[RCHH]

The optimum water temp for making coffe is 96℃, as that is the temperature where the release of the aromatic oils is at the best. So maybe a bigger battery might be in order Gents!
Any hotter, and you now have that nasty bitterness!
And I bet ERSKY9X can do it, and toast 'n all!! Lol!

[jhsa]

I'm surprised no one mentioned beer yet..

Ok, enough.. back on topic