Toshiba VF-AS3 drive

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire; word order and scaling are only confirmed at the hardware-verified rung.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale
frequency_command	64055	U16	0.01
torque_command	64064	U16	0.01
alarm_code	64657	U16	1
output_frequency	64768	U16	0.01
inverter_status_1	64769	U16	1
output_current	64771	U16	0.01
input_voltage_dc	64772	U16	0.01
output_voltage	64773	U16	0.01
input_terminal_status	64774	U16	1
output_terminal_status	64775	U16	1
speed_feedback_frequency	64790	I16	0.01
torque	64792	I16	0.01
pid_feedback_value	64802	U16	0.01
input_power	64809	U16	0.01
output_power	64810	U16	0.01
cumulative_run_time	65044	U16	1
terminal_rr_input_value	65077	U16	0.01
terminal_rx_input_value	65078	I16	0.01
terminal_ii_input_value	65079	U16	0.01
fm_output_monitor	65088	U16	1
am_output_monitor	65089	U16	1

link settings as documented (unverified): TCP; unit ID 0; FC 03,06,16,23,43; Modbus TCP over Ethernet. Unit ID 0 or C670 value is used to access the inverter. Unit ID 255 is used for the I/O Scanner.

bench facts as documented (unverified)

connector	Dual RJ45 shielded connector
wiring notes	Supports Daisy chain topology and Star topology. Auto MDI-X and LLDP are supported.
max registers/read	63
protocol notes	Writing via function codes 06 and 16 writes to EEPROM, which has a lifespan of approximately 100,000 writes. Writing via function code 23 (I/O scanning) writes to RAM.
identification notes	Supports Read Device Identification (0x2B) for Basic and Regular Device ID.
FC 43 device ID	supported
doc revision	E6582125②

generated by gemini:gemini-3.5-flash · harvested from https://www.toshibalatam.com/wp-content/uploads/2018/05/AS3-Embedded-Ethernet-Function-Manual-E6582125REV2.pdf (Toshiba); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.