RTCM Client - Revision history

Kg7qin at 01:41, 15 March 2021

2021-03-15T01:41:07Z

Kg7qin at 01:39, 15 March 2021

2021-03-15T01:39:54Z

KM4NNO at 16:14, 1 January 2021

2021-01-01T16:14:36Z

Ve7fet: Add additional TSIP debug information.

2020-12-07T06:10:03Z

Add additional TSIP debug information.

Ve7fet: /* Un-documented Menus/Features */

2020-12-07T05:47:53Z

Un-documented Menus/Features

Ve7fet: Update some GPS information for the RTCM/VOTER.

2020-12-07T02:53:35Z

Update some GPS information for the RTCM/VOTER.

Ve7fet: Added a link to the new Quantar RTCM page.

2020-06-27T20:29:26Z

Added a link to the new Quantar RTCM page.

Ve7fet: Add info about RTCM GPS connections and connecting uBlox GPS modules.

2020-06-27T16:08:38Z

Add info about RTCM GPS connections and connecting uBlox GPS modules.

W3KKC at 02:43, 19 August 2019

2019-08-19T02:43:56Z

N8THN: Added Voter Buffer section

2019-01-28T14:11:39Z

Added Voter Buffer section

@@ Line 1: / Line 1: @@
 [[Category:How to]]
 [[Category:Hardware]]
 The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an PTTLink computer.

← Older revision		Revision as of 01:39, 15 March 2021
Line 1:		Line 1:
		+	[[Category:How to]]
		+	[[Category:Hardware]]
	The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an PTTLink computer.		The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an PTTLink computer.

