Trimble SVeeEight GPS to RTCM

AllStarLink
1

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM… is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out… any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq…

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the

PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to

UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013

GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77

GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013

GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013

GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013

GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74

GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013

GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75

GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013

GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013

GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013

GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71

GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013

GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70

GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013

GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013

GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :

S/W Version: 1.38 10/09/2013

System Uptime: 1747.0 Secs

IP Address: 192.168.33.80

Netmask: 255.255.255.0

Gateway: 192.168.33.1

Primary DNS: 192.168.33.1

Secondary DNS: 8.8.8.8

DHCP: 0

VOTER Server IP: 192.168.33.60

VOTER Server UDP Port: 667

OUR UDP Port: 667

GPS Lock: 0

Connected: 0

COR: 0

EXT CTCSS IN: 1

PTT: 0

RSSI: 0

Current Samples / Sec.: 0

Current Peak Audio Level: 53448

Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400

Last Rx Pkt System time: , diff: 0 msec

Last Rx Pkt Timestamp time: , diff: 0 msec

Last Rx Pkt index: 0, inbounds: 0

image001.png782×858 60.4 KB

2

Try setting the time to UTC, rather than GPS time.

···

--
Tim
:wq

On Nov 27, 2013, at 8:34 AM, Gary Herzog Gmail <kc5daq@gmail.com> wrote:

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM.. is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out.. any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq..

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the
PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to
UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76
GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013
GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77
GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013
GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B
GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013
GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A
GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013
GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74
GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013
GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75
GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013
GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76
GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013
GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76
GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013
GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71
GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013
GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70
GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013
GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73
GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013
GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :
S/W Version: 1.38 10/09/2013
System Uptime: 1747.0 Secs
IP Address: 192.168.33.80
Netmask: 255.255.255.0
Gateway: 192.168.33.1
Primary DNS: 192.168.33.1
Secondary DNS: 8.8.8.8
DHCP: 0
VOTER Server IP: 192.168.33.60
VOTER Server UDP Port: 667
OUR UDP Port: 667
GPS Lock: 0
Connected: 0
COR: 0
EXT CTCSS IN: 1
PTT: 0
RSSI: 0
Current Samples / Sec.: 0
Current Peak Audio Level: 53448
Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400
Last Rx Pkt System time: <System Time Not Set>, diff: 0 msec
Last Rx Pkt Timestamp time: <System Time Not Set>, diff: 0 msec
Last Rx Pkt index: 0, inbounds: 0
<image001.png>
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

3

For just one site I am using a different GPS that also has this 10 microsecond pulse issue. I have tried a couple of different circuits to fix it. I first built a circuit using 2 transistors and that worked sometimes. Then I built a 555 circuit and that worked better but still not perfect. I am still experimenting with both hardware and software to improve the results. The biggest problem is with power cycle restart, it is almost always 1 second off. Then I do a telnet session to reboot the voter and it sometimes syncs up with the correct time. Once I get it synced it stays synced for months, till the next power interruption reboot, then the voter will be 1 second off again. All of my other sites use the Garmin GPS and they almost always start up fine with both power up and software reboot.
I have verified that the GPS itself is always exactly accurate, it is just the Voter syncs one second off.

Chuck

image001.png782×858 60.4 KB

···

On Wed, Nov 27, 2013 at 10:34 AM, Gary Herzog Gmail kc5daq@gmail.com wrote:

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM… is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out… any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq…

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the

PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to

UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013

GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77

GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013

GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013

GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013

GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74

GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013

GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75

GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013

GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013

GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013

GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71

GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013

GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70

GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013

GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013

GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :

S/W Version: 1.38 10/09/2013

System Uptime: 1747.0 Secs

IP Address: 192.168.33.80

Netmask: 255.255.255.0

Gateway: 192.168.33.1

Primary DNS: 192.168.33.1

Secondary DNS: 8.8.8.8

DHCP: 0

VOTER Server IP: 192.168.33.60

