autoreg and autofreg not working

[winthrop.polk]

I have been attempting to automatically registry a project on fresh install, but it doesn't seem to be working: I have tried with the command arguments in different order and both autoreg variations.

Code: Select all

$ /opt/WinCC_OA/3.16/bin/WCCOAui -config /opt/<redacted>/winccoa/<redacted>/config/config -autofreg
WCCOAui      (0), 2021.08.18 08:55:34.398,      WinCC_OA,       WCCOAui      (0), 2021.08.18 08:55:22.361: "/opt/<redacted>/winccoa/<redacted>/config/config" is not a registered config file !
WCCOAui      (0), 2021.08.18 08:55:34.388:  (-autofreg): could NOT re-register project "<redacted>" in "/opt/<redacted>/winccoa", rc = 63.

ATTENTION: default value of option vblank_mode overridden by environment.

So I need to register via the CLI, deployment must be automated... but I tested at the GUI:
- /opt/WinCC_OA/3.16/bin/WCCOAui -projAdmin
- click register project (runnable is checked)
- select the actual project folder --> "Error registering project! (Project: <redacted>)
- select the project config folder --> project is registered successfully... did it again to be sure and "This project is already registered"
- however, I do not see the project in either GUI, project admin or console.
- I then opened the file /etc/opt/pvss/pvssInst.conf and noticed this at the bottom

Code: Select all

[Software\ETM\PVSS II\Configs\config]
notRunnable = 1
PVSS_II = "/opt/<redacted>/winccoa/<redacted>/config/config/config"
InstallationDir = "/opt/<redacted>/winccoa/<redacted>/config"

Unknowns:
- why is notRunnable true when it was registered as runnable?
- why does the GUI error detection allow config/config/config to occur?

[winthrop.polk]

I seem to have figured it out:
- auto(f)reg only works on the pmon bin file.
- seems the pmon is designed to run continuously, so this is all designed to run as a service. Honestly learning how this software has been built and having much experience with other control systems, I can't imagine why someone wouldn't want to run it as a service... but I don't really understand why it was built without this piece... perhaps for developer work... but most IDEs run as services too, just different rolls.

This is the right way to register a project at the command line I guess... but it runs continuously so it's clearly only designed to be done as a service... /opt/WinCC_OA/3.16/bin/WCCILpmon -autoreg -config "/opt/<redacted>/winccoa/<redacted>/config/config" -proj <redacted>

[leoknipp]

The WCCILpmon (process monitor) can be started on demand or via the services.
Which is the preferred solution depends on the use case. E.g. in plant system most of the time the projects are started as service.
In engineering systems it is possibly easier to start the WCCILpmon (and a related project) on demand, especially when working on different projects during the day.

Best Regards
Leopold Knipp
Senior Support Specialist