ERSKY9X Coding

[jhsa]

think I found the problem.. details in a little while..

Question, when displaying range test mode in the multi menu, what is the number to the right of the RSSI? And why is it there?
Thanks

João

EDIT: Running a couple more tests..

[jhsa]

A quote from my post on RCG:


Ok, I asked Mike what is that number to the right of the RSSI value when in range test mode.. But i think he still didn't see my post.
anyway, when I was testing before and had the problem I have noticed that this field was always displaying a value of 200 and something.
Midelic was configuring his oXs to also test and he sent me his config.h file. I have loaded it on my oXs and by coincidence have noticed that this field to the right of the RSSI suddenly was showing zero. I also noticed that I had no alarms.
So, i went back to my own oXs config.h to see what I was sending, and found this line.

#define T2_SOURCE PPM

So I was sending the PPM value that oXs receives from the radio to control for example the vario sensitivity, or the LED sequencer on the oXs . Now what is T2? tremperature? How does this end up in the range test menu?

This also explains why the DJT and D8R never had a problem. The DJT uses PPM, not the multi menu.. And that makes me also believe that at least this problem might be in ersky9x because the oXs config file is still the same..

So, now might be much easier for you to find where the problem is.

here is a clean, 18 minute error free log file, apart from the Cvlt first decimal when is zero not being logged. 4.03 is logged as 4.3.

One thing that I still have to find an explanation for it is why did the DIY RX fail with the DJT? Maybe my fault.. Will test that after..

João

[jhsa]

ok, Test with DJT and DIY RX, fail..

João

[MikeB]

I'm trying to recreate the joao problem with cells voltage.
I have programmed an openx sensor to send vario Vfas and 3 voltage cells but I cannot see the cells individually on display,I have log them and is zero mostly .
Vfas is displayed correctly for a 2S lipo. I tested with XJT and multi and diy RX same firmware as joao had. All the same error.On his is shwoing cells voltage on mine no. I tried also older ersky 9x firmware the same problem.

Do you have some idea why is not cells displayed ,I see sometimes good values in the log but not consistent.
See the log attached .

The XJT is in D8 mode I assume. How are you getting the telemetry, from the XJT pin 5 (SPort connection) or from the 'D' telemetry connection to COM2 on the Futaba socket?

Either way, a log of the raw telemetry is useful. Go UP LONG, then right to the "DEBUG" menu. Press MENU LONG to enable "Raw Logging". Now, when you switch logging on it logs the raw data bytes. This setting is not saved if you power tha radio off.

Mike.

[MikeB]

João, I replied on RCG.
For the 9XT, it does seem as though the switch/button data from the AVR processor is not correct.What numbers do you have on the "Slave" menu at the bottom?

Mike.

[jhsa]

At the moment at the bottom I have twice zero. above the second zero at right I have 208. but i have just turned the radio ON
João

[midelic]

Mike

I use D8 This is raw telemetry.
I have no cells display.

[MikeB]

The telemetry data (user data) looks wrong. I see:
5E 10 66 00 5E
and
5E 10 67 00 5E
10 is the index for cell voltage
The value is then 0066 or 0067. The xx6x is the cell number, so cell 6, not cell 1, 2 or 3. The voltage is then 600 or 700, which don't look right either.

Mike.

[midelic]

I have found the problem.
The problem is openx sensor program.
If it is set to 3 cells it will not accept 2 cells lipo which is bullshit.My previous test was with 2 cells lipo.Why need to change the program if you put less lipo cells.
I attached 3 cells lipo and display is ok now.

[jhsa]

Mike, I think this problem might be triggered by low RSSI/Low signal. I explain why.
I have just done a test in normal mode (not range test mode) and the radio never failed.. Then I have just placed it inside the microwave and closed the door enough that it started alarming low signal.. After a while it failed. Cvlt went to zero.

João

[MikeB]

I think Pascal and I have sorted some problems in the Multi code. I'm just running a test to see if they are fixed. The problems include missing a telemetry packet and not getting it re-transmitted.

Mike.

[jhsa]

Thanks Mike, I am just logging the oxs telemetry directly to the radio HUBraw.. Would it help raw logging here?
´
João

[jhsa]

Mike, I have Logged the oXs directly connected to the radio. There are 2 logs on the same file. a normal log and a raw log.
I think the error is not in oXs..

João

[jhsa]

I think Pascal and I have sorted some problems in the Multi code. I'm just running a test to see if they are fixed. The problems include missing a telemetry packet and not getting it re-transmitted.

Mike.

And would this cause the problems I am seeing? Cells being sent even If the oXs is not sending them?

João

[MikeB]

I've posted a new test version:
Fix X9E switches bug - setting a switch in a menu didn't correctly detect a moved switch
Improve CVLT and CTOT operation
Enlarge "multi.txt" text buffer.
Support MULTI bind changes
There are also some cosmetic changes and removal of some debug values no longer needed.
There is a new option in the logging menu "New File". If ticked, then each time you start logging, a new logfile is created and the filename includes the time.

Mike.

[jhsa]

Thanks Mike.. Do I need to update or do I have already the latest?

Thanks

João

[MikeB]

You won't have some of the cosmetics (or the X9E changes!).
Probably worth updating so you have the same as anyone else.

Mike.

[jhsa]

Yeah, good idea.. Thank you
It will be fun to find out the cosmetic changes..

João

[MikeB]

