Advance Modbus Module Issue

Hello,

We want to configure the Ignition system as Modbus TCP Server. We installed and configure the Advance Modbus Module. Below is config

Device status shows connected. But we are not able to established connected with ignition using modscan running on the system with in the network.

Both device can ping each other and port 502 is also open between them.

Appericate any suggestion. Thanks in Advance.

I would suggest that you get in contact with Automation Professionals support, this is a commercially supported module and if you have bought a license for this module, they will be able to easily help you out.

Thanks for suggestion @David_Stone . We are in POC phase so we need to verify if this solution work with Ignition. I tried contacting them but was not helpful.

Sending me an email at midnight and calling it "not helpful" three hours later is not a good start. :frowning:

6 Likes

I could've sworn that AI never sleeps, you mean to tell us that you are actually mortal?

1 Like

That said, after setting up Unit #1 to use that limited set of registers, did you click the "Start or Restart" button? Changes to units do not take effect until then.

Did you check with the netstat utility to see if Ignition was listening on port 502?

Is there a reason you skipped 1.HR0 ? This module is always zero-based.

Also, show what you are attempting in ModScan.

Yes after setting up the unit we click on the start or restart button.

Below is message which i recieve

below is the output when i run netstat on the modscan system .253 is the ignition system

Below is modscan attempt

Also i notice that this is the error which i am getting in the ignition log

That means something else in your gateway is bound to port 502, blocking your use of the wildcard bind address. Use the -l option to netstat to show listening ports to help you find what that other software is.

1 Like

I tried this but does not give me result, I am using windows system. I also tried to restarting the system and servies no luck on that.

Try netstat -a -b in Windows. You'll have to manually identify the listening sockets.