openrcforums

FYI, I've released 1.3.2.61 and updated the doc.

Hi Rich, Great that this solution finally works. OpenTX relies completely on the multi telemetry to display protocols. If I disable it, it will break the selection... I'll update the doc since I don't think I've indicated that you have to check the disable telemetry box when you are done with the se...

Thanks guys for the feedback.
Can you test the latest code .61 on GitHub?
I think the best is to never enable the RX neither the interrupt in the first place which is what I've done now.
Completly untested as I have to run to pickup the kids.
Pascal

Could you try v1.3.2.60 from here: https://downloads.multi-module.org/latest-test/
(I don't have a FrSky radio to test myself...)

I'm thinking the RX interrupt of usart3 is triggered before I disable it so it loops there for ever...

If you can compile the Multi code by yourself, can you try to disable telemetry in the _config.h file: //#define TELEMETRY

Hummm, so the internal module playing with the SPort pin... It's why I can't reproduce the issue since the TX16S does not have this kind of shared telem pin problem...

Is it only happening with a RX protocol in CPPM mode?
Is the trainer radio powered on?
I've tried multiple times on a TX16S running OpenTX with DSM/FrSky/AFHDS2A RX with CPPM selected but no trainer radio transmitting and I can't reproduce this behavior...

Ok so apart from no pulse everything seems to work as it should. So let's call it good until I can get hold off a Futaba RX.

I'm totally puzzled, which firmware version are you using for this test? It should be done on using the nightly link I've sent you previously...
And the mixers of your channels are not set to the source MAX like I asked for...

@TPE331civil Fine for the servo reversal in failsafe. But what about my question of the servo throw in normal vs failsafe? To answer this question, set the mixer of CH1 to MAX +100%, set the failsafe of CH1 to +100%. Does the servo on CH1 move when you turn off/on the radio? Other tests I would like...

A test version with failsafe reversed is available here: https://downloads.multi-module.org/latest-test/ What I'm interrested in is the servo throw in normal and failsafe. It would have been too easy for them to use the same channel range for normal and failsafe packets... So I need to know if they ...

@TPE331civil I'm the dev of the mutliprotocol module. Can you confirm that on your RX all the channels are reversed when going to failsafe? Because you are only mentionning channel 2 and 3 but I find strange that only these 2 are reversed and not the others which doesn't make sense to me. I can do t...

Joao, since you don't trust anything I'm saying, here is the FrSky double game with Vantac and URUAV modules: http://fpvcentral.net/wp-content/uploads/2018/07/IMG_20180726_155819.jpg . Check the markings just above the USB plug: MultiProtocol Rev 0.2 with underneath a beautiful FrSky logo. This is t...

While fixing the servos sporadic issue by enabling hardware CRC, FrSky has added 6 anti "copy/clone" protections to their protocol: - 3 on the bind packets: 1 weak, 2 strong - 2 on the normal packets: 2 medium - 1 on the telemetry packets from the receiver: 1 weak The same applies to LBT and FCC wit...

"I personally think that it was a bad move the MPM development team to give direct support to a company" Can you give me a pointer to which direct support I'm giving? All the companies are using the schematics that are available as opensource. None of them have received support on how to build their...

"What I can't understand is why and how Pascal, the Multi Module developer, is actually giving direct support to the Jumper radio, unless...... :( :? :roll: and I keep the rest of the sentence for myself, but you know what I mean. João" What are you saying here. I'm not helping Jumper or any other m...

That was it... No Comment...
Thanks Guys!

Fully in agreement with what you just said Kilrah

Strange he has tried multiple times to redo the calibration. Over the phone I've even followed the calibration steps with him to make sure he was doing it properly. I need to see the radio by myself to be sure of what's going on... Before he comes, can I assume that there is no such setting to make ...

Hi, A friend has a problem on his 9XR Pro. I haven't seen it myself but had a long discussion over the phone with him to troubleshoot. I've updated it last July with R222 but not sure which exact version. It was working fine all summer until last WE. His issue is that the throttle is only going from...

Mike, I can't display within the script a correct value of A1. I can get the radio to display the correct value in Config->Telemetry -> A1 channel 13.5v 7.6 <= 7.6V is my 2S lipo voltage. This value is displayed correctly on the telemetry screen A1=7.6,RX=.., TX=... But within the script if I do: tm...

...

I confirm at least that r222a3 is solving the off grid inverse issue on my 9XR Pro.
I haven't tried r222a4...
Pascal

My script is attached and also a picture of the screen. If you load it, you should see T-CUT blinking at the top if the throttle cut switch is by default. If you push some other switches(AIL,ELE,...), you'll see other texts going blinking or not depending on the switch position. I'm using the screen...

Mike, Is there a way to improve the rendering of "Blink" and "Invers"?
When you use these features each letter is inverted indepently meaning that there is a space inbetween the caracters not inverted. It makes the text readibility quite hard.

Pascal

Mike, I've tested version g6 and everything seems to work fine from what I can see.
Thanks, Pascal

Cool. Are you thinking about implementing the telemetry script as I described using killevents(Event) to suppress the event from the queue that the radio fw should not interpret? The LONG EXIT press could also be an event that you could not supress from the queue (ie killevents can't suppress it) so...

Hummm, I will retry in which case it exit indicating a "false" error in the code.
For sure I always add either a model script or a telemetry script running in background. Usually the same script since I just wanted to get a display...

The main problem with that is the script could block ALL events, then you would never be able to leave the script's screen. Just intercept before launching the script the exit press long event and kill the script if it's the case. This way you can get out if really needed. That's what you are alrea...