RTCM Voting Configuration: Difference between revisions

From WLPS Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
Voting nos permite tener un repetidor con un transmisor de alta potencia a la ves y contar con dos o más receptores periféricos.
Voting nos permite tener un repetidor con un transmisor de alta potencia a la ves y contar con dos o más receptores periféricos.


= Equipos necesarios =
= Hardware needed =


== Sitio Main ==
== Main Site ==


El sitio Main, debe contar con:
The Main Site must be conformed by al least the following hardware:


* Un radio solo para recepción Motorola Pro3100, Pro5100 o Pro7100 o un repetidor MTR2000.
* 01 Duplexer and antenna or double antenna set (Tx/Rx).
* Un radio solo para transmisión Motorola Pro3100, Pro5100 o Pro7100 o un repetidor MTR2000.
* 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Rx).
* Duplexor.
* 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Tx).
* Una tarjeta Micro-Node RTCM.
* 01 Duplexer or double antenna set.
* Un GPS Garmin modelo GPS18x LVC, 5m.
* 01 Micro-Node RTCM board.
* Raspberry Pi modelo 3A o 3B.
* 01 Garmin GPS model GPS18x LVC, 5m.
* Conexión alámbrica a Internet sin doble NAT.
* 01 Raspberry Pi model 2A, 3A or 3B.
* 01 Wired Internet connection with port forwarding capabilities.


== Sitio Cliente ==
== Peer Sites ==


Cada sitio periférico o cliente debe contar con:
Each Peer Site must be conformed by al least the following hardware:


* Un radio solo para recepción Motorola Pro3100, Pro5100 o Pro7100 o MTR2000.
* 01 Antenna (Rx).
* Una tarjeta Micro-Node RTCM.
* 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Rx).
* Un GPS Garmin modelo GPS18x LVC, 5m.
* 01 Micro-Node RTCM board.
* Conexión alámbrica a Internet.
* 01 Garmin GPS model GPS18x LVC, 5m.
* 01 Wired Internet connection with port forwarding capabilities.


== Equipo para ajuste ==
== Tuning Hardware ==


* Monitor de servicio.
* Service monitor.


= Configuración =
= Configuration =


Edita el archivo voter.conf donde 12345 debe ser tu número de nodo y cada línea de Site# define un sitio Main o Cliente. pass# es la contraseña con la cual cada RTCM. Todas deben ser distintas.
Edit the voter.conf where 12345 should be your node number and each Site# will define your Main Site or each Peer Site. pass# is the individual password for each site. It is important to notice that each site must have a different password.


<pre>
<pre>
Line 40: Line 42:


[12345]
[12345]
Site1 = pass1,transmit,master
MainSite0 = pass0,transmit,master
Site2 = pass2,transmit
PeerSite1 = pass1,transmit
Site3 = pass3,transmit
PeerSite2 = pass2,transmit
Site4 = pass4,transmit
PeerSite3 = pass3,transmit
Site5 = pass5,transmit
PeerSite4 = pass4,transmit


# plfilter = n
# plfilter = n
Line 59: Line 61:
= RTCM =
= RTCM =


El usuario por default es '''admin''' y la contraseña es '''radios'''
Log in using telnet, the default user is '''admin''' and the default password is '''radios'''.




Line 85: Line 87:


* TELNET into your VOTER/RTCM and verify the new version is loaded with menu 98:
* TELNET into your VOTER/RTCM and verify the new version is loaded with menu 98:




= GPS =
= GPS =


El GPS debe ir conectado por medio de un DB-15 al RTCM de la siguiente forma:
The GPS should be connected thru the DB-15 port on the RTCM.


{| class="wikitable"
{| class="wikitable"
!colspan="4"| GPS
!colspan="4"| RTCM GPS pinout
|-
|-
| RTCM
| RTCM
| Flujo
| Direction
| Garmin 18x LVC
| Garmin 18x LVC
|-
|-
| 6 GRX
| 6 GRX
| <-- Rx Data
| <-- Rx Data
| Verde
| Green
|-
|-
| 7 GPPS
| 7 GPPS
| <-- Pulse Output
| <-- Pulse Output
| Amarillo
| Yellow
|-
|-
| 8 GND
| 8 GND
| Ground
| Ground
| Negro
| Black (2 cables)
|-
|-
| 13 +5V
| 13 +5V
| V in
| V in
| Rojo
| Red
|-
|-
| 14 GTX
| 14 GTX
| --> Tx Data
| --> Tx Data
| Blanco
| White
| TXD
|-
|}
 
 
= Tuning =
 
Don't disable COR in the RTCM/VOTER... it will cause it to disable the squelch and it will report an RSSI of 255 (full quieting) for all received signals.
 
 
{| class="wikitable"
!colspan="4"| RTCM Settings
|-
| '''Option '''
| '''Parameter '''
| '''Value '''
|-
| 7
| Tx Buffer Length
| 4000
|-
| 8
| GPS Data Protocol
| 0=NMEA
|-
| 9
| GPS Serial Polarity
| 0=Non-Inverted
|-
| 10
| GPS PPS Polarity
| 0=Non-Inverted
|-
| 11
| GPS Baud Rate
| 4800
|-
| 11
| External CTCSS
| 1=Non-Inverted
|-
| 12
| External CTCSS
| 1=Non-Inverted
|-
| 13
| COR Type
| 0=Normal
|-
|-
|}
|}


== Level Settings ==
Setting the audio levels for the RTCM/VOTER is pretty straight forward. Just follow these steps:
* Ensure you have a connection to your host Asterisk server/chan_voter instance
* Send a 1kHz@3kHz on-channel, full-quieting signal in to the repeater's RX
* Set the RX up so it reads 3kHz deviation on the RTCM's built in console meter
* Now set the TX level '''pot''' to get 3kHz out of the transmitter (No PL)
Now change the modulation from 1kHz tone to 800Hz followed by 1.8kHz and verify that the deviation level doesn't change as the tone frequency changes. '''Changing levels indicates a pre/de-emphasis issue.'''
If you are using the built-in "offline repeat" functions, fail the connection to the host Asterisk server, and make sure your repeat audio performs the same as above.
== RX/TX Buffers are NOT Both Millisecond Values ==
You might assume an RX buffer (in voter.conf) of 120ms would be equivalent of a TX buffer (in the RTCM) of 120ms. That is not the case.
The TX buffer is a number of 125 '''microsecond''' intervals, where the RX buffer is in milliseconds.
If you follow the buffer setting instructions, you should be fine, in most cases.





Revision as of 23:57, 13 April 2022

Voting nos permite tener un repetidor con un transmisor de alta potencia a la ves y contar con dos o más receptores periféricos.

Hardware needed

Main Site

The Main Site must be conformed by al least the following hardware:

  • 01 Duplexer and antenna or double antenna set (Tx/Rx).
  • 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Rx).
  • 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Tx).
  • 01 Duplexer or double antenna set.
  • 01 Micro-Node RTCM board.
  • 01 Garmin GPS model GPS18x LVC, 5m.
  • 01 Raspberry Pi model 2A, 3A or 3B.
  • 01 Wired Internet connection with port forwarding capabilities.

Peer Sites

Each Peer Site must be conformed by al least the following hardware:

  • 01 Antenna (Rx).
  • 01 Motorola Pro3100, Pro5100, Pro7100 or MTR2000(Rx).
  • 01 Micro-Node RTCM board.
  • 01 Garmin GPS model GPS18x LVC, 5m.
  • 01 Wired Internet connection with port forwarding capabilities.

Tuning Hardware

  • Service monitor.

Configuration

Edit the voter.conf where 12345 should be your node number and each Site# will define your Main Site or each Peer Site. pass# is the individual password for each site. It is important to notice that each site must have a different password.

[general]
port = 667
buflen = 500
password = BLAH
utos = y

[12345]
MainSite0 = pass0,transmit,master
PeerSite1 = pass1,transmit
PeerSite2 = pass2,transmit
PeerSite3 = pass3,transmit
PeerSite4 = pass4,transmit

# plfilter = n
; txctcss = 100.0
; txctcsslevel = 100
; txtoctype = none

thresholds = 255,110=5
; linger=6
; streams = 12.34.56.78:1667


RTCM

Log in using telnet, the default user is admin and the default password is radios.


Firmware update

The VOTER/RTCM firmware is updated with a Windows program EBLEX C3 Programmer. Download from here. Put both the exe and the ini file in a folder.

If you are upgrading an RTCM be sure to use a .cry file that contains smt in the filename.

If you are upgrading a through-hole VOTER, do not use the smt files.

Save the .cry file in the folder with the .exe and .ini files.

Download the firmware here that is appropriate for your application.

Run the EBLEX Programmer:

  • Fill in the target bootloader IP address (or the public IP, if your RTCM is behind a firewall) of the device.
  • Click File and load the .cry file you are going to program.
  • Click the Capture Target button.
  • Reboot the VOTER/RTCM with TELNET (r option), power cycle, or use the reset button. In a moment you should see text come up on the programmer that it captured the target.
  • Click the Program button.
  • In a few minutes you will see some more messages including a program complete message.
  • Click the Reset LIA button. The VOTER/RTCM will restart with the new firmware.
  • TELNET into your VOTER/RTCM and verify the new version is loaded with menu 98:


GPS

The GPS should be connected thru the DB-15 port on the RTCM.

RTCM GPS pinout
RTCM Direction Garmin 18x LVC
6 GRX <-- Rx Data Green
7 GPPS <-- Pulse Output Yellow
8 GND Ground Black (2 cables)
13 +5V V in Red
14 GTX --> Tx Data White


Tuning

Don't disable COR in the RTCM/VOTER... it will cause it to disable the squelch and it will report an RSSI of 255 (full quieting) for all received signals.


RTCM Settings
Option Parameter Value
7 Tx Buffer Length 4000
8 GPS Data Protocol 0=NMEA
9 GPS Serial Polarity 0=Non-Inverted
10 GPS PPS Polarity 0=Non-Inverted
11 GPS Baud Rate 4800
11 External CTCSS 1=Non-Inverted
12 External CTCSS 1=Non-Inverted
13 COR Type 0=Normal

Level Settings

Setting the audio levels for the RTCM/VOTER is pretty straight forward. Just follow these steps:

  • Ensure you have a connection to your host Asterisk server/chan_voter instance
  • Send a 1kHz@3kHz on-channel, full-quieting signal in to the repeater's RX
  • Set the RX up so it reads 3kHz deviation on the RTCM's built in console meter
  • Now set the TX level pot to get 3kHz out of the transmitter (No PL)

Now change the modulation from 1kHz tone to 800Hz followed by 1.8kHz and verify that the deviation level doesn't change as the tone frequency changes. Changing levels indicates a pre/de-emphasis issue.

If you are using the built-in "offline repeat" functions, fail the connection to the host Asterisk server, and make sure your repeat audio performs the same as above.




RX/TX Buffers are NOT Both Millisecond Values

You might assume an RX buffer (in voter.conf) of 120ms would be equivalent of a TX buffer (in the RTCM) of 120ms. That is not the case.

The TX buffer is a number of 125 microsecond intervals, where the RX buffer is in milliseconds.

If you follow the buffer setting instructions, you should be fine, in most cases.



Regresar a Radioafición en Español