I was using a Garmin GPS18C ‘puck’ type of GPS running at 4800 baud. I had to set the RS232 port to 4800 (9600 is now the default after a new firmware update) and it recognized the GPS on the next restart, so the Baud rate worked. I couldn’t exit the Sync screen. Did I miss something? The only way I could get out of it was by sending a pulse on C0.
The GPS that Alge is selling is running at 9600 baud. I know from talking to Albert, that they are looking for a $GPRMC sentance and a valid satellite signal (this sample is not valid).
On the other hand, the "Johnny Appleseed" feature of the Timy (impulse on channel 0 at Top Dead Center when holding down green & red OK) is *extremely* useful. Once you get a "reference Timy" going, it doesn't matter whether the reference is synched in any semblance to UTC or local time, as long as all your time bases match the reference, and therefore each other.
In any event, looking through the Garmin docs, the contents of the $GPRMC packet is dangerously misleading. Param #1 is the UTC time, and Param #2 is the Status Tag. You would think a Status Tag of "V" (as in Mike's example above) means "Valid", but the opposite is true. "V" is a "validity warning". "A" means the GPS is synched up.
Most GPSs have some non-volatile memory, so they "remember" the UTC time - but with substantial drift. Until that $GPRMC param #2 turns from "V" to "A", the GPS time is going from memory, not from the satellite, and may be off substantially. If the GPS has been moved or reset, then the UTC may start from 000000. The Garmin docs state that a full satellite synch from scratch takes about 5 minutes from the time the GPS is powered up and has a view of the sky.
I knew I was going to get in trouble posting that actual stream from my Garmin. I just didn't want to stand outside in the +14C rain here in Toronto (isn't this winter) to catch a valid signal. I thought I would hack the V to a A, but the Checksum at the end would have been wrong.
However, I couldn't agree with you more with having the top of minute function the most important feature. We use it all the time.
Short story, I was just doing it because it was there. Not really required for Ski Racing other than to rapidly resync a Timy at the start for a backup device (like hand timing or connected to a start wand for the 5th + backup system).
A our ski club we use 5 Timy for the ski race.
We use 2 hold timy for the manual chrono
Everything has double redundancy, The start gate feeds 2 pair of wires. At the finish, we have 2 set of photocell. The chrono 1 gets the input from the start 1 and finish 1. The chrono 2 use the start 2 and finish 2.
The Backup chrono receive the info from the start 1 using a wireless TED. and the finish from the wire from the photocell 1.
The problem is to sync 2 PC and 5 Timy. Setting the time on each is quite long. we Give them the impulse from a single button that feed 5 DB25 connector.
We would like to use a GPS to feed all 5 at the sime time. We have found out that the TIMY only support GARMIN GPS because it uses a non standard NMEA instruction PGRMF proritary of garmin.
Can someone tell me why they didn't use the real NMEA Standard and the proper time of day instructions. In their instruction they say that we need a GPS that support NMEA 0183 standard with a sync pin signal at the top of the second. They never mention anything as far as supporting GARMIN Commands.
Does someone have a PC program to set the time on the PC with the GPS...
The alternate solution would be to have a PC program that send the instructions to set the time to the timy and use a CTS signal from the PC to sent the SYNC to the TiMY. Does anyone have a program to send the TIME and Date instruction from the PC to the TIMY