Reply to thread

Message

Sorry for the delay. Here is the new version...

I'm off to bed now. It is 1:00am - too late to do anything more on this tonight...

Some "food for thought": right now the patch is a hack. I will have to think very hard about what we can do to create a patch that would be accepted by the team. I think the only option may be something like what you suggested earlier:

1. Find the distance that the motor has to move.
2. Send the switch command (if any).
3. Send a fake 18V (horizontal polarity) tune request so that the motor moves fast.
4. Wait for distance * motor movement multiplier.
5. Resend the switch command (if any).
6. Check for lock.

If the motor doesn't have to move, then all you have to do is send the normal switch command (if there is one).
The tricky parts are step 1 and step 3. We've already discussed the difficulty of step 1. It can be done, but will take careful thought. Step 3 is trickier to do because of the way the code is. To be completely honest, I think it is unlikely that the patch would be done in time to get added to 1.2.0 so I may have to keep building custom versions for you.

Alright, let me know if there is a problem with this release and I'll try and take a look again tomorrow. It would be good if you could test that scrambled channels work too.

[Edit: attachment removed to save space on my account]

<blockquote data-quote="mm1352000" data-source="post: 678688" data-attributes="member: 82144">Sorry for the delay. Here is the new version...I'm off to bed now. It is 1:00am - too late to do anything more on this tonight...Some &quot;food for thought&quot;: right now the patch is a hack. I will have to think very hard about what we can do to create a patch that would be accepted by the team. I think the only option may be something like what you suggested earlier:1. Find the distance that the motor has to move.2. Send the switch command (if any).3. Send a fake 18V (horizontal polarity) tune request so that the motor moves fast.4. Wait for distance * motor movement multiplier.5. Resend the switch command (if any).6. Check for lock.If the motor doesn't have to move, then all you have to do is send the normal switch command (if there is one).The tricky parts are step 1 and step 3. We've already discussed the difficulty of step 1. It can be done, but will take careful thought. Step 3 is trickier to do because of the way the code is. To be completely honest, I think it is unlikely that the patch would be done in time to get added to 1.2.0 so I may have to keep building custom versions for you.Alright, let me know if there is a problem with this release and I'll try and take a look again tomorrow. It would be good if you could test that scrambled channels work too. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />[Edit: attachment removed to save space on my account]</blockquote>

[QUOTE="mm1352000, post: 678688, member: 82144"] Sorry for the delay. Here is the new version... I'm off to bed now. It is 1:00am - too late to do anything more on this tonight... Some "food for thought": right now the patch is a hack. I will have to think very hard about what we can do to create a patch that would be accepted by the team. I think the only option may be something like what you suggested earlier: 1. Find the distance that the motor has to move. 2. Send the switch command (if any). 3. Send a fake 18V (horizontal polarity) tune request so that the motor moves fast. 4. Wait for distance * motor movement multiplier. 5. Resend the switch command (if any). 6. Check for lock. If the motor doesn't have to move, then all you have to do is send the normal switch command (if there is one). The tricky parts are step 1 and step 3. We've already discussed the difficulty of step 1. It can be done, but will take careful thought. Step 3 is trickier to do because of the way the code is. To be completely honest, I think it is unlikely that the patch would be done in time to get added to 1.2.0 so I may have to keep building custom versions for you. Alright, let me know if there is a problem with this release and I'll try and take a look again tomorrow. It would be good if you could test that scrambled channels work too. ;) [Edit: attachment removed to save space on my account] [/QUOTE]