0% found this document useful (0 votes)
50 views8 pages

s500 Nta 01 03 Annexe Modbus

Uploaded by

Ryan Torres
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views8 pages

s500 Nta 01 03 Annexe Modbus

Uploaded by

Ryan Torres
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Feb.

-09 Appendix – MODBUS


Table of contents

1 FUNCTION CODES 2

2 COMMUNICATION BETWEEN 2 S500 RTUS 2

3 DEVICE COMMUNICATION WITH MASTER S500 2


3.1 Number of data per block 2
3.2 Transmission formats 3
3.3 Conversion of numerical inputs 3

4 DEVICE COMMUNICATION WITH SLAVE S500 4


4.1 Access from a MODBUS device 4
4.2 Access from a SOFBUS device 5
4.2.1 Access to logical inputs and outputs 5
4.2.2 Access to numerical inputs 5
4.2.3 Access to numerical outputs 5
4.3 Access to other data types from a device 6
4.3.1 Identification code 6
4.3.2 Date and time 6
4.3.3 Weekly period 6
4.3.4 Exceptions 8
4.3.5 Universal period 8
4.3.6 Look-up tables 8

S500-nta_01-03_ANNEXE-MODBUS -1-
Annexe – MODBUS
1 Function codes
Code Function
1 Read logical data (or output bits)
2 Read logical data (or input bits)
3 Read numerical data (or output words)
4 Read numerical data (or input words)
5 Write one logical datum (bit)
6 Write one numerical datum (word)
15 Write logical data (bits)
16 Write numerical data (words)

2 Communication between 2 S500 RTUs


No conversion is required during exchanges between 2 S500 remote terminal units; data transmission
occurs in "real - 64 bit" format.

3 Device communication with Master S500


All data types can be transmitted within a block. The transmission format is defined by the operator when
creating the data block.

3.1 Number of data per block


The maximum number of data that can be transmitted within a block depends upon the type
of datum and the type of recipient remote terminal unit.

¾ To a S50 type remote terminal unit:


z 400 for TSs,

z 200 for TCs,


z 123 for TMs and RAs (122 data per spontaneous transmission block),
z 61 for RCs.

¾ To an S500 type remote terminal unit:


z 1000 data in binary format

z 123 data in "integer - 8 bit" and "integer - 16 bit" formats


z 61 data in "integer - 32 bit" format
z 30 data in "real - 64 bit" format

2 The maximum address for a datum in the block is 65535. The S500 data are transmitted
according to the user-defined format, with no conversion of maximum and minimum values. If
MODBUS conversion is required, a communication type output must be used in order to perform
a conversion using the affine function.

S500-nta_01-03_ANNEXE-MODBUS -2-
Annexe – MODBUS
3.2 Transmission formats
When an S500 Master communicates with Slave MODBUS devices (PLC for example),
different transmission formats can be defined:
z for logical data:
z Binary

z for numerical data: High Low

z Integer: 8 bits, w1 (word 1) w2 (word 2)


z Integer: 16 bits,
z Integer: 16 bits signed,
z Integer: 32 bits (w1 w2),
z Integer: 32 bits (w2 w1),
z Real: 32 bits (w1 w2),
z Real: 32 bits (w2 w1),
z Real: 64 bits (w1 w2 w3 w4).
2 For PSTN/GSM communications, the transmission formats for numerical data are
fixed: "Integer - 16 bits signed" and "Real - 64 bits W1W2W3W4".

3.3 Conversion of numerical inputs

¾ AI:
During transmission, it is possible to define a linear measurement conversion:
z the actual minimum value corresponds to a raw value of 0,
z and the actual maximum value corresponds to the raw value 65535.

¾ Meters:
When transmitting data of the "Terminal strip - DI counter" or "Counter on datum" type, a
conversion factor can be applied:
Factor to enter Conversion during transmission of a
S500 datum
onto S500 SOFBUS RTU/CS to S500
Pulse counter 0.1 Multiply by 10
Pulse counter 0.01 Multiply by 100
Hours always transmitted in seconds
Duration counter:
or minutes (if Hours, divide by 3600;
"Terminal strip" or "on datum"
or seconds if Minutes, divide by 60)

S500-nta_01-03_ANNEXE-MODBUS -3-
Annexe – MODBUS
4 Device communication with Slave S500
The Slave S500 responds to requests issued by the correspondent(s) (SCADA Central station, S500 or
S50 type remote terminal unit). It is therefore necessary to enter the MODBUS addresses of the exchanged
data (from 0 to 65535).

Consecutive data can be transmitted within a single block, independently of the fact that
they are transmitted in "binary", "integer" or "real" format.

4.1 Access from a MODBUS device


A master MODBUS SCADA Central Station or PLC accesses the S500 data via bit tables or integer
or real word tables, according to several transmission formats.

The following formulae are used to calculate a datum's MODBUS address


("n" corresponds to the number of the S500 datum):

Datum "n" access


Address range Function code Transmission format
formula

Bit table [40001 to 41000] 1, 2, 5 or 15 40000 + n Binary (0 or 1)

Integer - 8 bit unsigned


