MoTeC Global Forum

Chasing a bit of help with my display creator please, never had any issues before so not sure whats up.

Was at morgan park in QLD yesterday and i couldn't get any of my lap info on my dash to work.

The laptimer itslef is working because once i download the logging after the session i can see all the laptimes but on my actual c125 with display creator when im going around the track nothing is happening, no lap number, lap time or gain/loss etc.. the only thing i did when i got to morgan park was change the track to morgan park on dash manager.

Ive attached my display creator file and my dash manager file

Chers
Ben

Hi Ben,

I have tested the configuration in the simulate function in Display Creator using data from my car in i2 Pro, and all of the lap timing channels are updating form my test data. Are you able to send a lap sample from your dash that I can use for testing.

Did you send the configuration from a computer that had the Morgan Park venue with GPS coordinates in venue list?

Stephen Dean wrote:Hi Ben,

I have tested the configuration in the simulate function in Display Creator using data from my car in i2 Pro, and all of the lap timing channels are updating form my test data. Are you able to send a lap sample from your dash that I can use for testing.

I don't understand why its not working, the data is all spot on, its just on my actual dash when i'm driving around the running lap time just stays on 0, as does the best lap, lap number and the gain/loss says 0 as well.

I've attached my log from a session for you.

Thanks

David Ferguson wrote:Did you send the configuration from a computer that had the Morgan Park venue with GPS coordinates in venue list?

Yeah mate, the same laptop ive ben using for the last 2 years, went into dash manager changed venue to morgan park as i usually do and then nothing happens.

Hi Ben,

Looking at your logging, there is only one lap beacon that generated in the logging, at about 9 minutes into the log file, after you had done 4 laps. The Lap Distance is counting up the whole time and gets to 14465m until the beacon is seen and then it resets. What did you have set as the detection radius for the beacon? It looks like it didn't get close enough the the beacon to trigger.

Did you send the configuration back into the Dash after you changed the venue? You shouldn't need to do this, as long as there is no data in the logging and all of the venue files are loaded, then the Dash should detect its new venue and start timing automatically.