Mendon Systems

Well ...... You could temporarily remove the two input modules so that the OC211 module is plugged directly into the CJ1M and try testing by forcing the I/O. If you try doing that remember that the output numbers will change to 0.xx instead of 2.xx in that configuration. You should be able to test the relays by reading continuity between A8 & B8 to the output terminals. edit: The relays in the OC201 & OC211 will click loud enough for you to hear when they energize so you should be able to tell if they are even trying to energize.

If the LEDs are switching correctly then the PLC itself is working. One somewhat remote possibility is that the PLC power supply (probablay a PA202) is not providing the 24 volts to drive the OC211 relays. You might try another power supply. Another possibiliy is a bad connection in the bus between the modules but that would normally result in a CPU fault.

If you use the MAD42 internal calibration you must turn the calibration bits off when the procedure is completed. I have always found it easier to use whatever you get from the analog inputs and set up the gain and offset parameters in D registers that are adjustable from the touchscreen. You can then use a math calculation calculation to get the exact value you want. (Value = Input * Gain + Offset) For the case you have I would convert the input value to floating point and also use floating point for the gain and offset. If you have the MAD42 set up for 0-5 volts with a resoulution of 8000 your full scale input value (1.6 volts) would be 2560. To convert that to 16,000 you would need a gain setting of 6.25 and an offset value of zero. Once you get your math calculation working with fixed input values of zero and 1.6 volts you can adjust the gain and offset as required to get an accurate reading on the display.

The MAD42 does have a peak hold function that you could use. It requires some bit toggling to do it. The peak hold function is described in section 9-6 of the W345 manual.

The lowest scale available on the MAD42 module is 0-5vdc or 0-20ma. These are actually the same scale with a 250 ohm resistor connected in parallel by a switch to read the current. 20ma through that 250 ohm resistor results in a value of 5 volts into the input. The 10mv value from your power should be equal to .01 amps according to your power supply documentation.

I haven't seen anything simialr that is 24vdc. Encoders tend to be TTL output and that may also present a problem with connecting to your PLC

Something like these?? http://www.cui.com/product-spotlight/panel-mount-encoders-c14-and-acz-series/

I'm not sure that you can use timers and counters in ST in anything but a CJ2. I recall reading somewhere that they didn't work in a CJ1.

The CP1H-XA40 analog inputs are CIO addresses 200-203. The outputs are 210 & 211. The analog I/O description is in section 5-5 of the W450 manual

The "timer" and "counter" data types only exist in the CJ2 although CX-P will default to them in other PLCs. You need to change the data type to "number".

Some of the 900 mhz equipment is rated for that kind of range but the data rates are extremely slow, typically about 115kb/sec. The actual useable range will depend a lot on interference from outside sources and the antenna setup used. It can quickly become a very expensive project when antenna towers are required.

CJ2M-CPU3x PLC's can do that, other models are limited. Look through sections 6-9 of the W465 manual. 5 km over wireless will be a problem though. That is well beyond the range of most wireless networks without special trnasmitters and antennas.

Which version of Omron PLC??? Try working backwards from the output. I have seen things like SCL functions used to control analog outputs. If it's a TC module they are probably using the internal temperature control PID in the module. That instruction looks like an immediate refresh. Right clck on the contact and see what is selected in the options list.

The details of the A area assignments are in appendix C & D of the W462 manual.

Check the bit assignments for A280 and A281. They correspond to the two pulse outputs.

Yeah .... happens to all of us sooner or later!! I've lost count of how many times I've done that. The other one is forgetting to cycle power after making changes to the I/O setup!! That one has bit me a few times also.

Steve: I'm not sure what is going on. Here is what happens when I duplicate your rung in CX-P version 9.5. I created a symbol table with the same symbols that you have listed. Notice the difference in the way that the timer is displayed and that the timer is at preset when output 1.03 is off. The only suggestion that I can come up with is to try creating a stand alone program with only the timer rung and those symbols and test it that way. If that works OK then look for a duplicate symbol or timer used twice type of error.

It appears to me that there is something wrong with your Lamp_On_Time symbol definition. When I enter a similar rung CX-P displays the address of the symbol below the symbol name. Try entering the preset as just H10 and see what happens.

To use H10 as the timer preset you would replace the &50 in PDL's example with H10 and place the preset value in H10. The TIMX instruction allows the preset to be any decimal value, but regular TIM instructions require the preset value to be a BCD number.

Yeah, good point. The -V1 probably means he's got a CJ1W card. Dunno why he would do that unless he's trying to build a system with left over parts.

I suspect that he really has a CP1W-AD041 module, or at least that is what he needs.

Which PLC are you using and what analog module?

I would be very interested to know how the AD04U works out for you when you get it all set up. I have an application that uses a mixture of current loop and J thermocouple inputs that I am planning to try it on.

You must either use the differentiate up option on the inputs as shown in Mike's example or use an @++ instruction to increment the count. Either one of those will keep it from cycling more than once.

Try changing the upper an lower limit settings back to zero (none). You should get a result between zero and 4000 decimal.