![VIPA SSM-BG41 Manual Download Page 177](http://html1.mh-extra.com/html/vipa/ssm-bg41/ssm-bg41_manual_1029239177.webp)
Manual BG41/BG42/BG43
Software
Rev. 99/49
4-61
ANZW
Display word. The display word occupies a word. In the right byte status bits are
filed. In the left byte a wrong number is filed, when the identifier “finished with
error“ appears in the right byte.
The status identifiers in the right byte are structured as follows:
Bit 0: Not used
Bit 1: Job is running
Bit 2: Finished without an error
Bit 3: Finished with an error,
→
Error number in the left byte
Bit 4: Interface momentarily occupied
Bit 5-7:Not used
The data handling block imports at the polling of the interface building block
only as many bytes, as were parametrized as block size on the data handling block
SYNCHRON.
Due to these reasons the data handling block RECEIVE must often be loaded
several times, in order to import a complete telegram from the interface building
block. If the data handling block has one or more data blocks but has not yet
imported the last data block from the interface building block, it places as an
identifier for “job running“ bit 1 in the right byte of the display word.
If all data blocks have been correctly imported from the interface building block,
the data handling block places as identifcation for "finished without an error" the
bit 2 in the right byte of the display word.
If the telegram could not be imported from the interface building block, e.g. the
telegram is too long, the data handling block places as identifier for "finished
with error" the bit 3 in the right byte of the display word. In this case an error
number is then in the left byte of the display word.
ANZW Error code
05
Telegram header contains invalid target type
09
Receiver does not answer with DLE
14
Wrong telegram header (the first 2 bytes)
15
Transmission terminated by receiver
16
Wrong command code 2. letter (invalid target area)
20
DB error (DB0 used, DB too short, DB not available)
21
Receiver does not answer within QVZ (Timeout on SSM building block)
22
Wrong command code 1. letter (invalid source area)
23
QVZ in connection set-up
50
Coordination flags set
52
Data length greater than 128 bytes
Summary of Contents for SSM-BG41
Page 2: ...Lerrzeichen...
Page 8: ...Contents Manual BG41 BG42 BG43 iv Rev 99 49...
Page 10: ......
Page 16: ......
Page 26: ...Firmware s memory distribution Manual BG41 BG42 BG43 2 10 Rev 99 49...
Page 28: ......
Page 53: ...Manual BG41 BG42 BG43 Interface modules Rev 99 49 3 25 3 2 7 2 Data flow Fig 3 26 Data flow...
Page 114: ...Functional description and allocation of terminal pins Manual BG41 BG42 BG43 3 86 Rev 99 49...
Page 116: ......
Page 215: ...Manual BG41 BG42 BG43 Software Rev 99 49 4 99 Month 06h Year 95h Weekday Tuesday 02h...
Page 222: ...Application of interfaces without data handling blocks Manual BG41 BG42 BG43 4 106 Rev 99 49...
Page 224: ......
Page 258: ...Structure guidelines Manual BG41 BG42 BG43 5 34 Rev 99 49...
Page 260: ......
Page 274: ...Overview cycle load Manual BG41 BG42 BG43 6 14 Rev 99 49...
Page 275: ...Appendix A List of figures A 1 B Index of tables B 1 C Index C 1...
Page 276: ......
Page 280: ...List of figures Manual BG41 BG42 BG43 A 4 Rev 99 49...