brewer

ML1000 MSG Instruction

7 posts in this topic

I have a SCADA system communication over serial radios and to one of my site I am getting a Error Message in my MSG Instruction "Hex 37" MSG timeout in local Processor".  The odd thing is i have communication with this site.  I am only running one message at a time and cascading through the messages.  Some of the messages do get through. My message time out is set to 5 and am having this issue with three messages to the same PLC.  So it is slowing my system down.

Share this post


Link to post
Share on other sites

What is your master controller ?  

When you say "some of the messages do get through", do you mean that of the three to that site two of them always get through, or some of each of the three sometimes get through ?    Does your system do any statistical collection on error rates or counts ?

Have any changes been made to the system lately ?   Do your radios have any independent diagnostics ?

In general, Error code 0x37 really does mean "timeout";   the local controller sent a query to the remote controller, and never got a reply.

This is different from the sort of error that you would get if the data table was unavailable, or there was a corrupted value like a CRC error.   With a MicroLogix 1000, the data tables are fixed in size and type, so the risk of mis-addressing is mostly limited to typos at the master side.

 

Share this post


Link to post
Share on other sites

The master controller is a ML1100 Series B.  The controller it is having trouble communicating to a Compct Logix L5332E .  I am not doing error tracking yet but I would guess I am getting 1 out of every 3 successfully.  All the other controllers are communicating with are ML1100.   I just seems odd that I am getting messages through  so my config should be ok.  

I have dropped the time out from 5 to 1 in the MSG instruction and my poll is better but that's just because the timeouts are finishing sooner.  I am only reading 20 registers per instructions.

Share this post


Link to post
Share on other sites

OK, that's a different set of conditions and devices.

Is your communications over serial, or over TCP/IP ?

What revision of firmware is the CompactLogix 1769-L32E running ? 

What protocol are you using;  DF1 full duplex, or half-duplex, or half-duplex Radio-Modem ?

Telemetry can be hard to troubleshoot, and the tools and techniques aren't as commonplace as ordinary automation electronics.  I used to make my living hooking up protocol analyzers and hunting for the correlation between communication failures and weather/temperature/vibration/traffic/time.

Share this post


Link to post
Share on other sites

Serial Communications

L32E REv 20.19

DF1 Radio Modem

 

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now