The leader in industrial automation and control solutions

Introduction

All Maple Systems HMI+PLCs (HMCs) programmed with MAPware7000 are compatible with Modbus RTU Slave (Server). Configure your Controller and HMI+PLC (HMC) with the following parameters to establish reliable communication.

Applies to: MAPware7000

Overview

MAPware7000 supports Modbus RTU. Maple Systems HMI + PLC (HMCs) communicate with any device that uses the Modbus RTU protocol. The HMC/PLC uses the Modbus RTU (Unit as Slave) protocol driver to allow the Maple device to act as a slave in a single master, single slave or multiple slave format.

HMI+PLC Settings

The table below lists the communications settings that must be configured in MAPware7000. These settings can be found in the Network Configuration folder for the selected project in the Project Information window:

Shows the Recent Projects window in MAPware7000 when creating a Modbus RTU Slave (Server) project

Right-click the Com port that you will use to connect to the slave device, and then click Add… to display
the Node Information dialog box:

Shows the Node Information window in MAPware7000 when creating a Modbus RTU Slave (Server) project

NOTE: The Recommended Settings column is blank since the Modbus RTU Slave Protocol can be used with any controller supporting Modbus RTU Master. The available port may determine whether RS-232 or RS-485 should be used.

The Options column lists MAPware7000 options; your PLC may not support every option

NameRecommended SettingOptionsImportant Notes
PortNo recommended optionCOM1, COM2, EthernetThis is the HMC port that the PLC is connected to
ProtocolModbus RTU
(Unit as Slave)
No recommended optionSelect the appropriate protocol for your PLC
ModelModbus SlaveVaries depending on the selected protocolSelect the model that is most closely
associated with your PLC
Communication Setting: Baud Rate192004800, 9600, 19.2k,
38.4k, 57.6k, 115.2k,
187.5k
Must match the PLC serial port
Communication Setting: ParityNoneNone, Even, OddMust match the PLC serial port
Communication Setting: Data Bits87, 8Must match the PLC serial port
Communication Setting: Stop Bits21, 2Must match the PLC serial port
Power On PLC
Communication Time
No recommended option0-255 secondsDelays communications with the PLC after applying power to the HMC
Node Information:
Name
No recommended optionMaximum of 15
characters
Provide a meaningful description to the port
Node Information:
Address
10 to 255Assigns a network address to each PLC. Use when networking several PLCs on one COM port.
Node Information: Inter frame DelayNo recommended option0 to 3000 msecMinimum time delay between commands sent to the PLC
Node Information countNo recommended option0 to 5The maximum attempts by the HMC to resend unanswered command.
Node Information:
Response Time Out
No recommended option10 to 6000 msecThe time that must pass before the HMC reattempts to send an
unanswered command to the PLC

Connected Device Settings

The Modbus port on the connected device must be set to RTU master mode in order to properly
communicate with the HMC slave.

In IEC 61131-3 projects, a Modbus address must be manually assigned to each tag in the Tag Database.
To access the Tag Database go to Define > Tag Database, or click on the Tags folder in the project tree.
Assign the Modbus address in the appropriate COM column of the Tag Database.

NOTE: Read Write access will be specified in the tag database. Most tags are Read/Write, tags defined for input modules and some system tags will be Read Only.

Data TypesLengthModbus Address Range Notes
DINT, DWORD, REAL, TIME, UDINT2 Words (32-bits)400001 – 465534Note 1
INT, Retentive Registers, WORD, UINT1 Word (16-bits)400001 – 465535
BYTE, SINT, USINT1 byte (8-bits)400001 – 465535Note 2
BOOL1-bit000001 – 065535

NOTE 1: 32-bit types require two Modbus registers. The tag occupies the specified address and the next consecutive address. Tag addresses cannot overlap.

NOTE 2: 8-bit types require one Modbus address per tag. The data will reside in the low word of the register

IEC 61131-3 Modbus RTU Slave Mapping

Important note: Most Modbus Master Devices read blocks of data at a time; it is good practice to assign
consecutive Modbus addresses when using IEC Mode.

Important Memory Considerations

If your PLC memory range is smaller than the range supported by the Master Device, it is possible
to configure the unit to monitor PLC memory addresses that are not available. Because this can
cause unpredictable results, when you configure the Master Device, ensure that all selected PLC
memory addresses are valid for your PLC model.

Do not configure the Master device to write to any PLC memory address which should only be
written to by the PLC.

Wiring Diagram

The Maple HMC’s serial port connects directly to the communications port on the Master Device.

WARNING If your communications cable is not wired exactly as shown in our cable assembly
instructions, damage to the HMC or loss of communications can result.

Physical Port: 4.3″ Models

COM1: The 4.3″ models have 1 physical COM port that supports RS232 and RS485

1 Physical Port : COM1-RS232, COM2-RS485 for the HMC series

Physical Ports: 7.0″ Models

COM1: Terminal Block Port – RS232 / RS485

Terminal block port (COM1) pinout which for HMC series support RS232 / RS485 signal levels

COM2: DE9 Female Port – RS232 / RS485

DE9 female port (COM2) pinout for the HMC series which support RS232 / RS485 signal levels.

Physical Ports: 10.1″ Models

COM1 & COM2: The 10.1″ models have 2 physical COM ports that both supports RS232 and RS485

1 Physical Port : COM1-RS232, COM2-RS485 for the HMC series

Y Type Cable (all models)

  • Special “Y” cable for HMC unit (two communication levels on one port)
Wiring diagram for a special “Y” cable for HMC unit (two communication levels on one port

RS-485 – 2 Wire (all models)

RS485 2 Wire Instructions for the HMC

RS-485 – 4 Wire (all models)

RS485 4-Wire communication wiring connections for HMC