verified connector library

GF Signet 9900 transmitter

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
status0U32BE1
primary_reading2F32BE1
secondary_reading4F32BE1
measurement_type6U161
primary_units_of_measure_code7U161
secondary_units_of_measure_code8U161
modbus_address9000U161
network_termination9001U161
modbus_mode9002U161
baud_rate9003U161
parity9004U161
floating_point_endian9005U161
save_reboot9006U161
hsb_transactions9103U161
second_counter9104U161
bus_message_counter9105U161
bus_message_error_counter9106U161
slave_exception_counter9107U161
slave_message_counter9108U161
slave_no_response_counter9109U161
slave_nak_counter9110U161
slave_busy_counter9111U161
bus_character_overrun_counter9112U161

link settings as documented (unverified): RTU/ASCII; default 19200 8E1; unit ID 34; RTU is Default Mode. Data Bits and Stop Bits are automatically selected based on Mode (RTU: 8 data, 1 stop; ASCII: 7 data, 2 stop).

bench facts as documented (unverified)
terminalsTerminal board (M2 version), M12 Connector (M3 version), Wire Cable pig tail (M4 version)
A/B polarityD0 is RS485 -, D1 is RS485 +
terminationInternal programmable network termination enabled by Modbus command
connectorM12 or Terminal board or pig tail
shield/groundCom/Reset GND
protocol notesWrite 0 to register 49007 to save user device identification registers. Write Modbus Address to 49007 to save communication settings and reboot.
model register49561
serial register49591
firmware register49602
identification notesVendor Name at 49501, Product Code at 49516, Major/Minor Revision at 49526, Modbus Module Serial Number at 49596
power12 to 24 VDC Nominal, 10.6 to 32 VDC max regulated. Do not exceed 32 VDC.
doc revision3-9900.270.090 Rev 3 02/19
field reports — community-sourced, unverified (checked 2026-06-11)
  • Typo in the manual text on page 5: it references 'Register 490007' (6 digits) to save user device identification registers, whereas the correct register is 49007. [source]
  • The 9900 Transmitter in Batch mode (when the 3-9900.397 Batch Module is installed or when configured as a 9900-1BC Batch Controller) does not support the 3-9900.270-MX Modbus module or the 3-9900.395 HART Communication module. [source]
  • confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] with default 19200 — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Default Modbus Address (Unit ID) is 34 — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Modbus RTU and ASCII modes supported, with RTU as default — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Data bits and stop bits are automatically selected based on mode (RTU: 8 data, 1 stop; ASCII: 7 data, 2 stop) — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Default parity is Even (E) — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Power requirements are 12 to 24 VDC Nominal, 10.6 to 32 VDC max regulated — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: RS485 polarity is D0 as RS485 - and D1 as RS485 + — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)
  • confirmed: Shield ground is Com/Reset GND — confirmed by GF Signet 9900 Modbus Module Manual (3-9900.270.090)

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.