Splitting data files up.

[the_bluester]

I am new to the Motec analysis software and have been sent some logged data from a friends car to try to sift through it for him (He is new to the Motec world as well) Firstly, we need to sort out something to make session data more clearly delineated, but I so far have not looked at that in his setup.

What I have in the logged data he sent me is several consecutive sessions of information, one from when he had towed the car from Sale in Victoria to Melbourne to be tuned, and then another from several days afterward back at Sale at the cars first post tune track test. It has made building a track map from GPS data difficult as i2 is considering the entire data set to be one unit, so it has a tiny little mess of wiggles where the track is at one end of a 180km long line pointing to where the car was tuned.

Is there an easy way to delete the no longer useful data from the tuning day from the logged data so that we can build a GPS map of the test track at Sale? Or to split it into two files? I had my fist look at i2 at 11:00 last night but did not have any joy before I had to go to bed, trawling the raw data it was obvious which parts of it related to lapping the track as I could recognise appropriate speeds for the sections of track and lateral G in the right places for each of the corners but a track map was not buildable with the software trying to include a trip to Melbourne in the lap!

[AdamW]

In graph view, zoom in so that only the data period that you want to "keep" is displayed, then right click, choose export data. Set source to all channels, set extent to "visible data" and output format to Motec Log, then hit export. You then get to save this copied data as a new file so that the original data remains un-modified. I haven't tried this with GPS data before but Im pretty sure you should still be able to create the laps after the export.

[the_bluester]

I will give that a crack tonight. I don't think there will be much to create a track map with in any case as it was the very first shakedown and was only a couple of laps, and he was driving on and off the circuit in odd places on some laps (The circuit was on the RAAF airfield at Sale) to keep out of peoples way while he did his stuff.

He ran into an issue and wants to be able to see data from his PDM to see if the current to his fuel pump was all over the place. Hopefully he got his logging settings right and was actually logging PDM data as well as the engine basics.

Then he just needs to download and clear the data more often, having the tuning day in there as well makes things a little less than clear.

[adrian]

AdamW is correct, that method will create a new log file that only has the data you require.

To create a track map you will still need to create 'laps' in your data. If you don't have a beacon (or have GPS beacons) then you can add them manually. Select the location in the data where you want a beacon and press shift+F7. Once you have definable laps you can use the track editor to create you track map.

You can do this process with the whole data file if you don't want to create a new one as it will only use the lap you select to create the track map and not the whole data file.

The following link: http://www.youtube.com/watch?v=ZYog31f-7KU&hd=1 is a webinar on inserting beacons and track mapping that may be of some interest. There is also seminar notes on i2 (http://motec.com.au/downloads/downloadseminars/) for more information.

[the_bluester]

Thanks Adrian, I will have another look tonight. A problem I have at the moment is I have very limited data to work with, this was the cars first test outing since the dash went in and a problem was discovered quite quickly, so the owner parked it after just a couple of slow laps.

It is an opportunity to fine tune the logging setup more than anything else. First things first, RPM>100 proved not to be a useful start logging condition given it produced plenty of "Warm up idling" data and not a lot else, we think we will change it to road speed>30kmh or similar to avoid that in future, and RPM<100 for 30 seconds for stop logging. That way for hillclimb we can also configure a spare keypad button as a second logging start option so that logging can be manually started before launching the car.