54
Table24 – Ma nufacture Date
When troubleshooting, you may need to know a control module’s manufacture date
Obtain the manufacture da te from
a...
Notes
Modulestatus report (modstat) Toobtain a modstat with BACview6:
1.Press Function (FN) key and hold.
2.Then p ressp eriod (.)
3. Release both b uttons.
ThereportshowsthedateunderMainboard hardware.
Stickeron the b ack of the main control
moduleboard
”SerialNo: RMPYMxxxxN”
(BarCoded & Typed Number)
Theserial numbers are unique and contain embedded information:
“RMP” --- These first three digits are unique to RTU ---MPand are used as an id entifier.
“YM” --- Thesetwo dig itsid entify the last digit of the year and month (in hex, A =10/Oct)
ofmanuf acture. ”74” would represent a date of manufacture of ”April 2007”.
“xxxx” --- Thesefour digits represent the sequentialnumber of units produced for a given
product for the mentioned manufacturing time period.
“N” --- Thisfinal digit represents the decade a nd toggles between ”N” and ”M” every
tenye ars.
Table25 – Basic Protocol Troubleshooting
Problem Possiblecause Corrective action
Nocommun ication with 3rd
partyvendor
Incorrectsettings on SW1, SW2 and SW3 Verifya nd correct switch settings. Cycle
powertoRTU---MPafterchangingswitch
settings.
RS485Port has no v oltage output VerifyRTU ---MPhas correct power supply
(checkwith RTU---MPdisconnected from RS485 commu-
nicationbus)
Possiblebad driver on board.
Bacnet@ 9600/19.2K ---.01 to .045vdc CheckRS485 bus for external before re-
connectingto the bus
Bacnet@ 38.4K --- .06to .09vdc Voltage,shorts or groun ding
Bacnet@ 76.8K --- .1vdc before reconnectingto the bus
Modbus@ 9600 ---76.8K ---.124vdc
N2@ 9600 --- .124vdc
Verifydevices are daisy chained and repeaters and bias
terminatorsare correctly installed
Check3rd party vendorRS485 commu-
nicationwiring guidelines and trouble-
shootingprocedures
SMaxInfo Frames: This property defines the maximum
numberof responses that wil l be sent when our controller
gets the token. A valid number is any positive integer.
The default is 10 and should be ideal for the majority of
applications. In cases where the controller is the target of
many requests, this number could be incre ased as high as
100 or 200.
NOTE: MS/TP networks can be comprised of both
Master and Slave nodes. Valid MAC addresses for Master
nodes are 0 --127 and valid a ddresses for Slave nodes are
0 --254.
NOTE: See RTU--MP 3rd Party Integration Guide (or
alternatively Form 48--50H--T--1T Appendix) for Protocol
Maps.
Table26 – Mo dbusE xception Codes that May be
ReturnedFrom This Controller
CODE NAME MEANING
01 Illegal Function
TheModbus function code used
inthe query is not supported by
thecontroller.
02 Illegal Data Address
Theregister add ressu sed in the
queryis not supported by the
controller.
04 SlaveDeviceFailure
TheModbus Master has at-
tempted to write to a non---exist-
entregister or a read ---onlyregis-
terin the controller.
Modbus
1. Verify that the BAS and controller are both set to
speak the Modbus RTUprot ocol. The protocol of the
controller is set via SW3 (switches 3, 4, 5, and 6).
The protocolcan also be verified by getting a Modstat
of the controller through the BACview. Hit the ”FN”
key and the ’.’ key at the same time to pull up a
Modstat. Scrollto the bottom of the page and there is
a section entitled “Network Communications.” The
active protocol and baud rate will be shown in this
section.
2. Verify that the BAS and controller are set for the
same baud rate. The baud rate of the controller is set
via SW3 (switches 1 and 2). The baud rate can also
be verified via the BACview by obtaining a Modstat
(see above).
3. Verify that the BAS is configured to speak 2--wire
EIA--485to the controller.The BAS may have to con-
figure jumper or DIP switches on their end.
4. Verify that the BASa ndt he controller have the same
communication settings (8 data bits, No Parity,and 1
stop bit).
5. Verifythat the control lerhas a unique Modbus slave
address. The controller’s Modbus slave address is set
by its rotary addressswitches.
6. Verify that the BAS is using the proper Modbus func-
tion codes to access data from our controller. Sup-
ported function codes are shown above.
48TC