[App_rpt-users] rxondelay command

Angelo Glorioso n5uxt at hotmail.com
Tue Jun 24 18:54:33 EDT 2014

Here is a copy of the debug log. 

[Jun 24 18:47:45] NOTICE[3041]: app_rpt.c:20835 rpt: **** rx key
[Jun 24 18:47:48] NOTICE[3041]: app_rpt.c:20946 rpt: **** rx un-key
[Jun 24 18:47:48] NOTICE[3041]: app_rpt.c:10619 rpt_telemetry: Tracepoint rpt_telemetry() entered mode=4
[Jun 24 18:47:48] NOTICE[3041]: app_rpt.c:10910 rpt_telemetry: Tracepoint rpt_telemetry() exit

The part that is not shown, is that the receiver did not back on and start receiving until about
1 1/2 seconds.  

 Is this how the RXDELAYON works?? 

  ----- Original Message ----- 
  From: Angelo Glorioso 
  To: app_rpt-users at ohnosec.org 
  Sent: Tuesday, June 24, 2014 2:05 PM
  Subject: rxondelay command 

  I am having problems understanding what is going on with the RXONDELAY command in 
  duplex=1 mode. (simplex with telementry )

   From what I understand, this command turns off the reciever for a value of 20ms times (x) (my value 75) after the transmitting is dropped to prevent ping ponging or relay racing.

   Once this value is reached, should not the receiver come back on??? I find that this value will play a part when a valid signal comes back on as well. The usbradio will wait that (X) before 
  turning on the receiver even after the transmitting has already reached value of (X).

  So, if the signal has dropped for over 5 second lets say, why would rxondelay play any part again???? Should not this value have to wait until the valid signal is dropped again???

  I hope I have explained this correctly. 

  73 de Angelo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20140624/fe4812ad/attachment.html>

More information about the App_rpt-users mailing list