GE Multilin F650, Инструкция по эксплуатации, Страница: 780 / 1046

B-8 F650 DIGITAL BAY CONTROLLER GEK-106310-AF
B.4 MODBUS DATA APPENDIX B: MODBUS PROTOCOL
B.4 MODBUS data
B.4.1 Data management
The data managed in ModBus differs in size and functionality. Depending on the functionality and importance of certain
data, the use of ModBus is optimized in time for real time processes, as in the case of events.
Although some configuration settings, such as GRAPHIC, PLC equations, TEXTS, and ALARM and LED configuration can be
read and written using ModBus protocol, formats are not shown because they are subject to change. Use the EnerVista
650 Setup program to manage and format configuration settings.
B.4.2 Writing settings
The process for changing protection functionality usually involves the modification of a group of settings that belong to a
particular protection function. This guarantees protection functionality and offers versatility for possible legacy programs.
Writing settings must be performed in two consecutive steps: Writing and Confirmation.
In order to perform this process, the MODBUS master must write the selected settings and then confirm the operation by
writing a register in the last position of this group. For safety reasons, there is a set time window within which the confirm
settings modification must be completed. The time window between the last settings being written to confirmation cannot
exceed 15 seconds.
B.4.3 Snapshot events
In the F650, the NEW EVENTS concept has been extended, providing additional functionality. These are the events created
after the last request.
Firmware version 1.60 adds a new way of reading snapshot events in binary format. Before this version, the relay sent
information only in ASCII format. The snapshot event retrieval is similar to the ASCII.
SNAPSHOT EVENT READING IN ASCII FORMAT
1. Write a message to the ‘0xfe00’ address, including the file name to open:
“EVE .TXT”: to read all events.
“NEW_EVE.TXT": to read events created from the last request of this same file.
“EVE0234 .TXT “: to read events starting, for example, from event number 234.
2. Subsequent messages read the 0xff00 address , in blocks of 250 bytes (4 bytes that indicate the point value to the
file, 2 bytes that indicate the number of data bytes sent, and 244 data bytes). If the number of data bytes sent is lower
than 244, this indicates that it is the last message.
If during this process there is an error response, the request can be repeated in address 0xff02 reading 246 bytes (2
bytes that indicate the number of bytes sent, and 244 data bytes).
In the second step, many BUSY responses may be produced, because an ASCII file is being created internally.
SNAPSHOT EVENT READING IN BINARY FORMAT:
1. Write a message to the ‘0xfe00’ address, including the file name to open:
“EVE .BIN”: to read all events.
“NEW_EVE.BIN": to read events created from the last request of this same file.
“EVE0234 .BIN “: to read events starting, for example, from event number 234.
2. Subsequent messages read the 0xff00 address , in blocks of 250 bytes (4 bytes that indicate the point value to the
file, 2 bytes that indicate the number of data bytes sent, and 244 data bytes). If the number of data bytes sent is lower
than 244, this indicates that it is the last message.