HMM. NOTE, I've recently updated to the latest svn and since then noticed this. Anyone noticed that on an initial ID after setting idle for some time, when you have 2 nodes connected. When a signal comes in on the remote node, it causes the local node to start the ID, about 2/3 through, it cuts off the first one and immediately generates a second as if it were one complete ID. Doesn't do it all the time. .. Any idea what change in the code may have done this? Alan
IF you have idrecording set to a morse id, leave idtalkover unset Jim WB6NIL From: adamson_alan@hotmail.com To: app_rpt-users@ohnosec.org Date: Fri, 8 Jun 2012 12:16:56 -0400 Subject: [App_rpt-users] Double ID's Double ID's HMM… NOTE, I've recently updated to the latest svn and since then noticed this… Anyone noticed that on an initial ID after setting idle for some time, when you have 2 nodes connected. When a signal comes in on the remote node, it causes the local node to start the ID, about 2/3 through, it cuts off the first one and immediately generates a second as if it were one complete ID. Doesn't do it all the time… …. Any idea what change in the code may have done this? Alan _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
This is a sort of long-standing thing, I'm also still seeing it. You'll get the talk over ID folioed by the regular ID, though not every time. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Jun 8, 2012, at 12:16 PM, Alan Adamson <adamson_alan@hotmail.com> wrote:
HMM…
NOTE, I've recently updated to the latest svn and since then noticed this…
Anyone noticed that on an initial ID after setting idle for some time, when you have 2 nodes connected. When a signal comes in on the remote node, it causes the local node to start the ID, about 2/3 through, it cuts off the first one and immediately generates a second as if it were one complete ID.
Doesn't do it all the time… ….
Any idea what change in the code may have done this?
Alan
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
It's been like this for a while now (check the archives). Just comment out the "talkover" one. --- On Fri, 6/8/12, Buddy Brannan <buddy@brannan.name> wrote:
From: Buddy Brannan <buddy@brannan.name> Subject: Re: [App_rpt-users] Double ID's To: "app_rpt mailing list" <App_rpt-users@ohnosec.org> Date: Friday, June 8, 2012, 11:38 AM This is a sort of long-standing thing, I'm also still seeing it. You'll get the talk over ID folioed by the regular ID, though not every time. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY
On Jun 8, 2012, at 12:16 PM, Alan Adamson <adamson_alan@hotmail.com> wrote:
HMM…
NOTE, I've recently updated to the latest svn and since then noticed this…
Anyone noticed that on an initial ID after setting idle for some time, when you have 2 nodes connected. When a signal comes in on the remote node, it causes the local node to start the ID, about 2/3 through, it cuts off the first one and immediately generates a second as if it were one complete ID.
Doesn't do it all the time… ….
Any idea what change in the code may have done this?
Alan
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (4)
-
Alan Adamson -
Buddy Brannan -
Jim Duuuude -
Tony KT9AC