wow, what a great feature. took me a lot of calculations to have similiar feature set, so it will free up a lot of memory/cpu time.
there should be 0/1 channel for session finished/elapsed, so i can display a session finished signal.
great stuff!
Another useful feature, if we could set the RTC clock manually. sometimes the track clock is a few seconds off RTC, in that case I have to change the laptop clock.
maybe a manual seconds offset value, I don’t know. This could make a difference, If I know i’m on the last qualy lap, or I can have 1 more lap after the current.
I am currently adding some more sensors, but the Bosch temperature/pressure sensor (PST-F 1) is missing from the sensor wizard, could this sensor be added please?
As Michał already mentioned, there is a channel that should meet your requirement.
I am not sure what you mean. Could you elaborate a bit more?
The IsScheduledSessionOngoing channel is a standard channel, and you can use it in any operation within function or number elements.
This is something that is already on our to-do list, but I cannot declare when it will be implemented.
This is also on the to-do list, just like the previous one.
“I am not sure what you mean. Could you elaborate a bit more?
The IsScheduledSessionOngoing channel is a standard channel, and you can use it in any operation within function or number elements.”
After the session I need the falling edge.
Functions can’t check for falling edge as far as I know, i can only use the value of the flag in a function, and obviously adu.track.isScheduledSessionOngoing=0 does not mean session is finished.
other timers have .elapsed values, which are great for this!
Heading to a track tomorrow that has the start/finish in slightly different places, am I best to use the ‘hill climb’ lap timer? Will this still sync ok in data master?