IO_Rack

It is probably scaled in the HMI... or was scaled. It's also possible the data type is different. If I remember correctly, the CQM1 used only BCD data type for timers. Instruction set changed significantly with the CQM1H.  If you can post the PLC program then do so. If not, take a screen shot of the timer and we'll be able to help you with that.

Are you sure the program is lost? What do you see on the screen? The battery in the NT31C is for the clock only. The program is stored in flash memory.

From the looks of your picture, you have 2 Special I/O modules. The Host Link unit and (I think) a High Speed Counter module. As gtsuport mentioned, check the I/O Table. Make sure the Unit Numbers in the program match the dial settings on each unit. 

I've been using Omron products for over 30 years. This will still get me once in a while!

There is a lot of information in the manual for Pulse Output control. You should review it carefully. Here are some points that are helpful. If performing Absolute positioning, make sure to perform an Origin first using the INI instruction. You can perform all position moves using the PLS2 instruction. You can use the P_ER contact immediately after the PLS2 instruction to identify an instruction error and ensure you have input valid values. Before looking for motion, make sure the output is turning ON. This way you can verify your programming before troubleshooting the wiring.

That won't work. Here is the PLC to PT cable.

The counter reset is a function of the PLC because HSC is performed in hardware. What is the PLC model? In most cases it will be a bit in "A" memory. Take a look at the Operation Manual as opposed to the Programming Manual.

Every time I see one of these in the forums, there are no responses. I had experience with these many many years ago and the only thing I remember is it was very cumbersome. Hopefully the application is small because I believe you will have to rewrite.  If it's worth it to you, I would purchase an NV since you will likely have to rewrite. They have a small footprint, inexpensive and the software is installed with CX One.

If this is your program then you can call Omron Tech support. No other discussions will be allowed here in the forums.

Below appears to be a counting function at the end of the program. Zeros are moved into the the result when W40.01 and/or W40.02 are turned ON. This is internal memory in the PLC. They are most likely tied to a reset button on an HMI.

1)  Verify the actual machine with the electrical schematics. 2)  Identify all the physical I/O in the current program and label them before performing the conversion. 3)  Evaluate and completely understand the HSC and Interrupt control. This will indeed need to be re-written.  If you are not a programmer, I would take Crossbow's advice to seek an integrator for this. Contact your local Omron representative. Some very good offices may be able to help you with the conversion. I'm not sure about distributers in Egypt.  Also, depending upon the amount of I/O, you may want to use a CP series PLC. They have built in HSC but it will still need to be re-written.

You are welcome. How critical is your product rejection? You may want to evaluate the hardware and software to make it fail-safe. For example.... what happens if the sensor fails? What happens if the solenoid fails?

If this is the case then latch the Long Item Detected. Then look at this: Use Data Shift in the middle leg of the SFT instruction. This will push sensor data into the shift register and shift the data. Then use the Data Reset to reset the sensor latch (Long Item Detected).

1) The SFT instruction will store the value of your Long Item Detected. You do not need to latch it. Try using 2.13 (Long Item Detected) in the first leg of the SFT instruction. If the timing becomes an issue then you may need to latch it but only until it is stored in the SFT instruction. 2) The 3rd leg of the SFT instruction will reset all data bits in W41. Try using CF114 (Always OFF) for this.

Yes it works but it may take some adjustments. For starters, double click the PLC in the project tree. Then change the Device Type and Settings to the new PLC. The program will convert. Note:  You will have to change the addresses for your physical I/O in the program. Your High Speed Counter will be different. It is built in on the CQM1H. You will need to purchase a CJ1W-CT021 module for the CJ1M. The programming will be a little different. If you can post your program we can answer questions more directly.

"An item with the same key has already been added." You need to delete the variables from the Global Variables table and unmap them. I would then build the project, map the variables again. They should be automatically added to the Global Variables list. You can not map the same variable twice. I don't know why if would suddenly be unmapped after closing and reopening. When you get them added properly, copy and paste them into a spread sheet. This obviously doesn't fix the problem but will make things much easier.

The physical I/O may be different. There may be some errors with instructions but they are easy to replace with Omron. They are very good with backwards compatibility. Also, the fact that you have a CQM1H ("H" model) will make it even easier. The instruction set is much different between the CQM1 and the CQM1H. Do you have CX Programmer? This is easy to try in software. Can you post the program?

As suresh_ suggests, a shift register is the perfect method for this application. Below is an example of how to use it. I did not modify your program but I did label the contacts to make it clear. Notice I use the N.O. contact for Height. I typically do that to make the inspection fail safe. You may use inverted logic. 

1) Bits are accessible via the Dot ("."). Example address H50 may be any data type but you may access bit 4 in a boolean instruction (LD H50.04). 2) You may SET or RSET any BOOL. 3) NX1P is a small PLC with power supply and built in I/O. It will probably be the perfect fit for your application. The NX1P does not have built in high speed I/O. You will have to add an NX module for high speed.

You are likely to get a lot of different answers to this post. Here is a discrete method that uses a lot of contacts but does not use any special instructions. I don't have Siemens software handy.

You'll probably have to go with Prosoft Technology.

That would be my choice if I absolutely had to communicate serial.

Mine does not. I'm not sure if there are previsions to make that happen.  Version 5 should work on XP. I wouldn't upgrade on that PC. The newer 64 bit FTV will not run on XP. The changeover happened between version 6.  Check the hardware version of your PVP. If it is version 6 or newer then get a new PC and the latest version of FTV. If it is version 5 or older then you will not be able to create a runtime file with the newer software. If that's the case then either try to get your old software to work or buy a new PVP. To troubleshoot your old software.... check your Add/Remove programs in XP and make sure RSLinx Enterprise is listed. I've seen that once before when I did a fresh install. This was a long time ago so my memory only serves so much.

Version 5 is not supported on a 64 bit operating system.

Glad you got it working and thanks for the update.  Mixing up upper and lower words is common. I find it useful to create symbols before populating the instructions.