open9x-r1726

[bertrand35]

[stock]
- Latency sticks => pulses improved by 10ms (average)!
- DSM2_SERIAL bug fixes

[ATmel 128]
- Latency sticks => pulses improved by 10ms (average)!
- DSM2_SERIAL bug fixes

[gruvin9x]
- Latency sticks => pulses improved by 10ms (average)!
- DSM2_SERIAL bug fixes
- SOMO bug fixes by Cam

[sky9x]
- Support of Sky9x3.0 (bootloader difference)
- Mu-law codec added for SD File Playing (Useful for the US)

---

Previous announcement: open9x-r1670

Bertrand.

[kaos]

Great, Once I get my Sky9x V3 board and put it in (should be within next couple days ). I definitely is going to put all my existing voice file from ERSKY9x to open9X, after I figure out the sound files name in open9x.

[kone]

thanks a lot. now i can successfully connect with USB/serial to my 9x even after flashing. This was not working with an earlier version (bootloader issue).

greetings,
christian

[kone]

hmmmm, Current/Consumption is not working anymore on my Sky9x V3.0
unfortunatly RTC is still not fixed on that version as well...

[Peter]

I skipped a couple of versions and upgraded to 1726 @ arm.
And now I have big problems with flight fases. The mixers sometimes listen to the flight fase selection and most of the time it is random.
In the simulator the flight fases work fine! Been flying the model for months with this configuration.

EEPROM is attached, using model "Easystar 2".

[bertrand35]

Did you check the configuration of your mixes? Now a mix can belong to one or several phases.

When you say it's random, is it always the same value? I mean does it change every 20ms?

Which channel seems random? CH14?

Bertrand.

[Kilrah]

How many versions?
Some time ago a new system was introduced to select which phases each mixer is active in. Before it, on each mixer you could select one phase it would be active in. Now you can tick or untick each phase (a mixer can be active in a custom selection of phases, not just all or only one).

[Peter]

The final version with mass storage I thought.
I checked the mixers flight false assignments and they seem fine.
The mixers from throttle to the ailerons and the mixers from throttle trim to ailerons.
Every time I flick the switch it is interesting what it will do. The change of behaviour is at changing flight fases.

[Peter]

I did swap my sticks with my other 9x yesterday, so I will check the connections.

Current measurement does not work.
I have to upgrade the tiny yet.

[bertrand35]

Peter any update on this issue? If it happens to be a FW bug, would you find the set of mixes which is as little as possible to put some evidence on the issue? It would help tracking the bug if any!

Thanks,
Bertrand.

[Peter]

Bertrand, I will narrow it down tomorrow.
I saved the eeprom before version upgrade.

[Peter]

I have a little problem with testing an older version. Revision 1439. I think I was running that version before.
If I flash that version with my backup eeprom, it says bad eeprom and wants it to format. I assume the companion9x version is to new to flash that eeprom and converts it.
I also tried to flash the 1439, formatted eeprom, retrieve eeprom, add model and flash eeprom back. It still wants to format the eeprom
Next I retrieved a companion9x version from that same day (28 sept), r1431. But it doesn't compile:

Code: Select all

/home/peter/src/companion9x-1431/src/open9xinterface.cpp: In memberfunctie ‘bool Open9xInterface::loadModel(ModelData&, uint8_t*, int, unsigned int)’:
/home/peter/src/companion9x-1431/src/open9xinterface.cpp:120:76: fout: no matching function for call to ‘min(long unsigned int&, unsigned int&)’

So, back to the drawing board

[Romolo]

no when you write the eeprom back to the radio you need to check the "check for compatibility" or otherwise get an older companion

[Peter]

When does companion9x convert the eeprom to a new format? When reading from the tx or when writing to the tx?
Also, do you know until which revision the old format was supported?

[Romolo]

It converts in both moments:

When reading it converts to companion9x internal format (a superset of all firmwares)
When writing it writes to the proper firmware version and option.
Setting check for compatibility should force companion to read the radio and write the eeprom in proper version for the radio firmware.

[Peter]

Checking the "Check firmware compatibility" segfaulted.
But, I didn't try the easiest thing, just downgrade and trust companion9x in converting back.
That worked , Thanks!

Open9x revision 1439 works, no problems. Flashing 1726, problems are there again. So a firmware problem.

Steps to reproduce:
Load the above posted eeprom. Select "Easystar 2".
Disabled throttle cut by switching thr switch off. Throttle to zero and after that to full throttle.

ID0: flight fase 0:
Channel 1 should be full.
Other channels almost zero.

ID1: flight fase 1: thermal
Same as flight fase 0, but throttle trim sets camber, but max 20 percent.

ID2: flight fase 3: land with throttle stick controlling spoilerons
Throttle should be zero
Other (ailerons and elevator) channels significant output.

If I switch the three position switch between ID0 1 and 2, I get strange results. Sometimes full throttle, sometimes throttle stick spoilerons.
It can also be seen in the mixers screen. The mixers bold status is not consistent when changing the flight modes.

EDIT: I tried to compile revision 1670, but that doesn't compile with my toolchain. I seems that it tries to use gcc with a empty mmcu parameter.

[bertrand35]

Are your SWC and CH14 correctly working?
Bertrand.

[bertrand35]

For the Sky9x board, you have to compile with:

Code: Select all

make PCB=SKY9X SDCARD=YES

Bertrand.

[Peter]

Compiled revision 1670 and that works without problems.
Flashing 1726 and the problems are back.
Sticky throttle cut works, so I assume SWC and CH14 are working correctly.
The mixers that give problems have a flight fase asignment.

[bertrand35]

Bug found and fixed on SVN. It was related to fadein / fadeout on phases. Please keep me updated about your tests!
Bertrand.

PS: I ported from ersky9x the support for the aurora gimbals, not tested, I didn't buy them, the port is too expensive for me

[Peter]

I just tested revision 1732 and it does indeed work now, thanks!
Current consumption does also work again!

[kone]

I can confirm that too.
Current measurment works fine again.
Unfortunatly RTC still does not work for me on the sky9x v3 board...

best regards,
christian

[Scott Page]

Found a new little issue. Every click of the trim tab midtrim sound. http://youtu.be/O8egEUsHnVw for example

[Rob Thomson]

Are you using the most recent sound packs?

[Scott Page]

My sound - using Bertrand;s name scheme -- Ulaw sounds. Ulaw was only recently allowed - prior to last week (about) alaw was required. Your question makes me wonder if it's the Ulaw format.

[Gladiac]

Hi!
I was trying to start using open9x insted of er9x and as i flashed the tx i couldn't find out why thust doesnt work
Can anyone tell me how to fix that?
Is it eaven possible to copy models from er9x to open 9x?
And i belive this is the one sw i should use for frsky telemetry?

Thanks guys!

Best regards!

[Rob Thomson]

What exactly went wrong when you tried to flash it? This information will help solve the problem.

Open9x and er9x can both support frsky telemetry. They have many similar features, and some different features

Sent from my GT-I9300 using Tapatalk 2

[Gladiac]

Nothing went wrong
I flashed the open9x to tx and everything was working but throtle.
I will try to flash it again this week but i will try with a plane first
Thanks for trying

Best regards!

[Rob Thomson]

Probably a case that you needed to calibrate the tx

[ktgohdt125]

is this open9x-r1726 is the latest open9x firmware? any link that i can download it??
me still on open9x-r1692 date 05122012 and notice the tx will intermittent transmit a few milisec throttle tx signal to my plane...
any advice appreciated.
thanks