ASL-Corp members, Bureaucrats, Check users, Structured Discussions bots, oversight, Suppressors, Administrators, Upload Wizard campaign editors
1,714
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + Line 8:
Line 10: − Line 19:
Line 20: − − Line 38:
Line 37: − − − − − − − − − − − − − − − − − − − − − Line 111:
Line 89: − Line 118:
Line 95: − Line 124:
Line 100: − − − − − − Line 150:
Line 120: − Line 159:
Line 128: − Line 167:
Line 135: − − Line 189:
Line 155: − − − − − − − − − − − − − − − − − − − − − − Line 268:
Line 212: − − − Line 293:
Line 234: − − − Line 309:
Line 247: − − Line 333:
Line 269: − Line 348:
Line 283: − − Line 359:
Line 292: + + +
no edit summary
[[Category:How to]]
[[Category:Hardware]]
This page discusses interfacing the Motorola Quantar to the RTCM/VOTER interface, for use with AllStar.
This page discusses interfacing the Motorola Quantar to the RTCM/VOTER interface, for use with AllStar.
*Main repeater in a voting system
*Main repeater in a voting system
*Supporting "offline" repeater mode
*Supporting "offline" repeater mode
=Supporting Documentation=
=Supporting Documentation=
*[[Radio_Connections#Quantar | Quantar Connections]] The Quantar section on this site
*[[Radio_Connections#Quantar | Quantar Connections]] The Quantar section on this site
*[[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]
*[[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]
=Firmware=
=Firmware=
==Quantar Firmware==
==Quantar Firmware==
You will want to have newer (ie R020.014.048) firmware in the Station Control Module (SCM). Head on over to [https://wiki.w9cr.net/index.php/Quantar Bryan's site] to download the firmware files. You will also want to get the RSS manual and Service Manual when you are there.
You will want to have newer (ie R020.014.048) firmware in the Station Control Module (SCM). Head on over to [https://wiki.w9cr.net/index.php/Quantar Bryan's site] to download the firmware files. You will also want to get the RSS manual and Service Manual when you are there.
Upgrade the firmware in your SCM and Wireline module, using the instructions in your RSS manual. You should end up with something like this when you go look at the versions screen in the RSS:
Upgrade the firmware in your SCM and Wireline module, using the instructions in your RSS manual. You should end up with something like this when you go look at the versions screen in the RSS:
Note, you will want to update your codeplug too, that is under the Tools --> Codeplug Upgrade menu.
Note, you will want to update your codeplug too, that is under the Tools --> Codeplug Upgrade menu.
The firmware in the Exciter is not automatically upgraded. You will need to do that by burning a 27C512 EPROM, popping the cover off the exciter, and swapping the chip out. You DO want to do this, as there are a number of fixes in later firmware (apparently), especially if you plan on running P25 mixed mode at some point later.
The firmware in the Exciter is not automatically upgraded. You will need to do that by burning a 27C512 EPROM, popping the cover off the exciter, and swapping the chip out. You DO want to do this, as there are a number of fixes in later firmware (apparently), especially if you plan on running P25 mixed mode at some point later.
==RTCM Firmware==
==RTCM Firmware==
The Quantar is special in that the "discriminator" audio isn't really conventional analog discriminator audio as you would normally find in any other radio. The true discriminator audio is filtered through a 6kHz LPF filter, digitized, and then moved around the backplane buss to different cards.
The Quantar is special in that the "discriminator" audio isn't really conventional analog discriminator audio as you would normally find in any other radio. The true discriminator audio is filtered through a 6kHz LPF filter, digitized, and then moved around the backplane buss to different cards.
The RTCM traditionally uses high frequency (above the passband) discriminator audio to do it's RSSI calculations. Since the audio response is limited to <6kHz on the Quantar, this presents a challenge. To combat this, additional code was added to the RTCM firmware called the "DSP/BEW" option. Read about it more on the [[RTCM_Client | RTCM]] page.
The RTCM traditionally uses high frequency (above the passband) discriminator audio to do it's RSSI calculations. Since the audio response is limited to <6kHz on the Quantar, this presents a challenge. To combat this, additional code was added to the RTCM firmware called the "DSP/BEW" option. Read about it more on the [[RTCM_Client | RTCM]] page.
Regardless, you will need to upgrade the firmware in your RTCM (it likely comes with vanilla V1.50 firmware), to use one of the versions with DSP/BEW. Note that due to space constraints, the DSP/BEW firmware is mutually exclusive with the Diagnostics Mode in the RTCM (not enough room for both).
Regardless, you will need to upgrade the firmware in your RTCM (it likely comes with vanilla V1.50 firmware), to use one of the versions with DSP/BEW. Note that due to space constraints, the DSP/BEW firmware is mutually exclusive with the Diagnostics Mode in the RTCM (not enough room for both).
You will also likely want to install the version with "Chuck" squelch... this is really a buffer overflow fix that makes the squelch reporting behave a bit better.
You will also likely want to install the version with "Chuck" squelch... this is really a buffer overflow fix that makes the squelch reporting behave a bit better.
The RTCM needs the "smt" version files, the VOTER uses the non-smt version files.
The RTCM needs the "smt" version files, the VOTER uses the non-smt version files.
Firmware is available at [https://github.com/AllStarLink/voter/tree/master/board-firmware Github]. Instructions and the other utility needed are all listed on the [[RTCM_Client | RTCM]] page.
Firmware is available at [https://github.com/AllStarLink/voter/tree/master/board-firmware Github]. Instructions and the other utility needed are all listed on the [[RTCM_Client | RTCM]] page.
=Wiring/Connections=
=Wiring/Connections=
A good primer on the connections available on the backplane can be found over on [http://www.repeater-builder.com/motorola/quantar/q-interfacing/quantar-interfacing.html Repeater Builder], or dig through the various manuals.
A good primer on the connections available on the backplane can be found over on [http://www.repeater-builder.com/motorola/quantar/q-interfacing/quantar-interfacing.html Repeater Builder], or dig through the various manuals.
It is best to use the "Telco" connector, J17, to make the interface cable. This requires a 50-pin MALE Amphenol connector and 90 degree hood. Carefully solder the connections if you have to, or find your local communications installer buddy with an Amphenol "butterfly" tool to crimp one for you.
It is best to use the "Telco" connector, J17, to make the interface cable. This requires a 50-pin MALE Amphenol connector and 90 degree hood. Carefully solder the connections if you have to, or find your local communications installer buddy with an Amphenol "butterfly" tool to crimp one for you.
A good cable to use is this one:
A good cable to use is this one:
[[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]
[[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]
There are a couple minor notes when using this cable. The connection to Pins 26/27 are not required (those are Line 1- and Line 2-, which aren't used), instead, connect Pin 43 (RDSTAT-) to Pin 32 (GND).
There are a couple minor notes when using this cable. The connection to Pins 26/27 are not required (those are Line 1- and Line 2-, which aren't used), instead, connect Pin 43 (RDSTAT-) to Pin 32 (GND).
In reality, if you are using the RTCM to do squelch (which you should be), then the RDSTAT connection isn't even necessary.
In reality, if you are using the RTCM to do squelch (which you should be), then the RDSTAT connection isn't even necessary.
Build the necessary breakout cable for the DB15 to split out the serial console, and the connections to your GPS. Note that you will need to configure JP4 and JP5 inside the RTCM for TTL/RS-232, as required. '''Be aware''' the label on the RTCM is misleading, you want to use the GTX Pin (14) for data '''from''' your GPS '''to''' the RTCM. The GRX (data '''from''' the RTCM '''to''' the GPS is not required, as it is not used).
Build the necessary breakout cable for the DB15 to split out the serial console, and the connections to your GPS. Note that you will need to configure JP4 and JP5 inside the RTCM for TTL/RS-232, as required. '''Be aware''' the label on the RTCM is misleading, you want to use the GTX Pin (14) for data '''from''' your GPS '''to''' the RTCM. The GRX (data '''from''' the RTCM '''to''' the GPS is not required, as it is not used).
=Quantar Audio=
=Quantar Audio=
The biggest headache in the Quantar is audio.
The biggest headache in the Quantar is audio.
As mentioned above, you don't get "true" discriminator audio out of the shelf, but you do get a reasonable facsimile.
As mentioned above, you don't get "true" discriminator audio out of the shelf, but you do get a reasonable facsimile.
If you go dig DEEP in the Quantar Digital-Capable Station Instruction manual, p/n 6881095E05, (on [http://www.repeater-builder.com/motorola/quantar/quantar-index.html Repeater Builder]), and dive in to [http://www.repeater-builder.com/motorola/quantar/qim/part-14-station-configuration.pdf Part 14 - Station Configuration], you will find a section called "Fast Keyup Feature".
If you go dig DEEP in the Quantar Digital-Capable Station Instruction manual, p/n 6881095E05, (on [http://www.repeater-builder.com/motorola/quantar/quantar-index.html Repeater Builder]), and dive in to [http://www.repeater-builder.com/motorola/quantar/qim/part-14-station-configuration.pdf Part 14 - Station Configuration], you will find a section called "Fast Keyup Feature".
This is where it talks about using Pins 5 and 30 on J17 to get audio in and out of the station, using the "Splatter Filter Connection Configuration". It also talks about using Pin 23 on the MRTI connector for PTT, but ignore that, we'll use the EXT PTT input on J17 instead.
This is where it talks about using Pins 5 and 30 on J17 to get audio in and out of the station, using the "Splatter Filter Connection Configuration". It also talks about using Pin 23 on the MRTI connector for PTT, but ignore that, we'll use the EXT PTT input on J17 instead.
Note that the actual "Fast Keyup" feature only shows up in the RSS if you enable WildCard=Enhanced, then it shows up on the RF Configuration screen.
Note that the actual "Fast Keyup" feature only shows up in the RSS if you enable WildCard=Enhanced, then it shows up on the RF Configuration screen.
The audio that shows up on J17 30, J14 7, and J14 22 is all the same. They are also all gated audio. You can't get un-squelched (ie open discriminator) audio unless you either configure the station for Un-squelched Audio on the Channel Information screen, or program the WildCard. Also know that if the WildCard is not programmed, you will not get ANY audio out on the back, unless you turn on the Phone Patch option.
The audio that shows up on J17 30, J14 7, and J14 22 is all the same. They are also all gated audio. You can't get un-squelched (ie open discriminator) audio unless you either configure the station for Un-squelched Audio on the Channel Information screen, or program the WildCard. Also know that if the WildCard is not programmed, you will not get ANY audio out on the back, unless you turn on the Phone Patch option.
We are going to do all the pre-emphasis and de-emphasis in the RTCM/AllStar, so we want to make sure to disable any audio filtering on the channel inside the Quantar. If you don't your audio is going to sound like garbage.
We are going to do all the pre-emphasis and de-emphasis in the RTCM/AllStar, so we want to make sure to disable any audio filtering on the channel inside the Quantar. If you don't your audio is going to sound like garbage.
==Important Audio RSS Settings==
==Important Audio RSS Settings==
*WildCard: Enhanced
*WildCard: Enhanced
*Phone Patch Interface: Disabled
*Phone Patch Interface: Disabled
'''Channel Information Basic'''
'''Channel Information Basic'''
*Analog Rptr Hold-In: OFF
*Analog Rptr Hold-In: OFF
*Analog Rptr Access: NONE
*Analog Rptr Access: NONE
'''Channel Information Advanced'''
'''Channel Information Advanced'''
*De-emphasis: DISABLED
*De-emphasis: DISABLED
*High-Pass Filter: DISABLED
*High-Pass Filter: DISABLED
'''RF Configuration'''
'''RF Configuration'''
Repeater Operation: BASE
Repeater Operation: BASE
==WildCard Programming==
==WildCard Programming==
This is how you actually get the audio and logic to work. Without this, you can get audio out of the shelf using other configurations, but you can't key or or get modulation in.
This is how you actually get the audio and logic to work. Without this, you can get audio out of the shelf using other configurations, but you can't key or or get modulation in.
The WildCard Input and Output screens should be fine at defaults. Just make sure that Aux Input 9 is set for LO (this is our PTT).
The WildCard Input and Output screens should be fine at defaults. Just make sure that Aux Input 9 is set for LO (this is our PTT).
The important configuration is in the WildCard Tables.
The important configuration is in the WildCard Tables.
Delete any existing WildCard Tables, you are going to create two new ones. Configure them as shown below:
Delete any existing WildCard Tables, you are going to create two new ones. Configure them as shown below:
This is the important one to actually turn on the discriminator audio output on the backplane when the station boots/reboots:
This is the important one to actually turn on the discriminator audio output on the backplane when the station boots/reboots:
Inaction: NULL
Inaction: NULL
</pre>
</pre>
This is how we allow external PTT, and gate the AUX TX audio from Pin 5 to the Exciter:
This is how we allow external PTT, and gate the AUX TX audio from Pin 5 to the Exciter:
Inaction: KEY FROM WL; AUXTX-TX ON
Inaction: KEY FROM WL; AUXTX-TX ON
</pre>
</pre>
=AllStar (Asterisk) Configuration=
=AllStar (Asterisk) Configuration=
rxchannel=voter/<nodenumber>
rxchannel=voter/<nodenumber>
</pre>
</pre>
The rest of the configuration is done in voter.conf. We won't go in to all the details on the options here, but will go through some basic settings to get on the air and levels lined up.
The rest of the configuration is done in voter.conf. We won't go in to all the details on the options here, but will go through some basic settings to get on the air and levels lined up.
You are going to want to start with something basic in voter.conf like:
You are going to want to start with something basic in voter.conf like:
txtoctype = phase ; the type of "reverse burst" to send when de-keying
txtoctype = phase ; the type of "reverse burst" to send when de-keying
</pre>
</pre>
That takes care of the basic settings required in AllStar. During the audio alignment, the txctcsslevel will be adjusted for the correct deviation.
That takes care of the basic settings required in AllStar. During the audio alignment, the txctcsslevel will be adjusted for the correct deviation.
=RTCM/VOTER Configuration=
=RTCM/VOTER Configuration=
There is lots of stuff to configure in the RTCM too. You will want to establish a serial console connection (through the DB15), using 57600/8N1.
There is lots of stuff to configure in the RTCM too. You will want to establish a serial console connection (through the DB15), using 57600/8N1.
'''Remember to Save Values to EEPROM (99) and Reboot (r) when you make changes, or you will have unpredictable results'''. Some changes are immediate, but many are not, and will confuse you when things you expect to happen, don't.
'''Remember to Save Values to EEPROM (99) and Reboot (r) when you make changes, or you will have unpredictable results'''. Some changes are immediate, but many are not, and will confuse you when things you expect to happen, don't.
Start with the IP Parameters Menu. This should be all straight forward. This will get your RTCM on the network.
Start with the IP Parameters Menu. This should be all straight forward. This will get your RTCM on the network.
Back on the Main Menu, you will want to make sure your VOTER Server Address, Port, and Passwords are set. See the notes above about which password is which. You will also need to configure your GPS settings. Make sure to set the jumpers inside the RTCM for RS-232 or TTL, as needed. You may need to play with the GPS Serial Polarity and GPS PPS Polarity until you get data flowing.
Back on the Main Menu, you will want to make sure your VOTER Server Address, Port, and Passwords are set. See the notes above about which password is which. You will also need to configure your GPS settings. Make sure to set the jumpers inside the RTCM for RS-232 or TTL, as needed. You may need to play with the GPS Serial Polarity and GPS PPS Polarity until you get data flowing.
If you set the Debug Level to 32, you will know right away if you are getting GPS data in to the RTCM, as this setting will print the NMEA or TSIP strings being received. This is an immediate setting, no need to save and reboot. '''Set the Debug Level to 16 for normal operation, this marks the packets from the RTCM towards AllStar with TOS bits'''.
If you set the Debug Level to 32, you will know right away if you are getting GPS data in to the RTCM, as this setting will print the NMEA or TSIP strings being received. This is an immediate setting, no need to save and reboot. '''Set the Debug Level to 16 for normal operation, this marks the packets from the RTCM towards AllStar with TOS bits'''.
We want External CTCSS set to Ignore (this is where the RDSTAT would be connected, but we are not using that).
We want External CTCSS set to Ignore (this is where the RDSTAT would be connected, but we are not using that).
We want COR Type set to Normal. This is an important setting, as it also determines whether de-emphasis takes place, or not. See [[RTCM_Client#Receiver_De-emphasis|here]] for an explanation of how that works.
We want COR Type set to Normal. This is an important setting, as it also determines whether de-emphasis takes place, or not. See [[RTCM_Client#Receiver_De-emphasis|here]] for an explanation of how that works.
We want DSP/BEW Mode set to 1 to enable it. See [[RTCM_Client#DSP.2FBEW_Firmware_Version|here]] for a reminder of what this is.
We want DSP/BEW Mode set to 1 to enable it. See [[RTCM_Client#DSP.2FBEW_Firmware_Version|here]] for a reminder of what this is.
Finally, we will configure the Offline Mode Parameters Menu.
Finally, we will configure the Offline Mode Parameters Menu.
We want to fail over to repeater mode, if we lose connection to the host, so set Offline Mode to 3.
We want to fail over to repeater mode, if we lose connection to the host, so set Offline Mode to 3.
The CW "Offline" setting is what the RTCM will send when it goes in to offline mode, the repeater callsign should go here.
The CW "Offline" setting is what the RTCM will send when it goes in to offline mode, the repeater callsign should go here.
The "Offline" (CW ID) Period Time is how often the repeater will ID in offline mode, set to 18000 to ID every 30 minutes.
The "Offline" (CW ID) Period Time is how often the repeater will ID in offline mode, set to 18000 to ID every 30 minutes.
Set the Offline CTCSS Tone for 100.0Hz (or your desired TX PL tone). You will want this to be the same as you set in voter.conf.
Set the Offline CTCSS Tone for 100.0Hz (or your desired TX PL tone). You will want this to be the same as you set in voter.conf.
Leave the Offline CTCSS Level, for now, it will be adjusted later.
Leave the Offline CTCSS Level, for now, it will be adjusted later.
Set the Offline De-Emphasis Override to 1 (OVERRIDE). 1 is the correct setting for this application.
Set the Offline De-Emphasis Override to 1 (OVERRIDE). 1 is the correct setting for this application.
That should be it for software configuration, remember to save and reboot the RTCM.
That should be it for software configuration, remember to save and reboot the RTCM.
For hardware settings, in the RTCM you will want to make sure that JP1 is IN and JP2 is OUT. When you do the squelch calibration, the RTCM should calibrate in about 4-6 blinks, instead of around 12. The Squelch Noise Gain Value should be around 43 (versus 93). JP3 can remain at 1-2, as there is plenty of audio drive by default.
For hardware settings, in the RTCM you will want to make sure that JP1 is IN and JP2 is OUT. When you do the squelch calibration, the RTCM should calibrate in about 4-6 blinks, instead of around 12. The Squelch Noise Gain Value should be around 43 (versus 93). JP3 can remain at 1-2, as there is plenty of audio drive by default.
=Alignment=
=Alignment=
This section is based on using an HP8920 (HP8921) for alignment. Other test sets will differ. You '''must''' use a test set to properly tune the system... no "doing it by ear".
This section is based on using an HP8920 (HP8921) for alignment. Other test sets will differ. You '''must''' use a test set to properly tune the system... no "doing it by ear".
==Prerequisites==
==Prerequisites==
With the configuration above, you should have GPS lock, and the RTCM should be connected to the AllStar Host.
With the configuration above, you should have GPS lock, and the RTCM should be connected to the AllStar Host.
You should have already tuned the pre-selector on the receiver in the station. If not, follow the instructions in the manuals. Pro tip, with the station powered on, look in to the receive port with your return loss bridge, and tune for a null (best match).
You should have already tuned the pre-selector on the receiver in the station. If not, follow the instructions in the manuals. Pro tip, with the station powered on, look in to the receive port with your return loss bridge, and tune for a null (best match).
Do the squelch and diode calibration on the RTCM:
Do the squelch and diode calibration on the RTCM:
*Turn off DIP switches 2 and 3. The RTCM should reset. Confirm on the status screen (98) that the Squelch Noise Gain Value is around 43, and the Diode Cal. Value is around 39.
*Turn off DIP switches 2 and 3. The RTCM should reset. Confirm on the status screen (98) that the Squelch Noise Gain Value is around 43, and the Diode Cal. Value is around 39.
Set up your test set for Duplex Test.
Set up your test set for Duplex Test.
Connect the RF IN/OUT to the Exciter output. Connect the Duplex Out to the Receiver input.
Connect the RF IN/OUT to the Exciter output. Connect the Duplex Out to the Receiver input.
Duplex Screen Settings:
Duplex Screen Settings:
SINAD meter changed to AF Freq meter
SINAD meter changed to AF Freq meter
</pre>
</pre>
Confirm that when you turn on the RF Gen, the station keys, and you should get audio demodulating on the test set as audio goes through the AllStar host and back out. If not, troubleshoot your AllStar configuration, check your RSS settings, wiring, etc.
Confirm that when you turn on the RF Gen, the station keys, and you should get audio demodulating on the test set as audio goes through the AllStar host and back out. If not, troubleshoot your AllStar configuration, check your RSS settings, wiring, etc.
==AllStar (Asterisk) Alignment==
==AllStar (Asterisk) Alignment==
As mentioned above, we are starting by sending audio through the AllStar host.
As mentioned above, we are starting by sending audio through the AllStar host.
*Send 1kHz @ 3kHz on-channel in to the receiver
*Send 1kHz @ 3kHz on-channel in to the receiver
*Adjust the TX pot on the RTCM for 3kHz measured transmitter deviation on the test set
*Adjust the TX pot on the RTCM for 3kHz measured transmitter deviation on the test set
Sweep the AFGen1 Freq up and down from 1kHz, leaving the deviation at 3kHz, and observe that the transmitter deviation remains around 3kHz between 400-3kHz. The Quantar has pretty sharp filters, so you will see the deviation drop off below 400Hz (very sharply below 300Hz), and it will start to roll off slowly around 1.9kHz (measures around 2.7kHz deviation), but will drop sharply at 3kHz. If the deviation rolls off wildly, you have a setting wrong somewhere, either in the Channel Information in the RSS, or you didn't set the CTCSS tone and a level of 0 in voter.conf.
Sweep the AFGen1 Freq up and down from 1kHz, leaving the deviation at 3kHz, and observe that the transmitter deviation remains around 3kHz between 400-3kHz. The Quantar has pretty sharp filters, so you will see the deviation drop off below 400Hz (very sharply below 300Hz), and it will start to roll off slowly around 1.9kHz (measures around 2.7kHz deviation), but will drop sharply at 3kHz. If the deviation rolls off wildly, you have a setting wrong somewhere, either in the Channel Information in the RSS, or you didn't set the CTCSS tone and a level of 0 in voter.conf.
De-key the station (turn off the RF Gen), and disconnect the GPS to force the RTCM in to offline mode. Temporarily set the CTCSS tone to 0.0Hz, save and reboot.
De-key the station (turn off the RF Gen), and disconnect the GPS to force the RTCM in to offline mode. Temporarily set the CTCSS tone to 0.0Hz, save and reboot.
*De-key the station, save and reboot the RTCM with the final setting
*De-key the station, save and reboot the RTCM with the final setting
Lastly, we will set the PL deviation from the AllStar host. Restore the GPS connection to the RTCM, and ensure it locks and connects back to the host. The test set should still have the 1kHz modulation turned off, and filters set up to measure PL deviation.
Lastly, we will set the PL deviation from the AllStar host. Restore the GPS connection to the RTCM, and ensure it locks and connects back to the host. The test set should still have the 1kHz modulation turned off, and filters set up to measure PL deviation.
*Turn on the plfilter option in voter.conf (if desired), to filter out user's PL tones, if they are transmitting one
*Turn on the plfilter option in voter.conf (if desired), to filter out user's PL tones, if they are transmitting one
Finally, with nothing connected to the receiver (or probably better, with the station antenna connected to pick up all the site noise), turn the SQL pot on the RTCM CCW until the squelch opens. Then, turn the pot about 5 turns CW to tighten the squelch. Adjust as desired from there, you can note the squelch level setting in the Status Menu (98).
Finally, with nothing connected to the receiver (or probably better, with the station antenna connected to pick up all the site noise), turn the SQL pot on the RTCM CCW until the squelch opens. Then, turn the pot about 5 turns CW to tighten the squelch. Adjust as desired from there, you can note the squelch level setting in the Status Menu (98).
=Conclusion=
=Conclusion=
Once you get everything installed, the final thing you will need to do is configure all the buffer settings. See [[RTCM_Client#Setting_Voter_Buffers|setting buffers]] on the process to do that.
Once you get everything installed, the final thing you will need to do is configure all the buffer settings. See [[RTCM_Client#Setting_Voter_Buffers|setting buffers]] on the process to do that.
=Further reading=
For further reading on the Motorola Quantar visit [https://wiki.w9cr.net/index.php/Quantar W9CR's Motorola Quantar Page]