adccommunitymod (AutomationDirect) asked a question.
Created Date: April 15,2005
Created By: xterri
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Have a 450 with 60 inputs and 50 outputs, an analog module (3 channels), Ethernet communication with another 450, total of 650 lines of code. Scan time shows: Min 10 Max 25 Current ~18 Everything OK until a day ago when things started slowing down. Solenoids not responding. Motors not stopping at the spot they 're supposed to, but passing the spot. I remember that I had made a few changes two days ago, added a few lines of code. I am guessing that the scan time has gone longer than what it used to be. To shorten it, I put some GOTOs here and there to bypass some report generating lines, etc., but apparently not enough. Have not used STAGES at all. Not used to them, and don't know if I can do it really. The machine is a rotary table with half dozen stations. Read the manual, got some hints, but any ideas out there that can help shorten the scan time? I checked my WX/RX and it's not in a FOR NEXT Loop. Any other suggestions? Thanks.
Created Date: April 15,2005
Created by: xterri
Have a 450 with 60 inputs and 50 outputs, an analog module (3 channels), Ethernet communication with another 450, total of 650 lines of code.
Scan time shows:
Min 10
Max 25
Current ~18
Everything OK until a day ago when things started slowing down. Solenoids not responding. Motors not stopping at the spot they 're supposed to, but passing the spot.
I remember that I had made a few changes two days ago, added a few lines of code.
I am guessing that the scan time has gone longer than what it used to be. To shorten it, I put some GOTOs here and there to bypass some report generating lines, etc., but apparently not enough.
Have not used STAGES at all. Not used to them, and don't know if I can do it really. The machine is a rotary table with half dozen stations.
Read the manual, got some hints, but any ideas out there that can help shorten the scan time?
I checked my WX/RX and it's not in a FOR NEXT Loop.
Any other suggestions? Thanks.
Created Date: April 15,2005
Created by: Xeno_deicici
I am experiencing a similar problem with a 440 CPU. I found the DIV function would increase the scan time A LOT.
Maybe you have data collisions on the network and the 450 is taking too long to process a ethernet message?
Sorry if I don't help much, I am still a nubie myself
Created Date: April 15,2005
Created by: marksji
Are the scan times you listed the times before the problem or the times now? They are relativly short scan times; I don't know that you 're going to get them much shorter.
Are motors and solenoids getting their start/stop instructions via ethernet in any way? If so I'd look for trouble on your network.
Created Date: April 15,2005
Created by: elevmike
cant see the program but if you have configuration code that only needs to be scanned once, place that in a SBR that will only be called on the 1st scan. This may not be the problem, but it might improve overall scan time.
Just a thought...