AB messaging stopped working

Chris_M

Member
Join Date
May 2022
Location
PA
Posts
40
I have several AB 1769's that transmit messages to each other.

Sometime last night/this morning one of the messages stopped transmitting. It is not an issue with the PLC or network as I am able to connect and there are other messages on the PLC that are working.

I am using CIP Data Table Write

The "Enable" Radio button was lit and there was no error code/ text/ path.

I had this happen before and my work-around was to message to another PLC and use that PLC to write to the intended recipient.
Is there a way to reset the message tag when this happens again?
Some way of detecting these communication breaks?
Thanks.
 
One of the issues with the logic often used to trigger messages is that they are programmed to keep repeating the message over and over. And when that happens, you sometimes don't get a chance to see the Error (ER) bit coming on. The message just re-triggers and the ER bit is cleared. Perhaps though the error message/code is still available.

When looking at the MSG in the logic, click on the ellipsis button (the button with three dots). In the Message Configuration window down at the bottom you would hopefully be able to see the status of the message along with an Error Code and an Extended Error Code.

Knowing these codes could help us sort out the problem and how to recover.

OG
 
Make an alarm or fault for if the enable bit is on too long with a ton, then set a latch bit. and if the error bit is set with a ton , then latch a bit.

There is a cache connection check box if you want the connection to stay open. Check that so that it does not have to open the connection repeatedly.
 
One of the issues with the logic often used to trigger messages is that they are programmed to keep repeating the message over and over.
...
Knowing these codes could help us sort out the problem and how to recover.
OG
I'm using a timer to send the message every 5 seconds. There was no error message in the configuration and no error codes to report.


Make an alarm or fault for if the enable bit is on too long with a ton, then set a latch bit. and if the error bit is set with a ton , then latch a bit.

There is a cache connection check box if you want the connection to stay open. Check that so that it does not have to open the connection repeatedly.
Cache connections is set. The EN timer is a good idea I will look into that.
 
Use this instead:
Code:
XIO Timer.DN TON
XIC Timer.DN XIO Msg.EN Msg

This guarantees the Message is ready to be run and has no outstanding resource allocations from previous attempts (waiting for timeout, and so on). You can follow up with more rungs to get message diagnostic data but this is the simplest way to do messaging 100% reliably.
 
Last edited:
Use this instead:
Code:
XIO Timer.DN TON
XIC Timer.DN XIO Msg.EN Msg
This guarantees the Message is ready to be run and has no outstanding resource allocations from previous attempts (waiting for timeout, and so on). You can follow up with more rungs to get message diagnostic data but this is the simplest way to do messaging 100% reliably.


Thanks, will do.
 

Similar Topics

Hey guys. Got a strange one. Was sent to a site where the VNC access is very poor. The IT has assisted and a Wireshark report shows data...
Replies
5
Views
216
I have a redundant ControlLogix being set up. This program reads a value from a remote site which happens to be SLC PLC. Rockwell mentions SLC...
Replies
2
Views
90
Hello, I have a ControlLogix redundant controller being set up. The program reads a value from a remote site which hosts a SLC PLC. Rockwell...
Replies
0
Views
69
Hi, First time poster, long time reader. I've got a mass flow controller device for controlling the flow of gas. It has a flowmeter and an...
Replies
4
Views
262
I am trying to set up a read message in a MicroLogix1100 to read the value of a DINT in a ControlLogix5561. I have successfully set up a message...
Replies
2
Views
182
Back
Top Bottom