A change I've been looking at for some time is to increase the number of channels supported (currently 24) and the number of mixes supported (currently 48).
I'm looking to increase the number of channels to 32, I can't see any real reason to go for more than that.
For the mixes, I'm looking at going to 64, so still an average of 2 per channel. Would we really need more than that?

Mike.

[jhsa]

maybe you could go for that, but leave the eeprom already configured for more in case we find out in the future that more are needed.. Just thinking about future additions.. If we look back in time, you always had to create space for other features or improvements, So, if you already have enough space on these boards, why not leaving room for the future??

Mike, I was wondering if you found a solution to integrate the SBUS trainer in the normal Trainer Menu?? That would be cool. At the moment we always have to enable the SBUS trainer every time we turn the radio OFF, as the setting is not saved.
Trainer is probably another thing you could leave some space for improvement in my opinion. We never know what new forms of interaction between 2 radios, or even between radio and PC might come up in the future

You will virtually kill me but a couple more trainer profiles would be nice but not a priority in my opinion.
Thank you

João

[MikeB]

I've just posted a new test version, however it may be limited to a few users at present as it is for the new Taranis QX7.
Note that the file doesn't contain a valid bootloader so do NOT update the bootloader using it.
Continue to use the bootloader that comes with the QX7.
As this bootloader uses a lower case name for the (pseudo) disk drive that is the firmware and EEPROM, you will also need to use the included eepskye to be able to flash the QX7. This eepskye doesn't yet support the QX7 otherwise, I haven't had time to sort that. I only got my QX7 on Tuesday and only then started the port of ersky9x to it. Sorry it has taken 2 days to do

Mike.

[jhsa]

Nice, shame that I can't help you testing this one

João

[MikeB]

New test version posted for the QX7. This now includes the bootloader for the QX7, and also fixes a number os cosmetic problems where switches SE and SG were still displayed and sliders SL and/or SR were displayed.

Mike.

[Daedalus66]

Very timely. My QX7 arrived today, but it's 100Km away, so I probably won't pick it up till Monday. I will report on how the installation goes.

[MikeB]

I just updated the QX7 test version again. I forgot SE^, SE-, and SEv and the SG ones were still listing in switch selections. These now no longer show up.

Mike.

[jhsa]

Mike, if you just hide them, you could make them available in the hardware menu if the radio could be modded to add those switches. I guess the processor is the same as the other taranis? Or is it a version with less pins?

Thanks

João

[MikeB]

Yes, they are just mapped out in the switch mapping, very easy to map them back in.

Mike.

[jhsa]

Mike, I have been playing with some logical switches. Just took a challenge on another thread
One of them is the V1==V2
The values need to be exactly the same for the switch to turn ON. If you are triggering some other switches using this, for example, comparing a channel and a pot, the logical switch might not stay ON long enough for enabling another logical switch. I just had that problem on eepskye and the radio. I had to use the trims to make both values the same so I could see the logical switch turning ON. Not very usable like this in my opinion.
So my idea is to either allow the switch to turn ON at an approximate value, or create a completely new Logical switch function. V1~=V2. I would like to be able to compare 2 sources by an approximate value anyway. Needed this quite a few times.

Thanks

João

[Daedalus66]

Hi Mike
I got my Q X7 today. It worked OK with the OpenTX that was loaded. I tested the bootloader as far as doing the trims-in thing and it showed the right kind of words about firmware, etc.

Then I tried to load ErSky9x using the file x7_romC.zip. I unzipped it and copied X7_rom.bin to a Firmware folder in the root of the SD card. Then inserted the card and tried to get the OpenTX bootloader to recognize it. This was with no USB connected. I did the trims inward routine but that didn't get me the bootloader. Then I tried Maintenance mode. No dice.

So I turned the TX off and when I restarted it I could no longer get OpenTX. When I press and hold the ON button, The start up looks normal for a couple of seconds, but when it gets to the opening warning (Failsafe not set) the backlight turns off and the whole TX shuts off when I release the button.

I tried plugging in USB with the TX off and it makes the right USB recognition sound.

I'd appreciate any help you can offer.

Nigel

EDIT: Got it working again in OpenTX. Enough excitement for tonight. Tomorrow is another day!

[jhsa]

Mike, ERSKY9X, voice alarm. Select P4 as source. You will see the Value field will start flashing. I shouldn't?? The other Pots don't
Now highlight the value field. You will see that there is a problem on how it is displayed when flashing.

I have a suggestion as I continue to see people a bit confused when they want to program just some beeps. They don't look in the voice menu and I can understand why.
The suggestion is to change the name of the menu to Audio&Haptic.
Voice and Beeps are both a form of audio.

Also in "File Type" I think the "Numbers" type doesn't make sense anymore. I explain why. Numbered files can only be selected in the voice menu (forget the model names for a minute as the files are in a different folder).
A numbered file is also a named file. If you put it in the "User" folder, you can select any numbered file from the normal "Name" selection.
Currently, to select a GVAR or Scaler to trigger a voice (Numbered Files?), you have to scroll to the end of the numbered files. Over 500 I even forgot this existed, so difficult it is to find.
Scalers and GVARS could also look for numbered files inside the normal "user" folder.
So, based on this I suggest, replacing the "Numbers" Type with "GV&Scalers", or whatever name it fits. These would look for numbered files inside the "User" folder.


Off topic question, are you planning to implement the "Delay" option in The voice menu also in Er9x?
Also in Er9x, the File Type "Number" should probably be renamed to "Voice" (you can only have numbers in Er9x anyway).

Thanks

João