I remember seeing someone had posted how they set it up so that LED's would light in increments (.1, 2, .3) or whatever values you want depending on consistency. I cannot find that post and have searched a bunch.

I tried using an alarm where IF +/- is less than a certain negative increment (say for example IF PredictivedTimePlusMinus IS LESS THAN (-.2) THEN light LED 1. Reasoning being that the +- value in AIM will show as a negative value smaller than the time increment IF you are on a faster lap than a previous best of session. Didn't seem to work, so has anyone else done this or remembered where a post is on how they have set this up previously? This did not seem to work as tested stationary as the lights were on all the time - I did try adding the condition of +- not being '0', but perhaps it comes across as a NULL value?

I also set up an alarm using a Constant value in milliseconds of a historical best lap time (HBLT) that could be changed per track that will activate when Predicted Lap time is less than HBLT to get around AIM not storing/using Personal Best times in Predictive timing. I think this should work, but we'll see.

Thanks much for any pointers/advice.

 

The newer dashes (what they call the 1.2 hardware) natively support having the shift lights work for predictive as you describe. It's not supported on the older hardware (MXL2 and original MXS/MXP).

 

This is what I tried a couple weeks ago and it worked OK on my MXL2. Three alarms for LED6; slow, close, and faster:



Slow is 1 second or more behind the test best time. Close is between 1 second behind and even. Faster is ahead of Test Best Time. Here is an example:





It needs some work, but it did give me an indication where I was on a lap relative to my best time. I stopped working on it because of this issure:

A little warning. When I installed these alarms and then updated to 1.30 firmware I was no longer able to see data on the MLX2. The WiFi connected to the device, but could not download tests, see live data, etc.

AIM thinks it has something to do with my configuration originally being build with early RS software and copied/modified multiple time. The had me back date the firmware to 1.28 and build a new config from scratch with the current software. That didn't work, but after I deleted all my alarms I was able to download from WiFi see live measures, etc. I am able to connect with USB to download and apply updates. I've exported the configs and sent them to AIM for analysis.

FYI, AIM has been doing seminars 2X per week and last Thursday's was on alarms. It's recorded on youtube:


Greg