Download - Manual Mesi Bus
-
8/15/2019 Manual Mesi Bus
1/68
The Data – Logger 8040 is a product that provides a wide variety of featuresin a data acquisition and control application. It includes 3 I/O-slots Data –
Logger 8040 (Half 19” Rack) and 10 I/O-slots Data - Logger 8040(Full 19”
Rack). They are remotely controlled by the host computer through a set of
commands and transmitted in a RS-485/RS232 network. The modular design
also provides more flexibility in the system configuration. The following is a
summary of the major Data – Logger 8040 system components.
The Data – Logger 8040 (Half 19”) system architecture includes a SMPSCard, CPU card with a built-in RS-232/RS-485 communication port, one
built-in RS-422 communication and a Centronics Printer Port and 3 I/O – slot
backplane. The Data – Logger 8040 (Full 19”) system includes all of theabove components, except it has a 10 I/O – slot backplane. Details of the
system architecture features and more are covered in Next Chapter.
There are some software utilities available to the Data – Logger 8040systems. The Windows utility software helps you to configure your Data –
Logger 8040 Model. One can either configure the data-logger from operator
terminal or through host computer via RS232/RS485 port.
‘M81/om/101, Issue # 01A-801992 - 1 -
-
8/15/2019 Manual Mesi Bus
2/68
The following diagram shows the system configurations possible with the Data –
Logger 8040.
Figure 1.2.1:- System Configuration Setup for Data – Logger 8040 (Full 19”)
16 Ch. AnalogInput Module
16 Ch. DigitalInput Module
16 Ch. IsolatedAnalog Input
Module
16 Ch. OpenCollector OutputModule
8 Ch. RelayOutput Module
4 Ch. AnalogOutput Module
RS – 422 CONN.
RS-232OR
RS-485
9 PIN D - TYPE RJ45 CONNECTOR
OUTPUT
MODULE
INPUT
MODULE
‘M81/om/101, Issue # 01A-801992 - 2 -
-
8/15/2019 Manual Mesi Bus
3/68
The following diagram shows the system configurations possible with the Data –
Logger 8040.
Figure 1.2.2:- System Configuration Setup for Data – Logger 8040 (Half 19”)
16 Ch. AnalogInput Module
16 Ch. DigitalInput Module
16 Ch. IsolatedAnalog InputModule
16 Ch. OpenCollector OutputModule
8 Ch. RelayOutput Module
4 Ch. Analog
Output Module
RS – 422 CONN.
RS-232OR
RS-485
9 PIN D - TYPE RJ45 CONNECTOR
OUTPUT
MODULE
INPUT
MODULE
‘M81/om/101, Issue # 01A-801992 - 3 -
-
8/15/2019 Manual Mesi Bus
4/68
You should always make safety your first priority in any system application.
Chapter 2 provides several guidelines that will help provide a safer, morereliable system.
The main controller is the heart of Data - Logger 8040 system. Make sure youtake time to understand the various features and setup requirements.
It is important to understand how your I/O modules can be configured.
Before you begin to link your applications in your host computer with theData - Logger 8040 systems, it is very helpful to understand how the
Windows utility software helps you configure your Data - Logger 8040.
The Data - Logger 8040 system allows you to develop your applications inDOS or Windows. It provides an RTU command set with standard Modbus
protocol.
‘M81/om/101, Issue # 01A-801992 - 4 -
-
8/15/2019 Manual Mesi Bus
5/68
Environment SpecificationThe following table lists the environmental specifications that generally apply
to the Data – Logger 8040 system (Main Controller and I/O modules).
Specification Rating
Storage Temperature 0 to 55°C
Ambient Operating
Temperature0 to 55°C
Ambient Humidity 5 to 90% Non-Condensing
Atmosphere Non corrosive gases
Equipment will operate below 30% humidity. However, static electricity
problems occur much more frequently at lower humidity levels. Make sure you
take adequate precautions before you touch any input/output point of the
equipment. Consider using ground straps, antistatic floor coverings, etc. if you
use the equipment in low humidity environments.
Power RequirementAlthough the Data – Logger 8040 systems are designed for standard
industrial 230 V AC, 50Hz±5% power supply, they accept any power unit
that supplies within the range of 90 to 260 VAC.
The Data - logger 8040 system can be installed on a panel.
Figure 2.2.1:- Panel Mounting Details for Data – Logger 8040 (Half 19”)
‘M81/om/101, Issue # 01A-801992 - 5 -
-
8/15/2019 Manual Mesi Bus
6/68
Figure 2.2.2:- Panel Mounting Details for Data – Logger 8040 (Full 19”)
Figure 2.3.1:- Side View of Data – Logger 8040
‘M81/om/101, Issue # 01A-801992 - 6 -
-
8/15/2019 Manual Mesi Bus
7/68
Figure 2.3.2:- Dimension Details of Data – Logger 8040 (Half 19”)
Figure 2.3.3:- Dimension Details of Data – Logger 8040 (Full 19”)
‘M81/om/101, Issue # 01A-801992 - 7 -
-
8/15/2019 Manual Mesi Bus
8/68
Figure 2.3.4:- Front view of Operator terminal Unit.
Figure 2.3.5:- Panel cut out of Operator terminal Unit.
‘M81/om/101, Issue # 01A-801992 - 8 -
-
8/15/2019 Manual Mesi Bus
9/68
Figure 2.3.4:- Rear view and Side view of Operator terminal Unit.
‘M81/om/101, Issue # 01A-801992 - 9 -
-
8/15/2019 Manual Mesi Bus
10/68
This section provides basic information on wiring the power supply and I/O
units, and on connecting the network.
Power Supply Unit WiringBe sure that the power supply voltage remains within the allowed fluctuation
range of between 90 to 260 VAC. Terminals L, N and E are for power supply
wiring.
Note: The wire(s) used should be at least 2mm2.
Non – Isolated Analog Input Modules WiringThe system uses 50 pin ‘D’ type Male connector for the interface between
Input module and field devices. The following information must be
considered when connecting electrical devices to Input modules.
1. Always use a continuous length of wire, do not combine wires to attainneeded length
2. Use the shortest possible wire length3. Use the wire trays for routing where possible.4. Avoid running wires near high energy wiring
5. Avoid running input wiring in close proximity to output wiring where possible
6. Avoid creating sharp bends in the wires
Note: A Prefab 1 is to 1 cable is provided for connection from 50 pin D type
connector to the Extension Connector. Wiring to be done as shown in fig 2.4
.1.
Figure 2.4.1:- 50 Pin D - Type Connector Details
‘M81/om/101, Issue # 01A-801992 - 10 -
-
8/15/2019 Manual Mesi Bus
11/68
Isolated Analog Input Modules WiringThe system uses 50 pin ‘D’ type Male connector for the interface between
Input module and field devices. The following information must be
considered when connecting electrical devices to Input modules.
1. Always use a continuous length of wire, do not combine wires to attainneeded length
2. Use the shortest possible wire length3. Use the wire trays for routing where possible.4. Avoid running wires near high energy wiring5. Avoid running input wiring in close proximity to output wiring where
possible
6. Avoid creating sharp bends in the wires
Note: A Prefab 1 is to 1 cable is provided for connection from 50 pin D type
connector to the Extension Connector. Wiring to be done as shown in fig
2.4.2.
Figure 2.4.2:- 50 Pin D - Type Connector Details
Note(Non-Isolated & Isolated) :
1) For current input(0-20mA or 4-20mA connect 250Ω between High (+) and Low (-)
terminals.
2) For Voltage & TC input connect input between High (+) and Low (-) terminals.
3) For RTD (3wire) input connect input between High (+) , Low (-) & Common I .
‘M81/om/101, Issue # 01A-801992 - 11 -
-
8/15/2019 Manual Mesi Bus
12/68
Relay Output Module WiringThe system uses 25 pin ‘D’ type Female connector for the interface between
Relay module and field devices. The Relay Output Module has eight relaysAny output can be mapped to any channel for the alarm configuration or for
fault or on-off through PC as shown in the flow chart of relay configuration..
The following information must be considered when connecting electrical
devices to Relay modules.
1. Always use a continuous length of wire, do not combine wires to attainneeded length
2. Use the shortest possible wire length3. Use the wire trays for routing where possible.4. Avoid running wires near high energy wiring5. Avoid running input wiring in close proximity to output wiring where
possible
6. Avoid creating sharp bends in the wires
Note: A Prefab 1 is to 1 cable is provided for connection from 25 pin D type
connector to the field devices. Wiring to be done as shown in fig 2.4.3.
Figure 2.4.3:- 25 Pin D – Type Connector Details for Relay Card
‘M81/om/101, Issue # 01A-801992 - 12 -
-
8/15/2019 Manual Mesi Bus
13/68
Open Collector Output Module WiringThe system uses 25 pin ‘D’ type Female connector for the interface between
Open Collector Output module and field devices. The Open Collector Output
Module has sixteen Open Collector Outputs. Any output can be mapped to
any channel for the alarm configuration or for fault or on-off through PC as
shown in the flow chart of relay configuration. The following information
must be considered when connecting electrical devices to Output Collector
modules.
1. Always use a continuous length of wire, do not combine wires to attainneeded length
2. Use the shortest possible wire length3. Use the wire trays for routing where possible.4. Avoid running wires near high energy wiring5. Avoid running input wiring in close proximity to output wiring where
possible
6. Avoid creating sharp bends in the wires
Note:A Prefab 1 is to 1 cable is provided for connection from 25 pin D type
connector to the field devices. Wiring to be done as shown in fig 2.4.3.
Figure 2.4.3:- 25 Pin
D – Type Connector Details for Relay Card
‘M81/om/101, Issue # 01A-801992 - 13 -
-
8/15/2019 Manual Mesi Bus
14/68
Digital Output Module WiringThe system uses 25 pin ‘D’ type Female connector. The Digital Output
Module can be used in either one of the two modes.
16 – Channel Open Collector Fault Channel Indication
In Fault Channel Indication
If the LED is OFF, then the channel is healthy.
If the LED is ON, then the channel is faulty.
If the LED is blinking, then the channel is skip.
The following information must be considered when connecting electrical
devices to Relay modules.
1. Always use a continuous length of wire, do not combine wires to attainneeded length
2. Use the shortest possible wire length3. Use the wire trays for routing where possible.4. Avoid running wires near high energy wiring5. Avoid running input wiring in close proximity to output wiring where
possible
6. Avoid creating sharp bends in the wires
Note: A Prefab 1 is to 1 cable is provided for connection from 25 pin D type
connector to the field devices.
‘M81/om/101, Issue # 01A-801992 - 14 -
-
8/15/2019 Manual Mesi Bus
15/68
RS – 485 Port (J1)There is a DB9 port in the Data – Logger 8040 system. The port is designed
to link the RS-485 through a cable to a network in a system. The pin
assignment of the port is as follows:
Figure 2.4.4:- RS – 485 Connection Details
‘M81/om/101, Issue # 01A-801992 - 15 -
-
8/15/2019 Manual Mesi Bus
16/68
RS – 232 Port (J1)The RS-232 port is designed for field configuration and diagnostics. The Data
– Logger 8040 is used as Data Communication Equipment (DCE). Users may
connect a notebook PC to the RS-232 port to configure or troubleshoot your
system in the field. Further, the Data – Logger 8040 system can also be
configured as the slave of the host computer through this port connection.
The pin assignment of the port is as follows:
Figure 2.4.5:- RS – 232 Connection Details
‘M81/om/101, Issue # 01A-801992 - 16 -
-
8/15/2019 Manual Mesi Bus
17/68
Parallel Printer Port WiringThe Parallel Printer port is used for printing data form the Data – Logger
8040. The system uses a 25 – pin ‘D’ Type female connector for interface
between the printer and the CPU card. The printer port can also be used for
Data – Logging when an external trigger is given. The pin description for the
printer port is given below.
Figure 2.4.6:- Centronics Parallel Port Printer Connection Details
For Data – Logging first select Triggering YES, and then short pin no. 10
to pin no. 18. Here it should be noted that the printer is disconnected from
the printer port.
‘M81/om/101, Issue # 01A-801992 - 17 -
-
8/15/2019 Manual Mesi Bus
18/68
The Data – Logger 8040 series is a data acquisition and control system,
which can control, monitor and acquire data through multichannel I/O
modules. Encased in rugged industrial housing, the system provides
intelligent signal conditioning, analog I/O, digital I/O, RS-232 and RS-
485 communication. The system communicates with the controlling host
over a multi-drop RS-485 network.
The Data – Logger 8040 system consists of two major parts: the system
architecture and I/O modules. The system kernel includes a SMPS Card,
CPU card with a built-in RS-232/RS-485 communication port RS-422 port and a Centronics Printer Port and 3 I/O – Slot backplane/ 10 I/O –
Slot backplane. It also offers the following major features:
The CPU’s Basic FunctionsThe CPU is the heart of the system and has the following basic functions:
Data acquisition and control for all I/O modules in the system Communication software and command set Alarm monitoring
Management of the EEPROM device that holds the system parameters Data transformation Diagnosis Data-logging Printing
3 – Way Isolation & Watchdog TimerElectrical noise can enter a system in many different ways. It may enter
through an I/O module, a power supply connection or the communication
ground connection. The Data – Logger system provides isolation between
analog ground and System ground . Isolation is also provided between the
Serial Communication Port and the System ground. The 3-way isolation
design prevents ground loops and reduces the effect of electrical noise to the
system. It also offers better surge protection to prevent dangerous voltages or
spikes from harming your system. The system also provides a Watchdog
timer to monitor the micro – controller. It will automatically reset the micro –
controller in Data –Logger system if the software is affected due to spikes
and brown outs.
‘M81/om/101, Issue # 01A-801992 - 18 -
-
8/15/2019 Manual Mesi Bus
19/68
Remote Software Configuration & CalibrationThe Data – Logger system merely issues a command from the host computer,
you can change an analog input module to accept several ranges of voltage
input, current input, thermocouple input or RTD input. All the parameters
including speed, parity, HI and LO alarm, ZERO and SPAN setting, Decimal
position and calibration parameters setting may be set remotely. Remote
configuration can be done by using either the provided menu-based software
or the command set’s configuration and calibration commands. By storing
configuration and calibration parameters in a nonvolatile EEPROM, the
systems are able to retain these parameters in case of power failure.
Connectivity & ProgrammingThe Data – Logger 8040 systems can connect to and communicate with all
computers and terminals. They use either RS-232 or RS-485 transmission
standards and communicate with MODBUS RTU format commands.
However, users can only select and use one communication port at any time.
All communications to and from the system are performed in MODBUS
RTU, which means that the Data – Logger systems can be programmed in
virtually any high-level language.
Flexible Communication ConnectionThe Data – Logger’s built-in RS-232/485 conversion capability enables users
to freely choose either RS-232 port or RS-485 port to connect with host PC.
A Single System Setup through the RS – 232 PortIf users would like to use a PC to locally control and monitor a simple
application, the Data – Logger 8040 system provides up to 48 points or 160
points and front-end wiring through the RS-232 port to the host computer.
A Distributed I/O Setup through the RS – 485 NetworkUp to 32 Data – Logger 8040 systems may be connected to an RS-485 multi-
drop network extendable up to 100 by using RS-485 repeaters, extending the
maximum communication distance to 2,000 ft. The host computer is
connected to the RS-485 network from one of its COM ports through the RS-
232/RS-485 converter. Only two wires are needed for the RS-485 network:
DATA+ and DATA-. Inexpensive shielded twisted-pair wiring is employed.
‘M81/om/101, Issue # 01A-801992 - 19 -
-
8/15/2019 Manual Mesi Bus
20/68
Processor
CPU XAG49, 16 Bit Micro – Controller
RAM8 KB Volatile RAM
512 KB NVRAM (Battery Backed)
ROM 64 KB
I/O Capacity3 Slots (Half 19”)
10 Slots (Full 19”)
Watchdog Timer Yes
Real Time Clock Yes
Communication
RS – 485/RS – 232 1
Optional RS – 232 1
RS – 422 1
Wiring RS – 485, Twisted Cable
RS – 232, Straight Cable
RS – 422, Twisted Cable
Speed 4800 to 19200 bpsMax.
Communication
Distance
2000ft. for RS – 485
60ft. for RS – 232
Network Expansion Up to 99 Data – Logger 8040
systems per host
Protection Transient Suppression on RS –
485 Communication lines.
Protocol MODBUS RTU (Command
Response)
Asynchronous Data
Format
1 start bit, 8 data bits, 1 stop bit,
no parity (1 start, 8-N-1)Communication
Error Check
CRC
‘M81/om/101, Issue # 01A-801992 - 20 -
-
8/15/2019 Manual Mesi Bus
21/68
-
8/15/2019 Manual Mesi Bus
22/68
Analog input modules use an A/D converter to convert sensor voltage, current,
thermocouple or RTD signals into digital data. The digital data is then translated
into engineering units.
Thermocouple Inputs Types : J, K, T, E, B, S, R
CJC Error : ±2°C maximum 0 to 55°C Resolution : 1°C Accuracy : ±(0.1%of Full Scale + 1 digit) without CJC Error Temperature range : See table by type
Input Impedance : > 2MΩ
Lead resistance effect : Less than 55 micro volts/100Ω Cold junction compensation : 0 to +55°C Open thermocouple indication : “Open “ displayed
RTD Inputs Types : PT100
Resolution : 0.1°C Accuracy : ±(0.1%of Full Scale + 1 digit) Temperature range : -200 TO 850 3 Wire compensation : Using Hardware Technique Open RTD indication : “Open” displayed
Voltage & Current Input Type : 0 to 5V,1 to 5V, 4 to 20mA & 0 to 20 mA Temperature range : -19000 to 19000 Accuracy : ±(0.1%of Full Scale + 1 digit)
‘M81/om/101, Issue # 01A-801992 - 22 -
-
8/15/2019 Manual Mesi Bus
23/68
Operating Range :
I/P No. Type Range Resolution
0 E -200°C to +1000°C 1°C
1 J -200°C to +760°C 1°C
2 K -200°C to +1350°C 1°C
3 T -200°C to +400°C 1°C
4 B +450°C to 1750°C 1°C5 R 0°C to +1750°C 1°C
6 S 0°C to +1750°C 1°C
7 N 230°C to +1270°C 1°C
8 Ni- 120 -700°C to +2790°C 1°C
9 RTD -200°C TO 850°C 0.1°C
10 0 to 20 mA -19000 to +19000 1 COUNT
11 4 to 20 mA -19000 to +19000 1 COUNT
12 0 to 5V -19000 to +19000 1 COUNT
13 1 to 5V -19000 to +19000 1 COUNTTable: 4.2.1
The Data – Logger 8040 signal conditioner card is a 16-bit, universal
input module that features programmable input ranges on all channels.
This module is an extremely cost-effective solution for industrial
measurement and monitoring applications. Its opto-isolated inputs
provide 1,000 VDC of isolation between the analog input and the module,
protecting the module and peripherals from damage due to high input line
voltage.
It accepts voltage inputs (1V, 5V) and current input (20 mA, requires 250
ohms resistor), thermocouple input (J, K, T, R, S, E, B). The module
provides data to the host computer in engineering units (V, °C, °F or mA).
The signal conditioner module also has an ambient sensor to measure
ambient temperature. The ambient sensor also provides the CJC
compensation.
‘M81/om/101, Issue # 01A-801992 - 23 -
-
8/15/2019 Manual Mesi Bus
24/68
The Data – Logger is having an internal architecture with 16 channels per
multiplexer card-signal conditioners and hence calibration for each card is
separate, but common for all channels on the same card. Inputs are divided
into three groups i.e. T/C, Linear and RTD. For each group one channel needs
to be calibrated. So, the user needs to calibrate any one channel of every card,
for each group. The signal conditioner consists of various blocks, first block
is multiplexer to select the channel, and then the signal is given to
instrumentation amplifier. After instrumentation amplifier signal is fed to the
another multiplexer for the selection of the group of particular input type &
then it is fed to the gain of 25 (which is common for all inputs) & offset tomake it unipolar signal. By calibrating preferably ‘E’ type T/C all other
type of thermocouple of this group are calibrated, as same gain is used. For
PT-100, there is a current source, which is used to pump the current into
RTD. Then comes the lead wire cancellation circuit and then same block of
instrumentation amplifier and gain circuit is used. The user needs to calibrate
only ‘E’ type t/c for T/C, 0-5 Vdc for Linear & pt-100 to calibrate all the
available input types in this Data – Logger.
CALIBRATION METHOD :
The data of the channel being observed will be updated after every unskipped
channel is scanned. So, to see the effect of reading change instantly, first of
all select the channel you want to calibrate and skip rest of the channels of
Data – Logger.
Now Press key of the operator terminal & then go in to Calibration Mode
as mentioned earlier. Now user can set the particular channel, which he wants
to calibrate. Only unskipped channels are allowed for calibration so user has
to unskip the channel, which he wants to calibrate for particular Input Type.
If, by mistake user selects the skipped channel, LCD shows the error message
“Calibration Not Allowed”. Select the channel, which one wants to calibrate.
Now if Input Type of selected channel is ‘T/C’ type, one can do the
calibration in any type of T/C input but for better accuracy it is advisable to
calibrate in “E” type of thermocouple. Now pressing and key user can
select the calibration parameter like AMB. Calibration, ZERO calibration,
SPAN calibration. Now select the particular calibration parameter & feed
with in the range preferably near min value of range for ZERO & near max.
value of range for SPAN( Please check the range of particular input type
before doing the calibration) through reliable calibrated source. For ambient
calibration user need to check the ambient temperature of the room where
Data – Logger is kept. While calibrating to match given input use numericalkeypad or & thekeys. First calibrate ZERO and then SPAN and repeat
‘M81/om/101, Issue # 01A-801992 - 24 -
-
8/15/2019 Manual Mesi Bus
25/68
the above procedure until zero value & span value both does not show any
error in reading.
Now if input type is “PT-100” then only zero scale & span scale of the
input needs to be calibrated. Feed the zero scale value & calibrate by
using numerical keypad or and key.
For linear input like 0-20mA, 4-20mA user has to feed 250Ω - 0.1%
resistance to convert it into voltage source. One needs to check zero scale
& span scale value for calibration of input type. Value less than zero scale
& more than span scale is not acceptable for any type of input. If the user
feeds a value, which is not in the range, LCD of the Operator Terminalwill display “Not Acceptable”. So it will not allow to calibrate the
channel. The Data – Logger will not allow to do the calibration, if there is
no input feed to the channel, which is selected for calibration. The LCD
will show the message “Calibration not Allowed”. User must feed the
particular value of zero scale & span scale while doing the calibration.
Calibration mode is also password protected so unauthorized person is not
allow to do the calibration. Password for calibration mode is same as
password for program mode/ configuration mode.
‘M81/om/101, Issue # 01A-801992 - 25 -
-
8/15/2019 Manual Mesi Bus
26/68
There are two modes of operation for the data logger viz. RUN mode,PROGRAM MENU mode. The selection of Program Menu mode is bykey in Operator terminal. Password is provided to avoid unauthorizedchanging of programmed /configuration data. Factory settable passwordis 22.
Any modification of data can be done only in program mode & configuration
mode. The data could be scan rate, date, time, print rate, control set points, alarm
limits and skip/unskip status of a channel etc…
The user can not modify any data in run mode but can verify the data. The run
has two sub modes viz. – Auto mode and Manual mode. Normally data logger
is kept in auto mode, where all unskipped channels data is displayed
sequentially at the programmed scan rate. In case user wants to continuously
monitor data of a single channel, it is possible in manual mode. Although
the selected channel is only displayed, internal scanning of other channels is
continued as usual.
The operation of the Operator terminal along with Data – Logger can be
summarized in the flow chart given on the next page. The Keyboard of the
Operator Terminal is as shown below.
LOGGING
DATAPRN
I/P
TYPESKIP
AUTO
MAN
masibus
AL1
MAN
AL2
RUN
AL3
PRG
FAULT
VFYCAL
AL4
POWER
RXD
TXD
Figure 5.1.1:- Membrane Drawing of Operator Terminal
‘M81/om/101, Issue # 01A-801992 - 26 -
-
8/15/2019 Manual Mesi Bus
27/68
The various keys and operating modes are described below:
The Keyboard on the Operator Terminal consists of four sets of Keys:
1) Numeric Keys2) Arrow Keys3) Program Keys4) Function Keys
1) Numeric Keys
The Numeric Keys are used for entering values of Process Variable, Alarm Values
etc.
2) Arrow Keys
The Arrow Keys are used for navigating into the different menus and their sub-
menus. The Arrow Keys are also used for increment and decrement operations as
well as for Shift Left and Shift Right operations.
3) Program Keys
The Program Keys consist of mainly three keys, The Run/Program Mode Key, The
Escape Key and The Enter Key.
The Run/Program Key is used to switch between the Run Mode and the ProgramMode.
The Escape Key is used to come out of any Menu or its Sub-menu. The Enter Key is used to acknowledge the data entered for Process Value, Alarm
Value, and Password etc.
4) Function Keys
There are five Function Keys present on the data-logger Operator Terminal to
enable the user to directly perform the defined functions. The five Function Keys are
The Auto/Man Key, The Skip Key, The Input Key, The Print Key and The Head
PRN Key.
The Auto/Man Key is used to switch between Manual Mode and Auto Mode ofthe instrument
The Skip Key is used to Skip a particular channel directly. The Input Key is used to configure the input type for a particular channel.
‘M81/om/101, Issue # 01A-801992 - 27 -
-
8/15/2019 Manual Mesi Bus
28/68
The Print Key is used to print the complete information of the selected channels. The Head PRN Key is used to log the data of the channel selected.
External Dimensions:-
192(W)* 96 (H) * 45(D)
DC Power Supply:-
Rated Supply Voltage : 24Vdc
Power Supply capacity : 10W or less Power Connector : 2 terminal Strip
Normal Operating Conditions:-
Ambient Temperature : 0 to 55°C Relative Humidity : 0 to 90%
MODULE SPECIFICATIONS
Display:-
16 x 2 Large Character LCD Display An LCD screen with Back-Light
Keypad:-
24 Keys with Membrane Keypad 12 Numeric Keys :- Used for inputting Numerical Value 4 Arrow Keys :- Used to select the required numerical value
input field when there is more than one onthe screen
3 Menu Keys :- Used to Select/Entering/Escaping Menuitems.
5 Function Keys:- Used for various functional operation
Mode & Alarm LED :-
Power ON LED to indicate unit is in ON condition. 4 Alarm LEDs for alarm indication & 1 Fault LED for Fault indication in the
system.
5 Mode LEDs used while programming/ calibrating/verifying various parameters.
‘M81/om/101, Issue # 01A-801992 - 28 -
-
8/15/2019 Manual Mesi Bus
29/68
‘M81 e # 01A-801992 - 29 -/om/101, Issu
Storage Memory:-
In-built 2K Bytes EEPROM to store various parameters
Communication:-
Communication Interface : RS 422 – 4 wire full duplex communication
Baud Rate : fixed 19200 Connector : Straight RJ 45 PCB mounted Protocol : MODBUS RTU
-
8/15/2019 Manual Mesi Bus
30/68
RS 232/RS 485
Data - Logger
Run Mode Program Menu
Manual Mode Auto Mode
Set Alm - 1
Set Alm - 2
Skip/Unskip
Print Data
Data-Logging
Ch
Unit Data
Print Time
Scan Time
Logging Time
Set Alm - 1
Set Alm - 2
Skip/Unskip
Print Data
Data-Logging
Ch
Unit Data
Print Time
Scan Time
Logging Time
Today'sDate
Program Mode
Configuration
Mode
Calibration
Mode
Vfy. Program
Mode Vfy. Conf. Mode
Input Type
Zero Scale
Span Scale
DP
Position
Select
Channel
Zero
Span
Triggering
Log
Parameter
Sr. No.
Baud Rate
Password
Hysterisis
RS 232/ RS 485 SEL
Today's
Time
Input Type
Zero Scale
Span Scale
DP
Position
Set Point
Type
Log
Parameter
Sr. No.
Baud Rate
Password
Hysterisis
Today's
Time
Today'sDate
RS 232
RS 485
Hr: Min: Sec
Date: Mon th: Year
Set Alm - 3
Set Alm - 4
Relay Conf.
Set Alm - 3
Set Alm - 4
Relay Conf.
Print on alarmPrint on alarm
RS 232/ RS 485 SERS 232/RS 485
Data - Logger
Run Mode Program Menu
Manual Mode Auto Mode
Set Alm - 1
Set Alm - 2
Skip/Unskip
Print Data
Data-Logging
Ch
Unit Data
Print Time
Scan Time
Logging Time
Set Alm - 1
Set Alm - 2
Skip/Unskip
Print Data
Data-Logging
Ch
Unit Data
Print Time
Scan Time
Logging Time
Today'sDate
Program Mode
Configuration
Mode
Calibration
Mode
Vfy. Program
Mode Vfy. Conf. Mode
Input Type
Zero Scale
Span Scale
DP
Position
Select
Channel
Zero
Span
Triggering
Log
Parameter
Sr. No.
Baud Rate
Password
Hysterisis
RS 232/ RS 485 SEL
Today's
Time
Input Type
Zero Scale
Span Scale
DP
Position
Set Point
Type
Log
Parameter
Sr. No.
Baud Rate
Password
Hysterisis
Today's
Time
Today'sDate
RS 232
RS 485
Hr: Min: Sec
Date: Mon th: Year
Set Alm - 3
Set Alm - 4
Relay Conf.
Set Alm - 3
Set Alm - 4
Relay Conf.
Print on alarmPrint on alarmPrint on alarm
RS 232/ RS 485 SE
‘M81/om/101, Issue # 01A-801992 - 30 -
-
8/15/2019 Manual Mesi Bus
31/68
‘M81/om/101, Issue # 01A-801992 - 31 -
mV
Volt
VL
Relay Conf.
Al
High
VH
Low
H-VH
L-VL
H-L
VH-VL
Print
Yes No
Data -Logging
Channel
Yes No
Log Parameter
Reset
Hold
Overlap
Baud Rate
19200
9600
4800
2400
Unit
Amp
mA
Ohm
MegOhm
Watt
KW
MW
Deg C
Deg F
mmWC
cmWC
mmHg
cmHg
IHg
mmH2O
IH2O
Kg/
cm2g
Kg/cm2
Kg/cm2a
psi
psi(a)
psi(g)
PC
FAULT
-
8/15/2019 Manual Mesi Bus
32/68
In Run Mode the Data – Logger can be operated either in Auto Mode or in Manual
Mode.
Auto Mode : The Data – Logger is usually kept in Auto Mode of Operation. The values
of all the unskipped channels are displayed sequentially at the set SCAN Time on the
Liquid Crystal Display (LCD) of the Operator Terminal. During this mode of operation,
the RUN led is ON. However, the MANUAL led is in OFF condition. In Auto Mode, the
user can view the “CH. PR –VAL ALM”, “Time :- “ or “Date:-“ parameter on the
second line of the LCD using the or key.
Manual Mode : The mode of operation of the Data – Logger can be changed to Manual
Mode by pressing the button. On pressing the same, the MAN led will glow.
One can go out of Manual Mode by pressing the same key again.
AUTO N MA
As soon as the key is pressed, the display will stop at the currently displayed
channel. To view the data of any other channel, one can make use of the numeric key
pad provided on the Operator Terminal or can make use of the or keys.
AUTNO
MA
As for example on pressing the key, the LCD of the Operator Terminal displays AUTNOMA
1 mVCH32 15:47 21/07
The cursor on the LCD will be blinking on the displayed channel. Enter the new channel
no using the numeric keypad or using the or keys. Suppose the new channel no
entered is 38, then the display will show
1 °CCH45 15:47 21/07
‘M81/om/101, Issue # 01A-801992 - 32 -
-
8/15/2019 Manual Mesi Bus
33/68
The Program Menu is entered by pressing the key. There are six modes in the Program
menu.
1) Status Mode2) Vfy. Configuration Mode.3) Vfy. Program Mode4) Calibration Mode5) Configuration Mode6) Program Mode
Same key can be pressed again to go back to RUN Mode.
1) STATUS MODETo enter Status Mode, press the key. The Status Mode had sub menus as shown in the
flow diagram. The sub menu can be entered by pressing the key. The different
submenus of the Status Mode can be accessed by using the and keys. Once a
particular sub menu is selected, press key. The Status Mode in brief gives
information about the complete Data Acquisition System like card information (type of
card & slot No. for eg Slot No.3 Relay Card), status of computer and printer connected
to the Data – Logger and also status of memory and version no. of the software.
2) VFY. CONFIGURATION MODE :To enter Vfy. Configuration Mode, use key after pressing the key. The Vfy.Configuration Mode has sub menus as shown in the flow diagram. The sub menu can be
entered by pressing the key. The different submenus of the Vfy. Configuration Mode
can be accessed by using the and keys. Once a particular sub menu is selected,
press key. This will display the current settings of the selected parameter. In this
mode one can only view the parameters set but cannot modify them.
3) VFY. PROGRAM MODE :To enter Vfy. Program Mode, use key after pressing the key. The Vfy Program
Mode has sub menus as shown in the flow diagram. The sub menu can be entered by pressing the key. The different sub menus of the Vfy. Program Mode can be accessed
by using the and keys. Once a particular sub menu is selected, press the key.
This will display the current settings of the selected parameter. In this mode one can only
view the parameters set but cannot modify them.
‘M81/om/101, Issue # 01A-801992 - 33 -
-
8/15/2019 Manual Mesi Bus
34/68
4) CALIBRATION MODE :To enter Calibration Mode, press twice the key after pressing the key. The
Calibration Mode has sub menus as shown in the flow diagram. The sub menu can beentered by pressing the key. The LCD will display
1
Select Channel
The cursor will be on the Channel No. Once the desired channel is entered by pressing
the numeric keypad or the and keys, press the key. The LCD will display
K Amb 34.5
I/P Cal. Value
The cursor will be on the Amb. The Amb value can be changed using the numeric
keypad or the or keys. Once the ambient is set, press key. The LCD will
display “ACCEPTABLE”. Now using the key, go to Zero parameter.. The LCD will
display
K Zero 0
I/P Cal. Value
The cursor will be on the Zero. Press the key. The Zero value can be changed using
the numeric keypad or the or keys. Once the Zero is set, press the key.The LCD will display “ACCEPTABLE”. Now using the key, go to Span parameter.
The LCD will display
K Span 1200
I/P Cal. Value
The cursor will be on the Span. Press the key. The Span value can be changed using
the numeric keypad or the or keys. Once the Span is set, press the key.
The LCD will display “ACCEPTABLE”. Once the Calibration is set, press the key to
come out of the sub menu. Pressing the same key once again will come back to theCalibration Mode Menu. Press the key to come back to RUN Mode.
The Ambient parameter will not be displayed during calibration when the Input Type is
RTD or Linear.
‘M81/om/101, Issue # 01A-801992 - 34 -
-
8/15/2019 Manual Mesi Bus
35/68
-
8/15/2019 Manual Mesi Bus
36/68
Zero Scale:This parameter can be set only when Input type is linear. The Zero Scale is set
depending on the Input Type of the particular channel as per user requirement.
Span Scale:This parameter can be set only when Input type is linear. The Span Scale is set
depending on the Input Type of the particular channel as per user requirement.
DP Position:This parameter can be set only when Input type is linear. The DP Position can be
set between 0 to 4 for a particular channel depending upon the user requirement.
Triggering:
This parameter can be set as YES/NO as per user requirement. This parameter is basically used for Data – Logging. It should be ensured that when triggering
mode is set to YES, the Centronics printer cable should be removed form the
parallel port of the CPU card.
Log Parameter:Data Logging can be configured in any one of the three ways as per user
requirement. They are Reset, Hold and Overlap.
Sr. No:This parameter is used to assign the Sr. No. to the Instrument for Serial
Communication using RS – 232/RS – 422.
Baud Rate:The Baud Rate can be set as per user requirement. The Baud Rates that can be set
are 19200, 9600 and 4800.
Password:Password is set for entering into Program Mode, Configuration Mode and
Calibration Mode. The value of Password can be set between 0 to 65535. Factory
set password is 22. User can also change the password. User can avoid the
password protection by making it zero.
Hysteresis:The Hysteresis parameter is set for alarm limits. This parameter is can be set
individually for all channels. The Hysteresis value is set between 0.1% to 9.9%
of the complete range.
RS 232/RS 485:In this one can configure the serial communication to be RS 232 or RS 485
depending on the requirement. Select RS 232 or RS 485 using the up/down (
or )arrows and confirm the selection using enter key.
‘M81/om/101, Issue # 01A-801992 - 36 -
-
8/15/2019 Manual Mesi Bus
37/68
Today’s Time:The current time can be set in the Data – Logger by going into the Configuration
Mode. Press key to go into sub menu. Using the key go to today’s Time.Press again to enter the Today’s Time Parameter. The LCD will display
13 : 25 : 30Hour Min Sec
The cursor position will be on Hour parameter. Set the required hour using the
the or thekeys. Then press key. The LCD will show “ACCEPTABLE”.
Repeat the same procedure to change the Min and Sec parameter. Once the
Today’s Time Parameter is set, press the Key to come out of the Today’s
Time sub menu. Pressing the same key once again will come back to the
Configuration Mode Menu. Press the key to come back to RUN Mode.
Today’s Date: The current date can be set in the Data – Logger by going into the Configuration
Mode. Press key to go into sub menu. Using key go to Today’s Date.
Press the again to enter the Today’s Date Parameter. The LCD will display
14 : 2 : 3Date Month Year
The cursor position will be on Date parameter. Set the required date using thethe or he keys. Then press key. The LCD will show “ACCEPTABLE”.
Repeat the same procedure to change the Month and Year parameter. Once the
Today’s Date Parameter is set, press key to come out of the Today’s Date sub
menu. Pressing the same key once again will come back to the Configuration
Mode Menu. Press the key to come back to RUN Mode.
Print on Alarm:In this one can configure datalogger to print on alarm for the channel selected in
print data section of program mode. Datalogger prints the data on alarm in that
particular channel. Select Yes or No using the up/down ( or )arrows and
confirm the selection using enter key.
6) PROGRAM MODE :The Program Mode has sub menus as shown in the flow diagram. The sub menu can be
entered by pressing the key. The different sub menus of the Program Mode can be
accessed by using the and keys. Once a particular sub menu is selected, press the
the key. This will display the current settings of the selected parameter. The selected
parameter can be modified using the numeric key pad or the and keys. Once the
parameters are modified, press key. The LCD will display “ACCEPTABLE”.
Press the key to come out of the selected sub menu. Pressing the same key again, one
comes back to the Program Mode Menu.
‘M81/om/101, Issue # 01A-801992 - 37 -
-
8/15/2019 Manual Mesi Bus
38/68
-
8/15/2019 Manual Mesi Bus
39/68
Data Logging:If this parameter is set then data logging of the particular unskipped channel will
be carried out at the set Logging Time. Do not change this parameter duringlogging otherwise memory will be reset and start new data logging as per the
changes made.
Unit Data:This parameter is used to set the unit for the Process Value of the Input Type
selected for the particular channel.
Print Time:The Print Time value can be set between 0 to 99 Minutes. Printing of data of all
the unskipped channels will be carried out at the set time interval.
Scan Time:The Scan Time value can be set between 0 to 99 Seconds. Scanning of all the
unskipped channels will be carried out at the set time interval.
Logging Time:The Logging Time value can be set between 0 to 99 Minutes. Logging of data of
all the unskipped channels will be carried out at the set time interval.
Relay Configuration:The Relay configuration is enabled when a relay card is present in the Data –
Logger. To enter Relay configuration press key. The LCD will display
01 45 NO High
RL CH Sel Conf.
The first term RL on the lower line of the LCD display represents Relay no. The
Relay no can be changed by using the and keys. Once the desired Relay
is set, press the key. The cursor will shift to CH which represents the Channel
no. Any relay can be configured for any channel. The new channel no. can be
entered by using the and keys. Once the desired Channel is set, press thethe key. The cursor will shift to Sel. The user can select YES or NO using the the
and keys. Once the selection is done, press the key. The LCD will
display “ACCEPTABLE”. Now press key to shift to Conf. The user can set
any type of logic (as shown in flowchart) using the and keys. Once the
desired logic is set press key. The LCD will display “ACCEPTABLE”.
Press key to come out of Relay Configuration. In Relay configuration the
the key can also be used to switch between RL, CH, Sel and Conf .
Note:The key is used to undo the numeric parameters in all the modes of operation of the
Data – Logger except the RUN Mode.
‘M81/om/101, Issue # 01A-801992 - 39 -
-
8/15/2019 Manual Mesi Bus
40/68
Figure 5.6.1:- Front View Dimension Details
Figure 5.6.2:- Clamp Dimension Details
‘M81/om/101, Issue # 01A-801992 - 40 -
-
8/15/2019 Manual Mesi Bus
41/68
Figure 5.6.3:- Back View Details
Figure 5.6.4:- Panel Cut Out Details for Operator Terminal
‘M81/om/101, Issue # 01A-801992 - 41 -
-
8/15/2019 Manual Mesi Bus
42/68
MODBUS protocol defines a message structure that controllers will recognizeand use, regardless of the type of networks over which they communicate. It
describes the process a controller uses to request access to another device, how it
will respond to requests from the other devices, and how errors will be detected
and reported. It establishes a common format for the layout and contents of
message fields. During communications on a MODBUS network, the protocol
determines how each controller will know its device address, recognize a
message addressed to it, determine the kind of action to be taken, and extract any
data or other information contained in the message. If a reply is required, the
controller will construct the reply message and send it using MODBUS protocol.
On other networks, messages containing MODBUS protocol are imbedded into
the frame or packet structure that is used on the network.
The Query–Response Cycle
Figure 6.2.1:- Master–Slave Query–Response Cycle
‘M81/om/101, Issue # 01A-801992 - 42 -
-
8/15/2019 Manual Mesi Bus
43/68
Communication Interface Based on EIA RS-485 & RS 232
Communication method Half-duplex communication start
stop synchronous.
Communication Speed 4800/9600/19200 bps selectable by key.
Parity None.
Communication Protocol Modbus RTU.
Connectable number of
unit
Max.32 unit per host computer when RS485 selected
Communication error
detection
CRC check
The Serial Transmission Modes
RTU ModeWhen controllers are setup to communicate on a MODBUS network using RTU
(Remote Terminal Unit) mode, each 8–bit byte in a message contains two 4–bit
hexadecimal characters. The main advantage of this mode is that its greatercharacter density allows better data throughput than ASCII for the same baud
rate. Each message must be transmitted in a continuous stream.
The format for each byte in RTU mode is:
Coding System:
8–bit binary, hexadecimal 0–9, A–F
Two hexadecimal characters contained in each
8–bit field of the message
Bits per Byte:
1 start bit8 data bits, least significant bit sent first
1 bit for even/odd parity; no bit for no parity
1 Stop bit if parity is used; 2 bits if no parity
Error Check Field:
Cyclical Redundancy Check (CRC)
‘M81/om/101, Issue # 01A-801992 - 43 -
-
8/15/2019 Manual Mesi Bus
44/68
How Numerical Values are expressed
Unless specified otherwise, numerical values (such as addresses, codes, or data)
are expressed as decimal values in the text of this section. They are expressed as
hexadecimal values in the message fields of the figures,
Data Addresses in MODBUS Messages
All data addresses in MODBUS messages are referenced to zero. The first
occurrence of a data item is addressed as item number zero. For example: The
coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in
the data address field of a MODBUS message. Coil 127 decimal is addressed as
coil 007E hex (126 decimal). Holding register 40001 is addressed as register
0000 in the data address field of the message. The function code field already
specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is
implicit. Holding register 40108 is addressed as register 006B hex (107 decimal).
Function Codes Used by Data – Logger
Function code Action
01 Read Coil Status
03 Read Holding Registers
05 Force Single Coil
06 Preset Single Register
16 Preset Multiple Register
07 Read Exception Status
17 Report Slave ID
Table 1: Function Codes and action
‘M81/om/101, Issue # 01A-801992 - 44 -
-
8/15/2019 Manual Mesi Bus
45/68
01 Read Coil Status
DescriptionRead the ON/OFF status of discrete outputs (0X references, coils) in the slave.
Broadcast is not supported .
Query
The query message specifies the starting coil and quantity of coils to be read.
Coils are addressed starting at zero: coils 1–16 are addressed as 0–15. Here is an
example of a request to read coils 20–56 from slave device 17:
Figure 6.3.1:- Read Coil Status – Query
Response
The coil status in the response message is packed as one coil per bit of the data
field. Status is indicated as: 1 = ON; 0 = OFF. The LSB of the first data byte
contains the coil addressed in the query. The other coils follow toward the highorder end of this byte, and from ‘low order to high order’ in subsequent bytes. If
the returned coil quantity is not a multiple of eight, the remaining bits in the final
data byte will be padded with zeros (toward the high order end of the byte). The
Byte Count field specifies the quantity of complete bytes of data. Here is an
example of a response to the query (in fig 5):
Figure 6.3.2:- Read Coil Status – Response
‘M81/om/101, Issue # 01A-801992 - 45 -
-
8/15/2019 Manual Mesi Bus
46/68
The status of coils 27–20 is shown as the byte value CD hex, or binary 1100
1101. Coil 27 is the MSB of this byte, and coil 20 is the LSB. Left to right, the
status of coils 27 through 20 is: ON–ON–OFF–OFF–ON–ON–OFF–ON. By
convention, bits within a byte are shown with the MSB to the left, and the LSB to
the right. Thus the coils in the first byte are ‘27 through 20’, from left to right.
The next byte has coils ‘35 through 28’, left to right. As the bits are transmitted
serially, they flow from LSB to MSB: 20 . . . 27, 28 . . . 35, and so on. In the last
data byte, the status of coils 56–52 is shown as the byte value 1B hex, or binary
0001 1011. Coil 56 is in the fourth bit position from the left, and coil 52 is the
LSB of this byte. The status of coils 56 through 52 is: ON–ON–OFF–ON–ON.
Note how the three remaining bits (toward the high order end) are zero–filled.
03 Read Holding Registers
Description
Read the binary contents of holding registers (4X references) in the slave.
Broadcast is not supported.
Query
The query message specifies the starting register and quantity of registers to be
read. Registers are addressed starting at zero: registers 1–16 are addressed as 0–
15. Here is an example of a request to read registers 40108–40110 from slave
device 17:
Figure 6.3.3:- Read Holding Registers – Query
Response
The register data in the response message are packed as two bytes per register,
with the binary contents right justified within each byte. For each register, the
first byte contains the high order bits and the second contains the low order bits.
The response is returned when the data is completely assembled. Here is an
example of a response to the query (in fig 7):
The contents of register 40108 are shown as the two byte values of 02 2B hex, or
555 decimal. The contents of registers 40109–40110 are 00 00 and 00 64 hex, or
0 and 100 decimal.
‘M81/om/101, Issue # 01A-801992 - 46 -
-
8/15/2019 Manual Mesi Bus
47/68
Figure 6.3.4:- Read Holding Registers – Response
05 Force Single Coil
Description
Force a single coil (0X reference) to either ON or OFF. When broadcast, the
function forces the same coil reference in all attached slaves.
Query
The query message specifies the coil reference to be forced. Coils are addressed
starting at zero: coil 1 is addressed as 0. The requested ON/OFF state is specified
by a constant in the query data field. A value of FF 00 hex requests the coil to be
ON. A value of 00 00 requests it to be OFF. All other values are illegal and will
not affect the coil. Here is an example of a request to force coil 173 ON in slave
device 17:
‘M81/om/101, Issue # 01A-801992 - 47 -
-
8/15/2019 Manual Mesi Bus
48/68
Figure 6.3.5:- Force Single Coil – Query
Response
The normal response is an echo of the query, returned after the coil state has been
forced. Here is an example of a response to the query:
Figure 6.3.6:- Force Single Coil – Response
06 Preset Single Register
Description
Presets a value into a single holding register (4X reference). When broadcast the
function presets the same register reference in all attached slaves.
‘M81/om/101, Issue # 01A-801992 - 48 -
-
8/15/2019 Manual Mesi Bus
49/68
Query
The query message specifies the register reference to be preset. Registers areaddressed starting at zero: register 1 is addressed as 0. The requested preset value
is specified in the query data field. M84 and 484 controllers use a 10–bit binary
value, with the six high order bits set to zeros. All other controllers use 16–bit
values. Here is an example of a request to preset register 40002 to 00 03 hex in
slave device 17:
Figure 6.3.7:- Preset Single Register – Query
Response
The normal response is an echo of the query, returned after the register contents
have been preset. Here is an example of a response to the query :
Figure 6.3.8:- Preset Single Register – Response
‘M81/om/101, Issue # 01A-801992 - 49 -
-
8/15/2019 Manual Mesi Bus
50/68
16 Preset Multiple Registers
Description: Presets values into a sequence of holding registers (4X references).
When broadcast, the function presets the same register references in all attached
slaves.
Query: The query message specifies the register references to be preset.
Registers are addressed starting at zero: register 1 is addressed as 0. The
requested preset values are specified in the query data field. All other controllers
use 16–bit values. Data is packed as two bytes per register. Here is an example of
a request to preset two registers starting at 40002 to 00 0A and 01 02 hex, in
slave device 17:
Figure 6.3.9:- write multiple Registers – Query
Response: The normal response returns the slave address, function code, starting
address, and quantity of registers preset. Here is an example of a response to the
query shown above.
Figure 6.3.10:- write multiple Registers – Response
‘M81/om/101, Issue # 01A-801992 - 50 -
-
8/15/2019 Manual Mesi Bus
51/68
07 Read Exception Status
Description: Reads the contents of eight Exception Status coils within the slavecontroller. Certain coils have predefined assignments in the various controllers.
Other coils can be programmed by the user to hold information about the
controller’s status, for example, ‘machine ON/OFF’, ‘heads retracted’, ‘safeties
satisfied’, ‘error conditions exist’, or other user–defined flags. Broadcast is not
supported. The function provides a simple method for accessing this information;
because the Exception Coil references are known (no coil reference is needed in
the function).
Query
Here is an example of a request to read the exception status in slave device 17:
Figure 6.3.11:- Read Exception Status – Query
Response
The normal response contains the status of the eight Exception Status coils. The
coils are packed into one data byte, with one bit per coil. The status of the lowest
coil reference is contained in the least significant bit of the byte. Here is an
example of a response to the query on the next page:
Figure 6.3.12:- Read Exception Status – Response
In this example, the coil data is 6D hex (0110 1101 binary). Left to right, the
coils are: OFF–ON–ON–OFF–ON–ON–OFF–ON. The status is shown from the
highest to the lowest addressed coil.
‘M81/om/101, Issue # 01A-801992 - 51 -
-
8/15/2019 Manual Mesi Bus
52/68
17 (11 Hex) Report Slave ID
DescriptionReturns a description of the type of controller present at the slave address, the
current status of the slave Run indicator, and other information specific to the
slave device. Broadcast is not supported.
Query
Here is an example of a request to report the ID and status of slave device 17:
Figure 6.3.13:- Report Slave ID – Query
Response
The format of a normal response is shown below. The data contents are specific
to each type of controller. They are listed on the following pages.
Figure 6.3.14:- Report Slave ID – Response
‘M81/om/101, Issue # 01A-801992 - 52 -
-
8/15/2019 Manual Mesi Bus
53/68
Except for broadcast messages, when a master device sends a query to a slavedevice it expects a normal response. One of four possible events can occur from
the master’s query: If the slave device receives the query without a
communication error, and can handle the query normally, it returns a normal
response. If the slave does not receive the query due to a communication error,
no response is returned. The master program will eventually process a timeout
condition for the query. If the slave receives the query, but detects a
communication error (parity, LRC, or CRC), no response is returned. The master
program will eventually process a timeout condition for the query. If the slave
receives the query without a communication error, but cannot handle it (for
example, if the request is to read a non-–existent coil or register), the slave will
return an exception response informing the master of the nature of the error. The
exception response message has two fields that differentiate it from a normal
response:
Function Code Field: In a normal response, the slave echoes the function code
of the original query in the function code field of the response. All function codes
have a most–significant bit (MSB) of 0 (their values are all below 80
hexadecimal). In an exception response, the slave sets the MSB of the function
code to 1. This makes the function code value in an exception response exactly
80 hexadecimal higher than the value would be for a normal response. With the
function code’s MSB set the master’s application program can recognize theexception response and can examine the data field for the exception code.
Data Field: In a normal response, the slave may return data or statistics in the
data field (any information that was requested in the query). In an exception
response, the slave returns an exception code in the data field. This defines the
slave condition that caused the exception.
Figure 6.4.1:- Master Query and Slave Exception Response
‘M81/om/101, Issue # 01A-801992 - 53 -
-
8/15/2019 Manual Mesi Bus
54/68
In this example, the master addresses a query to slave device 10 (0A hex). The
function code (01) is for a Read Coil Status operation. It requests the status of the
coil at address 1245 (04A1 hex). Note that only that one coil is to be read, as
specified by the number of coils field (0001). If the coil address is non-–existent
in the slave device, the slave will return the exception response with the
exception code shown (02). This specifies an illegal data address for the slave.
Exception Codes
Code Name Meaning
01) ILLEGAL FUNCTION:
The function code received in the query is not an allowable action for the slave.
If a Poll Program Complete command was issued, this code indicates that no
program function preceded it.
02) ILLEGAL DATA ADDRESS:
The data address received in the query is not an allowable address for the slave.
03) ILLEGAL DATA VALUE:
A value contained in the query data field is not an allowable value for the slave.
04) SLAVE DEVICE FAILURE:An unrecoverable error occurred while the slave was attempting to perform the
requested action.
05) ACKNOWLEDGE:
The slave has accepted the request and is processing it, but a long duration of
time will be required to do so. This response is returned to prevent a timeout
error from occurring in the master. The master can next issue a Poll Program
Complete message to determine if processing is completed.
06) SLAVE DEVICE BUSY:
The slave is engaged in processing a long–duration program command. Themaster should retransmit the message later when the slave is free.
07) NEGATIVE ACKNOWLEDGES:
The slave cannot perform the program function received in the query. This code
is returned for an unsuccessful programming request using function code 13 or
14 decimal. The master should request diagnostic or error information from the
slave.
08) MEMORY PARITY ERROR:
The slave attempted to read extended memory, but detected a parity error in the
memory. The master can retry the request, but service may be required on theslave device.
‘M81/om/101, Issue # 01A-801992 - 54 -
-
8/15/2019 Manual Mesi Bus
55/68
• Data – Logger 8040/Operator Terminal does not Switch ON.
♦ Check the Mains Cord.
♦ Check fuse, if blown off replace it
♦ Check Power ON switch/ Power ON Indication LED.
♦ Check the S.M.P.S. O/P voltages of the Unit and the Operator Terminal
• Printing is not proper unknown characters printed/ unit isn’t printing.
♦ Check for the loose connection of printer cable connector.
♦ Check the printer cable
♦ Check the printer settings.
♦ Replace CPU card.
• Communication Problem between the Unit and Host PC/Operator Terminal
♦ Check the cabling.
♦ Check the serial No.
♦ Check the RS-485 to RS232 converter.
♦ Check the serial port of the computer & baud rate settings, etc.
♦ Check RJ – 45 connections between the Data – Logger 8040 and the OperatorTerminal.
♦ Replace the CPU
• Certain keys on the Operator Terminal not working. ♦ Check for Communication between the Unit and the Operator Terminal.
♦ Ensure that the unit is in program mode.
♦ If a particular row is failed, one of the lines of lay board matrix may behaving problem.
• Date/time other parameter changes when unit is restarted.
♦ Check the NVRAM on the CPU card. If not ok, replace the same.
• Calibration of the unit is doubted to have drifted.
♦
Calibrate the unit as explained in the manual. Select the proper methodaccording to your data - logger input type.
• Reading indicated by data - logger is unstable
♦ Check the process input.
♦ Ensure the perfect EARTHING to the unit & Neutral should not be floating.
♦ Shielded cables should used for input. Shield should be EARTHED near theunit only.
♦ Check any of the RTD’s is not getting EARTHED or having weak insulationwith respect to earth. If so, remove that RTD and check the cabling.
♦ Check the lead resistance of all the three arms of RTD’s. All the three leads
should have same lead resistance. If no, change the cables.
‘M81/om/101, Issue # 01A-801992 - 55 -
-
8/15/2019 Manual Mesi Bus
56/68
• In linear type input the unit shows false reading or ‘OVER’ or ‘UNDER’.♦ Check for the polarity of the I/P connections.
♦ Check that the 250Ω resistor is connected across the I/P terminals, if the I/Ptype is 4 – 20 mA.
♦ Check the current I/P coming from the field, it may be below 4 or over 20mA.
♦ Check for the proper range programmed in that channel.
• In thermocouple type input the reading indicated has got some error.
♦ Check for the proper I/p type selected.
♦ Ensure that the compensating cables used are of proper type and connected in proper direction.
♦ Check the calibration of the unit.
All inputs coming from the field must be shielded and shield should earthen near the
Data – Logger only.
‘M81/om/101, Issue # 01A-801992 - 56 -
-
8/15/2019 Manual Mesi Bus
57/68
MODBUS Protocol detail used in Data logger 8040
General Query Frame
0 Device Address
1 Function Code
2 Type
3 Channel No
4 No of registers Low byte
5 No of registers High byte
6 Byte Count
7 Hi Data
8 Low Data
9 CRC byte Lo10 CRC byte Hi
Table: M.1
Types are as followed:
If function (Type as above) is 11 (Common00 PV (Process Value)
01 IP (Input Type)
02 SET ALARM - 4
03 SET ALARM – 3
04 SET ALARM – 2
05 SET ALARM -1
06 ZERO
07 SPAN
08 HYSTRESIS
09 DP
10 UNIT
11 Common Parameter
12 Ambient
13 spare
14 Open Sensor Indication
15 Channel legend
16 Header Legend17 Set Alarm - 1
18 Set Alarm - 2
19 Set Alarm - 3
20 Set Alarm - 4
Parameter) Then it will be followed by sub-
Function code which is Ch. no for other
Function code
Table: M.2
Table: M.3
11.00 SCAN TIME
11.01 PRINT TIME
11.02 LOGGING TIME
11.03 SET POINT
11.04 RELAY TYPE
11.05 SLAVE ID
11.06 BAUD RATE
11.07 PASSWORD
11.08 SET Point, Open Sensor,
Alarm Latch, Relay Control
11.09 PRINTER
11.10 TIME - SEC
11.11 TIME – MIN11.12 TIME - HOUR
11.13 DATE - DAY
11.14 DATE - MONTH
11.15 DATE - YEAR
11.16 CARD INFORMATION
11.17 RECORD POINT
11.18 RELAY CONFIGURATION
‘M81/om/101, Issue # 01A-801992 - 57 -
-
8/15/2019 Manual Mesi Bus
58/68
Write Report Slave ID:1. Write Slave Id
Query: {DeviceNo, 0x11, CRCLo, CRCHi}
Response: {DeviceNo, 0x11, RegLo, RegHi, 0xff, Card1, Card2……, Card10, CRCLo,
CRCHi}
Card Types:
1 Relay Output cards 0x81
2 Analog Input cards 0x7f3 Analog Output cards 0x83
4 Digital Input cards 0x84
5 Digital Output cards 0x82
6 Fault Output cards 0x80
Write Input Values:
2. Write Process ValueQuery: {DeviceNo, 0x10, 0x00, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x00, ChNo, 0x00, 0x01, CRCLo, CRCHi}
3. Write Input TypeQuery: {DeviceNo, 0x10, 0x01, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x01, ChNo, 0x00, 0x01, CRCLo, CRCHi}
4. Write Set Alarm 4Query: {DeviceNo, 0x10, 0x02, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x02, ChNo, 0x00, 0x01, CRCLo, CRCHi}
‘M81/om/101, Issue # 01A-801992 - 58 -
-
8/15/2019 Manual Mesi Bus
59/68
5. Write Set Alarm 3Query: {DeviceNo, 0x10, 0x03, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x03, ChNo, 0x00, 0x01, CRCLo, CRCHi}
6. Write Set Alarm 2Query: {DeviceNo, 0x10, 0x04, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x04, ChNo, 0x00, 0x01, CRCLo, CRCHi}
7. Write Set Alarm 1
Query: {DeviceNo, 0x10, 0x05, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,CRCHi}
Response: {DeviceNo, 0x10, 0x05, ChNo, 0x00, 0x01, CRCLo, CRCHi}
8. Write Zero ValueQuery: {DeviceNo, 0x10, 0x06, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x06, ChNo, 0x00, 0x01, CRCLo, CRCHi}
9. Write Span ValueQuery: {DeviceNo, 0x10, 0x07, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x07, ChNo, 0x00, 0x01, CRCLo, CRCHi}
10. Write HystQuery: {DeviceNo, 0x10, 0x08, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x08, ChNo, 0x00, 0x01, CRCLo, CRCHi}
11. Write DP positionQuery: {DeviceNo, 0x10, 0x09, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x09, ChNo, 0x00, 0x01, CRCLo, CRCHi}
12. Write UnitQuery: {DeviceNo, 0x10, 0x10, ChNo, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x10, ChNo, 0x00, 0x01, CRCLo, CRCHi}
‘M81/om/101, Issue # 01A-801992 - 59 -
-
8/15/2019 Manual Mesi Bus
60/68
Write Common Parameters
13. Write Scan TimeQuery: {DeviceNo, 0x10, 0x0B, 0x00, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x00, 0x00, 0x01, CRCLo, CRCHi}
14. Write Print TimeQuery: {DeviceNo, 0x10, 0x0B, 0x01, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x01, 0x00, 0x01, CRCLo, CRCHi}
15. Write Logging TimeQuery: {DeviceNo, 0x10, 0x0B, 0x02, 0x00, 0x02, 0x04, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x02, 0x00, 0x02, CRCLo, CRCHi}
16. Write Set PointQuery: {DeviceNo, 0x10, 0x10, 0x0B, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x00, 0x01, 0x02, CRCLo, CRCHi}
17. Write RelayQuery: {DeviceNo, 0x10, 0x0B, 0x04, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x03, 0x0B, 0x04, 0x00, 0x01, CRCLo, CRCHi}
18. Write Device IDQuery: {DeviceNo, 0x10, 0x0B, 0x05, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x05, 0x00, 0x01, CRCLo, CRCHi}
19. Write Baud RateQuery: {DeviceNo, 0x10, 0x0B, 0x06, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x06, 0x00, 0x01, CRCLo, CRCHi}
‘M81/om/101, Issue # 01A-801992 - 60 -
-
8/15/2019 Manual Mesi Bus
61/68
20. Write PasswordQuery: {DeviceNo, 0x10, 0x0B, 0x07, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x07, 0x00, 0x01, CRCLo, CRCHi}
21. Write Relay, Alarm, open Sensor, Set pointQuery: {DeviceNo, 0x10, 0x0B, 0x08, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x08, 0x00, 0x01, CRCLo, CRCHi}
22. Write Printer
Query: {DeviceNo, 0x10, 0x0B, 0x09, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x09, 0x00, 0x01, CRCLo, CRCHi}
23. Write Current Time (Second)Query: {DeviceNo, 0x10, 0x0B, 0x0A, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0A, 0x00, 0x01, CRCLo, CRCHi}
24. Write Current Time (Minute)Query: {DeviceNo, 0x10, 0x0B, 0x0B, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0B, 0x00, 0x01, CRCLo, CRCHi}
25. Write Current Time (Hour)Query: {DeviceNo, 0x10, 0x0B, 0x0C, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0C, 0x00, 0x01, CRCLo, CRCHi}
26. Write Current DateQuery: {DeviceNo, 0x10, 0x0B, 0x0D, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0D, 0x00, 0x01, CRCLo, CRCHi}
27. Write Current MonthQuery: {DeviceNo, 0x10, 0x0B, 0x0E, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0E, 0x00, 0x01, CRCLo, CRCHi}
‘M81/om/101, Issue # 01A-801992 - 61 -
-
8/15/2019 Manual Mesi Bus
62/68
28. Write Current YearQuery: {DeviceNo, 0x10, 0x0B, 0x0F, 0x00, 0x01, 0x02, HiData, LoData, CRCLo,
CRCHi}
Response: {DeviceNo, 0x10, 0x0B, 0x0F, 0x00, 0x01, CRCLo, CRCHi}
Write Status Values:
29. Write Skip / Unskip StatusQuery: {DeviceNo, 0x05, 0x00, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x05, 0x00, ChNo, HiData, LoData, CRCLo, CRCHi}
30. Write Print StatusQuery: {DeviceNo, 0x05, 0x01, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x05, 0x01, ChNo, HiData, LoData, CRCLo, CRCHi}
31. Write Logging StatusQuery: {DeviceNo, 0x05, 0x02, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x05, 0x02, ChNo, HiData, LoData, CRCLo, CRCHi}
32. Write Relay StatusQuery: {DeviceNo, 0x05, RelayNo, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x05, RelayNo, ChNo, HiData, LoData, CRCLo, CRCHi}
Read Input Values:
33. Read Process ValueQuery: {DeviceNo, 0x03, 0x00, ChNo, 0x00, 0x10, CRCLo, CRCHi}
Query for common Parameter: {DeviceNo, 0x03, 0x00, ChNo, 0x00, 0x01, CRCLo,
CRCHi}
Response: {DeviceNo, CRCLo, CRCHi}
N o t e : Same sequence for other input values. Only change
function code and type similar to write commands.
‘M81/om/101, Issue # 01A-801992 - 62 -
-
8/15/2019 Manual Mesi Bus
63/68
Sr.No Parameter Absolute
address
Type Minimum
value
Maximum
value
Access
Type
1 Skip status 00001 Bit 0 1 R/W
2 Print Ch. status 00257 Bit 0 1 R/W
3 Log Ch. Status 00513 Bit 0 1 R/W4 Open Sensor 00769 Bit 0 1 R
5 Alarm 1 status 01025 Bit 0 1 R
6 Alarm 2 status 01281 Bit 0 1 R
7 Alarm 3 status 01537 Bit 0 1 R
8 Alarm 4 status 01793 Bit 0 1 R
9 Process Value 40001 Integer Table: M.4 Table: M.4 R/W
10 Input Type 40257 Integer 0 13 R/W
11 Set Alarm 4 40513 Integer Table: 4.2.1 Table: 4.2.1 R/W
12 Set Alarm 3 40769 Integer Table: 4.2.1 Table: 4.2.1 R/W
13 Set Alarm 2 41025 Integer Table: 4.2.1 Table: 4.2.1 R/W
14 Set Alarm 1 41281 IntegerTable: 4.2.1 Table: 4.2.1
R/W15 Zero 41537 Integer Table: 4.2.1 Table: 4.2.1 R/W
16 Span 41793 Integer Table: 4.2.1 Table: 4.2.1 R/W
17 Hysteresis 42049 Integer 0.1% 9.9% R/W
18 DP 42305 Integer 0 4 R/W
19 Unit 42561 Integer 0 58 R/W
20 Scan Time 42817 Integer 1sec 99sec R/W
21 Print Time 42818 Integer ----- ----- R/W
22 Log Time(R) 42819 Integer 0 59 R
23 Log Time(W) 44353 Integer 0 59 W
24 Logging Status 42820 Integer 0 1 R/W
25 Log Mode 42821 Integer 0 2 R/W
26 Slave ID 42822 Integer 1 99 R/W
27 Baudrate 42823 Integer 0 2 R/W
28 Password 42824 Integer 0 65535 R/W
29 Alarm Configuration 42825 Integer * * R/W
29 Sec 42827 Integer 0 59 R/W
30 Min 42828 Integer 0 59 R/W
31 Hour 42829 Integer 0 23 R/W
32 Date 42830 Integer 1 31 R/W
33 Month 42831 Integer 1 12 R/W
34 Year 42832 Integer 1 99 R/W
35 Open Sensor Modbus
[Alarm status]
42835 Integer 0 1 R/W
36 Ambient 43073 Integer ----- ----- R/W
37 Open Sensor Indication 43585 Integer 0 1 R/W
38 Alarm 1 Status 44353 Integer 0 1 R
39 Alarm 2 Status 44609 Integer 0 1 R
40 Alarm 3 Status 44865 Integer 0 1 R
41 Alarm 4 Status 45121 Integer 0 1 R
Table: M.4 Note: All above address are starting address for that particular group. End address will be starting address + 160.
for e.g. starting add [channel 1]for open sensor indication is 43585, end add. [160th channel] is 43585 + 160 =
43745. And from 43746 to 44353 will be reserved address for modbus.
* 42825 register description.
‘M81/om/101, Issue # 01A-801992 - 63 -
-
8/15/2019 Manual Mesi Bus
64/68
42825 register. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
X x x x x x x x x x x x x x x x
Set point configuration.
42825.1 – 000 - H-VH01 - L- H10 - VL – L.11 - VL – L – H – VH.
Open Sensor PV value upscale / down scale 42825. 80 - Down scale.1 – Upscale.
Alarm Latch value
42825. 12
0 - Alarm Latch No.1 - Alarm Latch Yes.
Relay control value
42825. 140 –Normal relay off.
1 – Normal Relay On.
Bit 42825.2,3,4,5,6,7,9,10,11,13,15 are reserved for future use.
‘M81/om/101, Issue # 01A-801992 - 64 -
-
8/15/2019 Manual Mesi Bus
65/68
Fetch History Data
Start
Transfer from RUN mode to LOG mode{sltrsdata}
Fetch Data (Read first / next Record, and size of record)
{trsdata}
Data Increment (Next 32 bytes of record)
{ditrsdata}
Fetch Data (Read 32 bytes of channel data){trsdata}
Record Increment (Go To next record position)
{ritrsdata}
Transfer from LOG mode to RUN mode
{sttrsdata}
Until Size of Record
Until Last Record (last
record gets error response)
End
‘M81/om/101, Issue # 01A-801992 - 65 -
-
8/15/2019 Manual Mesi Bus
66/68
Run mode to Log mode:
Query: sltrsdata[8] = { DeviceNo, 0x05, 0x05, 0x00, 0xff, 0x00, CRCLo, CRCHi }
Response: { DeviceNo, 0x03, 0x20, 0x00, 0xff, 0x00, CRCLo, CRCHi }
Fetch Data:
trsdata[8] = { DeviceNo, 0x03, 0x00, 0x00, 0x00, 0x10, CRCLo, CRCHi}
Response for First Record (37 bytes):
{ DeviceNo, 0x03, 0x20, 0x65, 0x66, 0x00, 0x01, 0x12, Logtime-Hour, Logtime-Minute,
Logtime-Second, LogDate-Date, LogDate-Month LogDate-Year, Ch1-Lo,Ch1-Hi, ……Ch8-
Lo,Ch8Hi, CRCLo, CRCHi }
Response for Other Records (32 bytes):
{ DeviceNo, 0x03, 0x20, Ch9-Lo,Ch9-Hi, ……Ch22-Lo,Ch22-Hi, CRCLo, CRCHi }
{ DeviceNo, 0x03, 0x20, Ch9-Lo,Ch9-Hi, ……Ch22-Lo,Ch22-Hi, CRCLo, CRCHi }{ DeviceNo, 0x03, 0x20, Ch9-Lo,Ch9-Hi, ……Ch22-Lo,Ch22-Hi, CRCLo, CRCHi }
Data Increment:
ditrsdata[8] = { DeviceNo, 0x05, 0x06, 0x00, 0xff, 0x00, CRCLo, CRCHi }
Data Decrement:
ddtrsdata[8] = { DeviceNo, 0x05, 0x06, 0x00, 0x00, 0x00, CRCLo, CRCHi }
Record Increment:
ritrsdata[8] = { DeviceNo, 0x05, 0x07, 0x00, 0xff, 0x00, CRCLo, CRCHi }
Record Decremtnt:
rdtrsdata[8] = { DeviceNo, 0x05, 0x07, 0x00, 0x00, 0x00, CRCLo, CRCHi }
Goto First Record:
frtrsdata[8] = { DeviceNo, 0x05, 0x08, 0x00, 0xff, 0x00, CRCLo, CRCHi }
Goto Last Record:
ertrsdata[8] = { DeviceNo, 0x05, 0x08, 0x00, 0x00, 0x00, CRCLo, CRCHi }
Log mode to Run mode:
sttrsdata[8] = { DeviceNo, 0x05, 0x05, 0x00, 0x00, 0x00, CRCLo, CRCHi }
‘M81/om/101, Issue # 01A-801992 - 66 -
-
8/15/2019 Manual Mesi Bus
67/68
Calibration:
Write Zero Calibration:
Query: {DeviceNo, 0x06, 0x0D, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x06, 0x0D, ChNo, HiData, LoData, CRCLo, CRCHi}
Write Span Calibration:
Query: {DeviceNo, 0x06, 0x0E, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x06, 0x0E, ChNo, HiData, LoData, CRCLo, CRCHi}
Write Ambient Calibración:
Query: {DeviceNo, 0x06, 0x0C, ChNo, HiData, LoData, CRCLo, CRCHi}
Response: {DeviceNo, 0x06, 0x0C, ChNo, HiData, LoData, CRCLo, CRCHi}
Read Zero Calibration:
Query: {DeviceNo, 0x03, 0x0D, ChNo, 0x00, 0x01, CRCLo, CRCHi}
Response: {DeviceNo, 0x03, 0x0D, ChNo, HiData, LoData, CRCLo, CRCHi}
Read Span Calibration:
Query: {DeviceNo, 0x03, 0x0E, ChNo, 0x00, 0x01, CRCLo, CRCHi}
Response: {DeviceNo, 0x03, 0x0E, ChNo, HiData, LoData, CRCLo, CRCHi}
Read Ambient Calibration:
Query: {DeviceNo, 0x03, 0x0C, ChNo, 0x00, 0x01, CR CLo, CR CHi}
Response: {DeviceNo, 0x03, 0x0C, ChNo, HiData, LoData, CRCLo, CRCHi}
‘M81/om/101, Issue # 01A-801992 - 67 -
-
8/15/2019 Manual Mesi Bus
68/68
Appendix B. Alarm status in open condit ion.
Set point Type :- H-VH INPUT :- OPEN
Open Sensor
ParameterSetting (Alarm
Status)
Modbus OpenSensor
ParameterSetting (PV
status)
On
ModbusPV
Value
ON
Modbus AL-1Status
On
Modbus AL-2Status
In OTU
PVValue
Display
In OTU ChannelStatus Display
Down Scale -200 OFF OFF OPEN -------Down Scale
Up Scale 850 OFF OFF OPEN -------
Down Scale -200 ON ON OPEN VHighUp Scale
Up Scale 850 ON ON OPEN VHigh
Set point Type :- VL-L INPUT :- OPEN
Open SensorParameter
Setting (AlarmStatus)
Modbus OpenSensor
ParameterSetting (PV
status)
OnModbus
PVValue
ONModbus AL-1Status
OnModbus AL-2Status
In OTUPV
ValueDisplay
In OTU ChannelStatus Display
Down Scale -200 ON ON OPEN V LowDown Scale
Up Scale 850 ON ON OPEN V Low
Down Scale -200 OFF OFF OPEN -------Up Scale
Up Scale 850 OFF OFF OPEN -------
Set point Type :- L-H INPUT :- OPEN
Open SensorParameter
Setting (AlarmStatus)
Modbus OpenSensor
ParameterSetting (PV
status)
OnModbus
PVValue
ONModbus AL-1Status
OnModbus AL-2Status
In OTUPV
ValueDisplay
In OTU ChannelStatus Display
Down Scale -200 ON OFF OPEN LowDown Scale
Up Scale 850 ON OFF OPEN Low
Down Scale -200 OFF ON OPEN HighUp Scale
Up Scale 850 OFF ON OPEN High
Set point Type :- VL-L,H-VH INPUT :- OPEN
Open SensorParameter
Setting (Alarm
Modbus OpenSensor
ParameterSetting (PV
OnModbus
PV
ONModbus AL-1
OnModbus AL-2
INModbus AL-3
INModbus AL-4
In OTUPV
Value
In OTUChannelStatus