Hello, I’m starting a demo/proof of concept with Ignition 8 for the plant where I’m currently working and as a starting point I’d like to get a modbus TCP device (SOCOMEC Diris A40 electricity meter) connected via Modbus. I tried reaching the device with Ananas64 and I can read correctly with the …

Can you get values from this device with another piece of software like Modscan? If so, it would be useful to compare settings and to get a Wireshark capture of the successful traffic.

Hello, I can get data using ananas64 (which seems similar to Modscan) from the device. I just downloaded Wireshark and will have a look at what may be going on. I’ll post some more details here.

I didn’t manage to get Wireshark going, but I had another try at getting the comms to work and happened to notice this on the driver information: "The address in the device that mapping will begin at. Note that since the table has already been selected by the Modbus Type property, this number shoul…

It’s still unclear to me what addresses you’re supposed to be reading, which is why I was hoping for a Wireshark to clear it up. Many devices erroneously refer to HR’s as starting in the 40000 range when they really mean HR0 or HR1. The problem is it’s ambiguous because 40000 is also a valid holdin…

You may have a hard time using the Ignition Modbus driver for a Modbus device with non-standard addressing. The Ignition Modbus driver uses register designations (HR, IR, C, etc) to prepend the standard starting address number (3XXXXX, 4XXXXX) onto the beginning of the register number. For example…

I am trying to communicate with a Modbus Device (DIRIS 30A). Modbus addresses are in the 50000 range. Addresses I want to read in the device: |VAB_THD|51536| |VBC_THD|51537| |VCA_THD|51538| |IA_THD|51542| |IB_THD|51543| |IC_THD|51544| |P_AVG+|51078| |P_AVG-|51080| |Q_AVG+|51082| |Q_AVG-|…

Try turning the “Span Gaps” setting off. If that doesn’t work it might be worth getting Wireshark captures of the various softwares reading these registers so we can compare.

I just read my post and I realise that I am using Modbus Type : Input Register (Float) (Function 4) I should be using Holding Register (Float) (Function 3)… Here is my post anyway… Turning the “Span Gaps” setting off didn’t work. [image] [image] [image] Wireshark captures monitoring tag P_…

Can you zip those captures and upload them or DM them to me? Screenshots aren’t really that useful.

I came across this thread when trying to get values from Diris, however mine had the RTU module not TCP installed, so I used a Moxa MB3170 as a middle man. For anyone that may come across this, use this manual: https://www.socomec.com/files/live/sites/systemsite/files/SCP/6_gestion_energie/diris/di…

Inductive Automation Forum

Ignition8 with Modbus TCP problems

Ignition

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled