Modbus Address Mapper

Convert coils and registers between Modbus reference numbers, zero-based offsets, and one-based element indexes.

Quick answer

Convert Modbus addresses between 40001-style references, zero-based offsets, and one-based element numbers.

This is most useful when manuals, PLC drivers, HMIs, and SCADA software all express the same register in different formats. Enter the object type and known address format to normalize the other two representations before commissioning.

  • Reference number matches common manual notation like 40001 or 30001.
  • Zero-based offset is often what communication drivers and APIs actually require.
  • One-based element helps map the point position inside the selected Modbus object family.

Mapping Inputs

Use this tool to normalize vendor manual addresses, PLC driver offsets, and SCADA tag configuration values before commissioning or troubleshooting.

Mapped Address

Reference Number
0 ref
Reference-style address for the selected Modbus object group.
Zero-Based Offset
0 offset
Zero-based offset often required by drivers and software integrations.
One-Based Element
0 element
One-based index inside the selected object type.
Mapping Note
Select a Modbus object type and input format to see the mapped values.

Why these values matter

Modbus address confusion usually comes from mixing human-readable reference numbers with driver offsets. If a point reads the wrong register, confirm that the integration expects a zero-based offset instead of a 4xxxx or 3xxxx reference.

Keep the object type aligned as well. A correct number on the wrong object group can still return invalid or misleading data.

Frequently Asked Questions

Does 40001 equal offset 0?

In common Modbus reference conventions, yes. Holding register 40001 is usually treated as the first register and corresponds to zero-based offset 0.

Can I use this for coils too?

Yes. The mapper supports coils, discrete inputs, input registers, and holding registers using practical reference-base assumptions.

What This Calculator Is For

Modbus addressing becomes confusing fast because device manuals, HMIs, PLC drivers, and SCADA packages do not always describe the same address in the same way. One system may show a holding register as 40001, while another expects an offset of 0, and another uses a one-based word index.

This tool helps convert those common Modbus representations into a cleaner practical reference.

Typical questions include:

What It Calculates

The tool maps common Modbus object groups:

It converts between:

Core Relationships

For a selected Modbus object group:

Practical base assumptions used here are:

Practical Use Cases

This tool is useful for:

Important Limitations

This tool handles the practical address-number mapping problem, but real integrations can still differ because of:

Always confirm object type and driver expectations before commissioning live equipment.

FAQ

Is 40001 the same as offset 0?

In many common Modbus references, yes. 40001 is typically the first holding register and often corresponds to zero-based offset 0.

Why do Modbus addresses cause so many mistakes?

Because some tools show full reference numbers like 40017, while others want only the offset like 16. Both may refer to the same location.

Does this tool handle byte swapping?

No. This tool focuses on address mapping only. Byte order and 32-bit value assembly must still be handled separately.

Related Tools