- September 1, 2008
- 21,578
- 8,228
- Home Country
-
New Zealand
You're absolutely right! Soooooo sorry!
:sorry:
The logic was reversed by mistake. Too late at night (or maybe too early in the morning actually). I have fixed that now...
Pause graph will be required for the moment because otherwise the code doesn't know what channel was last tuned, meaning that it doesn't know what position the motor is in. If it didn't know what position the motor is in then it would have to assume that the motor has to move every time which means waiting for the motor timeout for every channel change - not desirable! In fact, pause graph should be faster than stop graph anyway. That is why the option was made available. Stop graph is only left as an option for tuners with drivers that are not compatible. Your card seems to be okay with it...
In response to your earlier comments: I think the motor command only overrides the switch command when the motor has to move. Actually I think the command gets to the switch but the motor must somehow reset it when it starts to move. Resending the switch command takes at least 100ms. We don't want to do this unless we have to. For the moment I am only forcing the wait for the motor and then resending the switch command after that when the motor has to move to try and minimise the delay for tuning. If we find that the tuner doesn't lock when then motor hasn't moved then we'll have to resend the switch command for every tune. I'd like to avoid that if possible.
Try this version...
The logic was reversed by mistake. Too late at night (or maybe too early in the morning actually). I have fixed that now...
Pause graph will be required for the moment because otherwise the code doesn't know what channel was last tuned, meaning that it doesn't know what position the motor is in. If it didn't know what position the motor is in then it would have to assume that the motor has to move every time which means waiting for the motor timeout for every channel change - not desirable! In fact, pause graph should be faster than stop graph anyway. That is why the option was made available. Stop graph is only left as an option for tuners with drivers that are not compatible. Your card seems to be okay with it...
In response to your earlier comments: I think the motor command only overrides the switch command when the motor has to move. Actually I think the command gets to the switch but the motor must somehow reset it when it starts to move. Resending the switch command takes at least 100ms. We don't want to do this unless we have to. For the moment I am only forcing the wait for the motor and then resending the switch command after that when the motor has to move to try and minimise the delay for tuning. If we find that the tuner doesn't lock when then motor hasn't moved then we'll have to resend the switch command for every tune. I'd like to avoid that if possible.
Try this version...