42000 + n Integer - 16 bit unsigned
Integer table [42001 to 44000] 3, 4, 6 or 16 Integer - 16 bit signed

Integer - 32 bits W1W2 unsigned


42000 + (2n – 1)
Integer - 32 bits W2W1 unsigned

64 bit real table [46001 to 50000] 3, 4 or 16 46000 + (4n – 3) Real - 64 bits W1W2W3W4

Real - 32 bits W1W2 unsigned


32 bit real table [54001 to 56000] 3, 4 or 16 54000 + (2n – 1)
Real - 32 bits W2W1 unsigned

2 Access to a numerical datum via the binary format provides the following value:

z 0 if the value is nil

z 1 if the value is not equal to zero.

Example:

The MODBUS address of datum no. 73 is therefore dependent upon the transmission format defined
between the 2 communicating devices:
Address Address
in decimal in hexadecimal
format format

Bit table 40073 9C89


42073 A459
Integer table
42145 A4A1
64 bit real table 46289 B4D1
32 bit real table 54145 D381

S500-nta_01-03_ANNEXE-MODBUS -4-
Annexe – MODBUS
4.2 Access from a SOFBUS device
A SCADA Central Station or S50 remote terminal unit in Inter-RTU mode can access
the Slave S500 Unit’s data that have undergone "SOFBUS conversion".

2 For each S500 datum, transmission in TS, TM, RC, TC or RA format, must be
validated from the "Process" tab and the datum number to which it is transmitted
must be configured.

MODBUS MODBUS
Type Capacity Value
address function
TS 1 to 1000 1, 2, 5 or 15 1 bit per RS: max. 1,000 TSs 0 or 1 (bit)
TC 1001 to 2000 1, 2, 5 or 15 1 bit per RC: max. 1.000 TCs 0 or 1 (bit)
TM 1 to 500 3, 4, 6 or 16 1 word per RM: max. 500 TMs from 0 to 65535 (raw)
RC 501 to 1000 3, 4, 6 or 16 2 words per RCO: max. 250 RCs from 0 to 4294967295 (raw)
RA 1001 to 1500 3, 4, 6 or 16 1 word per RA: max. 500 RAs from 0 to 65535 (raw)

4.2.1 Access to logical inputs and outputs


¾ DI / DO:
The SOFBUS transmission must be validated:
z conversion of a logical input "X" to TS "X" format,
z conversion of a logical output "Y" to TC no. "Y" format.

4.2.2 Access to numerical inputs


¾ AI:
The conversion is linear and requires configuration:
z the actual minimum value corresponds to a raw value of 0,
z and the actual maximum value corresponds to the raw value 65535.

¾ Meters:
For data of the "Terminal strip - DI Counter" or "Counter on Datum" type, a conversion
factor must be applied:
Factor to enter Conversion during transmission of a
S500 datum
onto S500 SOFBUS RTU/SCS to S500
Pulse counter 0.1 divide by 10
Pulse counter 0.01 divide by 100
Hours always transmitted in seconds
Duration counter:
or minutes (if Hours, multiply by 3600;
"Terminal strip" or "on datum"
or seconds if Minutes, multiply by 60)

4.2.3 Access to numerical outputs


¾ AO:
The conversion is linear and requires configuration:
z the actual minimum value corresponds to a raw value of 0,
z and the actual maximum value corresponds to the raw value 65535.

S500-nta_01-03_ANNEXE-MODBUS -5-
Annexe – MODBUS
4.3 Access to other data types from a device
Datum Address Function Capacity / Format

1. Identification code 2990 and 2991 3 or 4 2 words

2. Date and time 31001 to 31007 3, 4, 6 or 16 7 words

3. Weekly period 25001 to 27825 3, 4, 6 or 16 113 words x 25 periods = 2825 words

4. Exception 28201 to 28350 3, 4, 6 or 16 3 words x 50 periods = 150 words

5. Universal period 29001 to 29200 3, 4, 6 or 16 8 words x 25 periods = 200 words

6. Look-up table 20001 to 21600 3, 4 or 16 80 words x 20 periods = 1600 words

4.3.1 Identification code


These additional codes to the remote terminal unit's site number allow the SCADA Central
station to accurately identify the S500 on the network.
Address Function Capacity / Format
2990 and 2991 3 or 4 2 words

4.3.2 Date and time


A MODBUS Master or SOFBUS device can read or write the remote terminal unit date and time.
Address Function Capacity / Format
31001 to 31007 3, 4, 6 or 16 7 words

Datum Value Address Function (read) Function (write)


Day 1 to 31 31001 3 or 4
Month 1 to 12 31002 3 or 4
Year 00 to 99 31003 3 or 4
Hour 0 to 23 31004 3 or 4
Minute 0 to 59 31005 3 or 4 16
Second 0 to 59 31006 3 or 4
Day of the week 1 = Monday 31007 3 or 4
2 = Tuesday
etc.

2 The day, month and year must be written in a single query. When setting the time,
a message is entered in the remote terminal unit’s operating log.

4.3.3 Weekly period


