In an installation there are 4 simovert VCs  - please look at the attached picture "simovert_VC (page 1)".

For the time being, each one is operated from the pmu local unit.

The customer wished to alternatively operate each one simovert from an operator panel op1s (operation is to be performed via pmu and op1s).

So, we provided the op1s for every drive (4 pieces in total), we connected it at X300 and we made the necessary modifications at the drive parameters, as follows:

-P53 (parameterization enable/disable) : 3 (parameterization only from pmu)

-P554 (S.ON/OFF1) : 619 (Bico 619 -OR1- is to operate the drive)

-P565 (S1.FaultReset) : 0 (No reset permitted)

-U239.0 (S.OR1. input 1) : 5 (ON/OFF1 from pmu)

-U239.1 (S.OR1. input 2) : 2100 (ON/OFF1 from op1s)

-U239.2 (S.OR1. input 3) : 0 (always 0)

-U950.90 (OR element 1 sampling time) : 6 (run OR element 1 every 5.2ms)

With this parameterization, the communication between op1s and the simovert is faultless, but the simovert cannot be operated from the op1s. Specifically, the following occurs:

1. The simovert starts and stops normally when operated from the pmu (by pressing"1" and "0" correspondingly).

2. When the "1" key is pressed at the op1s, the drive is trying to start and when the key is released the drive stops and the message "ON-COMMAND NOT AVAILABLE (to be released by parameter)"

appears in the lcd of the op1s - please look at the attached picture "simovert_VC (page 2)".

3. Also, when the "0" key is pressed at the op1s, the message "OFF(2/3)-COMMAND NOT AVAILABLE (to be released by parameter)" appears in the lcd of the op1s - please look at the attached picture "simovert_VC (page 3)".

As we have already mentioned, the op1s communicates without problem with the simovert and when we set the following parameter values :

-P53 (parameterization enable/disable) : 3 (parameterization only from pmu)

-P554 (S.ON/OFF1) : 2100 (ON/OFF1 from op1s)

-P565 (S1.FaultReset) : 0 (No reset permitted)

we can start and stop the simovert (by pressing the "1" and "0" key).

Could you please suggest any recommendations for the above problem ?

With Regards.

Thanks for your response.

I have intentionally prohibit the ability to parametrize the drive from the OP1s, because this is the client's specification.

But, as it is stated in the manual, P53 is : <<Function parameter for releasing interfaces for parameterization>> (for parameterization and not for operation).

Additionally, as I have already mentioned in my initial post :

<<... when we set the following parameter values :

-P53 (parameterization enable/disable) : 3 (parameterization only from pmu)

-P554 (S.ON/OFF1) : 2100 (ON/OFF1 from op1s)

-P565 (S1.FaultReset) : 0 (No reset permitted)

we can start and stop the simovert (by pressing the "1" and "0" key) from OP1s>>

So it is certain that, we can operate the drive from the OP1s, even if P53=3.

With Regards

Tasos