Skip to content
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

Losi Promoto-MX Motorcycle Receiver does not keep bind after power cycle #924

Open
bitogre opened this issue Dec 29, 2023 · 29 comments
Open

Comments

@bitogre
Copy link

bitogre commented Dec 29, 2023

Given RadioMaster just releases a ground radio with the 4-in-1 module, is there a plan to support DSMR? I would assume it would be a sub-protocol of DSM for surface receivers. I am specifically interested in using the RadioMaster MT12 with a Losi Promoto-MX Motorcycle and my Horizon boats.

@bitogre
Copy link
Author

bitogre commented Dec 29, 2023

Found this video that looks like DSMR is supported but that there is an issue with the Losi Promoto-MX Motorcycle receiver. Is work being done to fix the issue?

@bitogre bitogre changed the title DSMR Support Losi Promoto-MX Motorcycle Receiver does not keep bind after power cycle Dec 29, 2023
@pascallanger
Copy link
Owner

DSMR is already supported.
You are referring to a video where people commented that it works for them so most likely a bad bind or something he did... This video is really full of none sense with many things not working but in fact from someone who doesn't know how to use the radio obviously...
What do you exactly want?

@bitogre
Copy link
Author

bitogre commented Dec 29, 2023

What I want is the RadioMaster MT12 with the 4-in-1 module (when I get it - ordered but not yet received) to work reliable and not loose binding with the Losi Promoto-MX Motorcycle receiver. The one video I saw and linked to above does not have the comments of people saying it worked for them. Maybe that is a different video (or maybe a reply I didn't see). If you are saying it will work and keep bind with this receiver, then close this issue. I can re-open if I run into the same issue when I get my MT12.

@pascallanger
Copy link
Owner

I do not own such a model and I can't test/fix anything without getting my hands on it. So there is no point of requesting just in case. If you run into the issue then we will see but I will probably need the RX to be shipped to me in France to see what I can do.

@bitogre
Copy link
Author

bitogre commented Dec 29, 2023

If I run into the issue, I will be happy to chip in the $60 US cost for you to buy the receiver. Thanks.

@pascallanger
Copy link
Owner

I've received the confirmation that only the SR6300PM DSMR receiver is showing this specific behavior. Without the RX to test it will be hard to work on it.
Some trials:

  • use the latest test version of multi which has modified bind timing
  • launch the forward programming script to see how the RX behaves

@bitogre
Copy link
Author

bitogre commented Jan 9, 2024

@pascallanger Ok, if you re-open this issue and tell me what it would cost for you to buy it locally, I will send you the cost so you can buy this receiver and work on this issue.

@pascallanger pascallanger reopened this Jan 9, 2024
@pascallanger
Copy link
Owner

It loos like it's not only a Multi issue: https://www.arrmaforum.com/threads/having-trouble-keeping-the-binding-between-dx5c-and-sr6300pm-receiver.63720/ . Too bad the guy has not posted anymore... I'm wondering if it could be that some channels have to be set to some specific values to be accepted or have enough range.

@pascallanger
Copy link
Owner

pascallanger commented Jan 9, 2024

Reading through the SR6300PM RX manual it looks like the TX must have enough range on throttle and steering for the calibration to be successful. The calibration happens each time you bind the RX. So my guess is that you must set the "Enable max throw" in the model config and may be even use "Extended limits" at 125% for a full range. This is explained in the doc under "RX output ranges based on the radio settings": https://github.com/pascallanger/DIY-...ils.md#dsm---6

@Gaz-B
Copy link

Gaz-B commented Feb 1, 2024

I have now spent quite some time trying to get a Taranis X9D+ with a JP4in1-SE Module on the latest release to keep bind with a Spektrum SR6300PM receiver in a Promoto. I Tried calibrating and in never gives the final led off and back on again to indicate completion. What seems odd to me is the stock transmitter binds and keeps bind even with calibration. The other thing is all the time the X9D connected it's loosing and recovering telemetry unls the the sticks aren't touched for a few seconds. I've tried 11 and 22ms different numbers of channels. It only binds with the receiver number set to 00. At the moment my best option seems to be remove the teletry voice from the SD and disable the haptic feed back and a hole in the bodywork to access the bind button for every battery change. If i turn the TX off and back on it relinks it's power cycling the RC when it falls over. 🙏

@pascallanger
Copy link
Owner

pascallanger commented Feb 2, 2024

@Gaz-B I think the calibration never completes due to the channel output range being too narrow.
Can you check the box called "Max throw" which is near where you have selected the protocol DSMR and give it a try. If it's not enough, in the model check "Extended Limits" and set all the outputs end points of the channels you use to -125/+125%. This is explained in the DSM protocol: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md#DSM---6
For the telemetry, most of the DSM models send telemetry irregularly with none useful information. This is why a check box has been added on the telemetry page "Disable telemetry alarms", just use that option and setup your own alerts as needed.

@Gaz-B
Copy link

Gaz-B commented Feb 2, 2024 via email

@pascallanger
Copy link
Owner

That sounds really strange. If the calibration does not complete it means that a channel somewhere is not at the value it is expecting to be. On the all in one planes board, it's usually the throttle channel which doesn't go down enough, that's where you need to enable extended limits and push it to -125%.
Can you confirm that you've tried both settings turned on at the same time "Max throw" and "Extended limits" with all the outputs set to -125%/+125%?
The problem is that the % is subjective in the DSM world, that's what is annoying. At one point they switched from 1100=-100% 1500=0% 1900=+100% to 1000=-100% 1500=0% 2000=+100%. So basically depending on the radio age you don't get the same output... By default multi is using 1100..1900 which might be below the 80%.

On the original radio, can you see the values of all the channels. Are you setting the exact same thing? For that you want to activate the feature "Disable Ch. map" which would tell the module to send CH1 on the radio to CH1 on the receiver.

Only the RX number 0 works? You've tested all 22 possibilities?

@Gaz-B
Copy link

Gaz-B commented Feb 2, 2024 via email

@pascallanger
Copy link
Owner

pascallanger commented Feb 2, 2024

That's my point 100 100 doesn't mean anything neither 80%...
Please make sure to test with "Max throw" enabled (near where you have selected the protocol DSMR) and in the model config check "Extended Limits" then go to the output page and set all channels to -125 +125. You can always lower the outputs after that but we first need to test and see.

@Gaz-B
Copy link

Gaz-B commented Feb 2, 2024 via email

@pascallanger
Copy link
Owner

pascallanger commented Feb 2, 2024

Once again the 860 - 2060 µs or whatever % has nothing to do with the current protocol. This is what the radio would output when using PPM or a protocol outputting PPM which is not the case of DSM in general.
Have you set Max Throw and extended limits? Have you set all the channels to output -125/+125%? Have you looked at the position of all the channels on the original TX and reproduced the same? Have you disabled channel mapping to make sure that you are sending the correct channels where you think they should be?

@Gaz-B
Copy link

Gaz-B commented Feb 2, 2024 via email

@Gaz-B
Copy link

Gaz-B commented Feb 3, 2024 via email

@bitogre
Copy link
Author

bitogre commented Feb 3, 2024

@pascallanger Did you get my email about the money I sent you with regards to this issue?

@Gaz-B
Copy link

Gaz-B commented Feb 5, 2024

A little bit more testing no idea if it will help. I've tried with the new model both channels set to 125% and trid seeing if the order of channel to enter calibration has changed for the promoto as it's effectively a bespoke firmware but didn't help. Also the stock TX had throttle endpoints at 100/100 and steering at 125/125.

@Gaz-B
Copy link

Gaz-B commented Feb 5, 2024

Could the auto setup that spectrum does when binding to a different spectrum tx be causing it. Seems the receiver tells the TX it's a bike and auto configures everything.

@Gaz-B
Copy link

Gaz-B commented Feb 9, 2024

I can see it's an issue just with the promoto version of the RX. Even with Spektrum TXs they have to be flashed with V3.0 firmware or the bind isn't successful this sets everything to the bike settings and there is no manual calibration must be some hand shake to confirm it's a radio with bike setting to complete bind. Is there anyway to put my multi module on the TX into bind mode without going through the full menu holding the momentary switch while switching the TX on would be perfect. The gains of running edgeTX outweigh the hassle of rebing for every pack by quite some margin.

@pascallanger
Copy link
Owner

pascallanger commented Feb 28, 2024

To hopefully solve this issue I've finally decided to order a full Promoto set. The RX alone is not enough I also needed the TX. It will take some time before I get my hands on it but it's progressing.

@Gaz-B
Copy link

Gaz-B commented Feb 28, 2024 via email

@pascallanger
Copy link
Owner

@Gaz-B I haven't found this bundle in France... Too late I've placed the order yesterday and it has left the facility already.
You indicated that you've done some settings on the MT12 for the motorcycle. Can you share your model or settings?

@Gaz-B
Copy link

Gaz-B commented Feb 28, 2024 via email

@Gaz-B
Copy link

Gaz-B commented Feb 28, 2024 via email

@Gaz-B
Copy link

Gaz-B commented Apr 24, 2024

Have you made any progress with this issue ?.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants