Need help on how to change a configuration.

Here's what I am seeing on the screen when I have it set to delta +/- best lap of the day.

If, hypothetically, the best lap of the say is a 1:30.00 set in session 1, and in session two I run a 1:30.01 or slower, I get no +/- information during the lap; it just reads the lap time on the screen at start finish.

Then, if I beat that best lap of the day so far, for all the laps AFTER that lap, it will give me +/- to that lap (the new fastest lap of the day) in real time for the rest of the session.

Then, in session 3, this repeats. Until a session 3 lap is faster than the fastest lap of the day, I don't get +/- data unless a lap beats the best lap of the day.

This seems weird. Fixable?

 

That does sound weird. I went through a bunch of my data and what I see is that on the second lap the predictive starts. There could be a bug in the S2DL that it's not working, but I don't have a way to check it. If you believe what you wrote is correct, email a data file to AiM and tell them what you are seing. If you have video and it shows the predictive doing this on the S2DL, send that too. I did find an anomaly on the Shift Light Module a while ago, but I have an MXP and a completely different kind of setup.

.

Predictive time in green starting on the second lap.

 

It's a Solo2, not a DL but I don't think that matters.

It's definitely happening. I grabbed my solo2 and hopped in a buddy's much faster car. My best of the day was a 24.6; his first full lap was a 25.0 and there was no +/- data on the screen until he went 22 something the second lap; then it gave +/- the rest of the session off that 22 or whatever the fastest lap became. Not driving, it was easy for me to watch the solo screen while he was doing his thing.

What file extension would I send to Aim? I don't have video of the screen. I could create one if I created a track in the culdesac though.

 

Don’t need a video of the screen. Send them the .xrk files from the track sessions it was acting up.

 

You would need to send in the .xrk file. That has all the info in it (like the old drk and gpk together).

Just to make sure, the out lap will not have a predictive. What you see below is the first part was staging to s/f on pit road. From that point back to s/f is the out lap and there is no predictive timing there. After crossing s/f the second time, you will start getting info. It needs the full out lap to get the info. Depending on the pit setup, it could seem like 2 laps.



Predictive starts on the second full lap.

 

Here is an example where you have to cross s/f twice to start getting predictive. At NHMS, when you go down pit road to get in the track, you are too far from the s/f point (you could make it wider) to trigger correctly. So you do a full out lap, cross start finish, do a second flyer, and on the second time crossing s/f the predictive will start.



Sometimes you have to pass s/f twice to get predictive.

 

I ran my fastest lap in session 3. I did not get predictive timing at any point in the 17 lap 4th and final session. I then did not get predictive timing in my friend's car until after he went faster than my fastest lap. I'll send the file and see what's going on.

 

That is certainly messed up then. The only thing for you to check is to make sure the session had good satellite count and accuracy numbers.

 

NSAT ranged from 14-18 PosAccuracy ranged from 2.72 to 3.84.

No idea if those are good.

 

That is good on Satellites and I assume you have the unit of measure for the accuracy as feet. 2.7-3.8 is good. Copy firmware@aim-sportline.com when you email in too.

 

I don't (yet) have a resolution to this issue, but felt that an update was earned.

Since I posted this and emailed to Aim about this issue they have:

• asked me for additional files
• emailed me seeking clarification
• had a TeamViewer session so they could remote into the device and check its settings and configuration files
• sent me a custom firmware file
• are reviewing the files from sessions yesterday where the error reoccurred.

The level of support (on the lowest level of product they sell) has been amazing.