Configuration of the RK512 driver
The WCCOArk512 driver is started by the command line
WCCOArk512 [-num <driver number>]
Each driver running simultaneously must have a unique driver number so that the data points can be uniquely assigned to a driver.
If errors occur during program execution, for instance an invalid peripheral address is specified or the connection to the PLC fails, this is dealt with by sending the appropriate error data points to the Event Manager. The command line option -dbg 2 outputs on stderr all sent and received data plus the internal driver processes.
Table: WCCOArk512 driver parameters.
| Parameter | Comment |
|---|---|
| -num <driver number> | Assigns a unique driver number to the driver. The default value is 1. |
| -version | Returns the version number of WinCC OA and then closes the program. |
| -data [host name][:port number] | The driver tries to establish a connection to the data manager which is accessed on the computer given by host name under the port number specified by port number. |
| -event [host name][:port number] | The driver tries to establish a connection to the Event Manager which is accessed on the computer given by host name under the port number specified by port number. |
| -dbg [...] | Enables or disables various debug flags. The RK512 driver only uses debug flag 2. |
| -rcv [1, 2] | Displays the received messages in different levels of detail. |
| -snd [1, 2] | Displays the sent messages in different levels of detail. |
| -help | Returns a list of the possible command line parameters and then closes the program. |
| -log <filename> | Error messages are written to the specified file. A possible name is +stderr for instance. |
| -report 3 | The number of pending tasks are output in the Log viewer with this report command. |
