EdgeTX
NO MULTI_TELEMETRY detected
Is there an existing issue for this problem?
- [X] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
I am not certain if this is an EdgeTX issue or a MPM issue. I was trying to help someone on Facebook resolve the following issue. Upon turning on his RM TX16S, he went to his model settings. He scrolled to the Internal RF section. He had the message "NO MULTI_TELEMETRY detected".
After exchanging several messages, I turned on my TX16S and scrolled to the same settings. I had the same "NO MULTI_TELEMETRY detected". I downloaded MPM v1.3.3.7 again and I re-flashed by going to the FIRMWARE folder on my SD card and selecting the correct .bin file. This did not help.
I scrolled up to the Internal RF/Mode field and I changed it from "MULTI" to "OFF". Because it's a computer, I rebooted my radio. After rebooting, I selected the MODEL SETUP page and I scrolled to the same field. I changed it back to "MULTI". I saw the progress bar titled "MPM: Scanning Protocols". Now it is working normally again.
This all seemed to occur when I created a new model or I duplicated an existing model with the FlySky2A protocol. I don't know if my radio was transmitting RF when this occurred. It wasn't bound to an RX at the time.
Expected Behavior
To not see the message "NO MULTI_TELEMETRY detected" on all my models for unknown reasons.
Steps To Reproduce
I don't know how I started receiving the message "NO MULTI_TELEMETRY detected" on the Internal RF section of my MODEL SETUP page. I The only thing I remember doing is duplicating a model with DSM protocol and changing it to FlySky2A with the PWM,IBUS option. I cannot reproduce the issue.
Version
2.7.1
Transmitter
Radiomaster TX16S
Anything else?
No response
I have crazybeeF4FR board with spi frsky receiver and edge tx internal MPM module. I got same error messages sometime.
This message appears anytime the radio does not receive data from the MPM module. Having a precise way to reproduce would be highly beneficial! Otherwise it is going to be quite hard to debug.
Any further information on this? As indicated in the above comment, this error being shown is in relation to the link between the MPM RF module and the main radio board - not the RF telemetry link - so if you are getting that error, it is suggestive of an issue with the handset itself, given we haven't had any other reports of a similar error.
It could be that the connector between the MPM board and the mainboard isn't plugged in properly. It will also show up if for some reason you enable the "No Telemetry" option.
I believe you can close this issue. It has not occurred since. I now believe it was operator error. I think it had to do with the selection to turn off the internal RF module in Radio Settings/Information/Modules / RX version/Internal module.
It's been several months so I didn't remember having this situation until your reply came into my Inbox that I remembered this. My Internal RF module was turned off under radio settings. If I recall correctly, once I set this to my internal 4-in-1, I went back to Model settings. I turned on the Internal RF module and it scanned in the normal protocols.
One final thought, I know I was attempting to use my radio as an HID device for RealFlight 9.5s. I might have turned off my Internal RF module to conserve battery life. I also sort of remember this happening around the time this setting became an option in EdgeTX.
All is good now. Thanks for all your hard (and brilliant) work!
Fantastic! :) Yes, turning the module off in the hardware setup would indeed be a culprit also - better to use the model setup option and have a specific simulator profile. ;) Thanks for getting back so quickly... I was also just going through old messages and making sure none were missed.