DSM: Fix for timing afecting some DSMX receivers - #1190
frankiearzu wants to merge 1 commit into
Conversation
|
There was 2 delays change and all due to this specific receiver Spektrum SR6200A and the SR6100AT #1060
The first one is affecting all DSM. The second one is only affecting DSMR. So not sure how to proceed to get everything working together. It looks like I had this receiver in my hands so I should still have it to test. But I won't be able to get to it until next week. |
|
Looks like we have to be very specific with the SR6200A and the SR6100AT. My tentative fix was to keep the old/good timing of DSM_READ_DELAY of 400ms for all AIR protocols, and only change to 300ms (and the 10.900ms) for only surface, but looks like that change also affected other DSMR receivers. You are right, revert to how it was on 1.4.3.31, and see what we can do for those RXs. |
|
If you are releasing a new version.. consider including #1179, this was to fix to work with up to 16ch instead of just 15ch (due to the 4 bit limitation). |
|
No longer needed |
2 participants
Most newer Spektrum works well, but with LemonRX the movement of the servos is not that smoth. Seems like sometimes it stops for a bit.
On an OrangeRX R610V2, i also see some hesitation on the servo movement, but much less than with LemonRX.
The DSM_READ_DELAY change to fix the Surface telemetry is affecting some DSMX receivers.
On 1.4.3.31 everything was working fine, when upgrading to 1.4.3.63, the problem showed up.
On 1.4.3.31, DSM_READ_DELAY = 400, and it was reduced to 300 later to fix telemetry on a surface receivers.
The fix is to only use the new timing for surface protocols and use the older timing for Air.
That seems to fix the problem.
One of the reported problems on RCGroups:
https://www.rcgroups.com/forums/showpost.php?p=55105703&postcount=26692