VOTER Server UDP Port: 667

OUR UDP Port: 667

GPS Lock: 0

Connected: 0

COR: 0

EXT CTCSS IN: 1

PTT: 0

RSSI: 0

Current Samples / Sec.: 0

Current Peak Audio Level: 53448

Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400

Last Rx Pkt System time: , diff: 0 msec

Last Rx Pkt Timestamp time: , diff: 0 msec

Last Rx Pkt index: 0, inbounds: 0

App_rpt-users mailing list

App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

4

Thanks for your response Tim.

Yes it was set to GPS I changed it to UTC applied the settings and rebooted I repolled the GPS unit and the config screen is shows UTC but the Debug there appears to be no difference… this may be normal…??

I tried GPS PPS Polarity with both options 0=Non-Inverted and 1=Inverted no difference…

I have the GPS unit sending $GPGSV $GPRMC $GPGGA sentences to the RTCM .

GPS-DEBUG: mon: 10, gps_time: 1385576929, ctime: Wed Nov 27 18:28:49 2013

GPS-DEBUG: $GPRMC,182850.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385576930, ctime: Wed Nov 27 18:28:50 2013

GPS-DEBUG: $GPRMC,182851.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385576931, ctime: Wed Nov 27 18:28:51 2013

GPS-DEBUG: $GPRMC,182852.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*78

GPS-DEBUG: mon: 10, gps_time: 1385576932, ctime: Wed Nov 27 18:28:52 2013

GPS-DEBUG: $GPRMC,182853.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*79

GPS-DEBUG: mon: 10, gps_time: 1385576933, ctime: Wed Nov 27 18:28:53 2013

GPS-DEBUG: $GPRMC,182854.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7E

GPS-DEBUG: mon: 10, gps_time: 1385576934, ctime: Wed Nov 27 18:28:54 2013

GPS-DEBUG: $GPRMC,182855.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7F

GPS-DEBUG: mon: 10, gps_time: 1385576935, ctime: Wed Nov 27 18:28:55 2013

GPS-DEBUG: $GPRMC,182856.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7C

GPS-DEBUG: mon: 10, gps_time: 1385576936, ctime: Wed Nov 27 18:28:56 2013

GPS-DEBUG: $GPRMC,182857.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7D

GPS-DEBUG: mon: 10, gps_time: 1385576937, ctime: Wed Nov 27 18:28:57 2013

GPS-DEBUG: $GPRMC,182858.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*72

GPS-DEBUG: mon: 10, gps_time: 1385576938, ctime: Wed Nov 27 18:28:58 2013

GPS-DEBUG: $GPRMC,182859.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385576939, ctime: Wed Nov 27 18:28:59 2013

GPS-DEBUG: $GPRMC,182900.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7E

GPS-DEBUG: mon: 10, gps_time: 1385576940, ctime: Wed Nov 27 18:29:00 2013

GPS-DEBUG: $GPRMC,182901.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7F

GPS-DEBUG: mon: 10, gps_time: 1385576941, ctime: Wed Nov 27 18:29:01 2013

GPS-DEBUG: $GPRMC,182902.0,A,3009.808,N,09550.255,W,000.00,000.0,271113,05.5,E*7

···

From: Tim Sawyer [mailto:tim.sawyer@mac.com]
Sent: Wednesday, November 27, 2013 11:08 AM
To: Gary Herzog Gmail
Cc: app_rpt mailing list
Subject: Re: [App_rpt-users] Trimble SVeeEight GPS to RTCM

Try setting the time to UTC, rather than GPS time.

–
Tim
:wq

On Nov 27, 2013, at 8:34 AM, Gary Herzog Gmail kc5daq@gmail.com wrote:

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM… is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out… any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq…

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the

PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to

UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013

GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77

GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013

GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013

GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013

GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74

GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013

GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75

GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013

GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013

GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013

GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71

GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013

GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70

GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013

GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013

GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :

S/W Version: 1.38 10/09/2013

System Uptime: 1747.0 Secs

