Modbus TCP connection to a Eurotherm nanodac

Hello Everyone,

Has anyone had experience accessing a Nanodac parameter via Modbus TCP in Ignition?

I’ve added the device ,the statut of the device is connected, but when I attempt to read a parameter, I get a timeout error.

Here’s the error message I’m receiving:

I followed the Modbus addressing recommendations from the Nanodac datasheet, as shown here:

Let me know if you need more information,Thanks

  • Does the documentation indicate what unit number to use? Ignition defaults to unit #0, but many devices need something else. (Commonly, unit #1.)

  • That snippet of the documentation suggests that the device uses zero-based addressing. Check the advanced settings of your device in Ignition.

Perhaps you can share the complete doc? Or a link to it?

This is the link of the nanodac,

  • Does the documentation indicate what unit number to use? Ignition defaults to unit #0, but many devices need something else. Its not specified on the datasheet
  • That snippet of the documentation suggests that the device uses zero-based addressing. Check the advanced settings of your device in Ignition,i played tried to add and substitude 1 to check but same issue

Try using unit #1, and definitely use zero-based addressing. (Changing the latter would not get rid of the error caused by the wrong unit number.)

Try this OPC Item Path in a test tag:

[yourDevice]1.HR791

That should be AdvancedLoop.Main.MasterPV with one implied decimal place.

The floating point address for that is 0x8000 + 2 * 791 =>

[yourDevice]1.HRF34350
1 Like


I tried it ,it seems to give the same result

Why did you name that tag "Connected" ?

But anyways, you need to:

  • Scour the user manual for examples that might show what unit # that device actually uses, and
  • Use wireshark or similar to see if any communication to that device is occurring--perhaps a firewall is interfering.

:rofl:,i used the opc browser to add the tag connected (the modbus device status),i just keep it and work with it.
Thanks ,i will check that and let you know

Hello,

Was there a resolution to the issue? I am having the same issue on a nanodac controller; no communication possible via Modbus.