MODBUS TCP, Need Help!1

richleva

Member
Join Date
Sep 2012
Location
ontario
Posts
79
Hello,
I need some help/advice. I have a Micrologix 1400 series B on surface at a mine site. Underground I need to read hart data from a flow meter. We installed the Schneider STB with hart Modules. I can see that the STB module is properly retrieving all the data from the flow meter. But my problem is getting the PLC to retrieve the data from the STB module Via Modbus TCP.

I know that the ML 1400 Series B is compatible with Modbus TCP, I enabled it in the programming and setup my message instructions. But after I toggle a bit to enable the MSG instruction I get error "Local Communication is shut down?"

I made sure to enable the Modbus TCP Features.

As for the Schneider STB module, I can connect to it remotely from surface no problem and make changes to it, as needed.

I attached two Screen shoots of the RSlogix MSG configs for the totalizer and the STB registers.

Any advice is very appreciated.

Thanks everyone

Capture12.JPG Capture13.jpg
 
But after I toggle a bit to enable the MSG instruction I get error "Local Communication is shut down?"

This is (in my experience) a sure sign that you need to power cycle the PLC to get the changes to the Ethernet port to properly take effect.

Also, the node number (Unit Identifier) of 255 looks suspect. I'm not familiar with your other device, so it might be okay...some devices ignore the node number with Modbus TCP altogether since you are calling them out by IP address.
 
Ok Thanks Guys, I will try this tomorrow. But, when downloading to the controller. does it not cycle power on its own? Or maybe not...
 
Ok Thanks Guys, I will try this tomorrow. But, when downloading to the controller. does it not cycle power on its own? Or maybe not...

Not. It's only when making changes to the channel settings that a power cycle is required. Just changing the IP address may allow comms to keep working at least for a short while, but any changes to the port call for a power cycle. Enabling Modbus TCP and then going to run mode without power cycling has given me that same error.
 
This is (in my experience) a sure sign that you need to power cycle the PLC to get the changes to the Ethernet port to properly take effect.

Also, the node number (Unit Identifier) of 255 looks suspect. I'm not familiar with your other device, so it might be okay...some devices ignore the node number with Modbus TCP altogether since you are calling them out by IP address.

its been my experience that more times than not the unit id/slave id/node id whatever you want to call it, is significant even in modbus/tcp. you may want to ensure you are using the proper slave id number in your modbus poll.
 
Not. It's only when making changes to the channel settings that a power cycle is required. Just changing the IP address may allow comms to keep working at least for a short while, but any changes to the port call for a power cycle. Enabling Modbus TCP and then going to run mode without power cycling has given me that same error.

Everything Worked Perfect after the power cycle !!!
Thank you very much
 

Similar Topics

Does anybody have the available addressing (in Modbus TCP) for one of these recorders (or equivalent). ABB is being very stingy with information...
Replies
0
Views
1,205
Hi, I Have a TSX Premium with ethernet card and a Siemens PLC with a CP343-1 ethernet card. Both can speak Modbus. Anyone who have done this...
Replies
5
Views
5,236
If a device has Modbus RTU over serial and Modbus RTO over TCP and Modbus TCP then there is a difference between Modbus RTU over TCP vs Modbus TCP...
Replies
7
Views
348
Hi There. I have PC to get few tags from PLC into C# windows forms application. What is the best and fastest way? I could not find Omron in...
Replies
3
Views
160
I contacted Hach and bought a kit they recommended for a customer to add Modbus TCP capability to his Chlorine Analyzer with a SC4500 controller...
Replies
8
Views
193
Back
Top Bottom