PAmodulInit Module Configuration
- Aktualisiert2023-12-28
- 2 Minute(n) Lesezeit
PAmodulInit Module Configuration
Configuration is possible using (value) tables or PAbasic code.
Registration in PAbasic
Required include: PAmodulinit_Connect.I
| PAmodulInit_Software() | |
|---|---|
| ;$1 - IN [Normname/Const] [STRING] | label names |
| ;$2 - IN [Normname] [INT] | init-actuator |
| 0—deinitializing | |
| 1—initializing | |
| ;$3 - IN [Normname] [INT] | status |
| 0—not initialized | |
| 1—initialized | |
| -1—error when initializing | |
| -2—error when initializing | |
| PAmodulInit_Device() | |
|---|---|
| ;$1 - IN [Normname/Const] [STRING] | label names |
| ;$2 - IN [Normname] [INT] | init-actuator |
| 0—deinitializing | |
| 1—initializing | |
| ;$3 - IN [Normname] [INT] | status |
| 0—not initialized | |
| 1—initialized | |
| -1—error when initializing | |
| -2—error when initializing | |
| ;$4 - IN [Normname] [INT] | UserboxToDo |
| ;$5 - IN [Normname] [INT] | *_Remote.STS |
| ;$6 - IN [Normname] [TXT] | *_STS.TXT—status text from the module; optional: PAmodulinit_Dummy.TXT |
| PAmodulInit_Device_Ever() | |
|---|---|
| ;$1 - IN [Normname/Const] [STRING] | label names |
| ;$2 - IN [Normname] [INT] | init-actuator |
| 0—deinitializing | |
| 1—initializing | |
| ;$3 - IN [Normname] [INT] | status |
| 0—not initialized | |
| 1—initialized | |
| -1—error when initializing | |
| ;$4 - IN [Normname] [INT] | UserboxToDo |
| ;$5 - IN [Normname] [INT] | *_Remote.STS |
| ;$6 - IN [Normname] [TXT] | status text from the module |
| PAmodulInit_Userbox_Buttons_Reset() | |
|---|---|
| ;$1 - IN [INT] | UserboxToDo |
This macro can be used to reset userbox button variables (ToDo). If test components are used, this must be done partially.
Registration by (Value) Table
The (value) table for device modules is PAmodulinit_Device_Init.WTB.
The (value) table for software modules is PAmodulinit_Software_Init.WTB.
Device modules are divided into normal and permanently initialized modules, such as the PLC or the climatic chamber. The permanently (device-ever) initialized modules are automatically initialized by the Base Application when the test is loaded before the test bench goes into the basic state. Using PAmodulinit_ Device_Init.WTB an additional *_remote.STS (0 = wait for control, 1 = application controlled, 2 = user controlled) can be transferred for the device modules. This informs the PAmodulinit whether a user has taken over the manual control (_*remote.STS = 2) for a module. If this is the case, the corresponding module will not be initialized or deinitialized by PAmodule. However, a message is displayed in the message window. Furthermore, the status text for the device module can be transferred to the PAmodulinit, in column *_STS.TXT via a text variable.
In the case of the PAmodulinit_Software_Init.WTB (value) table only the module name, the initialization actuator and the initialization status have to be transferred.
When parameterizing via (value) tables, the columns *_remote.STS and *_STS.TXT are optional.
24.10.14 11:00:53;I; ; [PAmodulinit.P] INIT: module is controlled by user (name: Device20 (value table)) 24.10.14 11:00:58;I; ; [PAmodulinit.P] DEINIT: module is controlled by user (name: Device20 (value table))