-
-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DSMR issues - Spektrum surface receiver SR6200A #1060
Comments
Update to my earlier post: I tried different versions of the MM FW and got it to bind with version 1.3.3.14 of the Multi Module FW, higher versions all ad the same issue of connecting but not keeping the bind after a receiver power cycle. It even works now if I select the [01] receiver number which with the other FW versions resulted in no connection at all. |
I don't have any DSMR receiver to test... Can you narrow down the exact version from which the issue started?
|
Hello Pascal, Here is what I have tested so far:
Hope this helps |
Are you sure? There is not a single line changed in the DSM protocol between v1.3.3.14 and v1.3.3.20, nothing related to the CYRF and nothing related to the main loop. |
@benlye forget... I think I found the issue. |
@pascallanger, thanks for the quick fix. Only telemetry is still patchy. I might be imagining things but when I bind with Model Number 00 or 01, telemetry drops out sporadically but is semi stable (stays on for 15-30 seconds before dropping). If I bind with number 02 or 03, telemetry comes and goes every few seconds. Not sure how I can help you troubleshoot the telemetry part of the connection. Thanks ! |
That's surprising as I'm talking to someone else which has no telemetry drops on whatever model number. He has let his radio and car turned on for 30 minutes without a single telemetry lost message while walking around with the radio in his house to test at different distances. |
Thanks @pascallanger. I have tested 1.3.4.27 and it has the same issue unfortunately. :-( Does the other user use the Radiomaster MT12? Here is another report of a similar telemetry issue (Radiomaster MT12 and a Spektrum SR315 Receiver): #992 Another user in the link above states that it works better in low power mode vs normal mode. Here is another user (MT12 and SR6200A) with the same telemetry cut out issues: https://www.arrmaforum.com/threads/dx3s-avc-knob-and-replicating-advanced-avc-settings-with-the-radiomaster-mt12.73559/post-1190707 |
MT12 or any other radio doesn't change anything... |
Hello @pascallanger, thanks for the continued effort on this one. I have done the following:
Please see the video here: https://youtube.com/shorts/kMxNn5pEVag for the 2nd test I used the same setup as above but rebind the receiver on model # 02 Please see the video here: https://youtube.com/shorts/yFRZZUtY7v8 |
1 tested both 1.3.4.26 and 1.3.4.28 on my RadioMaster RM 4-in-1 External Module connected to my MT12. This is connecting to an SR6200A. Still get telemetry cutting out. In the telemetry screen I can see the RSSI will drop from 90 to 0 instantly. With 1.3.4.26, I feel like it's stuck at 0 when it happens, but with 1.3.4.28, it comes back and holds it more steadily. If I'm in the next room, holding the radio in certain positions, I can get telemetry to stay connected for quite some time (~30s to 1m). Many times (but not always) I seem to be able to bring it back by just wrapping my hand around the external antenna. When telemetry comes back online, the RSSI jumps from a steady 0 to 90 or so... |
Hi, I have exactly the same problem. I can reproduce it with the Spektrum SR6200A and the SR6100AT. Both are telemetry receivers with integrated AVC. With an SR515, which I also have here, it works absolutely without problems and the telemetry also remains constantly active. So it seems to be somehow due to the AVC RX. |
I have no idea where to look at. I have reports that SR215, SR315 and SR515 are working fine. I've used a SR215 during the dev of this protocol so that's what I would expect. |
Which country do you live in? I hope there is someone who can send you one to test. |
I'm located in France. |
@pascallanger, happy to chip in for you to purchase one. Probably not the cheapest but Amazon France seems to have them here for 92 Euro with free shipping: Horizon Europe is cheaper but not sure about the shipping costs: |
@IdefixRC, @pascallanger : Absolutely. |
I am from Germany. Shipping to France and back to me is 30€. I have an SR6200A here that I don't need at the moment. Would that be an option? And when you're done @pascallanger will you send it back to me? Or if you need to have your own permanently, we can also order a new one for you. Also ok for me. |
That might be a good idea. From the Spektrum website: |
My paypal account is my email address pascal _ langer @ yahoo . fr (remove the spaces) |
@pascallanger, sent you 40 Euro to contribute. |
I have also sent you @pascallanger 40€. Good luck and thank you very much! |
I just sent $40... Just want to say thank you for your efforts so far and thank you in advance for your continued efforts. |
@pascallanger : while we wait for you to get the Spektrum transmitter and receiver, is there anything we can do on our end to help? I have the DX3 and SR6200A and an oscilloscope with logic analyzer. I don't have an SDR though. Have my eye on the HackRF with the Portapack H4M. |
You could open the dx3 and look at the RF modulator. I think it would be good to do a dump there if we can. |
Edit: It appears that they've updated the Spektrum Dashboard Android app and it now appears to work on the latest Android versions i.e 13, 14, etc. Also, I was the one who submitted the other issue about inconsistent telemetry. I ended up learning that I can get telemetry fairly consistent when the transmitter and receiver are at a farther distance away from each other. Although it provides slower/less frequent telemetry updates than the Spektrum transmitter, which updates more than once per second compared to multi-module, which updates for me maybe every 5-15 seconds. It's almost as if the transmitter -and multi-module are experiencing RF overload or something from the telemetry transmission when you are too close to the receiver. In any case....make sure you are at least 10-15 feet (3-5 meters) away from your RC vehicle and see if it improves the consistency. I would love for it to work up close like the Spektrum transmitter, however outside of the less frequent updates, the telemetry is usable most of the time. My only other gripe with the Spektrum receiver and Radiomaster Mt12 / Multi-module combo is range seems to be about 2/3 or 1/2 of my Spektrum transmitter + SR315 Receiver. |
Also...I unfortunately caught this thread too late as I have a couple of DX3 transmitters sitting on my shelf that I don't use. I could have offered one up for you. |
Still waiting for the delivery of the RX + DX3... Should be there Saturday. |
Hi @pascallanger did the TX/RX arrive in the meantime and did you manage to take a look yet? Keen to hear what the issue might have been. |
@IdefixRC I've received the parcel but no time to look into yet. I'm working on multiple protocols at the same time and my personal life also getting in the middle so please be patient ;-) |
No worries @pascallanger. Looking forward to hearing what you find. Thanks |
Hello there,
I came across an interesting issue with my MT12 and a Spektrum surface receiver (SR6200A).
I have 2x MT12 and 2x Arrma Vorteks Cars with SR6200A receivers.
One radio (EdgeTX v2.10.5 with MM v1.3.4.0) connected using the R1-F mode (DSM2SFC - 6 is missing from the FW build as listed here) after a few tries and works although Telemetry comes and goes all the time.
The 2nd MT12 (same SW version as the other) and Vorteks connect when binding. Telemetry comes up, drops and never comes back up again and when I cycle the power on the receiver, the receiver goes back into binding mode directly when powered back on.
In addition the issue that only receiver number [00] can be used remains also in 1.3.4.0 - see video of the issue from another user here: https://www.youtube.com/watch?v=KLTIEe_VTGY
Any help would be highly appreciated ! Thanks a lot
The text was updated successfully, but these errors were encountered: