Sergei Troizky

Cannot see the attached pictures in this topic anymore! Are they deleted? For what reason?

I guess the HMI shows, not the PLC. What is the connection between the HMI and PLC?.

Yes.

I wish it existed. Lack of such is one of the biggest downsides of the tag addressing.

You could simply continuously copy the timer value to a data register, and move it to the timer in the first scan.

Did not read carefully the PLC model.

Yes, but if the output is defective, the OP will need to transfer the software to the replacement PLC, so it remains the password protection issue.

How did you apply 5000 value? Always remember, that in the Omron PLC instruction a bare number is not a number, but a CIO address. The speed is 32-bit, so MOVL should be used. Also, "if the SERVO UNLOCK, DEVIATION COUNTER RESET, EMERGENCY STOP, OR DECELERATION STOP command bit is turned ON, the jog command will be ignored. Be sure that all of these command bits are OFF before attempting a jog operation. "

For reverse jog, both Jog and Direction bits must be activated. Also, make jogging subject to the drive locked, and be sure to forbid any other commands to the axis during jogging.

An electronic calculator is a computer. It has all architectural components to be a computer by definition: CPU, memory, I/O devices. The most advanced ones are user-programmable for specific calculations. Any difference with personal computer is only quantitative. So, they might be sold as "handheld computer", "pocket computer", etc. And this is exactly what I meant for PLC vs PAC- a PAC is nothing else but just more powerful PLC.

Agree with this. Typical verbiage, to self-declare own product as "high end", like "magnum" in firearms or "pilsner" in beers. All the differences are quantitative and not all are that important or really necessary. And some are even disadvantageous, like the mentioned I/O update in the middle of the scan.

More speed- no. Probably, its speed limit will be even less. For more speed you will need to switch from the motor directly driving the ball screw to some transmission. More torque- yes. This is what a motor is made larger for. However, the ball screw will be in more danger in a case of jam or collision.

Read the Manual. There is a formula to calculate electronic gear for the motor encoder resolution and desired positioning pulses per motor turn. The default setup is NOT for the fastest possible motor speed at certain frequency.

The NC71 operates in positioning pulses. There are electronic gear parameters in the servodrive, defining the positioning pulses per motor turn. Are they set correctly for your application?

Here you are. Change the file extensions manually (this forum allows only limited type of file attachments). The 1st attached file is the .eds, the 2nd one is .ico (robot icon, if you want to have it in the Network Configurator). The eds works with R-30iA,R-30iB robots on CJ1W-EIP21 on CP1H and CJ controllers, and on the NJ CPU EIP port. Never tried it on CJ1W-EIP21 on NJ, but think it will work. Never tried it with older Fanuc controllers. fanucrobot0202.txt industrial_robot.txt

I used to be a long time user of FX0/1/2 but never worked with FX3. Recently, I was reading a FX3U program and discovered a new type of device- extension register R. The manual says it can be used the same way as D register, in 16- and 32-bit operations. Here comes the question: what are the extension registers intended for? Is there a case they MUST be used instead of D registers?

1516-1523 should indicate registered nodes. If zeros, these nodes are not registered for communication in the unit. Is the unit the connection originator? Is the unit #0? Was it restarted after the last download? Is the mentioned node address 59 decimal or hex? If hex, it is out of the 4-word range.

I would try this by adding a RS-232 module or board.

480V is not power, it's voltage. What power?

What power do you need during this seconds? What servodrives? Do they have DC bus terminals?

I already gave you a solution. Just replace the timers with any presently unused ones.

Not exactly, because the value must be BCD. A Hex notation may or may not look as a valid BCD notation, but the values described almost never are equal. Bridrum22, The BCD encoding dates back to the era of 7-segment indicators and thumbwheel switches. Today, I see no reason to use BCD encoding, except backwards compatibility on retrofit projects. Neither do I see any reason to use Hex encoding for numerical values. Use binary timers/counters, write and monitor values as decimal, and you will avoid many problems.

A scan is one pass of cyclic execution of the code by PLC. Physical outputs (Y) are being refreshed only once per scan, more specifically- between scans. Typical scan period is 5-10 milliseconds. Even toggling once per scan will not be properly executed by a solenoid valve, not to mention a cylinder. Did you probably mean activating the cylinder twice under the same conditions?

┬───(T1) │ T1 ├┤ ├─(T2) │ T1 ├┤/├┬(Y35) │ T2 │ └┤ ├┘ T1 is the 1st stroke duration. T2 is the valve off time between the strokes.

There is more than one way to reset a timer in Omron. 1. Put the reset condition as a NC contact in front of the timer (this is what Michael mentioned). 2. Use the CNR or CNRX timer/counter group reset instruction. It may be applied to a single timer. 3. Directly write the preset value into the timer. This may (but not necessarily has to) be done by the MOV instruction.