|
4.8.1 Protocol : Modbus-IDA, serial |
Telegram structure |
|
The telegram circulation is controlled by the master station, i.e. RTU only replies on inquiry. The analysis of the values in the telegram in monitoring direction is only possible concerning the command/ inquiry sent before in control direction. Therefore for line recording with LIAN 98 two channels are used and correspond with each other; you have the choice between channels 1 + 2 or 3 + 4 ( 5 + 6, 7 + 8, 9 + 10 or 11 + 12 ). On the first channel recording is done in control direction ( master -> RTU ) and on the second channel in monitoring direction ( RTU -> master ). The advantage of this 2 channel recording mode is that RTU messages can be represented with the previous master command, e. g. the correct measurement number is displayed. |
|
Information about the structure of the telegram see |
![]() |
|
With the channel button ( channel 1 ...12 ) on the bottom following settings are possible : |
|
Each character has one start bit ( binary = 0 ), 8 information bits and normally one even parity bit and one stop bit ( binary = 1 ). |
| Interface |
For each channel any COM port ( COM 1 till COM 24 ) can be selected. |
|||||
| Modem |
An individual modem can be installed and connected for each channel. LIAN 98 is able to process up to twelve modems in the range of COM1 till COM24 simultaneously. Select here the modem assigned to the selected channel. Normally this assignment will be recognized by LIAN 98 and the corresponding modem will be set. |
|||||
| Setup Modem |
The settings of the modem must be executed via the windows control panel "telephone and modem options". With this button you can check the modem settings and see if they correspond to the LIAN 98 configuration. |
|||||
| Connection type |
|
|||||
| RTS Leading delay |
0 ... 1000 msec |
|||||
| RTS Trailing delay |
0 ... 1000 msec |
| Baud rate |
Transmission speed : 25 - 115200 baud ( variable ) |
| Data byte |
8 bit ( fixed ) |
| Stop bit |
1 bit ( variable ) |
| Parity |
even ( variable ) |
| Timeout |
1 - 9999 msec ( variable ) |
| Direction |
|
|
Calculation of the timeout : |
|
The Timeout [ msec ] should be only a bit larger than the result of the
following calculation : |
|
LIAN 98 simulates a MASTER and can communicate in the polling mode with up to 32 connected substations simultaneously. |
![]() |
| Station Address ( address of the target station ) |
All telegrams to be sent are provided with the station address of the SIM list during master
simulation. |
| Response timeout |
1 - 30 000 msec |
| Number of frame retries |
0 - 255 |
| Insert Slave- / Server Addresses Number of addresses delete insert |
Multi-Point Traffic Line : ( party line ) |
| Disable automatic data requests |
yes / no |
| Data reqest ( TDBnum from ) |
Number of the TDB buffer containing the first request message. |
| Data reqest ( TDBnum till ) |
Number of the TDB buffer containing the last request message. |
| Request delay |
0 - 30 000 msec |
![]() |
| Station Address |
All telegrams to be sent will be provided with the station address out of the SIM list during slave simulation. |
| Initialize Process Image |
yes / no |
|
|
![]() |
| Enable router |
yes / no |
| Message format |
With this parameter the message format of the connected client/ master is selected. ( Modbus NET Client ). |
|
Insert routing channel Number of channels delete insert |
All connected clients which should be taken into account from the LIAN 98 router
have to be entered into the channel list. |
|
Monitoring filters reduce capture on particular pre-defined data records. By setting the corresponding filters a carefully directed data preselection can be achieved, which results in a reduction of the data to be analyzed later. |
![]() |
| Filter released |
yes / no |
||||||||||
| protocol specific filter mask |
Here monitoring can be filtered for telegram specific values in which several OR-linked filter masks can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
For the simulation and execution of data tests actions can be caused with the receipt of defined records. Therefore the possibility exists to define action filters, that effect the transmission of a send-sequence or transmit one or more message buffers ( TDB ). |
![]() |
| Action filter released |
yes / no |
||||||||||
| protocol specific filter mask |
The action filter is described over telegram specific features corresponding to a filter setting. Additionally each action filter requires an allocation to a send buffer or alternatively to a send sequence.
|
||||||||||
| Sendbuffer number ( from, from/ till ) |
In correspondence with the action filter the message buffer "from" or the message buffers "from/ till" are to be sent. |
||||||||||
| Sequence line number ( from, from/ till ) |
In correspondence with the action filter the send sequence is to be started at line number "from" or to be started at line number "from" and to be ended at line number "till". |
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
With the receipt of a telegram pre-defined as start trigger, recording is started. |
![]() |
| Start trigger released |
yes / no |
||||||||||
| protocol specific trigger mask |
Here you can define telegram specific start triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Monitoring can also be stopped by telegram-specific filters and/ or "stop on error" after a defined number of following records. The number of the following records is defined in the field "records after stop on error/ stop trigger" in the global parameters of the VFL settings. |
![]() |
| Stop trigger released |
yes / no |
||||||||||
| protocol specific trigger mask |
Here you can define telegram specific stop triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Each alteration in the settings is displayed by an asterisk * in the caption title and will be only effective after saving. |
|
The sent and received messages of all channels are entered binary into the archive file.
Before displaying on screen, the binary archived data are coverted to an easily readable procedure specific plaintext.
In order to optimize the representation it can be chosen between three different plaintext settings. The plaintext format
is set separately for each channel. |
![]() |
| Plain text format 1 |
Everything is displayed : Telegram header and information elements |
![]() |
| Plain text format 2, 3 |
No header is displayed : Only information elements are displayed. |
![]() |
| Plain text format 4, 5 |
No information element is displayed : Only telegram header is displayed. |
![]() |
|
Additional to the plain text output the transmission data can also be displayed in hexadecimal, decimal, ASCII, binary ( LSB first ) or binary ( MSB first ). Of course the plain text output can also be deactivated in order to display the transmission data only e.g. hexadecimal. |
![]() |
Error checks during receive |
| per character |
the start bit, the stop bit and the parity. |
| per frame |
the function code, the checksum and the length. |
| *** TimeOut ! |
Within a telegram, there may be no pause between characters. In case of timeout
occurs it is assumed that it is the end of the telegram and the telegram check is started. The sensitivity can be parameterized in the
configuration ( timeout ). |
| *E: COM-PORT ! |
Error during writing on the COM port. May be it is already occupied by another program. |
| E: Length ! |
The length of the telegram is wrong. |
| *E: Checksum ! |
Die Telegrammprüfsumme ( CRC16 ) im Prüfwort stimmt nicht. |
| *F: SYNC ! |
The protocol MODBUS provides no start byte for the identification of the telegram start. Therefore the receive routine sets the start of the telegram immediately after a TIMEOUT and checks the received telegram on plausibility. When this plausibility check fails, a synchronization error is noted and the telegram is entered into the PRO File. |
| *E: Overflow ! |
Error message from the UART. This error is noted only in the PRO file. |
| *E: Parity ! |
Error message from the UART. This error is noted only in the PRO file. |
| *E: Start/ Stop ! |
Error message from the UART. This error is noted only in the PRO file. |
|
| |
| *E: TypeID ! |
The function code in the telegram is wrong. |
Error checks during simulation |
| *E: Link address ! |
The received server address is incorrect or the entry in the SIM list is wrong. |
| *E: unexpected ! |
The respond at this time was not expected. |
MODBUS serial : Data Model |
|
|
![]() |
Total length of the Process Image |
maximum 64 kByte ( 0000... FFFF ) = 65536 bytes |
|
|
Starting address of Coils |
0... 65535 |
Length of Image for Coils |
maximum 16 kByte |
Starting address of Discrete Inputs |
0... 65535 |
Length of Image for Discrete Inputs |
maximum 16 kByte |
Starting address of Holding Registers |
0... 65535 |
Length of Image for Holding Registers |
maximum 16 kByte |
Starting address of Input Registers |
0... 65535 |
Length of Image for Input Registers |
maximum 16 kByte |
MODBUS serial : Process Image |
|
|
Setup Image for Coils and Diskrete Inputs |
![]() |
Setup Image for Holding- and Input Registers |
![]() |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |