AciConnect.dll

SUMMARY

This document describes the entries to connect the native ALPHA-VISION® VISUalisation to SoftPLC7.

INI-FILES

SoftPLC7.ini

Section [HLL-Functions]

In section [HLL_Functions] the function [AciConnect] has to be registered.
When registered, the values from SoftPLC7 are send to and read from ACI in advance to cycle start.
Prior the first cycle only a read is performed.

Entry Type Description / Example Default
PYstart,len [,part] string
The defined DLL-Function supplies the peripheral I/O bytes 0 to 255. The following syntax is used: <dll, function>
Note:
If parameter [, part] is missing, it will be replaced by the default '0'
Example 
PY0,256=MyDll, MyFunction

That entry assigns peripheral bytes to a process image. Actualization is done either after OB cycles or explicitly via SFC 26 and SFC 27, in that case a read after write is performed.

Note:
Prior to start of any first cycle only a read is performed.
For AciConnect the added line must exactly look like:
[HLL-Function] 
PY0, 0=SoftPLC7AciConnect, AciConnect

Section [AciConnect]

Entry Type Description / Example Default
<DataObject>.(Value|Status) string
Defines the data object and the attribute which is to be mapped to an address in the SoftPlc7. Currently only Value and Status are supported as attributes.

<S7-address>,(R|W|RW)[,F]

Defines the S7-address, read/write-access and data type.
WARNING
If both read AND write access RW are specified, and if the measuring value or status changes simultaneously in the SoftPlc7 and ACI / data source then one of the changes may be lost or different or toggling values in SoftPlc7 and ACI/data source may result.
A data type F means floating point / REAL, no data type means integer.
Example 
[AciConnect]
SINUS.Value=MD4,W,F
FIRE_DET.Status=DBX20.4,R
The value (Format=float) of data object SINUS is written to S7-Address MD4
The status of data object FIRE_DET is read from S7-Address DBX20.4
WatchdogRunState boolean
1: The ALPHA-VISION®-application watchdog is triggered only if SoftPlc7 is in RUN-State. See also Vision2000.ini where the watchdog data are specified.
0: The watchdog is triggered always.
0

Section [Aci]

Entry Type Description / Example Default
DoFile string
The Data Object File to connect to the Application Communication Interface
DebugOutput boolean
1: Enable debug output messages to a window.
0: Disable debug output messages.
0

Vision2000.ini

Section [WATCHDOG]

Entry Type Description / Example Default
<process> string
The point ID (for local monitoring only) and cycle time (seconds) for the watchdog touch of the process whose process ID is specified in the entry name <process>.
For a list of processes that support the watchdog functionality and further details, see: Watchdog
Example
Local monitoring: 
[WATCHDOG]
Prcs=PRCS_WDOG,10
Upd2Av=UDP_WDOG,25
Monitoring via multicast: 
[WATCHDOG]
Prcs=10
Upd2Av=25
FakeOsNo integer
Applies for monitoring via multicast only:
If this entry is active, the watchdog life signs of the operator station are sent with the fake operator station number instead of its own.
Example 
[WATCHDOG]
FakeOsNo=201

Section [WATCHDOG_CHECK]

Entry Type Description / Example Default
<station number>-<process ID> string
The point ID, time-out (seconds) and alarm value for evaluating watchdog life signs of the process running on the operator station specified in the entry <station number-process ID>.
For a list of processes that support the watchdog functionality and further details on receiving watchdog life signs via multicast, see: Watchdog
Example 
[WATCHDOG_CHECK]
101-Prcs= OS101_PRCS, 30, 2 
105-Udp2Av= OS105_UDP2AV, 20, 3
StartDelay integer
A delay time (in seconds) for the start of the watchdog check to avoid unwanted alarms at start-up.
Example 
[WATCHDOG_CHECK]
StartDelay=30