Hi Trygve and barnes,

Most configuraion values, as the BaseMValve.Node.OpAutoOnly can be set in the configurator. Otherwise you can use the FirstScan object and connect it to SetDp or CStoAp to set values at startup. In the BaseMValve case you can set Mode.OpAuto to simulate a click on the Auto button.

If you want realtime performance you should use the plc objects, and not gdh_GetObjectInfo and similar. Most gdh function uses a database lock and can be forced to wait for processes with lower priority.

About the switch statement I can't see anything wrong. If you compile the PlcPgm with debug, the generated c-code is kept on $pwrp_tmp and you can see which line the compiler is complaining about.

/Claes

Hi and thank you for the reply.

If you specify OpAutoOnly in the configurator will you then disable the possibility to set the valves in manual? I will need that option.

How can I use SetDp or CStoAp to set the valve in auto? The function block for BaseMValve does not have an input for OpAuto, does it? Do you have an example of how this can be done?

Regards
Trygve

Right, only Auto is available with OpAutoOnly set.

Any attribute is reachable with a Get, Set, Res or Sto,



/Claes

As simple as that.
Thanks a lot.

Trygve

Its always simple when you know the answer.

Thanks for the debug hint. The switch statement works fine when you fix the syntax errors.

I will also use the first scan block, very good.

For completeness and future reference CArithm blocks with three state HOA and open/close or stop/start functions.