Drivers/Managers connectivity status

[maherhodali]

Hello Everyone,

Can you please share how in WinCC OA we can identify if the driver/manager started or stopped. Or in case if there are internal data points that can detect such status ?

Regards

[leoknipp]

At the _Connections-datapoint the information is stored which managers are connected to the Event Manager.
For details please have a look at the WinCC OA Documentation: Reference tables --> Internal datapoint types.

Best Regards
Leopold Knipp
Senior Support Specialist

[tpjctrl]

I wanted to expand on this instead of starting a new topic and ask if it's possible to get the name / type of a driver when you have the driver number? the _Connections.Driver.ManNums holds the driver numbers of currently active connected drivers, but it would be nice to know the details of each active driver rather than just the numbers (as then you have to look at the console to understand what's what).

Cheers,
Tom

[dbindernagel]

You can have a look at how ETM does it in the System Overview (e.g. SystemOverviewNonRedundant.pnl).
(Looks like the work is done in the function 'workCBManagerTableDriver' in dist.ctl)

[leoknipp]

If the internal driver datapoint _Driver<num> (DP type _DriverCommon) is existing a running driver writes the information for the driver type to the element ".DT".

Best Regards
Leopold Knipp
Senior Support Specialist

[tpjctrl]

The _Driver[driver_num].DT works a treat, thanks!

[tpjctrl]

Further questions regarding _Driver<num> dps, from what I gather these are not auto created when a driver is added in the console, is there a way to auto generate them for all drivers on project startup? I can make the dps in a script when the project is running, but the problem is that once they are made, you then have to restart all drivers, so that the relevant info is added to the _Driver<num>.DT dpe. This is of course not very convenient on a live production project.

[kilianvp]

is there a way to auto generate them for all drivers on project startup?

No

[gschijndel]

these are not auto created when a driver is added in the console, is there a way to auto generate them for all drivers on project startup?

I think with an access control plug-in running in the data manager this is possible.
But it would be easier to add a script to the project that starts directly after the event manager and makes sure all drivers that are configured in the pmon have a driver datapoint. This only works if the datapoints are created before the drivers start, so perhaps an API manager is needed to delay the startup of the project.

[tpjctrl]

OK so perhaps someone can explain how the details are written into the _Driver#.DT dpes? if the _Driver# dp doesn't exist, there's no errors thrown in the log, so I'm assuming some script somewhere checks if _Driver#.DT exists, if so, it writes the data into the dpe, if not, it just carries on. Or is it not a script writing into the _Driver#.DT?