The logging capabilities of the RT-Range is expanding. The latest version is able to accurately start and stop the data logging using a trigger event. The data is stored in RCOM format and can be converted to CSV by RT-Range Post-process. The next version of RT-View will be able to load RCOM files and display the RT-Range measurements.
Many RT-Range applications can use the logging feature supplied with the RT-Range, rather than needing a CAN acquisition system. In turn this means that there is less equipment to install in the vehicle and test programs take less time.
Logging data to a file can be started from a trigger event to the hunter or any of the targets. When the targets are used, the exact trigger time is sent via wireless LAN and the software corrects any transmission delay by scanning back through the data to find the exact time when the trigger occurred. Since all measurements are synchronised accurately to GPS time, the event timestamp from any car is accurate.
The user can configure a pre-trigger period so that data just before the trigger can be recorded in the file. The “time from start” field in the file will be negative during the pre-trigger period and be a true representation of the time from the exact trigger time.
To cope with multiple trigger events, filenames have a numerical field in them. This is automatically incremented each time a file is logged. No user interaction is necessary once the logging is set up making it quick for users.
Files are logged in the binary RCOM format. They can be turned to CSV data using RT-Range Post-process or opened in RT-View. A description of the RCOM format is available for customers who want to decode the RT-Range binary outputs in their own software.
For more information on triggered logging or any of the other RT-Range features, please contact OxTS.
