Arduino Opta Modbus RS485 Guide: Wiring, Termination, Client/Server and ArduinoModbus

The Arduino Opta RS485 and Arduino Opta WiFi include a built-in half-duplex RS-485 interface that can be used directly for Modbus RTU.

You do not need an external USB-to-RS485 converter or separate transceiver.

The important details are:

Opta Lite does not include the RS-485 interface, so native Modbus RTU wiring requires either Opta RS485 or Opta WiFi.

Which Opta Models Support Modbus RTU?

Opta model	RS-485	Native Modbus RTU
Opta Lite	No	No
Opta RS485	Half-duplex	Yes
Opta WiFi	Half-duplex	Yes

All three Opta versions still support Modbus TCP through their built-in Ethernet port.

Opta RS-485 Terminal Pinout

The RS-485 terminal block is labelled:

For another Opta, connect:

A/B Naming Is Not Consistent Between Manufacturers

This is one of the most common RS-485 problems.

Arduino follows:

but other manufacturers may use:

and some vendors reverse the A/B convention.

If an Opta is wired to a third-party device and there is no communication, one of the first checks should be the data-line polarity.

Arduino specifically notes that reversing A(-) and B(+) will not normally damage the RS-485 hardware, but communication will fail until polarity is correct.

Use a Common Reference Ground

For short same-cabinet links, connect:

as shown in Arduino’s Opta wiring diagrams.

On long industrial links, cable shielding, equipotential bonding and galvanic-isolation requirements depend on the installation.

Do not assume that connecting two distant cabinet grounds is automatically safe just because both devices use RS-485.

Opta Has No Built-In RS-485 Termination

This is critical.

Arduino explicitly states that Opta:

so termination must be added externally where required by the bus topology.

Typical Termination

A normal RS-485 trunk uses a termination resistor at:

of the main cable.

Common values are around:

but the correct value should match the cable characteristic impedance and the Modbus/RS-485 network design.

Do Not Terminate Every Device

If five devices are installed on one bus, you normally do not fit five 120 Ω resistors.

Termination is normally located only at the two physical ends of the trunk.

Too much termination loads the bus and can reduce the differential voltage.

Cable Recommendations

Arduino’s current Opta Modbus tutorial recommends twisted-pair cable in the general range of:

with cable impedance in the region of:

depending on whether the cable assembly already includes termination.

For longer runs, use proper twisted-pair industrial RS-485 cable rather than loose hookup wire.

Half-Duplex Operation

Opta RS485 and Opta WiFi use:

which means the same differential pair is used alternately for transmit and receive.

A device cannot transmit and receive simultaneously.

Modbus RTU Client and Server Roles

Modern Modbus terminology uses:

Older documentation often uses:

for the same basic relationship.

Arduino PLC IDE currently exposes both modern and legacy terminology in different parts of the interface and documentation.

Server Address Range

Arduino PLC IDE allows an Opta Modbus RTU server address in the range:

Each server on the bus must have a unique address.

Baud Rate and Serial Format

Every device on the Modbus RTU segment must use the same:

• baud rate;
• data bits;
• parity;
• stop bits.

Arduino PLC IDE currently offers baud rates from:

with:

Typical Modbus Settings

Common configurations include:

There is no universal setting.

The Opta must match the device it is communicating with.

Arduino’s PLC IDE Example Uses 19200 8N1

Arduino’s current Opta-to-Opta PLC IDE tutorial demonstrates:

with one Opta configured as the Modbus RTU server and another as the client.

Modbus Data Types

Modbus defines four main data tables:

Data type	Typical notation	Access
Coils	0xxxx	Read/write bits
Discrete Inputs	1xxxx	Read-only bits
Input Registers	3xxxx	Read-only 16-bit registers
Holding Registers	4xxxx	Read/write 16-bit registers

Register Addressing Causes Frequent Errors

A manual may describe a value as:

while a software library expects:

because the leading:

is a documentation convention rather than part of the transmitted Modbus address.

Always check whether the manufacturer’s register table is:

before assuming the first register is address 0 or 1.

Modbus Function Codes

Common functions include:

Arduino Libraries

For Arduino IDE development, two official libraries are relevant:

ArduinoRS485 handles the physical RS-485 serial link.

ArduinoModbus implements Modbus RTU and Modbus TCP protocol operations.

Raw RS-485 Test Before Modbus

When commissioning a new installation, it can be useful to test the physical layer first.

This does not send valid Modbus frames.

It simply confirms that the RS-485 transmitter, wiring and receiving equipment are functioning.

RS-485 Turnaround Delay

Arduino’s current Opta RS-485 example calculates pre- and post-transmission delays based on approximately:

which is also important in Modbus RTU because frame separation is timing-based.

The official Arduino RS485 library provides:

for this purpose.

Simple Modbus RTU Client Example

The following pattern reads one holding register from server ID 10:

Reading an Input Register

For a sensor documented as an input register, use:

Do not use a holding-register read simply because both are 16-bit values.

Writing a Holding Register

This typically produces Modbus function code:

Simple Opta Modbus RTU Server Example

An Opta can also expose its own registers:

Why poll() Matters

