PLC5 to RSLogix5 update rate slow

One thing I just thought of:

If you check the main PLCs code for the MSG instructions to the troubled PLC, are they triggered by the DN bit of the previous MSG instruction to the same PLC ?
If that is so, the result will be that the PLC that responds to the MSG requests will work 100% on the channel, because there will allways be a new MSG instruction when the previous one finishes.

In that case, increasing the time slice will only mean that the troubled PLC will be just as bogged down with MSG requests as before, only it will be sending a lot more. It will probably then be the PLC that sends the MSG requests that becomes the bottleneck.

Also, I think that the most normal way to make MSG requests is to trigger them by event or by time (and not too frequent).
 
Jesper,

This is how our MSGs are triggered. Just for fun I did try to adjust the time slice, which had already been set at 10. I bumped up to 20 and down to 0 and saw no change whatsoever in update rate. I will do some searching on the MSG instruction and see if I can manipulate when we are using that to try to speed things up. Thanks a ton for the info.

Russ
 

Similar Topics

I'm having issues opening RSLogix5 version 8.0.0.3. on Windows 7. The program is unable to load and an error message stating "RSLogix5 PLC5...
Replies
2
Views
1,991
Hey guys! We been having issues opening RSLogix5 version 8.0.0.3. The program is unable to load and an error message stating "RSLogix5 PLC5...
Replies
1
Views
2,056
I try to start RSLogix5 and I get the following error; "RSLogix5 PLC5 Application has encountered a problem and needs to close. We are sorry for...
Replies
2
Views
2,172
Hi, does anyone know what the difference of the PLC5 programming software called TOPDOC and RsLogix5 is?? Which one would you recommend to purchase?
Replies
3
Views
4,068
Most of my lunch hour today has been spent searching the forum for help with this issue. While I did get some help from the various topics I still...
Replies
12
Views
4,920
Back
Top Bottom