@@ Line 1: / Line 1: @@
-The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an AllStarLink computer.
+The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an PTTLink computer.
-The Micro-Node RTCM and VOTER interfaces are typically used with AllStar in voting/simulcast applications. They MAY be used for ANY repeater interface application, through the chan_voter channel driver. The VOTER is the original through-hole board designed by Jim Dixon for this application. It is open-source, and the relevant Gerber files and BoM to build it are available. The [http://www.micro-node.com/thin-m1.shtml Micro-Node Radio Thin Client Module (RTCM)] is the commercial version of the VOTER. It uses surface mount parts (SMT), but is functionally equivalent to the original VOTER. In general, the two terms (RTCM/VOTER) are used interchangeably, as they operate the same, and use the same firmware (mostly, see below).
+The Micro-Node RTCM and VOTER interfaces are typically used with PTTLink in voting/simulcast applications. They MAY be used for ANY repeater interface application, through the chan_voter channel driver. The VOTER is the original through-hole board designed by Jim Dixon for this application. It is open-source, and the relevant Gerber files and BoM to build it are available. The [http://www.micro-node.com/thin-m1.shtml Micro-Node Radio Thin Client Module (RTCM)] is the commercial version of the VOTER. It uses surface mount parts (SMT), but is functionally equivalent to the original VOTER. In general, the two terms (RTCM/VOTER) are used interchangeably, as they operate the same, and use the same firmware (mostly, see below).
-This page will highlight some of the operational concerns, quirks, bugs, and other items of interest that relate to these interfaces. Much of the information has been gleaned off the AllStar mail list, comes from personal experience, or comes from notes in the firmware source code.
+This page will highlight some of the operational concerns, quirks, bugs, and other items of interest that relate to these interfaces. Much of the information has been gleaned off the PTTLink mail list, comes from personal experience, or comes from notes in the firmware source code.
 =Testing=
-RTCM's come preconfigured to login to [http://voter-demo-allstarlink.org voter-demo-allstarlink.org] for out of the box testing.
+RTCM's come preconfigured to login to [http://voter-demo-pttlink.org voter-demo-pttlink.org] for out of the box testing.
 =Factory Reset=
@@ Line 24: / Line 24: @@
-The current bootloader (.cof file) is available here: https://github.com/AllStarLink/voter/tree/master/voter-bootloader (the -smt file is for the RTCM). It needs to be loaded with a PICKit programmer.
+The current bootloader (.cof file) is available here: https://github.com/pttLink/voter/tree/master/voter-bootloader (the -smt file is for the RTCM). It needs to be loaded with a PICKit programmer.
-Current firmware (.cry file) is available here: https://github.com/AllStarLink/voter/tree/master/board-firmware . They are loaded with the EBLEX C30 Programmer.
+Current firmware (.cry file) is available here: https://github.com/pttLink/voter/tree/master/board-firmware . They are loaded with the EBLEX C30 Programmer.
@@ Line 40: / Line 40: @@
 ==Compiling Environment==
-If you look in the [https://github.com/AllStarLink/voter/blob/master/votersystem.pdf votersystem.pdf], you will find a procedure to modify and load the bootloader in to the dsPIC of a VOTER board.
+If you look in the [https://github.com/PTTLink/voter/blob/master/votersystem.pdf votersystem.pdf], you will find a procedure to modify and load the bootloader in to the dsPIC of a VOTER board.
@@ Line 55: / Line 55: @@
 Download MPLAB IDE 32-bit Windows v8.66:
 :http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_IDE_v8_66.zip
-:http://dvswitch.org/files/AllStarLink/Voter/MPLAB_IDE_v8_66.zip
+:http://dvswitch.org/files/pttLink/Voter/MPLAB_IDE_v8_66.zip
 Download MPLAB C Compiler for PIC24 and dsPIC DSCs v3.31 '''NOT v.3.25''':
 :http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc30-v3_31-windows-installer.exe
-:http://dvswitch.org/files/AllStarLink/Voter/mplabc30-v3_31-windows-installer.exe
+:http://dvswitch.org/files/pttLink/Voter/mplabc30-v3_31-windows-installer.exe
@@ Line 71: / Line 71: @@
 *Select Legacy Directory Name
 *'''Select Lite Compiler'''
-*Go to: https://github.com/AllStarLink
+*Go to: https://github.com/pttLink
 *Follow the links to: voter --> Clone or Download --> Download Zip. That will get you voter-master.zip which is a download of the whole VOTER tree from GitHub.
 *Extract it somewhere (ie. in the XP Mode Virtual PC)
@@ Line 157: / Line 157: @@
-Pre-compiled firmware versions including this option are available on [https://github.com/AllStarLink/voter/tree/master/board-firmware GitHub]. See above on how it is enabled/compiled, if you are rolling your own firmware modifications.
+Pre-compiled firmware versions including this option are available on [https://github.com/pttLink/voter/tree/master/board-firmware GitHub]. See above on how it is enabled/compiled, if you are rolling your own firmware modifications.
@@ Line 693: / Line 693: @@
 The VOTER is designed to accept both 3.3V or 5V signals, and ''should'' work fine.
-* Some of the Garmin GPS's come with 4800 baud set as default. If you are getting a "Warning: GPS Data time period elapsed" error on your RTCM, change both the GPS and RTCM to use 9600 baud. To do this, interface the GPS to a DB9 connector as per page 8 of the [http://wiki.allstarlink.org/w/images/4/41/GPS_18x_Tech_Specs.pdf manual] (remembering to ONLY use 5V as the power source *facepalm*). Once done, download, extract and open [http://www8.garmin.com/support/download_details.jsp?id=4053 SNSRXCFG_330.exe] and run.
+* Some of the Garmin GPS's come with 4800 baud set as default. If you are getting a "Warning: GPS Data time period elapsed" error on your RTCM, change both the GPS and RTCM to use 9600 baud. To do this, interface the GPS to a DB9 connector as per page 8 of the [http://wiki.pttlink.org/w/images/4/41/GPS_18x_Tech_Specs.pdf manual] (remembering to ONLY use 5V as the power source *facepalm*). Once done, download, extract and open [http://www8.garmin.com/support/download_details.jsp?id=4053 SNSRXCFG_330.exe] and run.
 # Select your GPS (in most cases GPS 18x PC/LVC). Press F10 to switch to NMEA mode (Config > Switch to NMEA Mode)
 # Select Config > Setup and choose the COM port your GPS is connected too. Leave baud rate as auto for now, OK.

@@ Line 802: / Line 802: @@
-So, the 1 after ok is the "happy gps" flag. The other 5 bytes are supposed to be bytes 9-14 from the packet... sort of. They are bytes 9-14 of the buffer, but they are actually bytes 8-13 of the binary message.
+So, the 1 after ok is the "happy gps" flag. The other 5 bytes are supposed to be bytes 9-14 from the packet... sort of. They are bytes 9-14 of the buffer, but they are actually bytes 8-13 of the binary message. '''Note that array byte 12 is Minor Alarm bits 0-7, and byte 11 is Minor Alarm bits 8-12.'''
@@ Line 817: / Line 817: @@
 GPS-DEBUG: TSIP: ok 1, 9 - 14: 00 00 00 00 00 00 - everything is good in the 'hood, Doing Fixes, Phase Locking
-GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 18 08 06 - not happy, Not Tracking Satellites, Not Disciplining Oscillator (0x18 --> 0b000000011000), No Usable Sats, Inactive
+GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 18 08 06 - not happy, Not Tracking Satellites, Not Disciplining Oscillator (0x18 --> 0b00011000, Bits 7-->0 of Minor Alarms), No Usable Sats, Inactive
 GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 08 08 05 - not happy, Not Tracking Satellites, No Useable Sats, Compensating OXCO (holdover)
@@ Line 826: / Line 826: @@
 GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 00 00 04 - not happy, Initializing Loop Filter
 </pre>
@@ Line 834: / Line 842: @@
 *Any Critical Alarms.
 *Any Minor Alarms.
 =Ubiquity ToS=

@@ Line 502: / Line 502: @@
 *Menu 1103 - set the "Glaser" timer value? No idea what this does.
-*Menu 1170 - set "Sawyer Mode". Developed for Tim Sawyer use on Yaesu VXR5000 repeater. It modifies de-ephasis behavior when on/off line.
+*Menu 1170 - set "Sawyer Mode". Developed for Tim Sawyer use on Yaesu VXR5000 repeater. Only applicable in OFFLINE mode. Disabled (default) when 0. When set to 1, it forces the PL filter OFF (bypassed) when in OFFLINE mode (not connected to the host), regardless of the state that it normally would be configured in voter.conf. Normally, the PL filter is IN during OFFLINE mode. That should effectively allow you to configure true pass-through (no PL filter or de-emphasis) audio through the device, if you set the rest of the options correctly.
 =Audio=

@@ Line 282: / Line 282: @@
 Enter Selection (1-9,99,c,x,q,r) :
 </pre>
 =Configuration Options=
@@ Line 561: / Line 605: @@
 $GPRMC
 </pre>
@@ Line 567: / Line 615: @@
-It is not unusual for it to take up to 20 mins to get a GPS lock LED (ie. using a Trimble Thunderbolt) after any reboot.
+It is not unusual for it to take up to 20 mins to get a GPS lock LED (ie. using a Trimble Thunderbolt) after any reboot. With the Trimble GPS', that is because it is waiting to complete the download of the almanac, and clear the status flags.
@@ Line 578: / Line 626: @@
 I found the debug setting of 32 useful in the RTCM, you can see a hex output of the GPS status.
 </pre>
@@ Line 600: / Line 651: @@
-We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, we have not done extensive testing to see how it affects other TSIP receivers.
+We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, it breaks other TSIP receivers (Resolution T). A better fix is being tested.
@@ Line 666: / Line 717: @@
 Make sure to save (99) and reboot (r) your VOTER/RTCM after making changes for them to be effective.

← Older revision		Revision as of 20:29, 27 June 2020
Line 190:		Line 190:
	*Don't "and" CTCSS with squelch. That may override the RTCM's squelch detection. Compare with CTCSS on and off to see effect if any.		*Don't "and" CTCSS with squelch. That may override the RTCM's squelch detection. Compare with CTCSS on and off to see effect if any.

		+	Also check the [[Quantar_RTCM\|Quantar RTCM]] page for detailed interfacing and configuration information.

	=RTCM/VOTER LED's=		=RTCM/VOTER LED's=

@@ Line 534: / Line 534: @@
 The firmware is specifically written to talk to Trimble Thunderbolt receivers using Trimble's TSIP binary data interface, however, other Trimbles GPS receivers that talk TSIP are generally compatible.
@@ Line 584: / Line 600: @@
 We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, we have not done extensive testing to see how it affects other TSIP receivers.
 ===Garmin===
@@ Line 635: / Line 652: @@
 # File > Save to a different file than step 5.
 # Press F9 or Config > Send Configuration to GPS. This will then send all the changes you made to the GPS unit (including baud rate so a reconnect may be needed)

@@ Line 453: / Line 453: @@
 *Menu 111 - show the "hidden" option values (normally they should all be 0).
-*Menu 11780 - set the "Elkes" value. Developed for Pete Elkes, this is for solar type sites. It shuts off the Tx after a period of no Rx activity.
+*Menu 11780 - set the "Elkes" value. Developed for Pete Elke WI6H, this is for solar type sites. It shuts off the Tx after a period of no Rx activity.
 *Menu 1103 - set the "Glaser" timer value? No idea what this does.

@@ Line 874: / Line 874: @@
 Of course Duplex Mode 3 support can't be used with voting or simulcast. You also loose Touch Tone muting, Time Out Timer and Repeater Disable functions because the repeat path is not through app_rpt.
 [[Category:How to]]
 [[Category:Node Configuration]]