The server must repeatedly call:

so incoming requests are processed.

A blocking loop that prevents regular polling can make the server appear unreliable.

Mapping Opta Inputs to Modbus Registers

A typical application might expose:

This keeps the external Modbus interface independent from the physical pin names.

Using PLC IDE Instead of Arduino C++

Arduino PLC IDE can configure the Opta as:

without writing low-level Modbus frame code.

The configuration is under:

PLC IDE Client Configuration

For client mode you define:

• baud rate;
• parity;
• stop bits;
• remote Modbus node address;
• polling time;
• register/function type;
• word-swap mode where required.

PLC IDE Server Configuration

Server mode additionally requires a unique:

and variables/registers to expose to clients.

Arduino’s Official PLC IDE Example

The current Arduino tutorial demonstrates:

with a server-side counter exposed through an input register and a second Opta polling it as a client.

Modbus RTU Polling Time

Do not poll every device as fast as the CPU allows.

A practical network may contain:

• drives;
• energy meters;
• temperature controllers;
• remote I/O;
• multiple Opta controllers.

Each request and response consumes bus time.

Choose polling intervals according to how quickly each value actually changes.

Example Polling Strategy

Timeouts

A Modbus client should always have a timeout strategy.

If a drive is disconnected, the Opta should not freeze indefinitely waiting for it.

The ArduinoModbus client API provides timeout/error reporting support that can be used to:

• retry;
• raise an alarm;
• mark a device offline;
• fall back to a safe operating mode.

Data Width: Modbus Registers Are 16 Bit

A Modbus register contains:

but industrial values are often:

• 32-bit integers;
• 32-bit IEEE-754 floats;
• 64-bit energy counters;
• packed bit fields.

Those values span multiple registers.

Word Order Can Differ

A 32-bit value may be transmitted as:

and byte order may also differ between devices.

Arduino PLC IDE includes a word-swap setting for this reason.

Example: Float Across Two Registers

If a manual says:

you must know:

• which register contains the high word;
• which contains the low word;
• byte endianness inside each word.

Do not assume that all Modbus float implementations use the same order.

Common Mistake 1: Using Opta Lite

Opta Lite has Ethernet and can run Modbus TCP, but it does not have the RS-485 terminal hardware required for native Modbus RTU.

Common Mistake 2: Forgetting Termination

Opta has no built-in RS-485 termination.

If the Opta is at a physical end of the trunk, termination may need to be installed externally.

Common Mistake 3: Terminating Every Node

Only the physical ends of the main RS-485 trunk should normally be terminated.

Common Mistake 4: A/B Reversed

If the bus is silent, verify:

against the other manufacturer’s polarity notation.

Common Mistake 5: Wrong Serial Format

These must match exactly:

A device using 19200 8E1 will not communicate correctly with an Opta configured for 19200 8N1.

Common Mistake 6: Wrong Device Address

Each server must have a unique address from:

Common Mistake 7: Register Off-by-One Error

If the manual says:

the library may expect:

Check the vendor’s addressing convention before changing the wiring or baud rate.

Common Mistake 8: Wrong Register Type

FC03 and FC04 both return 16-bit words, but:

are different Modbus tables.

Common Mistake 9: Polling Too Fast

A client hammering multiple servers continuously can create:

• timeouts;
• bus collisions from badly behaved devices;
• unnecessary CPU load;
• slow response for important devices.

Common Mistake 10: Assuming RS-485 Means Modbus

RS-485 is only the electrical layer.

The same Opta RS-485 port can carry:

• Modbus RTU;
• custom binary protocols;
• ASCII protocols;
• vendor-specific serial communication.

Both ends must speak the same protocol.

RS-485 vs Modbus TCP on Opta

Feature	Modbus RTU	Modbus TCP
Physical layer	RS-485	Ethernet
Opta variants	RS485 / WiFi	All Opta variants
Topology	Multi-drop serial bus	Ethernet network
Addressing	Device ID 1-247	IP + Modbus unit ID
CRC	Yes	No RTU CRC; TCP/IP framing instead
Typical use	VFDs, meters, field devices	SCADA, PLCs, Ethernet gateways

When Modbus RTU Is the Better Choice

Use Modbus RTU when the field devices already use:

• RS-485;
• long daisy-chain cable runs;
• simple low-cost serial interfaces;
• legacy drives and meters.

When Modbus TCP Is Better

Use Modbus TCP when:

• Ethernet is already available;
• higher throughput is useful;
• SCADA or servers are IP-based;
• devices are distributed through an Ethernet infrastructure.

Quick Wiring Reference

Final Thoughts

Modbus RTU on Opta is straightforward once the physical layer and addressing conventions are understood.

The hardware already includes the RS-485 transceiver, so the main installation tasks are:

For Arduino IDE projects, the official:

libraries provide the physical and protocol layers.

For automation engineers, Arduino PLC IDE provides graphical Modbus RTU client/server configuration without manually constructing Modbus frames.

For the complete terminal layout, see our Arduino Opta pinout and I/O guide. For choosing the correct Opta hardware first, see Arduino Opta Lite vs RS485 vs WiFi.