CLICK PLC Modbus address mapping

Ignition
1

I am communicating OK with Modscan32 with my CLICK plc but cannot communicate through Ignition OPC server.

Have tried several different approaches and still no success.

2

How are you mapping your addresses, maybe you can post a screenshot of the addressing window so I can see what you are doing.

3

Thanks I got some help. Working now. Found that in the addressing that the prefix start and end are defined by me and have nothing to do with the prfixes that the PLC uses. Also needed to change to reverse work order on advanced properties.

4

Hello, I am having somewhat of the same problem. Ignition can already detect the diagnostic tags, but it can’t detect the actual Input Output tags (X001, Y001, etc).
I have the OPC UA server already configured and connected to the click PLC, but I can’t successfully ready any tags from the PLC. I’ve used a combination of the following paths with no luck:
Data type: Boolean:
Path:
[Click_PLC]X001
[Click_PLC]X001 (02)

5

These aren’t valid Modbus addresses.

Somewhere in your PLC program or configuration you’re going to have to map your tags to Modbus registers and then manually create tags addressing those Modbus registers in Ignition.

See https://docs.inductiveautomation.com/display/DOC80/Modbus+Addressing#ModbusAddressing-ManuallyAddressingaModbusDevice for documentation about the Modbus address syntax used in Ignition.

6

Thank you Kevin, is there any video tutorial you may be able to provide? It’s the first time I do this so it may take me a while to get the correct syntax to connect to the CLICK PLC

7

I’ve never used a click, but does this help? (quick google)
https://www.automationdirect.com/microsites/productivity/software/help/Content/198.htm

1 Like