A weekly period comprises a maximum of 4 time periods for each day of the week. For each
time period:
z the hour is transmitted within a word ranging from 0 to 24 (0 = field unused),

z the minute is transmitted within a word ranging from 0 to 60 (0 = field unused).

Address Function Capacity / Format


25001 to 27825 3, 4, 6 or 16 113 words x 25 periods = 2825 words

These time periods are addressed in the following manner:


Datum Value Address Function Capacity / Format
∗ Validity indicator 0 or 1 25001 + [(SCADA CS dialing - 1) x 113] 3 or 4 1 word
Range time 12:00 AM to 11:59 PM 25002 + [(SCADA CS dialing - 1) x 113] 6 or 16 112 words

(∗) indicator not used by S500; present only for compatibility with the communication protocol.

S500-nta_01-03_ANNEXE-MODBUS -6-
Annexe – MODBUS
For each time period category (weekly, exception and universal), a "SCADA CS dialing" parameter
automatically assigns a fixed number to the SCADA central station, corresponding to the S500 time
period (number distinct from that of the S500 datum); this number corresponds to that of S500’s
rank number in its category.

& Example: to determine the MODBUS address of datum no. 50 "Weekly period", which is the 2nd weekly
period defined in the configuration (hence SCADA CS dialing = 2), and whose band no. 4 is
active on Wednesdays between [2pm and 6pm]:

- the address of the band start time is therefore:

3rd day of the week y = 1 (start time)

25001 + [(2 - 1) x 113] + [(3 - 1) x 16] + [(4 - 1) x 4] + 1 = 25159


SCADA CS dialing 4th time band of the period

- The calculation of the start minute (00) address is: 25159 + 1 = 25160 (y = 2).

2 Remark : user can modify the number of the S500 datum corresponding to this weekly
period, without affecting this period’s "SCADA CS dialing" in the S500
configuration.

Address Address Address Address


Start hour Start minute End hour End minute
Period 1 25002 25003 25004 25005
Period 2 25006 25007 25008 25009
Monday
Period 3 25010 25011 25012 25013
Period 4 25014 25015 25016 25017
Period 1 25018 25019 25020 25021
Period 2 25022 25023 25024 25025
Tuesday
Period 3 25026 25027 25028 25029
Period 4 25030 25031 25032 25033
… … … … …
… … … … …
etc.
… … … … …
… … … … …

The formula used to calculate the address of a time period's start or end hour or minute is as
follows:

25001 + [(SCADA CS dialing - 1) x 113] + [(day no. - 1) x 16] + [(band no. - 1) x 4] + y

z y = 1 for calculating the start hour,


z y = 2 for calculating the start minute,
z y = 3 for calculating the end hour,
z y = 4 for calculating the end minute.

2 From S500 V 3.21 onwards, the unit writing of a word to modify the time period
start or end hour or minute is possible as long as the time period is valid. To
validate an invalid time period, the end hour or minute must first have been
written.

S500-nta_01-03_ANNEXE-MODBUS -7-
Annexe – MODBUS

4.3.4 Exceptions
Address Function Capacity / Format
28201 to 28350 3, 4, 6 or 16 3 words x 50 periods = 150 words

Datum Value Address Function Format


Universal period number 0 to 25 (0 if none) 28201 + [(SCADA CS dialing –1) *3] 3 or 4 or 16 1 word
Number of the normal weekly
0 to 25 (0 if none) 28202 + [(SCADA CS dialing –1) *3] 3 or 4 or 16 1 word
period
1 to 25
Number of the substitute weekly
0 if always valid 28203 + [(SCADA CS dialing –1) *3] 3 or 4 or 16 1 word
period
65535 if always invalid

4.3.5 Universal period


Address Function Capacity / Format
29001 to 29200 3, 4, 6 or 16 8 words x 25 periods = 200 words

A universal period comprises a start date and time and an end date and time:
Datum Value Address Function Format
Start (day of the month) 0 to 31 (0 if field unused) 29001 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
Start (month) 0 to 12 (0 if field unused) 29002 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
Start (hour) 0 to 24 (24 if field unused) 29003 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
Start (minute) 0 to 60 (60 if field unused) 29004 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
End (day of the month) 0 to 31 (0 if field unused) 29005 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
End (month) 0 to 12 (0 if field unused) 29006 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
End (hour) 0 to 24 (24 if field unused) 29007 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word
End (minute) 0 to 60 (60 if field unused) 29008 + [(SCADA CS dialing –1) *8] 3 or 4 or 16 1 word

4.3.6 Look-up tables


Address Function Capacity / Format
20001 to 21600 3, 4 or 16 80 words x 20 tables = 1600 words

Datum Address Function Capacity Format


real - 32 bits
Input value 20001 + [(table no. –1) ∗ 80] + (point no. –1) 3 or 4 or 16 40 words
W1W2
real - 32 bits
Output value 20041 + [(table no. –1) ∗ 80] + (point no. –1) 3 or 4 or 16 40 words
W1W2

2 Reading from / writing to a look-up table is equivalent to reading / writing 80


indissociable words.

S500-nta_01-03_ANNEXE-MODBUS -8-

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy