C321 REDnet RS485

C321A0 Hub : Framing error on port: {signed}

A message with a malformed frame was passed to the HUB on specified port(0: Int 1: Ext0, 2: Ext1, 4: None)

 

C321A1 Hub : Alignment error on port: {signed}

A message with a malformed frame was passed to the HUB on specified port(0: Int 1: Ext0, 2: Ext1, 4: None)

 

C321A2 Data transmission unit : FiFo overflow on port {unsigned}

Transmission unit had a FiFo overflow on specified port (0: port a, 1: port b)

 

C321A3 Data transmission unit : code error on port {unsigned}

Transmission unit received a code error on specified port (0: port a, 1: port b), this should never happen

 

C321A4 Data reception unit : Alignment error on port {unsigned}

Reception unit was unaligned with message on specified port (0: port a, 1: port b)

 

C321A5 Data reception unit : Alignment fault on port {unsigned}

Reception unit was unable to align to incomming message on specified port (0: port a, 1: port b)

 

C321A6 Data reception unit : Code error on port {unsigned}

Reception unit saw an invalid control code on specified port (0: port a, 1: port b)

Contact your local Universal Robots service provider for assistance.

C321A7 Data reception unit : Disparity error on port {unsigned}

Reception unit got a disparity error on specified port (0: port a, 1: port b)

 

C321A8 Data reception unit : FiFo overflow on port {unsigned}

Reception unit had a FiFo overflow on specified port (0: port a, 1: port b)

 

C321A9 Upstream transport layer : Package CRC error

Upstream transport layer cought CRC error in package header

This might happen on occation. Can be ignored if only happens rarely

C321A10 Upstream transport layer : Bad package framing

Upstream transport layer had found a framing error.

 

C321A11 Upstream transport layer : Rx FiFo overflow

Upstream transport layer had a FiFo overflow

 

C321A12 Upstream transport layer : Tx FiFo overflow

Slave transport layer had a Tx FiFo overflow

 

C321A13 Upstream transport layer : Invalid hub count

Slave transport layer recieved a message with invalid hub-cnt

 

C321A14 Upstream transport layer : Request source not master.

Slave transport layer recieved a message request from a device different from the master

C321A15 Upstream transport layer : Response source not slave.

Slave transport layer recieved a message response from a device different from a slave

 

C321A16 Upstream transport layer : Sync package type received

Master transport layer recieved a message where the type was Sync

 

C321A17 Upstream transport layer : Trigger package type received

Master transport layer recieved a message where the type was a tigger

 

C321A18 Upstream transport layer : Request package type received

Master transport layer recieved a message where the type was a request

 

C321A19 Upstream transport layer : Invalid reponse type received

Master transport layer recieved a message where the type was an invalid response

 

C321A20 Upstream transport layer : Package from invalid source received

Master transport layer recieved a package with an invalid source

 

C321A21 Upstream transport layer : Missmatch between HUB count and package source

Master transport layer recieved a package where the src and HUB count did not match

 

C321A22 Upstream transport layer : Package longer than expected

Master transport layer recieved a package where the length was greate than expected, or lost a framing end

 

C321A23 Upstream transport layer : Package shorter than expected

Master transport layer recieved a package where the length was less than expected

 

C321A24 Upstream transport layer : Package was misaligned

Master transport layer recieved a package that did not align to 32bit

 

C321A25 Downstream transport layer : Package was shorter than expected

Downstream transport layer tried to transmit a package that was longer than the data available

 

C321A26 Downstream transport layer : Package was longer than expected

Downstream transport layer tried to transmit a package with more data than expected

 

C321A27 Downstream transport layer : Invalid package type

Master transport layer tried to transmit a package with an invalid package type

 

C321A28 Downstream transport layer : Package type missing

Master transport layer tried to transmit a package without a package type

 

C321A29 Downstream transport layer : Message length missing

Master transport layer tried to transmit a package without a message length

 

C321A30 Downstream transport layer : Package destination missing

Master transport layer tried to transmit a package without a destination

 

C321A31 Downstream transport layer : Package source missing

Master transport layer tried to transmit a package without a source

 

C321A32 Downstream transport layer : Package NML missing

Master transport layer tried to transmit a package without a next message length

 

C321A33 Downstream transport layer : Package TTTL missing

Master transport layer tried to transmit a package without a time to live

 

C321A34 Downstream transport layer : Package timeout(high byte) missing

Master transport layer tried to transmit a package without a timeout the high byte

C321A35 Downstream transport layer : Package timeout(low byte) missing

Master transport layer tried to transmit a package without a timeout the low byte

 

C321A36 Downstream transport layer : Invalid message length

Master transport layer tried to transmit a package with missmatch between stated and actual length

 

C321A37 REDnet controller : Received control pkg in data phase

REDnet controller received a control package when not in the control phase

 

C321A38 REDnet controller : Received data package in control phase

REDnet controller received a data package when not in the data phase

 

C321A39 REDnet controller : Got SOC before being ready

REDnet controller got a SOC interrupt while not ready

 

C321A40 REDnet scheduler : Got SOC before being ready

REDnet scheduler got a SOC interrupt while not ready

C321A41 REDnet scheduler : Node ID invalid

REDnet scheduler tried to send to Node ID outside valid range

If you are unable to resolve the issue, login or create an account at http://myUR.universal-robots.com and post a new ticket.