Search results for query: *

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.

I agree with TW, the output port on most modules is 2, with the exception of the DH/RIO module, which has ports 2 & 3.

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.

Have a look at this site: http://www.controlguru.com/ There's a lot of good loop tuning information there.

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...

Couldn't you get by with only two compares? If A > B Then move A to N7:100 Else move B to N7:100

Simple solution: Use two or more message instructions, one for each target device.

These LCD's appear to take ASCII input, The ML1000 doesn't support ASCII.

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...

type FILEDIA at the command line, it should be 1,

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...

No messages required. The Panelview directly accesses the data in the plc.

Should be the RS232-DF1 driver, at the same port setting you used for the DOS software. If that doesn't work try SLC-500 DH485.

A DH+ card for a PC, not cheap. There is not an inexpensive way to connect to a DH+ network. The one exception being if you have a SLC 5/04, you can use the serial port and setup a pass through link to the DH+ network. However, it is slow, since you are still using a serial connection at the...

The USB 1747-CP3 is for usb to serial communictions, it will not work on DH+ port. The adapter is for the Micrologix PLC's. The driver you need to use is DF1 or perhaps DH485.

Glad to be of service.

From the RSLogix 500 help files: Application note: You can write any value to S:4. It will begin incrementing from this value. You can use any individual bit of this word in your user program as a 50% duty cycle clock bit. Clock rates for S:4/0 to S:4/15 are: 20, 40, 80, 160, 320, 640, 1280...

I forgot to ask, why are you doing this?