VOTER-Hardware: Difference between revisions

From AllStarLink Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
No edit summary
 
(12 intermediate revisions by the same user not shown)
Line 3: Line 3:
This is the documentation page to support the through-hole implementation of the VOTER Hardware.
This is the documentation page to support the through-hole implementation of the VOTER Hardware.


See the [[VOTER]] page for more information on the background/history. If you have bought or built a through-hole VOTER, this page is for you. If you have an [http://www.micro-node.com/thin-m1.shtml RTCM], then you will want to reference the [http://173.248.148.139/unode_docs/rtcm_%20manual.pdf manual] for the RTCM. That said, most of the information here should be applicable.


<gallery mode=nolines>
File:1599px-Voter-assy-trim.png
File:Voterr-reva.jpg
</gallery>


= Firmware =


See the [[RTCM_Firmware_upgrading | firmware upgrade]] page for information on upgrading the firmware.
See the [[VOTER]] page for more information on the background/history. If you have bought or built a through-hole VOTER, this page is for you. If you have an [http://www.micro-node.com/thin-m1.shtml RTCM], then you will want to reference the [http://173.248.148.139/unode_docs/rtcm_%20manual.pdf manual] for the RTCM or our [[RTCM_Client | RTCM Client]] page. That said, most of the information here should be applicable too.




== Bootloader ==
The Micro-Node RTCM (and [[VOTER-Hardware | VOTER]]) interfaces are typically used with AllStar in voting/simulcast applications. They '''MAY''' be used for '''ANY''' repeater interface application, through the <code>chan_voter</code> channel driver, as they are primarily a Radio over IP (ROIP) adapter.


There are '''two parts''' to the firmware, a bootloader, and then the actual firmware file. The bootloader starts when power is applied, and allows you to talk to the dsPIC and load new firmware files over ethernet. If the bootloader is not intercepted by the EBLEX C30 loading tool, it will continue to boot the current firmware file.


= Firmware =


If you are building your own VOTER, or for some reason you need to replace U6, you will want to program in the bootloader to allow for remote firmware upgrades.
See the [[RTCM_Firmware_upgrading | firmware upgrade]] page for information on upgrading the firmware.
 
 
'''Note:''' You '''can''' compile your own firmware and program the resulting .hex file in to U6 and it will run, but why?
 
 
To program the bootloader code in the dsPIC, you will need a PICKit2/PICKit3 (or equivalent) programmer, and the [http://dvswitch.org/files/AllStarLink/Voter/MPLAB_IDE_v8_66.zip Microchip MPLAB IDE v8.86], and [http://dvswitch.org/files/AllStarLink/Voter/mplabc30-v3_31-windows-installer.exe MPLAB C Compiler for PIC24 and dsPIC DSCs v3.31]. You are going to probably want to find a Windows XP environment to install those on.
 
 
Download the bootloader files from [https://github.com/AllStarLink/Voter/tree/master/VOTER-bootloader here]. '''Note:''' the '''smt''' file is for the RTCM and NOT the VOTER.
 
 
Open the MPLAB IDE.
 
*Go to Project --> Open --> voter-bootloader.mcp --> Open (it is in the voter-bootloader folder of the GitHub source)
*Go to File --> Import --> voter-bootloader --> ENC_C30.cof --> Open '''This step is missing from the original procedure.'''
*Remove JP7 on the VOTER Board. This is necessary to allow programming by the PICKit2/PICKit3 device.
*Attach the PICKIT2/PICKit3 device to J1 on the VOTER board. Note that Pin 1 is closest to the power supply modules (as indicated on the board).
*If you have not already selected a programming device, go to Programmer --> Select Device and choose PICKit3 (or PICKit2, depending on what you are using).
*Go to Programmer --> Program. This will program the bootloader firmware into the PIC device on the board.
 
 
=== Changing the Default Bootloader IP ===
 
If you want to change the default IP address from 192.168.1.11 in the bootloader:
 
*Select View --> Program Memory (from the top menu bar)
*Hit Control-F (to "find") and search for the digits "00A8C0"
 
 
These should be found at memory address "03018".
 
 
The "A8C0" at 03018 represents the hex digits C0 (192) and A8 (168) which are the first two octets of the IP address. The six digits to enter are 00 then the SECOND octet of the IP address in hex then the FIRST octet of the IP address in hex.
 
 
The "0B01" at 0301A represents the hex digits 0B (11) and 01 (1) which are the second two octets of the IP address. The six digits to enter are 00 then the FOURTH octet of the IP address in hex then the THIRD octet of the IP address in hex.




Once you have modified the address to your desired IP, follow the programming procedure (above).
If you are building your own VOTER, or for some reason you need to replace U6, you will want to program in the bootloader in to the dsPIC to allow for remote firmware upgrades. See the [[RTCM_Firmware_upgrading#Bootloader_Installation | Bootloader section]] on how to do that.




Line 116: Line 82:
LED4 - (Yellow) Connection Indicator (indicates that connection was made with VOTER host)
LED4 - (Yellow) Connection Indicator (indicates that connection was made with VOTER host)
</pre>
</pre>
The COS (RX) LED on the VOTER will flash (same rate as Activity LED) if you have External CTCSS enabled, and the received signal has the wrong (or no) valid PL.




Line 142: Line 111:
=== JP2 - 20dB Pad ===
=== JP2 - 20dB Pad ===


Insert to attenuate discriminator input level by 20db. This pad affects the '''receive audio level'''. See the RX Input Level Calibration section.
Insert to attenuate discriminator input level by 20db. This pad affects the '''receive audio level'''. See the [[#Receive Level Input Calibration | Receive Level Input Calibration]] section.




Line 168: Line 137:
=== JP9 - Squelch Calibration ===
=== JP9 - Squelch Calibration ===


Insert to calibrate squelch. See below.  
Insert to calibrate squelch. See [[#Squelch Calibration and Setting | Squelch Calibration]] below.  




Line 181: Line 150:
=== JP11 - LED3/4 Receiver Level Mode ===
=== JP11 - LED3/4 Receiver Level Mode ===


Insert this jumper to temporarily re-purpose LED3 and LED4 to allow for visual indication of RX input level (see Rx Level Calibration, below). Alternatively, you can use menu 97.
Insert this jumper to temporarily re-purpose LED3 and LED4 to allow for visual indication of RX input level (see [[#Receive Level Input Calibration | Rx Level Calibration]], below). Alternatively, you can use [[VOTER-Menus#97_RX_Level_Display | Menu 97]].




Line 198: Line 167:




Be sure to do this at a reasonable human room temperature (like 60-80 deg. F). This is necessary because this procedure initializes the operating parameters in the EEPROM and also does a temperature compensation diode calibration, which needs to happen at room temperature.  
Be sure to do this at a reasonable human room temperature (like 60-80 deg. F). This is '''necessary''' because this procedure initializes the operating parameters in the EEPROM and also does a temperature compensation diode calibration, which '''needs''' to happen at room temperature.  




Once the jumper shunts have been installed, power-cycle the board and wait for the system activity light to come on steady (about 4 seconds or so after the 5 second initial wait time).
Once the jumper shunts have been installed, power-cycle the board and wait for the system activity light to come on ''''steady'''' (about 4 seconds or so after the 5 second initial wait time).




Then, remove the jumper shunts, and proceed with Squelch Calibration.
Then, '''remove''' the jumper shunts, and proceed with [[#Squelch Calibration and Setting | Squelch Calibration]].




Line 215: Line 184:




If unsuccessful, the LED will flash either fast to indicate that the discriminator noise level is too high, or slowly to indicate that the discriminator noise level is too low. If the discriminator level is too low, try inserting JP1 and try again.
If unsuccessful, the LED will flash either '''fast''' to indicate that the discriminator noise level is too '''high''', or '''slowly''' to indicate that the discriminator noise level is too '''low'''. If the discriminator level is too low, try inserting JP1 and try again.




Note, if JP10 is inserted during this procedure, the "Diode Calibration" process will also occur.
'''Note:''' If JP10 is inserted during this procedure, the "Diode Calibration" process will also occur.




If you still have troubles calibrating the squelch, you may need to try the Baseband Examination Window (BEW) firmware.
If you still have troubles calibrating the squelch, you may need to try the [[VOTER-Audio#DSP.2FBEW_Firmware_Version | Baseband Examination Window (BEW)]] firmware.




Line 237: Line 206:




Menu 98 will show the settings of the Squelch Calibration, Diode Calibration, and Squelch Levels:
[[VOTER-Menus#98_Status_Display | Menu 98]] will show the settings of the Squelch Calibration, Diode Calibration, and Squelch Levels:


<pre>
<pre>
Line 243: Line 212:
</pre>
</pre>


'''Note:''' Firmware >3.00 allows for the option to set the squelch via software, after initially setting it with the hardware potentiometer to get a baseline level. See the [[VOTER-Menus#s_Squelch_Parameters_Menu | Squelch Parameters Menu]].


= Receive Level Input Calibration =
= Receive Level Input Calibration =
See the [[VOTER-Audio]] page for additional considerations when it comes to connecting the VOTER to your receiver, and for level setting instructions.


Place a full-quieting saturated signal on the receiver, modulated by 1000 Hertz sine wave at 3KHz deviation.  
Place a full-quieting saturated signal on the receiver, modulated by 1000 Hertz sine wave at 3KHz deviation.  
Line 252: Line 226:




Alternatively, menu 97 from the console menu gives a more graphical method of setting the Rx input level:
Alternatively, [[VOTER-Menus#97_RX_Level_Display | Menu 97]] from the console menu gives a more graphical method of setting the Rx input level:


<pre>
<pre>
Line 269: Line 243:




This gets a little complicated, and will depend on how you have your system configured. This is a general guideline, adjust for your application. It assumes that you have a receiver co-located with a transmitter, and that this VOTER board is doing receive and transmit functions.  
See the [[VOTER-Audio]] page for considerations when it comes to connecting the transmit audio to your transmitter, and for level setting instructions.




Once you have completed the Receive Level Input Calibration (above), that audio will be sent in one of two places. If the VOTER is connected to the host, it will be sent to <code>chan_voter</code> and <code>app_rpt/Asterisk</code>. If the VOTER is '''not''' connected to the host, '''and''' you have "offline repeat" configured in the VOTER, the receive audio will be looped back to the transmitter (with any additional configuration details from offline repeat mode).
= Console Connection =


 
Serial Console access is provided by an RS-232 serial port (J3) at 57600 baud, 8 bits, No parity, 1 Stop Bit. It is also made available remotely (off-board) via TELNET. When TELNET-ing the default user is "admin" and the password is "radios".  
The "easiest" way to set the transmit level is to configure offline repeat.


<pre>
<pre>
OffLine Mode Parameters Menu
VOTER System Serial # 1234 Remote Console Access


Select the following values to View/Modify:
Login: admin
Password: radios


1  - Offline Mode (0=NONE, 1=Simplex, 2=Simplex w/Trigger, 3=Repeater) (3)
Logged in successfully, now joining console session...
2  - CW Speed (400) (1/8000 secs)
3  - Pre-CW Delay (4000) (1/8000 secs)
4  - Post-CW Delay (4000) (1/8000 secs)
5  - CW "Offline" (ID) String (N0CALL/R)
6  - CW "Online" String (OK)
7  - "Offline" (CW ID) Period Time (18000) (1/10 secs)
8  - Offline Repeat Hang Time (15) (1/10 secs)
9  - Offline CTCSS Tone (136.5) Hz
10 - Offline CTCSS Level (0-32767) (0)
11 - Offline De-Emphasis Override (0=NORMAL, 1=OVERRIDE) (1)
99 - Save Values to EEPROM
x  - Exit OffLine Mode Parameter Menu (back to main menu)
q  - Disconnect Remote Console Session, r - reboot system
 
Enter Selection (1-9,99,c,x,q,r) :
</pre>
</pre>




Ensure that the ''Offline Mode'' is set to '''3'''.
When done with the console session, please use the 'q' command to disconnect. The local serial port and the TELNET (remote) user share the same (and only) console session.




''Offline CTCSS Tone'' doesn't matter but ''Offline CTCSS Level'' '''must''' be set to '''0'''.
= Console Menus =


For a thorough explanation of the different menus, see the [[VOTER-Menus | VOTER Menus]] page.


''Offline De-Emphasis Override'' will depend on how you have your transmit audio coupled to your transmitter. If you are using microphone audio input (so that the audio gets pre-emphasized and splatter filtered), this would be set to '''0'''. If, however, you are using an auxiliary modulation input that goes direct to the modulator (because you may want the VOTER to generate CTCSS), then this would be set to '''1'''.


= Debug Options =
The VOTER/RTCM firmware supports some additional debugging information that can be turned on.


With the Ethernet cable removed (so there is no connection to the host), applying a 1kHz tone at 3kHz deviation should cause the VOTER to key the transmitter (in offline mode).
Adjust R63 to set the transmitter deviation to 3kHz (3kHz in, 3kHz out).
Remove the receiver signal, and (optionally) set the ''Offline Mode'' back to '''0'''.
At this point, if you have a properly configured AllStar host (including settings in <code>voter.conf</code>), re-connect the Ethernet cable to the VOTER. Ensure that the connection to the host is established. Now, when you send your 1kHz at 3kHz deviation in to the receiver, it should come out the transmitter at 3kHz deviation as well.
== CTCSS Level Setting ==
As noted above, if you have a direct modulator connection to your transmitter, and wish to have AllStar '''and''' the VOTER generate CTCSS for you on transmit, you will need to set the levels.
=== Offline Repeat CTCSS Level ===
Configure your offline repeat mode as noted above, and set the transmitter deviation.
Set the ''Offline CTCSS Tone'' for the desired tone. Save the settings (99).
Now, remove the 1kHz modulating tone from the audio you are injecting in to the receiver.
Adjust the ''Offline CTCSS Level'' until you get about 500Hz deviation of your CTCSS tone (check your filters on your service monitor, you probably want 300Hz LPF enabled to get an accurate measurement).
Remember to save the settings (99) and probably reboot (r) to ensure everything is playing nice.
=== voter.conf CTCSS Level Setting ===
Re-connect your VOTER to your host.
The requisite settings in your <code>voter.conf</code> file are:


From the source code, the different Debug Options are listed as:
<pre>
<pre>
txctcss = 136.5
1 - Alt/Main Host change notifications
txctcsslevel = 47              ;***this is a calibrated value, DO NOT CHANGE***
2 - Ignore HWlock (GGPS only)
txtoctype = phase
4 - GPS/PPS Failure simulation (GGPS only)
8 - POCSAG H/W output disable (GGPS only)
16 - IP TOS Class for Ubiquiti
32 - GPS Debug
64 - Fix GPS 1 second off
</pre>
</pre>




Set the transmitter deviation as noted above.
Not sure what they all do, but that is what they are. Here are the most common ones used:
 


*''Alt/Main Host change notifications'' shows when the connection to the Asterisk server changes state (when configured for redundant servers).


Set the ''txctcss'' and ''txtoctype'' options in <code>voter.conf</code> as necessary for your application.  
*''IP TOS Class for Ubiquity'' in firmware >2.00, this '''disables''' marking the IP headers from the RTCM/VOTER '''TO''' the network with ToS C0/DSCP 48 (UBNT shows this as 802.1p Class 6 (Voice <10mS latency). Other sources show this as a Network Control TOS.) If you are using TOS, you also will want to have ''utos=y'' in your <code>voter.conf</code> to mark the packets from the network '''TO''' the RTCM/VOTER.


*''GPS Debug'' will print NMEA or TSIP debug strings from the connected GPS.


Any time you make a change to <code>voter.conf</code>, you will need to do a <code>voter reload</code> from the Asterisk console, or restart Asterisk.
*''Fix GPS 1 second off'' this is for NMEA GPS '''only'''. It will add one second to the time.




Now, send a full-quieting, un-modulated signal in to the receiver (no modulating tone). Your transmitter should key.
The way this works is you add together the options you want to enable (it is a bitmask), and set the debug level accordingly.




Pick a value for the ''txctcsslevel'' and put it in <code>voter.conf</code>. Do a <code>voter reload</code> from the Asterisk console, and measure the CTCSS deviation on your service monitor (check your filters on your service monitor, you probably want 300Hz LPF enabled to get an accurate measurement).
For example, if you want to enable GPS Debug and disable IP ToS, set debug to 48.




Continue the process above of adjusting the ''txctcsslevel'', until you get about 500Hz deviation of your CTCSS tone.
If you just want to turn on GPS Debug, set debug to 32.
 
 
= Console Connection =
 
Serial Console access is provided by an RS-232 serial port (J3) at 57600 baud, 8 bits, No parity, 1 Stop Bit. It is also made available remotely (off-board) via TELNET. When TELNET-ing the default user is "admin" and the password is "radios".  


<pre>
VOTER System Serial # 1234 Remote Console Access


Login: admin
If you just want ToS disabled, set debug to 16.
Password: radios


Logged in successfully, now joining console session...
</pre>


Set debug back to 0 to clear all debug settings.


When done with the console session, please use the 'q' command to disconnect. The local serial port and the TELNET (remote) user share the same (and only) console session.


= Related Pages =


= Console Menus =
Documentation on the VOTER/RTCM is extensive, and as such, has been split across multiple pages. They are usually linked, where appropriate, throughout the content. However, here are all the related pages that are available:


For a thorough explanation of the different menus, see the [[VOTER-Menus | VOTER Menus]] page.
*[[VOTER | Main VOTER Page]]
*[[RTCM_Client | RTCM Hardware Documentation]]
*[[VOTER-Menus | Menu Structure and Definitions]]
*[[RTCM_Firmware_upgrading | Firmware Upgrading]]
*[[VOTER-Audio | Audio Interfacing and Configuration]]
*[[VOTER-GPS | GPS Interfacing and Configuration]]
*[[Voter.conf | <code>voter.conf</code> Documentation]]
*[[RTCM_Channel_Driver | <code>chan/voter</code> and Asterisk Console Documentation]]
*[[VOTER-Simulcasting | Simulcasting Configuration]]
*[[VOTER-Buffers | Buffer Tuning]]
*[[Quantar_RTCM | Interfacing to the Motorola Quantar]]

Latest revision as of 18:07, 20 March 2022

Introduction

This is the documentation page to support the through-hole implementation of the VOTER Hardware.



See the VOTER page for more information on the background/history. If you have bought or built a through-hole VOTER, this page is for you. If you have an RTCM, then you will want to reference the manual for the RTCM or our RTCM Client page. That said, most of the information here should be applicable too.


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, as they are primarily a Radio over IP (ROIP) adapter.


Firmware

See the firmware upgrade page for information on upgrading the firmware.


If you are building your own VOTER, or for some reason you need to replace U6, you will want to program in the bootloader in to the dsPIC to allow for remote firmware upgrades. See the Bootloader section on how to do that.


Board Layout

The through-hole board typically looks like this:


Connectors

J1 - 6 pin MTA-100 connector for PIC programmer (PICKit3 or equivalent). A reset switch may be placed across pins 1 and 3.
J2 - Ethernet (10-Base-T).
J3 - RS-232 (console 57600 bps 8N1, DCE)
J4 - 5 pin MTA-100 connector for GPS (see below for pinout).
P1 - Radio Connector (9 pin D-shell Male) (see below for pinout).


P1 - Radio Connector Pinout (DB9 Male)

1 - + VIn (6.5-30 Volts DC).
2 - Transmit Audio Out
3 - Receive (discriminator) Audio In
4 - External CTCSS Input (optional)
5 - Gnd
6 - Gnd
7 - /PTT Out (open-collector, active-low)
8 - Gnd
9 – Gnd


J4 - GPS Connector (5 Pin MTA-100 Male) Pinout

1 - Gnd
2 - 5 Volts DC Out (to power GPS device)
3 - GPS TXD (Gnd, actually)
4 - GPS RXD (in)
5 - GPS PPS (in)


LED Designations

LED designations (shown from right to left along front of VOTER board, see photo above): 

LED1 - (Green) System Activity Indicator (should toggle every 500ms)
LED5 - (Red) Transmit Indicator
LED2 - (Green) Receive Signal Indicator (solid green is valid Rx signal, flashing is signal without CTCSS)
LED3 - (Yellow) GPS Indicator (sold is GPS received and locked, flashing is GPS received, lock in progress)
LED4 - (Yellow) Connection Indicator (indicates that connection was made with VOTER host)


The COS (RX) LED on the VOTER will flash (same rate as Activity LED) if you have External CTCSS enabled, and the received signal has the wrong (or no) valid PL.


Jumpers

JP1  - Discriminator Level Boost
JP2  - 20dB Pad
JP3  - Output Amp Power Source
JP7  - Bootloader Programming
JP8  - Initialize EEPROM
JP9  - Squelch Calibration
JP10 - Diode Calibration
JP11 - LED3/4 Receiver Level Mode


JP1 - Discriminator Level Boost

Insert if low discriminator level. If squelch cannot self-calibrate with JP1 removed (too low), try with JP1 inserted.


Note: this jumper affects the squelch calibration circuit only. Not to be confused with JP2, which is the pad for the receive audio.


JP2 - 20dB Pad

Insert to attenuate discriminator input level by 20db. This pad affects the receive audio level. See the Receive Level Input Calibration section.


JP3 - Output Amp Power Source

Selects power source for output audio amplifier. 1-2 is to power it from the 5VDC power supply. 2-3 is to power it directly from Vin.


DO *NOT* CHANGE THIS JUMPER WITH POWER ON. DAMAGE MAY OCCUR IF YOU DO!!


JP7 - Bootloader Programming

This jumper only needs to be removed when programming the bootloader in the dsPIC using the ICSP header.


JP8 - Initialize EEPROM

Initialize the configuration parameters in EEPROM (factory reset). If JP8 is inserted when firmware starts, the operating parameters in the EEPROM will be set to default values. The system activity LED (LED1, Green) will stay off for approx. 4 seconds, then stay on steady to indicate that the initialization process is complete. Afterwards, the jumper may be removed and the system will continue running as usual.


Note, if JP10 is inserted during this procedure, the "Diode Calibration" process will also occur.


JP9 - Squelch Calibration

Insert to calibrate squelch. See Squelch Calibration below.


JP10 - Diode Calibration

Insert to perform "Diode Calibration". This is a form of temperature compensation, where a power supply voltage is sampled that is dependent on the temperature coefficient of a diode (D5).


This may only be done in conjunction with an EEPROM Initialization (see JP8, above), or a Squelch Calibration (see JP9, above).


JP11 - LED3/4 Receiver Level Mode

Insert this jumper to temporarily re-purpose LED3 and LED4 to allow for visual indication of RX input level (see Rx Level Calibration, below). Alternatively, you can use Menu 97.


Potentiometers

R22 - Squelch adjustment
R36 - Rx Input Level
R61 - Tx Output Level


Initialization

Once you have verified that the firmware is running, place a jumper shunt on JP8 and JP10.


Be sure to do this at a reasonable human room temperature (like 60-80 deg. F). This is necessary because this procedure initializes the operating parameters in the EEPROM and also does a temperature compensation diode calibration, which needs to happen at room temperature.


Once the jumper shunts have been installed, power-cycle the board and wait for the system activity light to come on 'steady' (about 4 seconds or so after the 5 second initial wait time).


Then, remove the jumper shunts, and proceed with Squelch Calibration.


Squelch Calibration and Setting

With the receiver connected and its antenna removed, insert JP9. In the next few seconds the "Receive Signal Indicator" (LED2, green) will flash on and off, then (hopefully) on steady.


This indicates that the squelch calibration has occurred successfully.


If unsuccessful, the LED will flash either fast to indicate that the discriminator noise level is too high, or slowly to indicate that the discriminator noise level is too low. If the discriminator level is too low, try inserting JP1 and try again.


Note: If JP10 is inserted during this procedure, the "Diode Calibration" process will also occur.


If you still have troubles calibrating the squelch, you may need to try the Baseband Examination Window (BEW) firmware.


Once the Squelch Calibration procedure has been performed, the squelch adjustment (R22) needs to be properly set. Make sure that the "External CTCSS" is set to "ignore" (value: 0). 

12 - External CTCSS (0=Ignore, 1=Non-Inverted, 2=Inverted) (0)


Adjust R22 until the Receive Signal Indicator (LED2) is lit. Then, advance R22 clockwise until LED2 is no longer lit. That is the minimum squelch setting. You probably will want to crank it up at least another turn clockwise, because if you leave it there it will open on a REALLY low level signal.


After proper setting has been achieved, return the "External CTCSS" configuration to its original setting.


Menu 98 will show the settings of the Squelch Calibration, Diode Calibration, and Squelch Levels: 

Squelch Noise Gain Value: 45, Diode Cal. Value: 60, SQL Level 675, Hysteresis 10


Note: Firmware >3.00 allows for the option to set the squelch via software, after initially setting it with the hardware potentiometer to get a baseline level. See the Squelch Parameters Menu.

Receive Level Input Calibration

See the VOTER-Audio page for additional considerations when it comes to connecting the VOTER to your receiver, and for level setting instructions.


Place a full-quieting saturated signal on the receiver, modulated by 1000 Hertz sine wave at 3KHz deviation.


With JP11 inserted, LED3 will indicate (by brightness) if the RX level is too low, and LED4 will indicate (by brightness) if the RX level is too high. So the idea is to tune R36 so that there is minimal brightness on both LED3 and LED4 (like a null, more or less).


Alternatively, Menu 97 from the console menu gives a more graphical method of setting the Rx input level: 

RX VOICE DISPLAY:
                                  v -- 3KHz        v -- 5KHz
|=================================>


Again, tune R36 until the input level matches 3kHz (since that is the deviation you are feeding in to the receiver).


Transmit Level Calibration

Transmit output level is adjusted with R63. Transmit Level Calibration is not required for satellite receiver sites, obviously.


See the VOTER-Audio page for considerations when it comes to connecting the transmit audio to your transmitter, and for level setting instructions.


Console Connection

Serial Console access is provided by an RS-232 serial port (J3) at 57600 baud, 8 bits, No parity, 1 Stop Bit. It is also made available remotely (off-board) via TELNET. When TELNET-ing the default user is "admin" and the password is "radios". 

VOTER System Serial # 1234 Remote Console Access

Login: admin
Password: radios

Logged in successfully, now joining console session...


When done with the console session, please use the 'q' command to disconnect. The local serial port and the TELNET (remote) user share the same (and only) console session.


Console Menus

For a thorough explanation of the different menus, see the VOTER Menus page.


Debug Options

The VOTER/RTCM firmware supports some additional debugging information that can be turned on.


From the source code, the different Debug Options are listed as: 

1 - Alt/Main Host change notifications
2 - Ignore HWlock (GGPS only)
4 - GPS/PPS Failure simulation (GGPS only)
8 - POCSAG H/W output disable (GGPS only)
16 - IP TOS Class for Ubiquiti
32 - GPS Debug
64 - Fix GPS 1 second off


Not sure what they all do, but that is what they are. Here are the most common ones used:

  • Alt/Main Host change notifications shows when the connection to the Asterisk server changes state (when configured for redundant servers).
  • IP TOS Class for Ubiquity in firmware >2.00, this disables marking the IP headers from the RTCM/VOTER TO the network with ToS C0/DSCP 48 (UBNT shows this as 802.1p Class 6 (Voice <10mS latency). Other sources show this as a Network Control TOS.) If you are using TOS, you also will want to have utos=y in your voter.conf to mark the packets from the network TO the RTCM/VOTER.
  • GPS Debug will print NMEA or TSIP debug strings from the connected GPS.
  • Fix GPS 1 second off this is for NMEA GPS only. It will add one second to the time.


The way this works is you add together the options you want to enable (it is a bitmask), and set the debug level accordingly.


For example, if you want to enable GPS Debug and disable IP ToS, set debug to 48.


If you just want to turn on GPS Debug, set debug to 32.


If you just want ToS disabled, set debug to 16.


Set debug back to 0 to clear all debug settings.


Related Pages

Documentation on the VOTER/RTCM is extensive, and as such, has been split across multiple pages. They are usually linked, where appropriate, throughout the content. However, here are all the related pages that are available:

Retrieved from "https://wiki.allstarlink.org/index.php?title=VOTER-Hardware&oldid=7157"