MoTeC Global Forum

I am trying to import some data using MoTeC CSV format. I've tried to figure it out from exporting CSV data (which imports fine), but some of my own files don't import.

Specifically, can I get details on how the fields in the header are processed (like Beacon Markers), etc.

Hi David,

We don't have any specific information/documentation on how to format the csv files, exporting some data to csv and copying that is the best way to go.

In terms of the beacon markers they are the number of seconds to 3dp since the start of the log file.

If you have any specific questions, or have a file that isn't working you want me to have a look at, let me know. You can always send data to support@motec.com.au if you prefer it not to be publicly available.

One other thing (that you may already know), it is better not to use excel to view/modify .csv files. It often ends up formatting them incorrectly.

Adrian McGregor

OK, it does appear that because I was editing the CSV files in Excel, one of the things it did -- it removed the quotes around all the fields. Does Motec's CVS import require the quotes for every field?

I tried switching to OpenOffice and it can be configured to put quotes around each field, but when I try to import that file, I immediately get "Not a valid MoTeC CSV file" right away.

Next the Beacon Marker. I2 generates a single field with times for laps separated by only a single space. If I have a single field with a comma and a space between times (all within quotes) will that import correctly, or do I need to remove the commas?

My big problem is that the exported data has time that resets to zero at the start of each lap. I need to edit that, but so far all attempts to do that corrupt the CSV data and I2 import fails. I would export single laps, and import them (which is working!) if there were a way to merge data files (I see a File -> Merge Data..., but it's always grayed out, and there is no help topic for it)

Yes the quotes are required for every field. The reason for this is that in a number of regions a comma is used as the decimal place separator. The quotes remove the obvious issues caused by this.

You will need to remove the commas from the Beacon Markers it only uses spaces to delimit the beacon points.

The merge feature is designed to combine data from the same time range. So for example if you have ECU and Dash data from the same session you can use the merge function to make a single file from the two. I2 doesn't have a method of merging data that is from different time periods.

Removing the commas between time values in the Beacon Marker line using Notepad instead of Excel was the key to my multi-lap import issues.

I2 can handle the time channel resetting to zero at each lap, but the Beacon Marker needs to be space separated in that field.