Carrier RTU-MP, Integration Manual

Page: 28 / 58

Troubleshooting
24 RTU-MP Controller
2
Verify that the BAS and the controller are both set for the same baud rate:
○
9600 for N2
○
Comm Selector DIP switches DS2 and DS1
○
By getting a Modstat of the controller through the BACview. Click and hold the FN key and then click
the . key at the same time. Scroll to the bottom of the page to the section entitled Network
Communications to view the active protocol and baud rate.
3
Verify that the BAS is configured to speak 2-wire EIA-485 to the controller. The BAS may have to
configure jumper or DIP switches on their end.
4
Verify that the BAS and the controller have the same communication settings (8 data bits, No Parity, and
1 stop bit).
5
Verify proper connection wiring between the BAS and the controller.
6
Verify that the rotary address switches are set for the controller's unique slave address.
7
BAS must be reading or writing to the proper point addresses on the controller.
8
BAS is sending requests to the proper slave address of the controller.
NOTE Refer to Appendix C for the Protocol Implementation Conformance Statement.
LonWorks
Check the following to troubleshoot your RTU-MP:
1
Verify that the BAS and controller are both set to speak the LonWorks protocol:
○
Comm Selector DIP switches DS3 - DS6
○
By getting a Modstat of the controller through the BACview. Click and hold the FN key and then click
the . key at the same time. Scroll to the bottom of the page to the section entitled Network
Communications to view the active protocol and baud rate.
2
Verify that the BAS and the controller are both set for the same baud rate:
○
38.4k for LonWorks
○ Comm Selector DIP switches DS2 and DS1
○
By getting a Modstat of the controller through the BACview. Click and hold the FN key and then click
the . key at the same time. Scroll to the bottom of the page to the section entitled Network
Communications
to view the active protocol and baud rate.
3
BAS must be reading or writing to the proper point addresses on the controller.
4
Verify that the Comm Option port is enabled on the controller. The Comm Option port setting must be set
via SW3 (switch DS7 ). It should be in the ON position to enable LonWorks communication.
5
Verify that controller has been properly commissioned onto the LonWorks network. Commissioning is
done with a Network Management tool such as LonMaker and allows the system integrator to associate
the controller with the LonWorks system’s network layout diagram. This is done using the controller’s
unique Neuron ID. The Network Management tool is also used to upload the controller’s .XIF file to
determine the network variables that reside inside of the controller.
6
Use the Browse feature of the Network Management Tool to verify that you can communicate and get
real-time values from the controller before connecting the BAS.
7
Once you have confirmed communications with the controller using the Network Management tool,
connect the BAS.
8
Verify that the BAS is connected properly to the LON-OC's 2-wire TP/FT-10 Net port. The LON-OC’s TP/FT-
10 port is polarity insensitive. The BAS may have to configure jumper or DIP switches on their end to
support TP/FT-10.