Harry's GPS Suite Forum

I was testing out autocross triggers using the standard start/stop and the compass that pops up and notice it's not paying attention to direction, is this supported?

Test setup...
Nexus 7 in landscape, facing inside car using default sensor setting for gyro/accl
dual 160 gps & bluetooth elm27

Start point: facing west
course: I drive to the end of my driveway and turn around and come back
stop point: half way back to the start point about 1/3 mile but facing east as I'm coming back.

Laptimer start trigger works properly, but the stop trigger stops as soon as I cross the stop point, going west rather than coming back east, is this how it works? I thought the trigger paid attention to the direction I'm going to avoid false stops on a tight autocross course

I was not sure what the compass that pops up when you set a stop/start point is for

The compass is giving you a visual feedback on the direction you are pointing the device to. As the help text says "Point the device to the direction you will pass the trigger at, and press Set", you either need to point the top of the device into driving direction (and press "Set", or skip direction setting completely. To me it sounds like you set the direction in the opposite direction than what you wanted? You can verify this after the fact by looking into the trigger definition (Lap List ‣ your AX track ‣ User Defined Track Set ‣ Finish or Stop.

- Harry

You can also look at the Map View. Triggers with directions set show up as black and white checkered lines with a red triangle pointing in the direction of travel. With no direction set, it's a flag with a red dot in the middle.

Ok I just tested a few times, android is not recording the direction on the finish, no arrow on the map view.

When I set start point, it pops up the compass and lets me click set
When I set the stop point, it does not pop up the compass until after it asks if I want to purge the old track and does not seem to save the directions when I click set

Bug reproduced for both Android and iOS, I plan to have it fixed for 20.0.6.

- Harry