User`s manual

Western Reserve Controls, Inc. 1782-JDC User’s Manual
38
If the answer to your question is not found here, or you require further assistance, please contact
Western
Reserve Controls at:
1485 Exeter Road
Akron, OH 44306
330-733-6662 (phone)
330-733-6663 (fax)
For product information, e-mail: [e-mail]
For technical support, e-mail: [e-mail]
D. Troubleshooting
This section identifies some of the common problems that may be observed when commissioning
or operating a DeviceNet and JDCx.
Problem:
JDCx does not power up; both LED’s are off.
Possible Causes:
1. Power not applied to DeviceNet cable or JDC connector.
2. Cabling not properly connected.
3. The module is damaged.
Problem:
JDCx will not communicate on the network.
Module Status LED is solid Green.
Network Status LED is flashing Green.
Possible Causes:
1. Network does not have a terminating resistor. Add a 121-ohm resistor across
the CAN_H and CAN_L signals at the first and last nodes.
2. Incorrect baud rate.
3. Cabling not properly connected.
4. No messaging connections are allocated.
5. Message sent to incorrect node.
6. JDCx is not in Master device’s Scan List.
Problem:
JDCx will not return data.
Module Status LED is solid Green.
Network Status LED is solid Green.
Possible Causes:
1. Message sent to incorrect node.
2. JDCx is not mapped into Master’s data map
Problem:
JDCx will only update the output buffer when an overflow condition is detected.
Possible Causes:
1. The receive delimiter is not a valid value. See Table 5-1, Parameter 5.
2. The receive delimiter value is never received.
Problem:
JDCx is not being scanned after changing the ASCII transmit and receive buffer