Exporting event records and shutdown waveforms: registers 51005 / 51006 / 51007 to 53501-55601
Summary: Appendix 2 of the PCS event and shutdown-waveform protocol defines a four-step read: write 51006 for the start index, write 51007 for the record count, write 0xBB to 51005 to refresh the data, then read registers 53501-55601. It answers why a unit shut down and what happened at a failed transfer far better than a panel fault code alone.
Appendix 2 of the PCS event and shutdown-waveform protocol defines a four-step read: write 51006 for the start index, write 51007 for the record count, write 0xBB to 51005 to refresh the data, then read registers 53501-55601. It answers why a unit shut down and what happened at a failed transfer far better than a panel fault code alone.
Four-step export and raw frames
(1) Write 1 to 51006 for start index 1, for example 01 06 C7 3E 00 01 14 B2. (2) Write the record count to 51007; reading one record is 01 06 C7 3F 00 01 45 72. (3) Write 0xBB to 51005 to refresh detailed fault data, for example 01 06 C7 3D 00 BB 65 01. (4) Read registers 53501 to 55601. The protocol describes 160 records, each containing 20 sixteen-bit variables sampled 100 times plus 4 date/time points, giving 2004 u16 values or 4008 bytes.
Reading the 20 waveform variables
Each sample holds, in order: inverter fault code, grid fault code, system fault code, battery fault code, unbalanced inductor current, phase A modulation value, maximum IGBT temperature, mode and status code, phase B and C modulation values, phase A/B/C voltages, phase A/B/C inductor currents, DC voltage, DC current, and positive and negative bus voltages. The first three fault codes map directly to the status bitfields (neutral anomaly, islanding, EMS communication-loss shutdown), turning a fault word into the 100 samples preceding the trip.
Timestamp parsing and field use
The first two date bytes are a bitfield: bDate 8 bits, bMonth 8 bits and bYear 16 bits with the year expressed as 2000 plus the value. The following two bytes are a 32-bit millisecond count equal to hours x 3600 x 1000 + minutes x 60 x 1000 + seconds x 1000 + milliseconds. On site, align the exported data, EMS event log, AEMS100 configuration screenshots and external waveform capture on one time axis to determine responsibility for failed transfers, spurious shutdowns, nuisance tripping and genset paralleling surges.
Frequently asked questions
Why write 51005 before reading?
0xBB triggers the refresh of detailed fault data; only after that command does the device stage the selected records into the read area starting at 53501. Skipping it returns stale or empty data.
Must all 160 records be read at once?
No. Register 51007 sets the count and the protocol example reads just one. Remember that 0x03 reads at most 125 registers per request, so split the reads by partition and reassemble the byte stream yourself.
Related equipment and guides
SP125HCPS · SP1350H54SW · STS200 · SP200/150HAPV · All technical guides · Product catalogue。
FAQ
Why write 51005 before reading?
0xBB triggers the refresh of detailed fault data; only after that command does the device stage the selected records into the read area starting at 53501. Skipping it returns stale or empty data.
Must all 160 records be read at once?
No. Register 51007 sets the count and the protocol example reads just one. Remember that 0x03 reads at most 125 registers per request, so split the reads by partition and reassemble the byte stream yourself.