IP Address: 192.168.33.80

Netmask: 255.255.255.0

Gateway: 192.168.33.1

Primary DNS: 192.168.33.1

Secondary DNS: 8.8.8.8

DHCP: 0

VOTER Server IP: 192.168.33.60

VOTER Server UDP Port: 667

OUR UDP Port: 667

GPS Lock: 0

Connected: 0

COR: 0

EXT CTCSS IN: 1

PTT: 0

RSSI: 0

Current Samples / Sec.: 0

Current Peak Audio Level: 53448

Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400

Last Rx Pkt System time: , diff: 0 msec

Last Rx Pkt Timestamp time: , diff: 0 msec

Last Rx Pkt index: 0, inbounds: 0

<image001.png>

App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

5

Hmm interesting thanks for the info yes I would use the Garmin but I have 25 of these Trimble units that I would hate not to be able to use them I wonder if there is anything in the TRCM that could be tuned to enable the 10 microsecond pulse?

Thanks for your response.

image001.png782×858 60.4 KB

···

From: Chuck Henderson [mailto:rpt2@chuck.midlandsnetworking.com]
Sent: Wednesday, November 27, 2013 12:45 PM
To: Gary Herzog Gmail
Cc: app_rpt mailing list
Subject: Re: [App_rpt-users] Trimble SVeeEight GPS to RTCM

For just one site I am using a different GPS that also has this 10 microsecond pulse issue. I have tried a couple of different circuits to fix it. I first built a circuit using 2 transistors and that worked sometimes. Then I built a 555 circuit and that worked better but still not perfect. I am still experimenting with both hardware and software to improve the results. The biggest problem is with power cycle restart, it is almost always 1 second off. Then I do a telnet session to reboot the voter and it sometimes syncs up with the correct time. Once I get it synced it stays synced for months, till the next power interruption reboot, then the voter will be 1 second off again. All of my other sites use the Garmin GPS and they almost always start up fine with both power up and software reboot.

I have verified that the GPS itself is always exactly accurate, it is just the Voter syncs one second off.

Chuck

On Wed, Nov 27, 2013 at 10:34 AM, Gary Herzog Gmail kc5daq@gmail.com wrote:

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM… is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out… any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq…

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the

PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to

UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013

GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77

GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013

GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013

GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013

GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74

GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013

GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75

GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013

GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013

GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013

GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71

GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013

GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70

GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013

GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013

GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :

S/W Version: 1.38 10/09/2013

System Uptime: 1747.0 Secs

IP Address: 192.168.33.80

Netmask: 255.255.255.0

Gateway: 192.168.33.1

Primary DNS: 192.168.33.1

Secondary DNS: 8.8.8.8

DHCP: 0

VOTER Server IP: 192.168.33.60

VOTER Server UDP Port: 667

OUR UDP Port: 667

GPS Lock: 0

Connected: 0

COR: 0

EXT CTCSS IN: 1

PTT: 0

RSSI: 0

Current Samples / Sec.: 0

Current Peak Audio Level: 53448

Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400

Last Rx Pkt System time: , diff: 0 msec

Last Rx Pkt Timestamp time: , diff: 0 msec

Last Rx Pkt index: 0, inbounds: 0

App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

6

Gary:

I know that there have been some other emails about this that I have not had time to
read, since I worked 13.5 hours yesterday and 13 hours the day before. I will probably
be doing it again tomorrow, so if you have time today (hopefully), I will be happy to
contact you directly (like on the phone or something), and work with you to resolve this
problem.

From what little I can see here, I have a serious problem believing that a 10us pulse
is too short. I think it is likely to be something else.

Please email me off-list with contact info.

Thanks

Jim WB6NIL

image001.png782×858 60.4 KB

···

From: kc5daq@gmail.com
To: app_rpt-users@ohnosec.org
Date: Wed, 27 Nov 2013 10:34:27 -0600
Subject: [App_rpt-users] Trimble SVeeEight GPS to RTCM

