- Home
- Home security & automation
- Security device components
- ABB
- Arc Guard System TVOC-2-COM
- User manual
ABB Arc Guard System TVOC-2-COM helps protect personnel and equipment from electrical arc flash hazards by instantly detecting and interrupting dangerous electrical arcs. It utilizes advanced optical sensing technology to detect and differentiate between dangerous arc flash events and harmless light sources, providing reliable protection for your electrical system.
advertisement
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
1SFC170 017M0201 EN, RE V C
Arc Guard System™ – TVOC-2-COM
Modbus configuration manual
— A
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
Read this first
Warning and safety
Thank you for selecting this ABB TVOC-2 Arc Guard
System™. Carefully read and make sure that you understand all instructions before you mount, connect, configure the Arc Guard System.
This manual is intended for configuration of the TVOC-2-
COM Modbus interface.
The manual is available on: http://new.abb.com/low-voltage/products/arc-guard
• Only authorized and appropriately trained personnel are allowed to install and make the electrical connection of the Arc Guard System in accordance with existing laws and regulations.
• Only authorized personnel are allowed to do service and repair on the Arc Guard System.
• Unauthorized repair will effect the warranty.
• This manual is a part of the TVOC-2 Arc Guard System.
Always keep this manual available when working with the TVOC-2 Arc Guard System.
• Examine the Arc Guard System and the package when you unpack your new product. If there are damages, please contact the transportation company or the ABB reseller/office immediately.
General safety information
WARNING
Only authorized and appropriately trained personnel are allowed to install and make the electrical connection of the Arc Guard System in accordance with existing laws and regulations.
WARNING
Examine the Arc Guard System and the package when you unpack your new product. If there are damages, please contact the transportation company or the ABB reseller/office immediately.
WARNING
Only authorized and appropriately trained service personnel are allowed to do service and repair on the Arc Guard System. Note: unauthorized repair will effect the warranty.
Personal
Service and repair should be performed by authorized personnel only. Note that unauthorized repair affects safety and warranty.
Safety notes
In this user manual, these symbols are used:
WARNING
General warning symbol indicates the presence of a hazard which could result in personal injury and damage to equipment or property.
WARNING
Warning symbol indicates the presence of hazardous voltage which could result in personal injury.
INFORMATION
Information sign alerts the reader to relevant facts and conditions.
Modifications to data in this manual can be applied without notice.
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
Arc Guard System™
TVOC-2-COM Modbus
Configuration manual
GENERAL
INFORMATION
P. 7
MODBUS
INSTALLATION
P. 11
CHANGING MODBUS ID
AND COMMUNICATION
PARAMETERS
P. 15
FUNCTIONAL
DESCRIPTION
P. 19
TROUBLESHOOTING
P. 33
INDEX
P. 36
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
1 General information
7
8
8
8
1.1 Introduction
1.2 references
1.3 Quick start-up
1.1 Introduction
This manual covers the Modbus interface, which offers a direct connection to Modbus-RTU for the Arc Guard
System™ TVOC-2.
TVOC-2-COM will behave as a slave. This means all communication will be performed by a master device on the same Modbus system. Mostly this will be a PLC. This manual explains how to install the Arc Guard System™
TVOC-2-COM to your Modbus system.
1.2 References
[1] http://www.modbus.org/docs/Modbus_Application_
Protocol_V1_1b3.pdf (2012)
[2] http://www.modbus.org/docs/Modbus_over_serial_ line_V1_02.pdf (2006)
[3] https://www.modbusdriver.com/modpoll.html
1.3 Quick start-up
1 Make sure your Modbus master has been installed to the system.
2
The TVOC-2-COM will be delivered with the following configuration:
• baud rate 19200
• parity even
• stop bits 1
• Modbus ID 248*
*Modbus ID 248 is not a valid id for a Modbus system but is used to indicate that the communication is disabled.
3 Physically connect the system to the Modbus network.
4 Test communication between your master and the TVOC-2 system. For example see chapter 5
Troubleshooting.
START
1
2
Master present
Set Modbus id of TVOC-2
Figure 1
Quick start-up
3
4
Connect
TVOC-2
System
Test
Ready
9
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
2 Modbus installation
12
12
12
13
2.1 General
2.2 Modbus connector
2.3 Modbus cables
2.4 Termination
11
2.1 General
Modbus/RTU is a 2-wire, RS485-based field bus communication system for parameter value exchange.
INFORMATION
The implementation of the Modbus interface is based on standards [1] and [2].
2.2 Modbus connector
The supplied Modbus connector has the following pin configuration:
Table 1 Modbus Connector
Terminal
+(B)
-(A)
DGND
EIA/TIA-485 name
B/B’
A/A’
C/C’
ITr/IDv
D1
D0
Common
Description
Transceiver terminal 1
Terminator 1 input*
Transceiver terminal 0
Terminator 2 input*
Signal common
* If the device is connected as first or last device in a multi-drop system, a 120Ω terminator resistor should be installed between terminator inputs (A) and (B).
+(B) -(A) DGND
Figure 2
Modbus connector
2.3 Modbus cables
Recommended cable: Belden 3105A (AWG22).
2.4 Termination
For best quality of data transfer, Modbus should be terminated correctly.
The following figure shows Modbus installation according to [3].
2.4.1 Termination resistors
A 120Ω resistor is added in parallel with TVOC-2 System connection if it is installed as first or last device on the network. For this purpose there are double terminals for
+(B) and -(A) connections.
2.4.2 Pull-up / pull-down resistors
When the Modbus network is not being actively driven by a device, the bus line is in an undefined state. Bias resistors should then be used to obtain a defined voltage potential on the data lines. The bias resistors act for data line B (D1) as pull-up resistors against 5V and for data line A (D0) as pull-down resistors against GND. This is illustrated in Figure 20 in [2].
The following devices usually have built-in bias resistors:
• Modbus masters
• Gateways
• Repeaters
Figure 3
General 2-Wire Topology
13
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
3 Changing Modbus ID and
communication parameters
15
16
16
3.1 Changing Modbus ID and communication parameters
3.2 Configuration via HMI
3.1 Changing Modbus ID and communication parameters
On delivery the default parameters are:
• Modbus ID 248
• Baud rate 19200
• Parity even
• Data bits 8
• Stop bits 1
The parameters should be changed to fit the existing network.
3.2 Configuration via HMI
Use the HMI to navigate to menu 3.4 Modbus
Select appropriate submenu to change configuration.
Note: The Modbus ID must be changed to enable communication. The default ID of 248 only indicates that the Modbus communication is disabled. It is not a valid ID in a Modbus network. Valid ID range is 1-247.
Figure 4
Menu 3.4 Modbus
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
4 Functional description
19
20
20
20
28
28
30
30
30
30
31
31
25
26
26
27
27
4.1 Functional description
4.2 Implementation class
4.3 Supported Modbus functions
4.4 Register data format
4.4.1 Trip information
4.4.2 Diagnostics information
4.4.3 Error information
4.4.4 Custom name registers
4.4.5 Installed modules
4.4.6 Dip switches
4.4.7 Version information
4.4.8 Reset
4.4.9 System date
4.4.10 System time HHMM
4.4.11 Modbus failure register
4.4.12 System state
4.4.13 Diagnostic Trouble Code, number x
4.1 Functional description
The information found here is the basic information needed for the installation of a Modbus system.
4.2 Implementation class
The physical and data link layer are implemented conforming to the “basic slave” implementation class as described in document [2] “MODBUS over Serial Line specification and implementation guide V1.02”.
The following options have been implemented:
Table 2 Modbus Parameters
General settings
Parameter
Addressing
Baud rate
Parity
Data bits
Stop bits
Electrical interface
Options Remarks address configurable 1-248 (default 248) When set to 248, the communication is disabled.
9600
19200 (default)
38400
57600 none even (default) odd
8 Not configurable.
1 (default)
1.5
2
RS485 2W cabling
The use of no parity requires 2 stop bits.
4.3 Supported Modbus functions
This section describes the supported Modbus function codes.
4.3.1 Read Registers (03, 04)
Both function 03, Read Holding Registers and function 04,
Read Input Registers, can be used. The addresses are the same.
Table 3 Read Exceptions
Possible exception responses
Code
02
Name
ILLEGAL_DATA_ADDRESS
Meaning
Address refers to a register that is not available or not readable.
4.3.2 Write Registers (06, 16)
Functions 06, Write Single Register and function 16, Write
Multiple Registers, are supported.
Table 4 Write Exceptions
Possible exception responses
Code
02
Name
ILLEGAL_DATA_ADDRESS
03 ILLEGAL_DATA_VALUE
4.3.3 Available registers
Trip 1 detector, low
Trip 1 detector, low
Trip 1 detector, high
Trip 1 relay
Trip 1 date
Trip 1 time HHMM
Trip 1 time SS
Trip 2 detector, low
Trip 2 detector, high
Trip 2 relay
Trip 2 date
Trip 2 time HHMM
Trip 2 time SS
Trip 3 detector, low
Trip 3 detector, high
Trip 3 relay
Trip 3 date
Trip 3 time HHMM
Trip 3 time SS
Trip 4 detector, low
Trip 4 detector, high
Trip 4 relay
Trip 4 date
Trip 4 time HHMM
Trip 4 time SS
Trip 5 detector, low
Trip 5 detector, high
Trip 5 relay
Trip 5 date
Trip 5 time HHMM
Trip 5 time SS
Trip 6 detector, low
Trip 6 detector, high
Modbus registers are numbered from 1 to 65536.
In a Modbus PDU (Protocol Data Unit) these registers are addressed from 0 to 65535.
The following table lists the available parameters. More details about the data format can be found in
4.4 Register data format below.
Modbus registers
Parameter name Access PDU Address
Hex
0x0079
0x007A
0x007B
0x007C
0x007D
0x007E
0x0080
0x0081
0x0082
0x0083
0x006D
0x006E
0x006F
0x0070
0x0072
0x0073
0x0074
0x0075
0x0076
0x0077
0x0084
0x0085
0x0087
0x0088
0x0064
0x0064
0x0065
0x0066
0x0067
0x0068
0x0069
0x006B
0x006C
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Dec
125
126
128
129
130
131
121
122
123
124
132
133
135
136
114
115
116
117
118
119
109
110
111
112
103
104
105
107
108
100
100
101
102
Meaning
Address refers to a register that is not available or not readable.
The value written is not permitted for this register.
Register Number
Hex Dec
0x007A
0x007B
0x007C
0x007D
0x007E
0x007F
0x0081
0x0082
0x0083
0x0084
0x006E
0x006F
0x0070
0x0071
0x0073
0x0074
0x0075
0x0076
0x0077
0x0078
0x0085
0x0086
0x0088
0x0089
0x0065
0x0065
0x0066
0x0067
0x0068
0x0069
0x006A
0x006C
0x006D
126
127
129
130
131
132
122
123
124
125
133
134
136
137
115
116
117
118
119
120
110
111
112
113
104
105
106
108
109
101
101
102
103
Remark
X1:1 – X2:5
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
21
Modbus registers
Parameter name
Trip 6 relay
Trip 6 date
Trip 6 time HHMM
Trip 6 time SS
Trip 7 detector, low
Trip 7 detector, high
Trip 7 relay
Trip 7 date
Trip 7 time HHMM
Trip 7 time SS
Number of trips
Diagnostics error date
Diagnostics error time HHMM
Diagnostics error time SS
Diagnostics error DTC, number 2 and 1
Diagnostics error DTC, number 4 and 3
R
R
Diagnostics error DTC, number 6 and 5
Diagnostics trip
Diagnostics trip date
Diagnostics trip time HHMM
Diagnostics trip time SS
Diagnostics trip detector low
Diagnostics trip detector high
Diagnostics trip relay
Perform diagnostics
0 = no-operation
Last performed diagnostics date R
Last performed diagnostics time R
Error 1 date R
R
R
R
R
W
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Error 1 time HHMM
Error 1 time SS
Error 1 DTC, number 2 and 1
Error 1 DTC, number 4 and 3
Error 1 DTC, number 6 and 5
Error 2 date
Error 2 time HHMM
Error 2 time SS
Error 2 DTC, number 2 and 1
Error 2 DTC, number 4 and 3
Error 2 DTC, number 6 and 5
Error 3 date
Error 3 time HHMM
Error 3 time SS
Error 3 DTC, number 2 and 1
Error 3 DTC, number 4 and 3
Error 3 DTC, number 6 and 5
Error 4 date
Error 4 time HHMM
Error 4 time SS
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Access PDU Address
Hex
0x0089
0x008A
0x008B
0x008C
0x008E
0x008F
0x0090
0x0091
0x0092
0x0093
0x0095
0x00C8
0x00C9
0x00CA
0x00CB
0x00CC
0x0133
0x0134
0x0135
0x0136
0x0137
0x0138
0x013A
0x013B
0x013C
0x013D
0x00DC
0x00DD
0x012C
0x012D
0x012E
0x012F
0x0130
0x0131
0x013E
0x013F
0x0141
0x0142
0x0143
0x00CD
0x00CE
0x00CF
0x00D0
0x00D1
0x00D2
0x00D3
0x00D4
0x00D5
203
204
311
312
314
315
316
317
307
308
309
310
318
319
321
322
323
302
303
304
305
220
221
300
301
209
210
211
212
213
205
206
207
208
Dec
146
147
149
200
201
202
142
143
144
145
137
138
139
140
0x00CC 204
0x00CD 205
0x00CE
0x00CF
0x00D0
0x00D1
0x00D2
0x00D3
0x00D4
0x00D5
0x00D6
210
211
212
213
214
206
207
208
209
312
313
315
316
317
318
308
309
310
311
319
320
322
323
324
303
304
305
306
221
222
301
302
0x0134
0x0135
0x0136
0x0137
0x0138
0x0139
0x013B
0x013C
0x013D
0x013E
0x00DD
0x00DE
0x012D
0x012E
0x012F
0x0130
0x0131
0x0132
0x013F
0x0140
0x0142
0x0143
0x0144
Register Number
Hex Dec
0x008A
0x008B
0x008C
0x008D
0x008F
0x0090
0x0091
0x0092
0x0093
0x0094
0x0096
0x00C9
0x00CA
0x00CB
147
148
150
201
202
203
143
144
145
146
138
139
140
141
Remark
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
K4 (LSb), K5, K6
Days since January 1, 1970
MSB = hours, LSB = minutes
Number of trips in trip log
Days since January 1, 1970
MSB = hours, LSB = minutes
MSB = hours, LSB = minutes
X1:1 – X2:5
X2:6 – X3:10
1 = perform diagnostics,
Days since January 1, 1970
Days since January 1, 1970
Days since January 1, 1970
Days since January 1, 1970
Modbus registers
Parameter name
Error 4 DTC, number 2 and 1
Error 4 DTC, number 4 and 3
Error 4 DTC, number 6 and 5
Error 5 date
Error 5 time HHMM
Error 5 time SS
Error 5 DTC, number 2 and 1
Error 5 DTC, number 4 and 3
Error 5 DTC, number 6 and 5
Error 6 date
Error 6 time HHMM
Error 6 time SS
Error 6 DTC, number 2 and 1
Error 6 DTC, number 4 and 3
Error 6 DTC, number 6 and 5
Error 7 date
Error 7 time HHMM
Error 7 time SS
Error 7 DTC, number 2 and 1
Error 7 DTC, number 4 and 3
Error 7 DTC, number 6 and 5
Error 8 date
Error 8 time HHMM
Error 8 time SS
Error 8 DTC, number 2 and 1
Error 8 DTC, number 4 and 3
Error 8 DTC, number 6 and 5
Error 9 date
Error 9 time HHMM
Error 9 time SS
Error 9 DTC, number 2 and 1
Error 9 DTC, number 4 and 3
Error 9 DTC, number 6 and 5
Custom name, letter 1 and 2
Custom name, letter 3 and 4
Custom name, letter 5 and 6
Custom name, letter 7 and 8
Custom name, letter 9 and 10
Custom name, letter 11 and 12
Custom name, letter 13 and 14
Custom name, letter 15 and 16
Installed modules
Dip Switches
Arc Monitor SW version XXYY
Arc Monitor SW version ZZ
Arc Monitor HW version
Arc Monitor CPLD version XXYY R
Arc Monitor CPLD version ZZ R
Arc Monitor ID, byte 0
Arc Monitor ID, byte 1
R
R
Arc Monitor ID, byte 2
Arc Monitor ID, byte 3
R
R
R
R
R
R
R
RW
RW
RW
RW
RW
RW
R
R
R
R
RW
RW
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Access PDU Address
Hex
0x0161
0x0162
0x0164
0x0165
0x0166
0x0167
0x0168
0x0169
0x0190
0x0191
0x0156
0x0157
0x0158
0x0159
0x015A
0x015B
0x015D
0x015E
0x015F
0x0160
0x0144
0x0145
0x0146
0x0148
0x0149
0x014A
0x014B
0x014C
0x014D
0x014F
0x0150
0x0151
0x0152
0x0153
0x0154
0x0192
0x0193
0x0194
0x0195
0x0196
0x0197
0x01F4
0x0258
0x0320
0x0321
0x0322
0x0323
0x0324
0x032B
0x032C
0x032D
0x032E
Dec
358
359
360
361
400
401
353
354
356
357
346
347
349
350
351
352
342
343
344
345
335
336
337
338
339
340
330
331
332
333
324
325
326
328
329
803
804
811
812
813
814
406
407
500
600
402
403
404
405
800
801
802
Register Number
Hex Dec
0x0162
0x0163
0x0165
0x0166
0x0167
0x0168
0x0169
0x016A
0x0191
0x0192
0x0157
0x0158
0x0159
0x015A
0x015B
0x015C
0x015E
0x015F
0x0160
0x0161
0x0145
0x0146
0x0147
0x0149
0x014A
0x014B
0x014C
0x014D
0x014E
0x0150
0x0151
0x0152
0x0153
0x0154
0x0155
0x0193
0x0194
0x0195
0x0196
0x0197
0x0198
0x01F5
0x0259
0x0321
0x0322
0x0323
0x0324
0x0325
0x032C
0x032D
0x032E
0x032F
359
360
361
362
401
402
354
355
357
358
347
348
350
351
352
353
343
344
345
346
336
337
338
339
340
341
331
332
333
334
325
326
327
329
330
804
805
812
813
814
815
407
408
501
601
403
404
405
406
801
802
803
Remark
Days since January 1, 1970
Days since January 1, 1970
Days since January 1, 1970
Days since January 1, 1970
Days since January 1, 1970
23
Modbus registers
Parameter name
Arc Monitor ID, byte 4
HMI SW version XXYY
HMI SW version ZZ
HMI HW version
HMI ID, byte 0
HMI ID, byte 1
HMI ID, byte 2
HMI ID, byte 3
HMI ID, byte 4
Other HMI SW version XXYY
Other HMI SW version ZZ
Other HMI HW version
Other HMI ID, byte 0
Other HMI ID, byte 1
Other HMI ID, byte 2
Other HMI ID, byte 3
Other HMI ID, byte 4
X2 HW version
X2 CPLD version XXYY
X2 CPLD version ZZ
X2 ID, byte 0
X2 ID, byte 1
X2 ID, byte 2
X2 ID, byte 3
X2 ID, byte 4
X3 HW version
X3 CPLD version XXYY
X3 CPLD version ZZ
X3 ID, byte 0
X3 ID, byte 1
X3 ID, byte 2
X3 ID, byte 3
X3 ID, byte 4
Reset trip
System date
System time HHMM
Modbus failure register
System state
Active DTC, number 1
Active DTC, number 2
Active DTC, number 3
Active DTC, number 4
Active DTC, number 5
Active DTC, number 6
Access PDU Address
Hex
0x0378
0x0379
0x037A
0x037B
0x037C
0x03E8
0x044C
0x044D
0x04B0
0x0514
0x035D
0x035E
0x0364
0x0365
0x0366
0x0367
0x0368
0x0370
0x0371
0x0372
0x0341
0x0348
0x0349
0x034A
0x0351
0x0352
0x0353
0x0354
0x0355
0x035C
0x032F
0x0334
0x0335
0x0336
0x033D
0x033E
0x033F
0x0340
0x0515
0x0516
0x0517
0x0518
0x0519
0x051A
R
R
R
W
RW
RW
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Dec
888
889
890
891
892
1000
1100
1101
1200
1300
870
871
872
880
881
882
861
862
868
869
1301
1302
1303
1304
1305
1306
849
850
851
852
853
860
833
840
841
842
829
830
831
832
815
820
821
822
Register Number
Hex Dec
0x0379
0x037A
0x037B
0x037C
0x037D
0x03E9
0x044D
0x044E
0x04B1
0x0515
0x035E
0x035F
0x0365
0x0366
0x0367
0x0368
0x0369
0x0371
0x0372
0x0373
0x0342
0x0349
0x034A
0x034B
0x0352
0x0353
0x0354
0x0355
0x0356
0x035D
0x0330
0x0335
0x0336
0x0337
0x033E
0x033F
0x0340
0x0341
0x0516
0x0517
0x0518
0x0519
0x051A
0x051B
889
890
891
892
893
1001
1101
1102
1201
1301
871
872
873
881
882
883
862
863
869
870
1302
1303
1304
1305
1306
1307
850
851
852
853
854
861
834
841
842
843
830
831
832
833
816
821
822
823
Remark
1 = reset, 0 = no-operation
4.4 Register data format
This section describes details about the data format for selected registers.
4.4.1 Trip information
The trip registers contain information about the last 7 trips that has occurred. If less than 7 trips has occurred, which can be checked by reading register Number of trips, the register values will be 0xFFFF.
4.4.1.1
Trip x detector, low
This register contains a bit field that contains which detectors triggered the trip.
Bit 15
-
14
X2:5
13
X2:4
12
X2:3
11
X2:2
10
X2:1
9
X1:10
8
X1:9
7
X1:8
6
X1:7
5
X1:6
4
X1:5
3
X1:4
2
X1:3
1
X1:2
0
X1:1
4.4.1.2
Trip x detector, high
Bit 15 14 13 12
X3:10 X3:9 X3:8
11
X3:7
10
X3:6
9
X3:5
8
X3:4
7
X3:3
6
X3:2
5
X3:1
4
X2:10
3
X2:9
2
X2:8
1
X2:7
0
X2:6
4.4.1.3
Trip x relay (IGBT)
Bit 15 14 13
-
12
-
11
-
10
-
9
-
8
-
7
-
6
-
5
-
4
-
3
-
2
K6
1
K5
0
K4
4.4.1.4
Trip x date
The date the trip occurred. The date is expressed as number of days since January 1, 1970.
Example: the value 0x42B6 (17078) corresponds to
October 4, 2016.
4.4.1.5
Trip x time HHMM
The hours and minutes of time the trip occurred. The time is expressed in 24h format as a 16 bit value where the most significant byte contains the hours and the least significant the minutes.
Example: the value 0x0922 (2338) corresponds to 09:34.
4.4.1.6
Trip x time SS
The seconds of the time the trip occurred.
4.4.1.7
Number of trips
The number of trips that has occurred.
25
4.4.2 Diagnostics information
The following registers contain the same information as menu 2. Diagnostics on the HMI.
Diagnostics error registers contain information about the current active error. If there is no active error they contain
0x0000. The format of the registers are as described in
4.4.3 Error information below.
Diagnostics trip registers contain information about the current active trip. If there is no active trip they contain
0x0000. The format of the registers are as described in
4.4.1 Trip information above.
Register System state can be read to see if there is an active error/trip.
4.4.2.1
Perform diagnostics
Write value 1 to this register to perform diagnostic test.
4.4.2.2
Last performed diagnostics date
Date of last performed diagnostics. Format as described in 4.4.1.4 Trip x date above.
4.4.2.3
Last performed diagnostics time HHMM
Time of last performed diagnostics. Format as described in 4.4.1.5 Trip x time HHMM above.
4.4.3 Error information
The error registers contain information about the last 9 errors that has occurred. If less than 9 errors has occurred, which can be checked by reading register Number of errors, the register values will be 0xFFFF.
4.4.3.1
Error x date
The date the error occurred. The date is expressed as number of days since January 1, 1970.
Example: the value 0x42B6 (17078) corresponds to
October 4, 2016.
4.4.3.2
Error x time HHMM
The hours and minutes of time the trip occurred. The time is expressed in 24h format as a 16 bit value where the most significant byte contains the hours and the least significant the minutes.
Example: the value 0x0922 (2338) corresponds to 09:34.
4.4.3.3
Error x time SS
The seconds of the time the trip occurred.
27
4.4.3.4
Error x DTC, number y and z
A diagnostic trouble code (DTC) consist of 6 numbers.
When displayed on the HMI it has the following format: n6-n5-n4-n3-n2-n1, where n<n> denotes number n.
Example: With DTC 64-0-0-2-0-0, number 3 has value 2 and number 6 has value 64.
Two numbers are stored in each register, the first number
(y) in the most significant byte and the second (z) in the least significant.
4.4.3.5
Number of errors
The number of errors that has occurred.
4.4.4 Custom name registers
The custom name registers contains the letters in the custom name that can be programmed to the HMI.
Allowed characters are the alphanumeric characters plus
“-“, “_” and “ “ (space). This means ASCII character 32, 45,
48-57, 65-90, 95, 97-122. If not all 16 characters are needed, the trailing characters should be set to value 32 (space) to keep the layout of the name center aligned.
In each register, two characters are stored. One in the most significant byte and one in the least significant.
Example: To set the custom name to “Example” the registers should be set as follows
Custom name, letter 1 and 2
Custom name, letter 3 and 4
0x4578 (Ex)
0x616D (am)
Custom name, letter 5 and 6
Custom name, letter 7 and 8
0x706C (pl)
0x6520 (e )
Custom name, letter 9 and 10 0x2020 ( )
Custom name, letter 11 and 12 0x2020 ( )
Custom name, letter 13 and 14 0x2020 ( )
Custom name, letter 15 and 16 0x2020 ( )
Using modpoll (see 5.2 Example of reading with modpoll below) the command is: modpoll -m rtu -a 247 -0 -r 400 COM1 0x4578 0x616D 0x706C 0x6520 0x2020 0x2020 0x2020 0x2020
4.4.4.1
Custom name, letter x and y
Letter x is stored in the most significant byte, letter y in the least significant byte.
4.4.5 Installed modules
This register contains a bit field that reflects which modules are installed and detected on the Arc Guard
System™ TVOC-2.
A high bit signals an installed module.
Bit 15
-
14
-
13
-
12
-
11
-
10
-
9
-
8
-
Example: the value 0x000E shows a system that contains an internal HMI and extension modules X2 and X3.
7
-
6
-
5
CSU22
4
CSU21
3
X3
2
X2
1
External
HMI
0
Internal
HMI
4.4.6 Dip switches
This registers contains the status of the dip switches on the Arc Monitor in its least significant byte.
Bit
Dip switch
15
-
14
-
13
-
12
-
11
-
10
-
9
-
Example: the value 0x0004 indicates that dip switch 3,
TripMatrix 4, is On and all others are Off.
8
-
4.4.7 Version information
Software (SW) and CPLD versions are specified with three numbers XX.YY.ZZ. Each version is presented using two
Modbus registers, one for the first two numbers and one for the last.
4.4.7.1
Arc Monitor SW version XXYY
This registers contains the first number of the version in the most significant byte and the second number of the version in the least significant byte.
Example: If the Arc Monitor software version is 00.03.43 this register has value 0x0003.
4.4.7.2
Arc Monitor SW version ZZ
This registers contains the third number of the version in the least significant byte.
Example: If the Arc Monitor software version is 00.03.43 this register has value 0x002B.
4.4.7.3
Arc Monitor HW version
This register contains the Arc Monitor hardware version in the least significant byte.
4.4.7.4
Arc Monitor CPLD version XXYY
This registers contains the first number of the version in the most significant byte and the second number of the version in the least significant byte.
Example: If the Arc Monitor CPLD version is 00.02.01 this register has value 0x0002.
4.4.7.5
Arc Monitor CPLD version ZZ
This registers contains the third number of the version in the least significant byte.
Example: If the Arc Monitor software version is 00.02.01 this register has value 0x0001.
4.4.7.6
Arc Monitor ID, byte x
The ID number is presented using 5 bytes.
Each register contains one byte in the least significant byte.
7
-
6
-
5
CSU22
4
CSU21
3
X3
2
X2
1
External
HMI
0
Internal
HMI
The first part of the ID number is static, it is always
“1S16010”.
Then byte 4, 3 and 2 follows in decimal format with 2 digits for each number.
Finally a 16-bit word constructed from byte 1 as most significant and byte 0 as least significant is added as a 4 digit decimal number (byte 1 << 8 | byte 0).
Example: If the Arc Monitor ID registers contains the following values:
Arc Monitor ID, byte 0
Arc Monitor ID, byte 1
Arc Monitor ID, byte 2
Arc Monitor ID, byte 3
Arc Monitor ID, byte 4
HMI SW version XXYY
0x00D9
0x0007
0x0012 (18)
0x000E (14)
0x0048 (72)
The HMI is the HMI that is queried on the Modbus network.
See 4.4.7.1 Arc Monitor SW version XXYY above.
4.4.7.7
HMI SW version ZZ
See 4.4.7.2 Arc Monitor SW version ZZ above.
4.4.7.8
HMI HW version
See 4.4.7.3 Arc Monitor HW version above.
4.4.7.9
HMI ID, byte x
See 4.4.7.6 Arc Monitor ID, byte x above.
4.4.7.10
Other HMI SW version XXYY
Other HMI is the HMI that is not queried on the Modbus network.
See 4.4.7.1 Arc Monitor SW version XXYY above.
4.4.7.11
Other HMI SW version ZZ
See 4.4.7.2 Arc Monitor SW version ZZ above.
4.4.7.12
Other HMI HW version
See 4.4.7.3 Arc Monitor HW version above.
4.4.7.13
Other HMI ID, byte x
See 4.4.7.6 Arc Monitor ID, byte x above.
4.4.7.14
X2 HW version
See 4.4.7.3 Arc Monitor HW version above.
4.4.7.15
X2 CPLD version XXYY
See 4.4.7.4 Arc Monitor CPLD version XXYY above.
This corresponds to ID
1S16010 72 14
0x48 0x0E
18 2009
0x12 0x07D9
29
4.4.7.16
X2 CPLD version ZZ
See 4.4.7.5 Arc Monitor CPLD version ZZ above.
4.4.7.17
X2 ID, byte x
See 4.4.7.6 Arc Monitor ID, byte x above.
4.4.7.18
X3 HW version
See 4.4.7.3 Arc Monitor HW version above.
4.4.7.19
X3 CPLD version XXYY
See 4.4.7.4 Arc Monitor CPLD version XXYY above.
4.4.7.20
X3 CPLD version ZZ
See 4.4.7.5 Arc Monitor CPLD version ZZ above.
4.4.7.21
X3 ID, byte x
See 4.4.7.6 Arc Monitor ID, byte x above.
4.4.8 Reset
Write value 1 to this register to reset currently active trip, if any.
4.4.9 System date
Read or update the system date. The date is stored in the
Arc Monitor so if updated it will take up to 2 seconds for the change to reflect in the HMI.
The date is expressed as number of days since January 1,
1970.
Example: the value 0x42B6 (17078) corresponds to
October 4, 2016.
4.4.10 System time HHMM
Read or update the system time. The time is stored in the
Arc Monitor so if updated it will take up to 2 seconds for the change to reflect in the HMI.
The time is expressed in 24h format as a 16 bit value where the most significant byte contains the hours and the least significant the minutes.
Example: the value 0x0922 (2338) corresponds to 09:34.
4.4.11 Modbus failure register
This register contains the PDU Address of the Modbus register that was involved in the last Modbus exception.
Example: if one attempts to read System date and System time HHMM (PDU addresses 1100, 1101) but accidently specifies 3 registers instead of 2, one will get an Illegal
Data Address exception as response since also address
1102 will be queried. The Modbus failure register will contain value 0x044E (1102).
31
4.4.12 System state
This register contains a 4-bit bit field that reflects the system state.
Bit 15
-
14
-
13
-
12
-
11
-
10
-
9
-
8
-
7
-
6
-
5
-
4
-
3
Diagnostics running
2
System start sequence
1
There is an active error
0
There is an active trip
4.4.13 Diagnostic Trouble Code, number x
These registers contain the same data as Diagnostics error
DTC number x and y but with only one byte per register.
It might be easier to retrieve the information this way.
See 4.4.3.4 Error x DTC, number y and z above for more information.
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
5 Troubleshooting
34
34
5.1 Visual diagnostics
5.2 Example of reading with modpoll
33
5.1 Visual diagnostics
The yellow Com LED flashes when a Modbus request is received.
5.2 Example of reading with modpoll
Using the application modpoll [3] from a windows environment, it is easy to query the Arc Guard System™
TVOC-2.
The following command is an example of how the TVOC-2 status can be read:
C:\Windows\System32>REM This connects to a slave with Modbus id 247 on COM1
C:\Windows\System32>modpoll -m rtu -0 -a 247 -r 1300 COM1
RTU protocol, pdu addressing, Modbus id, register, com_port modpoll 3.4 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2013 proconX Pty Ltd
Visit http://www.modbusdriver.com
for Modbus libraries and tools.
Protocol configuration: Modbus RTU
Slave configuration...: address = 247, start reference = 1300 (PDU), count = 1
Communication.........: COM35, 19200, 8, 1, even, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
-- Polling slave... (Ctrl-C to stop)
[1300]: 0
-- Polling slave... (Ctrl-C to stop)
[1300]: 0
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
6 Index
Symbols
2-Wire Topology
A application modpoll
Arc Monitor CPLD version ZZ
Arc Monitor HW version
Arc Monitor ID, byte x
Arc Monitor SW version XXYY
Arc Monitor SW version ZZ
ASCII
Available registers
B
Bias resistors
C communication parameters
Configuration via HMI
CPLD
Custom name, letter x and y
Custom name registers
D
Diagnostics
Diagnostics information diagnostic trouble code (DTC)
Diagnostic Trouble Code, number x
Dip switches
DTC
E
Error information
Error x date
Error x DTC, number y and z
Error x time HHMM
Error x time SS
Example of reading with modpoll
G
Gateways
H
HMI SW version XXYY
HMI SW version ZZ
I
Implementation class
Installed modules
Introduction
11
32
26
26
27
26
26
25
19
11
14
14
26
25
25
24
24
25
29
26
25
24
24
25
24
24
32
11
27
27
18
25
7
L
Last performed diagnostics date
Last performed diagnostics time HHMM
M
Modbus
Modbus cables
Modbus connector
Modbus failure register
Modbus functions
Modbus id
Modbus installation
Modbus masters
Modbus registers
N
Number of errors
Number of trips
O
Original instruction
P
PDU Address
Perform diagnostics pin configuration
Pull-up / pull-down resistors
Q
Quick start-up
R
Read Registers
Read this first
Register data format
Repeaters
Reset
Revision
RS485
S
4,725 mm
System date
System state
System time HHMM
29
24
10
11
7
25
23
2
28
34
10
18
3
23
11
3
28
29
28
24
24
7, 10
10
10
29
18
14
11
11
19
T
Termination
Termination resistors
Transceiver
Trip information
Trip x date
Trip x detector
Trip x detector, high
Trip x detector, low
Trip x time HHMM
Trip x time SS
TVOC-2-COM
V
Version information
Visual diagnostics
W
Warning and safety
Write Registers
26
32
3
19
10
23
11
11
23
23
23
23
23
23
7
37
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
Notes
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
—
Notes
Draft, ne pas diffuser Wed Dec 05 2018 12:41:51 GMT+0100 (Romance Standard Time)
ABB AB
Electrification Products Division
Low Voltage Products and Systems
Protection & Connection
Motorgränd 20
SE-721 61 Västerås / Sweden
You can find the address of your local sales organisation on the ABB home page.
http://new.abb.com/low-voltage/products/arc-guard http://www.abb.com/lowvoltage
We reserve the right to make technical changes or modify the contents of this document without prior notice.
ABB does not accept any responsibility whatsoever for potential errors or possible lack of information in this document.
We reserve all rights in this document and in the subject matter and illustrations contained therein. Any reproduction, disclosure to third parties or utilization of its contents – in whole or in parts – is forbidden without prior written consent of ABB.
Copyright© 2018 ABB - All rights reserved
advertisement