I-O Communication SIWAREX U en

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

1st Question: Why and how to use I/O’s communication for SIWAREX U?

Answer :

Why use I/O communication:


Communication via IO area is fast, easy to program with small data volume but
complicated programming for large data volume.
Communication via SFC is easy to program for large data volume.

Attention: Simultaneous use of both communication types is not possible

How to use I/O communication:


SWAREX U occupies 16 bytes in the I/O area.

Eight bytes per channel are available for communication via the I/O area

Weighing- Byte S5 Output Area S5 Input Area


Channel
0 Read read–identifier (n) for Read read–identifier
DR(n) and DR(n+1) acknowledgment n for DR(n) and
DR(n+1)
1 Write write-identifier m for DR(m) Status byte
2 Not yet used Weight(H) (is updated cyclically)
3 Job control Weight(L) (is updated cyclically)
1 4 Value input(H) acc. w. identifier Value output(H) in acc. w. identifier
m n
5 Value input(L) acc. w. identifier m Value output(L) in acc. w. identifier
n
6 Specified value 1(H) Value output(H) in acc. w. identifier
(is transferred cyclically) to n+1
remote display
7 Specified value 1(L) Value output(L) in acc. w. identifier
(is transferred cyclically) to n+1
remote display
8 Read read–identifier (n) for Read read–identifier
DR(n) and DR(n+1) acknowledgment n for DR(n) and
DR(n+1)
9 Write write-identifier m for DR(m) Status byte
10 Not yet used Weight(H) (is updated cyclically)
11 Job control Weight(L) (is updated cyclically)
2 12 Value input(H) acc. w. identifier Value output(H) in acc. w. identifier
m n
13 Value input(L) acc. w. identifier m Value output(L) in acc. w. identifier
n
14 Specified value 2(H) Value output(H) in acc. w. identifier
(is transferred cyclically) to n+1
remote display
15 Specified value 2(L) Value output(L) in acc. w. identifier
(is transferred cyclically) to n+1
remote display
The communication between PLC and Siwarex U is realized thru data records.

Overview of the Data Records:

DR No. Function Channel Length Interfaces


hex. dec. Bytes SFC/DS E/ RS EEPROM
A 232
39 57 Commands X 2 - I - No
S5/S7- 3A 58 Module number - 2 - I/O - Yes
data 3B 59 Interfaceparameters - 2 - I/O - Yes
records 3C 60 Agjustment digit 0 X 2 - I/O - Yes
3D 61 Adjustment digit 1 X 2 - I/O - Yes
(once 3E 62 Adjustment weight X 2 - I/O - Yes
per 3F 63 LED allocation - 2 - I/O - Yes
channel) 40 64 Zero setting value X 2 - I/O - Yes
41 65 Char. value of LC/ X 2 - I/O - Yes
filter/ setting data
42 66 Limit value 1 on X 2 - I/O - 3)
43 67 Limit value 1 off X 2 - I/O - 3)
44 68 Limit value 2 on X 2 - I/O - 3)
45 69 Limit value 2 off X 2 - I/O - 3)
46 70 Specification value - 2 - I/O - No
1 for TTY
47 71 Specification value - 2 - I/O - No
2 for TTY
48 72 Remote display - 2 - I/O - Yes
type
49 73 Current digit value X 2 - O - No
4A 74 Gross X 2 - O - No
4B 75 Asynchronous X 2 - O - No
errors
4C 76 Synchronous errors X 2 - O - No
4D 77 Version - 2 - O - No
4E 78 Checksum - 2 - O - No
4F 79 Reserved - 2 - O - No

1st Example Read the weight of channel 1

SIWAREX U starting at address 256

L PIW 258 // 256 +2


T MW 100

2nd Example Write the adjustment weight of channel 1

SIWAREX U starting at address 256

L PIB 257 //Read the status byte:


T MB 200

L 62 // DR for Adjustment weight (See chapter Commands & Messages)


T PQB 257 // Write-identifier for channel 1 is Byte 256 +1
L 100 // weight value
T PQW 260 // Value input for channel 1 is Word 256 +4
AN M 200.7 // Bit 7 from Status byte
= M 10.7
L MB 10
T PQB 259 // change bit PQ 259.7 to activate the command

//State of the job (end) and errors should be checked in the status byte

3rd Example Set as Zero of channel 2

//SIWAREX U starting at address 256

L PIB 265 // Read the status byte:


T MB 200

L 57 //DR for Command


T PQB 265 //Write identifier for channel 2 is byte 256 +9
L 3 //Command for Set as Zero (See chapter Setting to Zero)
T PQW 268 //Value input for channel 2 is Word 256 +12
AN M 200.7
= M 10.7
L MB 10
T PQB 259

//State of the job (end) and errors should be checked in the status byte

You might also like