ABB FSCA-01 Modbus adapter (ACS580/880)
Register map(s) for this device, with a note of how far each has been checked. Addresses are
0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.
coherence-checked
Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
| point | address (0-based) | type | scale | unit |
|---|
| ABB Drives Profile Control | 0 | U16 | 1 | |
| ABB Drives Profile Reference 1 | 1 | I16 | 1 | |
| ABB Drives Profile Reference 2 | 2 | I16 | 1 | |
| ABB Drives Profile Status | 3 | U16 | 1 | |
| ABB Drive Profile Actual 1 | 4 | I16 | 1 | |
| ABB Drive Profile Actual 2 | 5 | I16 | 1 | |
| DATA OUT 8 | 10 | U16 | 1 | |
| DATA OUT 9 | 11 | U16 | 1 | |
| DATA OUT 10 | 12 | U16 | 1 | |
| DATA OUT 11 | 13 | U16 | 1 | |
| DATA OUT 12 | 14 | U16 | 1 | |
| ABB Drives Profile Status | 50 | U16 | 1 | |
| ABB Drive Profile Actual 1 | 51 | I16 | 1 | |
| ABB Drive Profile Actual 2 | 52 | I16 | 1 | |
| DATA IN 1 | 53 | U16 | 1 | |
| DATA IN 2 | 54 | U16 | 1 | |
| DATA IN 3 | 55 | U16 | 1 | |
| DATA IN 4 | 56 | U16 | 1 | |
| DATA IN 5 | 57 | U16 | 1 | |
| DATA IN 6 | 58 | U16 | 1 | |
| DATA IN 7 | 59 | U16 | 1 | |
| DATA IN 8 | 60 | U16 | 1 | |
| DATA IN 9 | 61 | U16 | 1 | |
| DATA IN 10 | 62 | U16 | 1 | |
| DATA IN 11 | 63 | U16 | 1 | |
| DATA IN 12 | 64 | U16 | 1 | |
| Reset internal error registers | 89 | U16 | 1 | |
| Function code of the failed query | 90 | U16 | 1 | |
| Internal error code | 91 | U16 | 1 | |
| Failed register | 92 | U16 | 1 | |
| Last register that was written successfully | 93 | U16 | 1 | |
| Last register that was read successfully | 94 | U16 | 1 | |
link settings as documented (unverified): RTU; default 9600 8N1; unit ID 1; FC 03,06,08,16,23,43
bench facts as documented (unverified)
| terminals | X1 |
| wiring notes | RS-485 Adapter Module |
| FC 43 device ID | supported |
| doc revision | 3AUA0000044530 REV A |
field reports — community-sourced, unverified (checked 2026-06-11)
- The FSCA-01 RS-485 adapter module Quick Guide (document 3AXD50000158546 Rev A) contains a critical pinout labeling error for connector X1. It incorrectly labels Pin 2 as 'DATA_A (Data positive)' and Pin 3 as 'DATA_B (Data negative)'. The correct pinout, as documented in the User's Manual (3AUA0000109533) and Hardware Manual (3AUA0000044521), is Pin 2 = DATA_B (Data positive) and Pin 3 = DATA_A (Data negative). Connecting them according to the Quick Guide will trigger a crosswise connection error (indicated by a flashing orange NETWORK LED). [source]
- confirmed: comms.baud_rates: [9600, 19200, 38400, 57600, 115200] — confirmed by parameter 4 (BAUD RATE) in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A)
- confirmed: comms.default_baud: 9600 — confirmed by parameter 4 (BAUD RATE) default setting (0 = 9.6 kbit/s) in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A)
- confirmed: comms.default_unit_id: 1 — confirmed by parameter 3 (STATION ID) default setting (1) in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A)
- confirmed: comms.framing: ["RTU"] — confirmed by the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A) stating support for Modbus/RTU
- confirmed: comms.function_codes: [3, 6, 8, 16, 23, 43] — confirmed by the "Function codes" section in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A) (03h, 06h, 08h, 10h, 17h, 2Bh/0Eh)
- confirmed: comms.parity: "N" — confirmed by parameter 5 (PARITY) default setting (0 = 8 NONE 1) in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A)
- confirmed: comms.stop_bits: 1 — confirmed by parameter 5 (PARITY) default setting (0 = 8 NONE 1) in the ABB FSCA-01 Modbus Protocol Manual (3AUA0000044530 REV A)
- confirmed: facts.doc_revision: "3AUA0000044530 REV A" — confirmed by the title page of the ABB FSCA-01 Modbus Protocol Manual
The trust ladder
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
- generated — A prompt produced it. Unproven — anyone can regenerate this.
- structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
- coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
- hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.