Jump to content

Recommended Posts

  • 1 year later...
  • MVP 2023

Create an entry in your scan table of one big Stream type variable that will be larger than any message you anticipate receiving.  When something comes in that doesn't match your other entries it will land there-

image.png.1a656725b28a607d638045895c6abd40.png

 

image.png.0bae8cbc059d086a5520dfef9533ab48.png

 

I find the pre-defined string / variable entries in the Protocol Scan block to be extremely unpredictable.  I do almost everything with a general-purpose string receiver (as shown above) and then sort it out in ladder logic.  It's a little more complicated to do it this way but a lot more robust.

Joe T.

 

 

.

  • Thanks 1
Link to comment
Share on other sites

Thanks to you, it seems to work. But I have a question: Does the "incorrect message" when it appears can make my index MI3 equal to 9 or will it only affect MI900?

I tested it and it doesn't make MI3=9, but I want to make sure that it won't happen.  

imageforum1.png

imageforum2.png

Link to comment
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
×
×
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.