We are trying to interface a Trimble-SVeeEight-Plus to the RTCM. I am running the S/W Version: 1.38 10/09/2013 on the RTCM and I am seeing the GPS info listed below in Debug mode 32 but I think I may be having issues with the PPS. The Trimble indicates that it has a 10 microseconds negative going pulse I noticed that the Garmin GPS 78X LVC has a default pulse width of 100 milliseconds. I am wondering if the Trimble is too fast for the RTCM… is this going to be a problem?? It appears that I cannot adjust the pulse width on the SVeeEight as its grayed out… any ideas. Your help would be greatly appreciated. Thanks Gary Kc5daq…

The 1PPS signal is an open collector interface on pin 9 of Ports 1 and 2. The polarity of the

PPS signal is an inverted, 10 microseconds negative going pulse with the falling edge synchronized to

UTC

GPS-DEBUG: $GPRMC,181436.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403276, ctime: Mon Nov 25 18:14:36 2013

GPS-DEBUG: $GPRMC,181437.0,A,3009.798,N,09550.252,W,000.00,000.0,251113,05.5,E*77

GPS-DEBUG: mon: 10, gps_time: 1385403277, ctime: Mon Nov 25 18:14:37 2013

GPS-DEBUG: $GPRMC,181438.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7B

GPS-DEBUG: mon: 10, gps_time: 1385403278, ctime: Mon Nov 25 18:14:38 2013

GPS-DEBUG: $GPRMC,181439.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*7A

GPS-DEBUG: mon: 10, gps_time: 1385403279, ctime: Mon Nov 25 18:14:39 2013

GPS-DEBUG: $GPRMC,181440.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*74

GPS-DEBUG: mon: 10, gps_time: 1385403280, ctime: Mon Nov 25 18:14:40 2013

GPS-DEBUG: $GPRMC,181441.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*75

GPS-DEBUG: mon: 10, gps_time: 1385403281, ctime: Mon Nov 25 18:14:41 2013

GPS-DEBUG: $GPRMC,181442.0,A,3009.798,N,09550.251,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403282, ctime: Mon Nov 25 18:14:42 2013

GPS-DEBUG: $GPRMC,181443.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*76

GPS-DEBUG: mon: 10, gps_time: 1385403283, ctime: Mon Nov 25 18:14:43 2013

GPS-DEBUG: $GPRMC,181444.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*71

GPS-DEBUG: mon: 10, gps_time: 1385403284, ctime: Mon Nov 25 18:14:44 2013

GPS-DEBUG: $GPRMC,181445.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*70

GPS-DEBUG: mon: 10, gps_time: 1385403285, ctime: Mon Nov 25 18:14:45 2013

GPS-DEBUG: $GPRMC,181446.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*73

GPS-DEBUG: mon: 10, gps_time: 1385403286, ctime: Mon Nov 25 18:14:46 2013

GPS-DEBUG: $GPRMC,181447.0,A,3009.798,N,09550.250,W,000.00,000.0,251113,05.5,E*72

Enter Selection (1-27,97-99,r,q,d) :

S/W Version: 1.38 10/09/2013

System Uptime: 1747.0 Secs

IP Address: 192.168.33.80

Netmask: 255.255.255.0

Gateway: 192.168.33.1

Primary DNS: 192.168.33.1

Secondary DNS: 8.8.8.8

DHCP: 0

VOTER Server IP: 192.168.33.60

VOTER Server UDP Port: 667

OUR UDP Port: 667

GPS Lock: 0

Connected: 0

COR: 0

EXT CTCSS IN: 1

PTT: 0

RSSI: 0

Current Samples / Sec.: 0

Current Peak Audio Level: 53448

Squelch Noise Gain Value: 18, Diode Cal. Value: 40, SQL pot 400

Last Rx Pkt System time: , diff: 0 msec

Last Rx Pkt Timestamp time: , diff: 0 msec

Last Rx Pkt index: 0, inbounds: 0

App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users