2
« on: 2011-10-21, 19:28:14 »
Summary of running RRCs for one week:
1. OS used: Windows, Linux, Mac os
2. Programs tried: HRD (win and Linux), MacloggerDX (mac), Commander (win)
3. All programs tested with direct connections to the rig to baseline the performance (ic746pro, microham USB interface II), and with RRCs running across Internet (average ping time 6-10 ms, fiberoptic ISP connections at both ends, routers set up in DMZ mode for the remote RRC IP, all SIP/NAT/DDOS filtering off).
I. Regardless of OS, application and network setup, the direct USB0 control of the rig stops working after a short time (minutes).
II. When operating remote using serial interfaces between the computer and the control RRC, the setup worked without freeszing, but there were considerable Icom response delays when rapidly changing the frequency through the software.
III. MacloggerDX reported "poll errors". Further debugging revealed the following messages associated with those errors.
RadioController:getRadioReport:elapsed time: [176.227987] ms
The elapsed time would vary from 100ms to 1000ms. The constantly running ping tests did not show any network degradation.
Most likely the RRCs were choking on frequency change data running across the link. (CPU overrun?)
If you need any specific log data, please ask.
Regards,
Sergey
RX3DUX.