er9x and multi-protocol telemetry mod

[adiezarr]

Hi Mike,
attachment photos mod. In this Turnigy I had the 9xtreme installed.

[MikeB]

Please confirm you flashed the firmware before you did the telemetry mod.
Do you have a 9xtreme installed in any Tx now? erskyTx that runs on it already has debug capabilities built in that would help solve your problem.

Mike

[adiezarr]

As on this turnigy 128 I had xtreme, I removed the pcb, then I made the mod and finally upgraded from erskyTx to er9x-128pz3r822.hex

My 9xtreme has never worked well, That's why I've decided to make the telemetry mod and move on to Frsky.

[adiezarr]

The eepe messages, I noticed now that it seems to fail in a previous backup attempt?

[adiezarr]

pantallazos

[MikeB]

It probably won't fix the flashing problem, but the EEPROM pre-read may be disabled in the File|Preferences menu of eepe.

The suggestion of doing a very careful check of all the connections is the best next step. Checking continuity from the USBASP to the pads is a good idea.

Mike

[adiezarr]

Hi Mike,

Disable the previous reading of the eeprom and continue with the same error. Then, following your advice with the polymeter, I tested continuity from the pads to the pins of the MOSI, RST, SCK, MISO, VCC and GND programmer connector,There seems to be continuity.

I also tested the programmer with the Turnigy 64 and it flashes correctly, just in case that was a problem with this.

I didn't back up the eeprom as you recommended before I flocked the equipment. Is it possible that this is the problem? Because it seems that when I try to update it's like I can't access this memory.

It makes me angry, because the telemetry works perfectly, I'm afraid I've killed something...

[MikeB]

When you did the telemetry mod, connecting the red wire to the 2nd pin of the back board, did you remove the back board and cut the tracks connecting the 2nd pin to the ground plane?
If not, try disconnecting the red wire (not actually needed for the MPM), then try flashing the firmware (do I see a connector in the connection so this just needs unplugging?).
If you haven't cut the ground connections to the 2nd pin, you need to disconnect the red wire as the processor is driving the serial TX ouput to it.

Mike

[adiezarr]

Finally, when the connector was removed, it was allowed to flap. I'm flying, I think I've tried this before.... And it didn't work.

I also tell you that in my case, if I don't connect this connector, the telemetry doesn't work.

[adiezarr]

Well, and after all the problems and having managed to load er9x-128pz3r822.hex I did the test with the altimeter and the equipment started to flicker the light and stop working...., I turned it off and set the protocol as Rate 50 as you asked me to. The team stopped doing weird things, but the altimeter still doesn't work. If you want us to try more things, you can tell me anything you want.

[adiezarr]

And finally, removing the red wire, as you say, and leaving only the black one with the resistance, the equipment flashes and the telemetry works.

[MikeB]

Is the Altimeter now working as well?
You say you set the option to "Rate 50", for AFHDS2A telemetry you need it as "T-Rate 50".

Mike

[adiezarr]

With both the Rate 50 and T-Rate 50, when the altimeter is plugged in, the illumination on the screen starts flashing and the telemetry is lost and the software is locked out. Tested with both test firmware er9x-128pz2r822.hex and er9x-128pz3r822.hex

[MikeB]

New test version posted!
The code now matches that for erskyTx when processing AFHDS2A telemetry.

Mike

[adiezarr]

Hi Mike,

Load the latest firmware and it does the same as the previous ones, I attach a small video for you to see, you can see that the lighting flashes, lowers the battery voltage to 5v, as if the connector of the altimeter sensor tested a kind of short circuit...

Sorry, the video turned upside down.

[MikeB]

The backlight is flashing because the Tx battery voltage is being reported as too low.
I may have a buffer overflow, the MPM telemetry for AFHDS2A is longer than I have configured. RAM is limited on the ATMEGA devices so everything has to be kept as small as possible.
There may also be a problem with calculating the altitude using too much stack space also causing RAM problems of the stack becoming too large and then data and stack are using the same memory.

I've posted a test version with the MPM telemetry buffer larger and also instead of calculating the altitude I just report the raw value sent by the sensor (pressure I think) as the altitude. So not a useful value, but it should be shown and should vary as the sensor moves up and down.

Mike

[adiezarr]

Hi,
Sure enough, it looks like a buffer and RAM memory problem, I installed the firmware ER9X-128PX5R822 and at least the sensor already marks as you mentioned. And as you mentioned, the values are not coherent, even if you raise the sensor the data goes down.

Do you think that this inconsistency in the data can be solved or the 9x buffer is no longer enough....

[MikeB]

I'll see if I can simplify the altitude calculation, I just copied the code from erskyTx that was copied from somewhere else!
Do you get a sensible value for TEMP1 with the sensor plugged in?

Mike

[adiezarr]

A new fact that I didn't know, I just tested. T1=21. I understand you mean temperature??

[adiezarr]

I discovered another one that I can't find in the manual that is at the end TmOK=2, this I don't know what it is...

[MikeB]

T1 is temperature from the altitude sensor.
TmOK is Telemetry OK, indicates telemetry is being received.

Mike

[adiezarr]

Thanks Mike for the explanation. Well, it looks like the temperature sensor is dialing correctly then. I'm waiting for your changes for the altitude calculation. You are a phenomenon, thank you so much for your help.

[MikeB]

It may take a few days to sort out what the calculation is doing.

Mike

[MikeB]

Another test version posted, I found edgeTx had changed to a different calculation that was easier to copy to the 'M128.

Mike

[adiezarr]

Hi Mike,

I've already tried the new version, it seems that the data is more consistent, although I don't see that moving the sensor up and down raises or lowers the height. I've tried giving the sensor a bit of heat, it raises the temperature and decreases the height..., Perhaps this is best tested by flying the models.

One last thing, does the dual-rate aleiron switch get lost? How can I set this parameter then? Do I have to do some mixing?

When I activate the gear switch on the display marks AIL and GEA, Is this so correct by the telemetry mod?

[MikeB]

I suggest checking the mod, particularly the two wires soldered to the processor pins. It is likely there is a short there.

Mike

[adiezarr]

The Dual-Rate AIL should it work properly with the mod done?

[MikeB]

Yes. But if both AIL and GEA appear to operate together when you change the GEA switch, then it strongly suggests the two signals at the processor pins are connected together.

Mike

[adiezarr]

Hi Mike,

Finally I solved it, I've gone a little crazy looking for the short, but in the end I saw it, with the datasheet of the turnigy 9x, it has also helped me to better understand the mod and finally find the error, I got the wrong pad, I soldered the resistance of the AIL on a pad that goes to the GEAR.

I attach an image so that you can see the mistake and others who try it do not make the same mistake.

Thank you so much for the support. I've already received Frsky receivers and sensors and I'm testing them, so far they're going great.

[adiezarr]

Hi Mike,

I continued with the tests on the two teams 64 and 128. Testing sensors and setting alarms. In the 64 made missing in the mixes menu, the warning option to be able to configure the alarms. I've tried the er9xProv822z and er9xProv822z1 versions and I don't see this option.

Could it be added or is there another version that does appear?