CMM5 Error Conditions

ProductsCMM5
knowledge-base
https://community.cambiumnetworks.com/t/cmm5-error-conditions/58730
Nov 2018
1/1
Nov 2018
Nov 2018

JBoeldtCambium
Nov '18
The Controller tracks various error conditions which may occur on the connected Injectors
and displays warning notifications as appropriate. Common error conditions are described
in the following paragraphs.

Master Injector Communications Lost

The Controller periodically checks communications with the Master Injector. If
communications are lost, the Controller GUI will display an error message as shown below:

Master Injector Communications Lost.png1880×626 57.6 KB

Slave Injector Communications Lost

The Controller periodically checks communications with any Slave Injectors that are present
in the CMM5 configuration. If communications are lost, the data for the affected Injector(s)
will be grayed out in the Controller CMM5 Services tab, as shown below:
Slave Injector Communications Lost.png1881×626 53.1 KB

Note: Commands cannot be initiated on the affected Slave Injector(s) when the Controller
indicates that communication has been lost.

his condition may be due to loss of power to the affected Slave Injector, disconnection of
the daisy-chain communication cable to that Injector, or by an internal hardware fault in the
unit.

USB Connection Lost

The Controller monitors communications with the Master Injector over the USB cable and
displays the following error message if the communications are interrupted:

USB Connection Lost.png1881×626 59.6 KB

Note: The error message indicating loss of communications with the Master Injector is also
displayed in this case.
If this error occurs check the integrity of the USB cable connection between the Controller
and the Master Injector.

ODU Port Tripped

The Controller indicates if any of the ODU ports have tripped due to triggering of the
overcurrent protection mechanism. Ports for which this is the case will be highlighted in red
on the CMM5 Services screen and the Port Status and Sync Status will be displayed as
“TRIPPED”.

ODU Port Tripped.png1881×627 52.9 KB

This condition can be caused by a short circuit in the wiring to the radio, connection of
inappropriate equipment (e.g. plugging a 29V radio into a 56V injector), or by an internal
fault in the radio itself.

The ODU port overcurrent protection algorithm is implemented as follows:

 When a fault condition is detected on an ODU port, the port is immediately shut down
and the port status is displayed as TRIPPED.
 After 15 seconds the Controller attempts to re-enable the port. If the fault condition is
resolved then the port is enabled automatically and port status changes from TRIPPED
to ON.
 If another fault condition is detected within two minutes of the previous trip event, or if the
previous fault is still present, the port is again shut down and the status reverts to
TRIPPED. As before, the Controller will attempt to re-enable the port after 15 seconds.
 If more than three faults are detected consecutively at intervals of less than two minutes,
the port will shut down and the status will change to TRIPPED as above, but the
Controller will wait for a full two minutes before attempting to reset the port again.
 After the two minute waiting period is up, the port is reset and all internal counters and
timers are cleared. The process above is then repeated for any further error conditions
which may occur.
Note: The above description applies to version 00.21 Injector firmware. Versions 00.14 and
earlier differ in that the ODU ports are not automatically reset by the Controller. Instead the
operator must manually reset tripped ports by clicking the port status button for the affected
port after resolving the physical error condition.