verified connector library

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 confirmed at the hardware-verified rung and at no rung below it.

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.

pointaddress (0-based)typescaleunit
frequency_command64055U160.01
torque_command64064U160.01
alarm_code64657U161
output_frequency64768U160.01
inverter_status_164769U161
output_current64771U160.01
input_voltage_dc64772U160.01
output_voltage64773U160.01
input_terminal_status64774U161
output_terminal_status64775U161
speed_feedback_frequency64790I160.01
torque64792I160.01
pid_feedback_value64802U160.01
input_power64809U160.01
output_power64810U160.01
cumulative_run_time65044U161
terminal_rr_input_value65077U160.01
terminal_rx_input_value65078I160.01
terminal_ii_input_value65079U160.01
fm_output_monitor65088U161
am_output_monitor65089U161

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)
connectorDual RJ45 shielded connector
wiring notesSupports Daisy chain topology and Star topology. Auto MDI-X and LLDP are supported.
max registers/read63
protocol notesWriting 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 notesSupports Read Device Identification (0x2B) for Basic and Regular Device ID.
FC 43 device IDsupported
doc revisionE6582125②

⚠ disputed: output_power @ 64810 — disputed by Embedded Ethernet Function Manual E6582125, which states output_power is at 0xFD30 (64816). 64810 (0xFD2A) is an invalid/unused address.

field reports — community-sourced, unverified (checked 2026-06-11)
  • Siemens S7-1200 MB_CLIENT block may return error 8381 (Function code not supported) when attempting to read registers like FD01h (64769) if the Unit ID is set to 0. To resolve this, change the inverter's C670 parameter (Emb Eth. Unit ID) to 1 and set the PLC's MB_Unit_ID to 1. [source]
  • The VF-AS3 does not have parameters for communication numbers ending in A through F (e.g., 0xXXXA to 0xXXXF and 0xXXAX to 0xXXFX). Reading a block of registers that spans these non-existent ranges will result in a Modbus error unless parameter F830 (MODBUS continuous address) is enabled (set to 1), which allows the drive to skip these addresses. [source]
  • confirmed: comms defaults and function codes (03, 06, 16, 23, 43) — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: Unit ID 0 or C670 value is used to access the inverter, and Unit ID 255 is used for the I/O Scanner — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: Dual RJ45 shielded connector supporting Daisy chain and Star topologies, Auto MDI-X, and LLDP — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: Writing via FC06 and FC16 writes to EEPROM (lifespan ~100,000 writes), while FC23 writes to RAM — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: frequency_command @ 64055 (0xFA07) — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: torque_command @ 64064 (0xFA40) — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: alarm_code @ 64657 (0xFC91) — confirmed by Embedded Ethernet Function Manual E6582125
  • confirmed: output_frequency @ 64768 (0xFD00) — confirmed by Embedded Ethernet Function Manual E6582125

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.