i2 Pro - Incorrect track maps & Constant offset

[Kometes]

Hi Guys,

I'm having a few issues with i2 pro:

1. Track maps generated for Eastern Creek (beacon) appear to cross over each other, as if there were bridges. Where do I check that the track is specified as closed? The track length is accurate (+/- a few %). This is occurring on ALL the cars we are running. The data was logged before my time so I'm unsure of the beacon location etc. I read elsewhere that this may be because of an issue with the lat & long G sensors on a banked track but I doubt that EC would be considered such a track.

2. When data from certain cars is compared there is a constant distance offset for each track required in order to line the data up. i.e. At Winton car A must be offset 40m from car B for the laps to line up, PI might be 60m etc. All cars are running the beacon receiver in the same location, wheel speed sensors are all working and the same settings for calculation of corrected distance is used.

Any possible solutions to these?

[PaulGM]

Kometes,

Your track map does not change between cars, it is saved to an individual installation of i2. Therefore, if all the log files are referencing the same track name (even if they come from different cars), then they will all show the same, incorrect track.

The option you are referring to is under Tools->Track Editor->Generate Track->Track Generation Settings. The "Generate Track" dialog will also show you some other options you will need to double-check, including your method of track generation (GPS or Lateral G & Speed), the channels you are using to generate the track, and whether or not you need to invert your Lateral G channel (if you are using Lateral G & Speed). Once you have adjusted and/or viewed them, hit OK to generate your track again (make sure you have a lap selected which you believe to have the best distance calculated).

As for your second problem, it sounds like someone may be running another beacon on the same code, which one car is set to ignore properly in the dash configuration and the other is not, and only one of them is picking that beacon hit up. The distances are different because your competitor who is running the same beacon code does not place them the exact same distance away from yours each time.

You will be able to tell by logging Beacon Hits and Beacon Numbers, and then your log files will show you whether or not this is the case. If it is, you should either raise the ignore time in your dash configuration so that their beacon is disregarded, or discuss using a common beacon with said team.