New ADU software version 121.0-beta is now available.
What’s new:
Download the update here: https://www.ecumaster.com/tv
Sincerely,
The Ecumaster Team
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.
there should be 0/1 channel for session finished/elapsed, so i can display a session finished signal.
“adu.track.isScheduledSessionOngoing - Value is 1 when a session is in progress, 0
otherwise”
I think falling edge on that channel would be enough to trigger the behaviour you’re looking for.
does that work inside a function?
Maybe an option could be added to allow the RTC time to synchronize with GPS
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.
Try below settings.
“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!
Thanks
You can achieve it using function:
which gives you result as below:
However - we can add ‘session elapsed’ channel or something like this in next release.
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?
Are you driving on a closed track with start/finish in separate points?
Yes, it’s actually a very popular sprint track here in the uk. Possible future track to have in the ADU? 
Okay, then use the hill climb mode. We have tested it with Data Master and had no issues, but if you find something unordinary let us know.
edit: please remember to use “Rally” project type, as it is the one supporting separate start/finish
Regarding the ADU, @mfudala_ECUMASTER I don’t know if our current setup for build-in tracks can support separate start/finish points?
No, built-in tracks support only circuits where the start and finish lines share the same coordinates.
There is a rough plan to allow creating user tracks for hill climb mode in the future.
Until then, hill climb mode works only with button-defined tracks.
will be cool to add new page design 
