openrcforums

6. Normally I would not expect to see any errors, or only a handful over a minute. Yes a pullup may reduce the errors. Ah ok, then my non-inverted setup works fine. I get 1 or 2 errors every couple of minutes. I'll test a 4.7k resistor when I flash the standard firmware back. I have news related to...

1. That is the value being sent by the multi-module, for the selected protocol, that is what it is! Any idea what TSSI means? Telemetry signal strength calculated by the MPM I suppose? 2. Best I know is here: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details....

So long story short : 1. TSSI values seems incorrect. 2. Is there any logical documentation about the option value? 3. Is the debug firmware considered stable, or is it better to flash the latest normal build? 4. Is there a way to embed the telemetry ( DEBUG ) screen in the normal statistics? 5. di...

but the cover does not open easily once the 2 screws are removed. I don't want to break anything so I backed off. With the iRangeX module there are retaining clips on one side, but they are easly dislodged at the right angle. take a look at this video ( at timestamp 0:59 ) snapshot.JPG Maybe yours ...

I also noticed someone seems to have found alternative soldering pads for the resistors that makes an even cleaner job. @Mike, it seems we posted at almost the same time

Timeless: In the protocol menu, change the "Option" value to a negative number (try -128). Great! it indeed works now. ( couldn't find -128, any option only goes as low as -127 ) Decent telemetry refresh rate and normal RSSI value, when I put it on anything else than rateX. Doesn't matter...

the telemetry data is being sent in FrSky Hub format, not AFHDS2A format. Also things like the RSSI value are not being scaled to match the normal, FrSky range. Is that because OpenTX had some issues in the beginning with RSSI and AFHDS2A, like discussed here ? Also, it looks like a hub telemetry p...

@MikeB: I've tested the 2nd debug build and it does display hexadecimal data now :). I uploaded a small 3min video to OneDrive, hope this is sufficient? https://cddbyg.bn.files.1drv.com/y4mMuvupwzikupiRsTzKcdR09FqUiZXyYCZ-mt-QT2P6tLzfZW-Xaxx40tK37tVnaELL0HRRkf3RfxQeCp9K8b29unS4n5nDAWkL022Si5F2lHWt4...

I'll have another look at the code and debug tomorrow (I'll add to the debug) Thanks :) One question about flashing, I noticed that I have to unplug the back ( side with battery ) from the mainboard in order to flash the M64. Any idea why that could be? the USBasp is unable to detect the M64 with t...

I've tested the debug firmware and pressed ' menu ' repeatedly ( because of irregular RSSI updates ) but no telemetry packets appeared. The counter does increase very rapidly but luckily the bad packet counter stays relatively low. I did see the protocol menu jitter again tho. debug_screen.jpg Seems...

Thanks Mike, I'm waiting patiently. No need to rush .

I've changed the 470ohm resistor to a 100ohm so I have at least some ESD protection on the module bay. The protocol screen is now stable, fast and no jitter. ( have to say I only saw it jitter once or twice with the 470ohm resistor ) However the RSSI and TSSI didn't change, still way above 100 and i...

But what does TSSI mean? Is it the Transmitter's RSSI for telemetry messages?

Funny that almost all STM flashing tutorials mention not to put the serial adapter on 5V even when not providing power the the STM.

Ok I will try a direct connection. But the resistor is to limit the current, is the current into the Atmega really that high that the voltage drops? And the RSSI is always visible, and drops evenly when I walk away from the receiver while holding the transmitter. If there is jitter on the line shoul...

Yes only the FrSky mod is installed. And flashed er9x-frsky.hex.

EDIT
I've seen this post where someone does say that RSSI values work.

I've done the telemetry mod Flashed er9x-frsky.hex and multi-stm-opentx-aetr-noinv-v1.3.1.49.bin to the transmitter and MPM. ( I've read somewhere that the opentx version is recommended and can be used with er9x? ) when I browse the protocol menu it does jitter a bit at first ( incomplete version nu...

Thanks for the explanation Mike :). Now I know that the telemetry mod of the MPM and FrSky are almost identical. Which means the pictures are also valid for the MPM telemetry mod. May I ask how the Atmega communicates with the MPM afther the mod? Because only ( Atmega )PIN2 RX is connected to ( MPM ...

Hi All, I've been a happy user of er9x( M64 ) in combination with a multi-protocol for quite some time now ( thanks developers ), and thus it seems the appropriate time to do the MPM telemetry mod to receive the ( AFHDS 2A ) RSSI readings. But there does not seem any exact documentation on how to in...

So when you were using pin 2 it was all working correctly! Mike I have a couple of questions about the MPM telementry mod: 1. The pin on the processor should be pin2, which is listed as MOSI in the flashing tutorials? 2. What value should the series resistor have? 3. Do I need to cut the trace of p...