Marker-files - How to remove those from Dash2?

[Michael]

We have a lot of difficulties with the Dash2. After several testing sessions we found no way to load a MARKER01.LAP file into the Dash2 when there was a manually set lap marker and sector marker already present. If I understand the manual correctly all markers are in one file and not every marker in a separate file with lap marker in MARKER01.LAP, the first sector marker in MARKER02.LAP etc.

Maybe the file still present in the Dash2 has to be removed first. Any idea how to do this?

Has ANYBODY found a way to load a lap file into the Dash2 regardless whether there is a manually set file present or not and receive correct lap and sector times?

[jlucas]

As far as I understand, the marker files are not "uploaded" and resident in the DASH, they are just read from the CF card.
Are these differing lap files from the same track? If they are, you will have to remove the one you do not want to use from the CF card. I would retain a copy on the laptop in case you want to switch back to it later.

Middle of last year I experimented with analysis software created marker files for the DASH1 and there did appear to be some inconstancy in if the names of the markers & sectors created impacted the ability of the DL1/DASH1 to be able to read them. Because of the inconstancy I found it safest to use the name format the same as a DASH button created lap file. I haven't checked this lately in the newer software/firmware/DASH2 scenarios but I mention it in case it would help in your situation.

[Michael]

jlucas,

thanks for your answer. The marker file remains resident in the Dash2 as when you cut off the power and repower the file is still there while the CF-card in the DL1 has no marker file to send to the Dash2 or even no CF card present.

Files were from the same track. Removing the files from CF card doesn't help, as explained above.

The notation format of the file on CF card was the same as the ones the Dash2 creates when adding markers via the buttons.

I think it will be necessary that RT looks into this issue ASAP. Racing season has started and every customer is more than upset. Worst thing is that I can't help. Spent lots of time and money into testing but with no success.

[jlucas]

Michael, since you are in Europe (my assumption from your email address) you should call RT on Monday if you want a quick resolution. I have not heard of any reports similar to yours. RT UK does not frequent the forums (or at least does not respond to posts) lately, and RT USA is on holiday this coming week.

[Michael]

Thanks again, Jeremy!

You and Al seem to be monitoring the forum more closely than RT.

I had at least two telephones with RT last week but Martin in on holiday in Spain and no one else can answer the questions re. hardware. Sometimes you get a fix easier via the forum as the users are using the products while RT produces and sells the goods but - as it seems - without testing the products as intensive as customers do on the race tracks.

If it needs Einsteins and Newtons et al. to use the devices then something is wrong, right?

[RTUSA]

Michael:

I need to slightly correct what Jeremy has stated - I monitor the forums as the RT representative, referring back to the development team as needed. (Having said that, I AM on holiday the coming week and may just ask one of them to take over for me - or maybe do it in the evenings???)

Anyway - as I have not yet escaped.....

Here is my understanding of how the DASH1 & DASH2 work:

The *.LAP file is held on the CF card in the DL and is uploaded (or at least data from it is uploaded) on powerup or when a new card is loaded. Specifically, a .LAP file is uploaded if one is found whose coordinates are close to the current GPS location. I do not think that it is retained in any NVRAM in the DASH2, or if so will be overwritten the next time a .LAP file is uploaded.

(As the choice of files to upload is coordinate based, it is OK to have multiple lap files on a CF card if they are from different tracks, but not OK if from the same track. As a radical simplicity advocate, I'd rather only have one .LAP file on a card, but maybe that's just me.)

To replace a .LAP file it should be sufficient to merely delete the current .LAP file from the CF card (ie reformat the card from within Analysis or using Windows being vareful to use FAT NOT FAT32. Then load a new .LAP file from the PC or create a new one by using the switches.

All data for a particular set of markers and sectors is held within a single .LAP file. For a PC created .LAP file to work on the DL1/DASH2 it must contain both markers and sector definitions.

I have created .LAP files on the PC and loaded them to the DL1/DASH2 multiple times w/o problems, and got very consistent operation. I will admit, though, that I have never done this using a DASH2 that had previously had a "button" created .LAP file resident.

It sounds, though, as if you have done most or all of this and are still having problems?? Are you absolutely certain that the DASH2 is reporting lap times even when powered up with a DL1 containing no CF card? Is the power to the DASH2 being removed for sure? If the power were left on the DASH2 (remembering that it is powered independently of the DL1, unlike the DASH1) it certainly would retain the old .LAP file data.

BTW, though most DASH2 customers are only now starting their race seasons, we have had several customers in the US use them extensively over the fall/winter with uniformly good results so far as I know. Including some cars in the Daytona 24 hour race. Not to say that there can't be a bug or two still lurking....

Also, anyone with any odd DASH behavior needs to make sure that a config file was not created using the DASH-unfriendly version of V6.3.100 that was posted by mistake for a few days early in March, see the pinned post.

Regards,

[RTUSA]

Well I just reread the DASH2 Help and it does look as if markers can be held in memory - presumably NV memory.

There is a function described in the Help for using the DASH2 menu to turn on and off "used stored sectors" (I paraphrase).

Have a look at that and if it's on turn it off...

[Michael]

With extensive testing our specialist Ti has found a way to use the lap timing. Or at least a way around the problems.

Still existing is a hardware fault in the sector and lap timing comparison to the best lap/sector time. You always get a "+" even if you drive massively faster than in any lap before.

RT, make sure that this will be fixed by another firmware reflash, please.

[RTUSA]

Michael:

I'm sure other users would appreciate your sharing some specifics of what you have found.

Thanks,

[Michael]

Michael:

I'm sure other users would appreciate your sharing some specifics of what you have found.

Thanks,

Will do when time allows.

But isn't it RTs duty to write a manual that buyers allows to use their Dash in the first place???

[RTUSA]

Michael:

Not disputing that at all. But if you've found a bug - and it sounds as if you probably have - RT needs details. Not saying you haven't, I'm not in the main office and don't know. Also, if you've found a workaround to the bug, I'm sure other users would be interested.

That's my only point. It certainly is RT's responsibility to iron out bugs and produce usable documentation.

Thanks and good luck!

[Michael]

Al,

I have reported and emailed to Lorne who passed the issues to Andy. He will produce a fix for some of the issues today.

The issue with the permanent "+" on the lap-time slip is new to RT and they will look into matters.

I hope that a fix will become available prior to the all crucial weekend.

[Michael]

Some of the issues with the Dash2 will be a matter of the past when the new configuration software is used.

Analysis software 6.3.109 now available.

Thanks RT for acting quite quickly!

[jlucas]

Michael, did they tell you if you could open your old config file and resave it or do you have to recreate the config setup with the new version?