I am involved with a group that wants to transition to RTCM’s, using a single receiver away from the repeater site for now, where the current repeater site will be TX only. One of the features they want is a distinct CT for each receiver, and/or an easy way just by listening to the repeater to get an idea how strong the user’s signal is coming in to any given voting receiver when they start adding them. I have heard repeaters with voter systems do that, but I don’t know enough about any of this stuff to know what is being deployed to make this happen.'As far as I understand it, all the receivers would appear to ASL as a single node with the RTCM Channel Driver configured, so I don’t know how, or if, this kind of configuration would be possible.
I have never used RTCM before, so I am starting from know knowledge on this whatsoever.
I know little of the rtcm, but understand it in basic form.
Someone may chime in with a better idea, but I can share only a couple of ideas on how to get there… You will need to somewhat put your programmers hat on.
ON EVENT programming allows you to make decisions on the fly based on varibles declared and take action.
(see on event programming in the wiki)
Asterisk also has a global variable declaration at the top od extensions.conf
If you use no CT and play sounds (ct’s) based off of RSSI variable, you can simulate this by the event when the user unkeys…
Someone may have worked out something better, so wait for it.
Just a lead to follow if you find none.
Each RTCM does not appear as a single node. The RTCMs appear to the VOTER channel driver as individual “clients”, but are combined into a single node in the channel driver before being presented to Asterisk/app_rpt. Therefore, app_rpt sees a VOTER node as a single radio interface, no differently than a simpleUSB or usbradio interface.
To my knowledge, there is no way to do what you are asking. This would be difficult to implement even if you were to do it - the voted receiver could change a hundred times in the course of a single received transmission when mobile - how would you calculate which CT to send?
Also, there does not seem to be any active development on any of the VOTER stuff and hasn’t been for a while. I don’t think it’s used or even understood enough for anyone to work on it or improve it. I’d like to fork it myself and make some improvements to the channel driver / firmwares, maybe track down some bugs, but the amount of time it would take just to dig through Jim’s thousands on thousands of lines of code and even begin to understand the logic is something I probably won’t have for a long time.
There is a way to do this. With a bit of programming and this python api: asterisk-ami · PyPI , you can access the internal voter data.
On the K8SN repeater, we measure the time each voter is active, then play a CT for the longest active receiver. We also disable the internal CT, and use the python script to manage CT’s.
I never intended to distribute the CTPicker, so it’s a bit of a programming mess. Your welcome to give it a try on your system with a bit of work
Our version includes deciding which Hall voter channel is active on RTCM (if it wins), or which RTCM voter “won” if not the hardware voter RTCM.
