Darin

First, make sure you have the model CPM2C with the clock. The clock information is resident in AR17 - AR21. The day of the week is represented in bits 0-7 of AR21. A value of 00 - 06 will be the day (00=Sunday, 01=Monday, etc). You can find this information in the programming manual (W353). Hope this points you in the right direction.

How fast do you need the input to respond? You can change the response time on the general inputs. The default is 8ms, but you can lower it to increase input response. Just make sure you don't have any chatter on the input point. Hope this helps.

Does anybody know how to map data from the Smart Active Parts in the NS to a CJ1? I would like to use the 3G3MV drive serial SAP's, however, I need to get data in and out of the drives by the PLC. Also is there a way to read the status of the drive? The standard serial SAP's look at parameters, but not the faults. I use the protocol macro now, but the SAP's might be an easier approach. I looked at using the drive function blocks in CXP, but could not get them working and would take more code then the macro does. Thanks for any input.

Thanks everybody for the help!

Does anybody have the details on the TXDU command for the new version 3 serial cards for the CS1/CJ1? Omron has not updated their manuals yet. I need to setup the RS-232 port on a CJ1W-SCU41 to no-protocol. The instruction help in CXP version 5.0 does not show the breakdown of the control words. Thanks in advance for any help.

I assume you are talking about CX-Programmer. Make sure you do not have any other software using a serial port open. Allen-Bradley software is especially nasty about keeping hold of the serial port even though the software is not running. When this happens, I have seen CX-Programmer give me errors you describe. Use your Windows task manager to make sure there is nothing else running. Also, double check your cabling.

When you set the counting mode to circular it will automatically start over when the counts exceed the maximum count setting. It behaves like an old drum counter. If you do not reset before the total counts it resets itself. Change the counting mode to linear if you want the counts to continue until you set the software reset of the counter.

In your program when you turn off 0.00 you move 20 to DM1 and 10 to DM2. Timers do not accept a new setpoint until they are reset and activated again. However, the scan is not fast enough to update the setpoint and start the timer. If you monitor your timer setpoints you will see the first time you run it works, but then after timer 1 is set at 2 seconds and timer 2 is at 1 second. The setpoint never changes back. I put a 0.1 second delay after 0.00 comes on before starting timer 1 and timer 2. It works and you can see the timer setpoints change back and forth. However, it will always have timer 1 at 1 second and timer 2 at 2 seconds because it is the last setpoints before the timer start.

I did a test program on this. You will want to use the floating point mutiply (*F). Your first word should be the 100000, which I loaded in a data memory (REAL data type). The second word is your D146 and then the third is your result (2 words). One thing to remember is as long as the logic is true the multiply function is executing (re-calculating). On a CJ1 that can be alot of calculations. If you want it to execute once when the logic goes true then put a "@" in front of the function (example: @*F). This will differentiate (one-shot) the function. It won't execute until the logic goes false and then true. This works on all the math and move functions in the Omron.

First, you need to define the registers you are using as REAL. In the NS-Designer change the data type for your numeric field to REAL. In CX-Programmer add your Data Memories to the symbol table and define them as REAL. A REAL value takes up two words, so in your application degrees will be DM140 and 141. Now all the values will be in the correct format. Omron's radian and tangent instructions requires the data be in REAL format to execute. By having the DM's already assigned as REAL the conversion is done. This instructions use two inputs and two output words. You should be using the Double Move (MOVL) instruction. This will move the real values properly. Hope this helps.

One other thing, make sure the proceesor is not a C200HE-CPU11. This is the only Alpha processor that does not support communication boards.

You will need a C200HW-COM01 or COM04 and the C200HW-CE001 bridge to connect a C200HW-CLK21 to an Alpha processor. The Controller Link card must be in the first slot next to the processor. The bridge is only long enough to go from the slot next to the processor to the communication card (COM01 or COM04). Hope this helps.

You might want to speed up the baud rate on the com port. The default com speed is 9600 so there usually is a delay from what is happening in the PLC and when you see it on your PC. On the SRM1 you can set the port up to 19200. It does make a difference in the communications.

Jay, Thanks for the tip about the Max NTLink Unit. I had mine set to 0 and so the screen did not work. I changed both processors to 1 and I have 1:N communications on both ports! Now I won't need the RS-422 adapters. I also created a screen which has data from both PLC's. It works just fine. The key was the maximum unit for the NTLink in the processor. Thanks so much for your help. I really am impressed with the wealth of Omron knowledge in this online community. I look forward to contibuting my knowledge as well.

I am in need of some help with connecting 2 CJ1M processors to a single NS screen. I was told by our Omron Distributor Manager from Texas (Jay you know who he is) that this could be done on NT-Link and CJ1W-CIF11 converters. He said register the hosts and set the unit numbers in the processors and it will work. Well, I am trying it and seem to have no luck. Jay, you did a good job training me on the NS (Certified 10/2002), however need some help with this one. I am using CJ1M-CPU12 processors, NS10-TV00B-V1 screens and CJ1W-CIF11 converters. Thanks in advance for any insight.