I would guess your false trips are at start up or shut down.
Add a small time delay to your logic. If all the conditions are met for say 5-10 seconds, then trip.
Post your question in the forums at www.mrplc.com, that board allows you to post your program. Then someone can take a look and tell you exactly what's wrong with it.
I don't know if this works in 2004, but it does in later releases.
There is a system variable called zoomwheel.
Just type in "zoomwheel" (without the quotes) at the command line.
0 (zero) Moves wheel forward zooms in; moving wheel backwards zooms out.
1 (one) Move wheel forward zooms out...
Has it every worked correctly?
Sounds like you need to write a homing routine in the logic.
On first pass or after E-stop, have the homing routine run.
Or it could be that the system is/was setup with absolute encoders, and someone replace the encoder with the wrong part.
You also have to match the baud rate and hardware or software error checking. Do you have a backup copy of the program? If you do, you can open that and see what the channel settings are, then configure the driver to match. You can also try the autoconnect feature.
In the PLC-5 family, when you add a remote chassis, depending on your addressing scheme, a certain number of words are already assigned in the I/O image table, even though the slots are empty. If you look right now, before adding the cards, you should see memory addresses for the slots. As long...
I assume you all ready have a counter that counts parts, cycles, whatever....
You need to know how often you want the rate updated. In my example I will use 5 seconds, but it could be any reasonable amount of time.
Use a 5 second self-resetting timer.
When the timer done bit is true:
1...
