Reply to thread

Message

Hi again MaxT

Would you agree that we're getting pretty close to an adequate solution? The logs for version 5 look like the tuner only fails to lock in a few cases. Most of the time it is very successful. The cases where lock does fail are strange. In some cases the motor code decides that the motor needs to move when I don't think it needs to. I have created another test version which listens to the motor code. If the motor code says it sent motor commands then my patch waits for the motor to finish moving (motor timeout) and resends the switch command. If the motor code says it *didn't* send motor commands then I don't wait or resend the switch command. Hopefully this should make things more reliable...

I'm off to bed now since it is after midnight here and I have to work tomorrow. Hopefully this version 6 works even better than version 5...

<blockquote data-quote="mm1352000" data-source="post: 679025" data-attributes="member: 82144">Hi again MaxTWould you agree that we're getting pretty close to an adequate solution? The logs for version 5 look like the tuner only fails to lock in a few cases. Most of the time it is very successful. The cases where lock does fail are strange. In some cases the motor code decides that the motor needs to move when I don't think it needs to. I have created another test version which listens to the motor code. If the motor code says it sent motor commands then my patch waits for the motor to finish moving (motor timeout) and resends the switch command. If the motor code says it *didn't* send motor commands then I don't wait or resend the switch command. Hopefully this should make things more reliable...I'm off to bed now since it is after midnight here and I have to work tomorrow. Hopefully this version 6 works even better than version 5... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="mm1352000, post: 679025, member: 82144"] Hi again MaxT Would you agree that we're getting pretty close to an adequate solution? The logs for version 5 look like the tuner only fails to lock in a few cases. Most of the time it is very successful. The cases where lock does fail are strange. In some cases the motor code decides that the motor needs to move when I don't think it needs to. I have created another test version which listens to the motor code. If the motor code says it sent motor commands then my patch waits for the motor to finish moving (motor timeout) and resends the switch command. If the motor code says it *didn't* send motor commands then I don't wait or resend the switch command. Hopefully this should make things more reliable... I'm off to bed now since it is after midnight here and I have to work tomorrow. Hopefully this version 6 works even better than version 5... ;) [/QUOTE]