Hi Jim and all; Running app_rpt v0.287 (full duplex); when I issue a DTMF command to re-enable the repeater (from it's disabled cop 3 state), the repeater keys up, we hear Alison announce 'RPT ENA' and then the PTT remains keyed. I have to send a '*0' to get the PTT to drop. This is on a system that I just rebuilt recently. AFAIK, this problem did not exist with an earlier version of app_rpt (sorry, I can't be more specific than that!). Wonder if this is a bug or something that I am missing from my config file, etc? Cheers! Ramesh. www.freestar.us
I have been meaning to bring this up as well, but I have a little different scenario. I have a macro that runs the following: Cop 33, *71, then a series of node connects and then COP 34 If this is performed on the RF side, the CLI verbose output shows a stuck RX carrier. (I use PL decode via discriminator) All that is needed is a onetime quick PTT on the input and it clears. Seems as it gets back into sync. If I issue the macro via CLI I don't get this issue. It happens to all of my nodes and it is pretty consistent. -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Saturday, October 29, 2011 9:20 PM To: app_rpt Subject: [App_rpt-users] cop 2 - causing PTT lock Hi Jim and all; Running app_rpt v0.287 (full duplex); when I issue a DTMF command to re-enable the repeater (from it's disabled cop 3 state), the repeater keys up, we hear Alison announce 'RPT ENA' and then the PTT remains keyed. I have to send a '*0' to get the PTT to drop. This is on a system that I just rebuilt recently. AFAIK, this problem did not exist with an earlier version of app_rpt (sorry, I can't be more specific than that!). Wonder if this is a bug or something that I am missing from my config file, etc? Cheers! Ramesh. www.freestar.us _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Hi Lu; I believe that I tried the PTT trick as well - I don't even get a courtesy tone. I will check the CLI tomorrow morning. Cheers! Ramesh. Sent on the TELUS Mobility network with BlackBerry -----Original Message----- From: "Lu Vencl" <vencl@att.net> Date: Sat, 29 Oct 2011 21:35:11 To: 'Ramesh Dhami \(VA3UV\)'<Ramesh@va3uv.com>; 'app_rpt'<app_rpt-users@ohnosec.org> Subject: RE: [App_rpt-users] cop 2 - causing PTT lock I have been meaning to bring this up as well, but I have a little different scenario. I have a macro that runs the following: Cop 33, *71, then a series of node connects and then COP 34 If this is performed on the RF side, the CLI verbose output shows a stuck RX carrier. (I use PL decode via discriminator) All that is needed is a onetime quick PTT on the input and it clears. Seems as it gets back into sync. If I issue the macro via CLI I don't get this issue. It happens to all of my nodes and it is pretty consistent. -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Saturday, October 29, 2011 9:20 PM To: app_rpt Subject: [App_rpt-users] cop 2 - causing PTT lock Hi Jim and all; Running app_rpt v0.287 (full duplex); when I issue a DTMF command to re-enable the repeater (from it's disabled cop 3 state), the repeater keys up, we hear Alison announce 'RPT ENA' and then the PTT remains keyed. I have to send a '*0' to get the PTT to drop. This is on a system that I just rebuilt recently. AFAIK, this problem did not exist with an earlier version of app_rpt (sorry, I can't be more specific than that!). Wonder if this is a bug or something that I am missing from my config file, etc? Cheers! Ramesh. www.freestar.us _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
When you do "rpt showvars xxxx" does it show RPT_RXKEYED=0 or 1? I've seen this if the levels/squelch setting not being right, lower noise being received signal, etc. GeorgeC W2DB ----- Original Message ----- From: "Lu Vencl" <vencl@att.net> To: "'Ramesh Dhami (VA3UV)'" <Ramesh@va3uv.com>; "'app_rpt'" <app_rpt-users@ohnosec.org> Sent: Saturday, October 29, 2011 8:35 PM Subject: Re: [App_rpt-users] cop 2 - causing PTT lock
I have been meaning to bring this up as well, but I have a little different scenario. I have a macro that runs the following: Cop 33, *71, then a series of node connects and then COP 34 If this is performed on the RF side, the CLI verbose output shows a stuck RX carrier. (I use PL decode via discriminator) All that is needed is a onetime quick PTT on the input and it clears. Seems as it gets back into sync. If I issue the macro via CLI I don't get this issue. It happens to all of my nodes and it is pretty consistent.
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Saturday, October 29, 2011 9:20 PM To: app_rpt Subject: [App_rpt-users] cop 2 - causing PTT lock
Hi Jim and all;
Running app_rpt v0.287 (full duplex); when I issue a DTMF command to re-enable the repeater (from it's disabled cop 3 state), the repeater keys up, we hear Alison announce 'RPT ENA' and then the PTT remains keyed. I have to send a '*0' to get the PTT to drop.
This is on a system that I just rebuilt recently. AFAIK, this problem did not exist with an earlier version of app_rpt (sorry, I can't be more specific than that!).
Wonder if this is a bug or something that I am missing from my config file, etc?
Cheers!
Ramesh.
www.freestar.us
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 30/10/2011 12:01 AM, George Csahanin wrote:
When you do "rpt showvars xxxx" does it show RPT_RXKEYED=0 or 1?
I've seen this if the levels/squelch setting not being right, lower noise being received signal, etc.
<-- Hi George and all: Tried my COP2 (dtmf command) via the CLI and as Lu mentioned, that works fine, as soon as I hear RPT ENA, the PTT drops and life is good. Then I disabled the repeater and tried the dtmf command from my HT - this is what I captured on CLI: [Oct 30 07:41:31] NOTICE[19419]: app_rpt.c:7957 wait_interval: Delay complete -- <Zap/pseudo-475079875> Playing 'letters/r' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/p' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/t' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/e' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/n' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/a' (language 'en') -- Hungup 'Zap/pseudo-475079875' [Oct 30 07:41:46] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1423219721' [Oct 30 07:41:49] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1492162812' [Oct 30 07:41:52] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-13915100' [Oct 30 07:41:55] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-971235839' [Oct 30 07:42:04] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char * duration 127 ms [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 0 duration 84 ms [Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:4288 cancel_pfxtone: cancel_pfxfone!![Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:10544 rpt_call: exit channel loop -- Hungup 'Zap/pseudo-895837731' [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 -- Hungup 'Zap/pseudo-2118062105' va3pmo_asterisk*CLI> Notice how I tried to key-up a few times - and no joy. Further even the end, when I sent a *0; app_rpt tells me: nowchan=00, waschan=00 So it believes that the ptt was actually off to start with. So OK, now I will bump the squelch up a bit... (Current setting was 450 with a signal level of 140) - the squelch is already kinda' high (I think?) - anyway, I bumped the squelch up to 500 - tried again and voila! - problem solved :) As soon as I finished sending the dtmf and dropped ptt on my HT, I heard the courtesy tone come back and knew instantly that this was going to work! So that's it - my dual mode DV and FM repeater is ready!!! ;P). Thanks!!! Ramesh. www.freestar.us
----- Original Message ----- From: "Ramesh Dhami (VA3UV)" <Ramesh@va3uv.com> To: "'app_rpt'" <app_rpt-users@ohnosec.org> Sent: Sunday, October 30, 2011 6:51 AM Subject: Re: [App_rpt-users] cop 2 - causing PTT lock
On 30/10/2011 12:01 AM, George Csahanin wrote:
When you do "rpt showvars xxxx" does it show RPT_RXKEYED=0 or 1?
I've seen this if the levels/squelch setting not being right, lower noise being received signal, etc.
<-- Hi George and all:
Tried my COP2 (dtmf command) via the CLI and as Lu mentioned, that works fine, as soon as I hear RPT ENA, the PTT drops and life is good.
Then I disabled the repeater and tried the dtmf command from my HT - this is what I captured on CLI:
[Oct 30 07:41:31] NOTICE[19419]: app_rpt.c:7957 wait_interval: Delay complete -- <Zap/pseudo-475079875> Playing 'letters/r' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/p' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/t' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/e' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/n' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/a' (language 'en') -- Hungup 'Zap/pseudo-475079875' [Oct 30 07:41:46] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1423219721' [Oct 30 07:41:49] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1492162812' [Oct 30 07:41:52] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-13915100' [Oct 30 07:41:55] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-971235839' [Oct 30 07:42:04] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char * duration 127 ms [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 0 duration 84 ms [Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:4288 cancel_pfxtone: cancel_pfxfone!![Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:10544 rpt_call: exit channel loop -- Hungup 'Zap/pseudo-895837731' [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 -- Hungup 'Zap/pseudo-2118062105' va3pmo_asterisk*CLI>
Notice how I tried to key-up a few times - and no joy. Further even the end, when I sent a *0; app_rpt tells me:
nowchan=00, waschan=00
So it believes that the ptt was actually off to start with.
So OK, now I will bump the squelch up a bit...
(Current setting was 450 with a signal level of 140) - the squelch is already kinda' high (I think?) - anyway, I bumped the squelch up to 500 - tried again and voila! - problem solved :)
As soon as I finished sending the dtmf and dropped ptt on my HT, I heard the courtesy tone come back and knew instantly that this was going to work!
So that's it - my dual mode DV and FM repeater is ready!!! ;P).
Thanks!!!
Ramesh.
www.freestar.us
Squelch at 450 and signal 150? Yeah, that's REAL tight. But the 150 seems like the audio noise level into the CM108 is possibly too high. I've never seen it that high( backwards to what may be thought...lower signal level number = higher number, as rx quiets with signal that level number goes up) GeorgeC
On 30/10/2011 12:34 PM, George Csahanin wrote:
Squelch at 450 and signal 150? Yeah, that's REAL tight. But the 150 seems like the audio noise level into the CM108 is possibly too high. I've never seen it that high( backwards to what may be thought...lower signal level number = higher number, as rx quiets with signal that level number goes up)
<-- I'll try and re-cal' the audio levels this evening. This is not the final hardware that I'll be using (I'll be installing the dual mode DV / FM repeater on a Kenwood TKR-850). R.
OK, good luck. My node is 2360 GeorgeC W2DB ----- Original Message ----- From: "Ramesh Dhami (VA3UV)" <Ramesh@va3uv.com> To: "George Csahanin" <george@dyb.com> Cc: "'app_rpt'" <app_rpt-users@ohnosec.org> Sent: Sunday, October 30, 2011 11:37 AM Subject: Re: [App_rpt-users] cop 2 - causing PTT lock
On 30/10/2011 12:34 PM, George Csahanin wrote:
Squelch at 450 and signal 150? Yeah, that's REAL tight. But the 150 seems like the audio noise level into the CM108 is possibly too high. I've never seen it that high( backwards to what may be thought...lower signal level number = higher number, as rx quiets with signal that level number goes up)
<-- I'll try and re-cal' the audio levels this evening. This is not the final hardware that I'll be using (I'll be installing the dual mode DV / FM repeater on a Kenwood TKR-850).
R.
Ramesh, I will have to check but if I am decoding PL, how should this even begin to plan with a squelch setting? -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Sunday, October 30, 2011 7:52 AM To: 'app_rpt' Subject: Re: [App_rpt-users] cop 2 - causing PTT lock On 30/10/2011 12:01 AM, George Csahanin wrote:
When you do "rpt showvars xxxx" does it show RPT_RXKEYED=0 or 1?
I've seen this if the levels/squelch setting not being right, lower noise being received signal, etc.
<-- Hi George and all: Tried my COP2 (dtmf command) via the CLI and as Lu mentioned, that works fine, as soon as I hear RPT ENA, the PTT drops and life is good. Then I disabled the repeater and tried the dtmf command from my HT - this is what I captured on CLI: [Oct 30 07:41:31] NOTICE[19419]: app_rpt.c:7957 wait_interval: Delay complete -- <Zap/pseudo-475079875> Playing 'letters/r' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/p' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/t' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/e' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/n' (language 'en') -- <Zap/pseudo-475079875> Playing 'letters/a' (language 'en') -- Hungup 'Zap/pseudo-475079875' [Oct 30 07:41:46] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1423219721' [Oct 30 07:41:49] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-1492162812' [Oct 30 07:41:52] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-13915100' [Oct 30 07:41:55] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 -- Hungup 'Zap/pseudo-971235839' [Oct 30 07:42:04] NOTICE[4141]: app_rpt.c:19882 rpt: Got PL 103.5 on node 2182 [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char * duration 127 ms [Oct 30 07:42:05] NOTICE[4141]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 0 duration 84 ms [Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:4288 cancel_pfxtone: cancel_pfxfone!![Oct 30 07:42:05] NOTICE[4141]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:10544 rpt_call: exit channel loop -- Hungup 'Zap/pseudo-895837731' [Oct 30 07:42:05] NOTICE[19396]: app_rpt.c:16792 channel_revert: remoterig=, nowchan=00, waschan=00 -- Hungup 'Zap/pseudo-2118062105' va3pmo_asterisk*CLI> Notice how I tried to key-up a few times - and no joy. Further even the end, when I sent a *0; app_rpt tells me: nowchan=00, waschan=00 So it believes that the ptt was actually off to start with. So OK, now I will bump the squelch up a bit... (Current setting was 450 with a signal level of 140) - the squelch is already kinda' high (I think?) - anyway, I bumped the squelch up to 500 - tried again and voila! - problem solved :) As soon as I finished sending the dtmf and dropped ptt on my HT, I heard the courtesy tone come back and knew instantly that this was going to work! So that's it - my dual mode DV and FM repeater is ready!!! ;P). Thanks!!! Ramesh. www.freestar.us _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (4)
-
George Csahanin -
Lu Vencl -
Ramesh Dhami (VA3UV) -
Ramesh Dhami, VA3UV/M