You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Chart Archive" mode "hangs" there with a revolving circle and cannot exit - I have to use the browser "back" button to clear it. This condition exists on nodes that have no RF Connections. Suggest fix as well as provide an option for the user to totally disable the SNR Logging system along with related Crontabs processes when no RF is present with the RF deck enabled. I see that the option has been removed when the MESH RF is disabled. Could this be contributing to the excessive "load" issue?
The text was updated successfully, but these errors were encountered:
I have an AirRouter running dev-176 operating as a Tunnel Server, no RF Buddy and phone attached that runs with low load values and does not "Hang" when selecting the archive. (for my reference: KM4GJR-ARHP-201-WBY-CCE911 on the Southmesh system)
Joe - well - in a way yes in that this condition (#204) represents an "unknown" connection and the process hangs and doesn't allow selection display the other available valid connections either in the Archive or the "LIVE" Real-Time connection selection area even though they are connected and working fine.
Further review of this issue looks like this may no longer be a problem. Running Production 3.22.1.0 on a GL AR750 (Creta) with no RF Buddy. Will check a few more nodes and report back.
The "Chart Archive" mode "hangs" there with a revolving circle and cannot exit - I have to use the browser "back" button to clear it. This condition exists on nodes that have no RF Connections. Suggest fix as well as provide an option for the user to totally disable the SNR Logging system along with related Crontabs processes when no RF is present with the RF deck enabled. I see that the option has been removed when the MESH RF is disabled. Could this be contributing to the excessive "load" issue?
The text was updated successfully, but these errors were encountered: