21.02.2013 Views

Download - Little, Big Racing

Download - Little, Big Racing

Download - Little, Big Racing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

R&S Business Unit Automotive<br />

4.2 – Memory / Cobra<br />

Via L.Romagnoli, 24 - 41033 Concordia sulla Secchia (Modena) Italy<br />

Tel.: +39 0535 57711 (r.a.) - Fax.: +39 0535 54550<br />

Uffici amministrativi: Via G. Brodolini, 35 - Fax.: +39 0535 54533<br />

Email : guest@digitek.it - Internet : http://w w w .digitek.it<br />

The Cobra data logger has 1 memory location of 32Mb referred to as Local disk.<br />

DATAVIEW Pg. 34/133<br />

Lap storage<br />

The data is divided within the logger as separate files; the file division is normally created when a lap beacon signal<br />

is seen. With this method the user is able to download individual laps rather than removing all of the laps stored in<br />

memory. A download of multiple laps only creates a single file on your PC.<br />

Latest data - on/off<br />

From table Manager the user is able to decide which type of memory management is used.<br />

Latest data on – When the logger memory becomes full the oldest lap file is deleted from memory as an entire block<br />

Latest data off - When the logger memory becomes full the memory storage stops, new data can only be stored if<br />

the Clear data command is used. See section 5.1<br />

Auto lap Limit<br />

This is an internally imposed maximum size for any one internal lap file, when the limit of 3Mb (typical Cobra setting)<br />

is reached a new lap file is automatically created. This Auto lap Limit is needed for data security, systems which do<br />

not use a lap timing beacon may fill up the memory without ever seeing a lap beacon signal, the latest data function<br />

would then automatically remove the oldest lap file, which in this scenario would be all of the data. The 3Mb Auto lap<br />

limit avoids this possible problem.<br />

Notes about Auto lap limit<br />

The internal channels Time and Space are not incremented by Auto lap limit<br />

The LAP counter is not incremented by Auto lap limit<br />

The ABS lap counter does increment at the Auto lap limit<br />

The LAPTIM message records the time from logger on to the previous Auto lap limit<br />

Auto lap limit is applied to Local disk as well as flash card memory.<br />

The size of the auto lap limit is a compromise between ensuring that the Auto lap limit does not interfere with the<br />

normal lap beacon > lap beacon events and possible data loss resulting from use without a beacon.<br />

The maximum data throughput of the Shark at 40,000 bytes per second (typical value) means that at maximum<br />

acquisition rate the 3Mb (3,000,000 bytes) / 40,000 = 75 seconds (approx) between each Auto lap limit. At maximum<br />

acquisition throughput this would conflict with any normal lap of less than 1:15<br />

data view_std_manual v1.4.doc Digitek Spa Digitek Spa

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!