non-USA-standard repeater offset for freq-agile radios
I have added (still experimental) code in app_rpt version 0.211 (available this evening in SVN) to attempt to support non-USA-standard repeater offsets for frequency agile radios. I have tested the code on a TMG-707A, but not on any of the other models supported, which are TM-271, TM-D700, FT-897 and IC-706. The other radios did not seem to support such functionality. There are 2 ways of configuring this: the new rpt.conf parameters (that go into the node clause in rpt.conf), are split2m and split70cm, which specify the default offset for 2 meters and 70 centimeters in kilohertz. split2m = 600 split70cm = 5000 You may also specify the offset in a memory channel by adding an additional parameter before the options, for example: 01 = 147.435,103.5,1035,h-t ; This would be for W6NUT in Los Angeles with input of 146.40 JIM WB6NIL
It would appear to work on the TM-271a Thanks, Scott KB2EAR ----- Original Message ----- From: Jim Duuuude To: dg8ngn@googlemail.com ; app_rpt mailing list Sent: Thursday, March 25, 2010 8:06 PM Subject: [App_rpt-users] non-USA-standard repeater offset for freq-agileradios I have added (still experimental) code in app_rpt version 0.211 (available this evening in SVN) to attempt to support non-USA-standard repeater offsets for frequency agile radios. I have tested the code on a TMG-707A, but not on any of the other models supported, which are TM-271, TM-D700, FT-897 and IC-706. The other radios did not seem to support such functionality. There are 2 ways of configuring this: the new rpt.conf parameters (that go into the node clause in rpt.conf), are split2m and split70cm, which specify the default offset for 2 meters and 70 centimeters in kilohertz. split2m = 600 split70cm = 5000 You may also specify the offset in a memory channel by adding an additional parameter before the options, for example: 01 = 147.435,103.5,1035,h-t ; This would be for W6NUT in Los Angeles with input of 146.40 JIM WB6NIL ------------------------------------------------------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
yea!!!!!! And there was much rejoicing!!! Thanks for letting me know. JIM From: kb2ear@kb2ear.net To: telesistant@hotmail.com; dg8ngn@googlemail.com; app_rpt-users@qrvc.com Subject: Re: [App_rpt-users] non-USA-standard repeater offset for freq-agileradios Date: Thu, 25 Mar 2010 23:26:09 -0400 It would appear to work on the TM-271a Thanks, Scott KB2EAR ----- Original Message ----- From: Jim Duuuude To: dg8ngn@googlemail.com ; app_rpt mailing list Sent: Thursday, March 25, 2010 8:06 PM Subject: [App_rpt-users] non-USA-standard repeater offset for freq-agileradios I have added (still experimental) code in app_rpt version 0.211 (available this evening in SVN) to attempt to support non-USA-standard repeater offsets for frequency agile radios. I have tested the code on a TMG-707A, but not on any of the other models supported, which are TM-271, TM-D700, FT-897 and IC-706. The other radios did not seem to support such functionality. There are 2 ways of configuring this: the new rpt.conf parameters (that go into the node clause in rpt.conf), are split2m and split70cm, which specify the default offset for 2 meters and 70 centimeters in kilohertz. split2m = 600 split70cm = 5000 You may also specify the offset in a memory channel by adding an additional parameter before the options, for example: 01 = 147.435,103.5,1035,h-t ; This would be for W6NUT in Los Angeles with input of 146.40 JIM WB6NIL _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Hi Jim, it doesn't work here on my system. Revision 576 was OK, but 587 will not work with my tmd700. After a login using iaxRpt I will get "invalid frequency" (voice). rpt.conf: [2595] rxchannel = Radio/usb ioport = /dev/ttyS1 remote = tmd700 split2m = 600 split70cm = 7600 [memory] 00 = 144.675,71.9,h 01 = 439.250,71.9,l- 02 = 438.625,71.9,l- 03 = 438.775,71.9,l- 04 = 436.650,71.9,l- I tried to uncomment "split2m" and "split70cm", but it didn't work. 73, Jann
Has anyone figured out how to show a real-time monitor of which connected nodes are talking at any particular time? I have to imagine there is some way to do this. The data seems to be there given the node has the ability to report the exact time each connected node transmitted. Any clues would be helpful. Thanks, Steve
For scripting? I just make a script call for this: asterisk -rx "rpt stats 27099" which will show you the status, replace node 27099 with your node number. On Thu, 1 Apr 2010, Steve Passmore wrote:
Has anyone figured out how to show a real-time monitor of which connected nodes are talking at any particular time? I have to imagine there is some way to do this. The data seems to be there given the node has the ability to report the exact time each connected node transmitted. Any clues would be helpful.
Thanks, Steve _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
participants (5)
-
Jann Traschewski -
Jim Duuuude -
ke6sth＠ke6sth.ampr.org -
Scott Weis -
Steve Passmore