GE B30 Communications Manual

Also see for b30: Maintenance manual Instruction manual Instruction manual Instruction manual Instruction manual

Contents

CHAPTER 2: MODBUS COMMUNICATION FILE TRANSFERSUR FAMILY – COMMUNICATIONS GUIDE 2-9232 Bit Binary — UR 7.4 supports this.32 Bit Float — UR 7.4 supports this.Single-file (.CFF) — Supported by devices that support IEEE 2013, so UR 7.4 supports this. One file with .CFF extensioninstead of four separate .CFG, .INF, .HDR, and .DAT files.Multi-file (.CFG) — When IEEE 1999 is selected, this option is selected automatically. When IEEE 2013 is selected,choose between CFF or CFG format.3. Click the Ok button to save and exit.2.3.1.4 Reading oscillography filesFamiliarity with the oscillography feature is required to understand the following description. See the Oscillography sectionin chapter 5 of the Instruction Manual for details.The "Oscillography Number of Triggers" register increments by one every time a new oscillography file is triggered(captured) and cleared to zero when oscillography data is cleared. When a new trigger occurs, the associatedoscillography file is assigned a file identifier number equal to the incremented value of this register; the newest file numberis equal to the "Oscillography Number of Triggers" register. This register can be used to determine if any new data has beencaptured by periodically reading it to see if the value has changed; if the number has increased then new data is available.The "Oscillography Number of Records" register specifies the maximum number of files (and the number of cycles of dataper file) that can be stored in memory of the relay. The "Oscillography Available Records" register specifies the actualnumber of files that are stored and still available to be read out of the relay.Writing “Yes” (that is, the value 1) to the "Oscillography Clear Data" register clears oscillography data files, clears both the"Oscillography Number of Triggers" and "Oscillography Available Records" registers to zero, and sets the "OscillographyLast Cleared Date" to the present date and time.For the IEEE 2013 standard, the following four time fields are added at the end of the configuration (.cfg) file:• Time Code (time_code) and Local Code (local_code) — The Time Code is the time difference between local time andUTC. The Local Code is the local time. Both are set to the same value as the Local Time Offset from UTC setting, andwhen this setting is 0, the time used is UTC time and the time zone is at UTC.• Time Quality Indictor Code (tmq_code) and Leap Second Indicator (leapsec) — The quality indicator indicates themaximum time error between recorded time and the time synchronizing source. Examples: 0 means clock uses itssource, 4 means time good within 1 ms, and F means unreliable. The leap second indicates when a second has beenadded or deleted, resulting in time stamps with a duplicate or missing second. Examples: 1 adds a leap second, 2subtracts a leap second, and 3 means that time source cannot address leap seconds.The fields are added in the file in two lines for time and time quality. An example is-6h30, -6h30A, 0They display in the software.Figure 2-3: Waveform image showing time fields