Rally configuration

[devenh]

I created the hlptrz file, mailed it to my iPhone, LT recognized it, but failed to import it. I tried a couple of different variations, but no luck. I error checked the XML and it passed.

I have an existing track, SSCC, on my iPhone. It simply consists of the start and finish coordinates:

START: N38.49.900 W115.00.652 (38.831667 -115.010867)
FINISH: N37.37.700 W115.13.179 (37.628333 -115.21965)

So the lap I am trying to import should find its way to this track.

Thanks,

Deven

[devenh]

Harry,

I've continued to work on the process.

I tried downloading a lap, changing the date and lap time (as well as making the individual fixes (<fix>...</fix>) consistent with the new lap time) and sent it back to HLT. This worked. I also tried creating a big gap in fixes (which occurs in my Google Maps GPS generated coordinates), and this worked too.

Then I tried to generate a virtual lap using a spreadsheet. I kept refining it until every field that was in the successful upload was in the virtual lap. The only one I'm not sure about is the <coordinate> tag in <acceleration>. For now I am using 0,0.

Attached are two files. mtrose.hlptrl is the successful upload (I had to gzip it so I could attach it here -- when I send the file to my iPhone the extension is .hlptrz). mtrose7.hlptrl is the unsuccessful one.

Here is the fix from mtrose:

Code: Select all

		<fix index="7851">
				<date>01-SEP-13,14:36:12.74</date>
				<coordinate>39.390007,-119.802754,1628.0</coordinate>
				<speed>0.0</speed>
				<positioning>0,3</positioning>
				<satellites>0</satellites>
				<direction>243.3</direction>
				<hdop>0.00</hdop>
				<accuracy>5.0</accuracy>
				<relativeToStart>0.0,00:00.00</relativeToStart>
				<acceleration>
					<source>1</source>
					<lateral>0.01</lateral>
					<lineal>0.02</lineal>
					<coordinate>39.390003,-119.802751</coordinate>
				</acceleration>
			</fix>

And from mtrose7:

Code: Select all

			<fix index="9001">
				<date>02-SEP-13 00:00:00.00</date>
				<coordinate>39.38992,-119.8027,1636.8</coordinate>
				<speed>0.0</speed>
				<positioning>0,2</positioning>
				<satellites>0</satellites>
				<direction>249.9</direction>
				<hdop>0.00</hdop>
				<accuracy>5.0</accuracy>
				<relativeToStart>0.0,00:00:00.00</relativeToStart>
				<acceleration>
					<source>1</source>
					<lateral>0.0</lateral>
					<lineal>0.0</lineal>
					<coordinate>0,0</coordinate>
				</acceleration>
			</fix>

Thanks,

Deven

[Harry]

In fix 7851 displayed above, the "date" tagged field misses a comma. Please set the coordinate field in acceleration to exactly the coordinate of the fix. The acceleration coord is the position LapTimer uses to print lateral acceleration curves (red, yellow, green). Setting the coordinate to the fixe's coordinate will not show any lateral acceleration, but at least leads to a track plot that can be displayed.

- Harry

[devenh]

I made the changes you pointed out, plus I found some of my own:

relativeToStart distance was in kilometers, not meters and elapsed time was in HH:MM:SS.SS format, not MM:SS.SS.

Code: Select all

			<fix index="8134">
				<date>02-SEP-13,01:07:59.59</date>
				<coordinate>39.34001,-119.87711,2274.4</coordinate>
				<speed>104.6</speed>
				<positioning>0,2</positioning>
				<satellites>0</satellites>
				<direction>167.5</direction>
				<hdop>0.00</hdop>
				<accuracy>5.0</accuracy>
				<relativeToStart>12974.4,07:59.59</relativeToStart>
				<acceleration>
					<source>1</source>
					<lateral>0.0</lateral>
					<lineal>0.0</lineal>
					<coordinate>39.34001,-119.87711</coordinate>
				</acceleration>
			</fix>

Thanks for your help!

Deven

[devenh]

Okay, I think I have it working. More info when I confirm.

[devenh]

Removing the <acceleration> tag seems to have gotten things working. Not sure whether it played a role, but I also set a unique lap index. All vehicle info could be safely removed from the file too.

Even without the acceleration data, HLT did manage to generate all the normal charts (Lateral, Lineal, Overall, Yaw), but sometimes resulting in 2+ g's. This is not an issue.

Over the next few days I'll try to do some on road testing.

[devenh]

One issue has surfaced. Once the lap has been imported, when I view the Lap Details the Track Info Length is 4.197mi. It should be 90mi.

[devenh]

I created another track and lap. This time the imported lap had the correct length. Not sure why the other lap had the wrong length.

Also, importing seems to be sensitive to the Lap Index value. Sometimes when an import fails, simply changing the Lap Index fixes it.

Deven

[Harry]

The overall distance is stored in the <lap> section (<overallDistance>). The value should be the same as the last fix's <relativeToStart> distance value.
The index attribute in the <lap> tag is definitively ignored.

- Harry

[Fursty]

Harry:

I would like to do the same thing that devenh has done, but for a different race. Could you please help me with writing the xml file to create the reference lap for my track?

Ryan