Technical FAQs

Ask a Question

Are EBOOLs used in UAG?

IO_PLC variables are mapped in Unity Pro to topological addresses of type EBOOL. In Unity Application Generator they are displayed with type BOOL.
PLC_HMI variables are mapped in Unity Pro to BOOL or EBOOL depending on the memory address.

UAG Type Connection Type Communication
Frame
Memory Address Unity Pro Type
BOOL IO_PLC text text EBOOL
BOOL PLC_HMI unlocated unlocated BOOL
BOOL PLC_HMI RW_BOOL %M EBOOL
BOOL PLC_HMI RW_ANY %MW BOOL

Unlocated variable can be generated in UAG by checking out the option 'Create unlocated PLC_HMI variables' in UAG customization as shown in following screen shot:



Unity Pro prerequisites:

Compatibility between BOOL and EBOOL:
EBOOL data types follow the rules below:
An EBOOL type variable cannot be passed as a BOOL type input/output parameter.
EBOOL arrays cannot be passed as ANY type parameters of an FFB.
BOOL and EBOOL arrays are not compatible for instructing assignment (same rule as for FFB parameters).
On Quantum:
EBOOL type located variables cannot be passed as EBOOL type input/output parameters.
EBOOL arrays cannot be passed as parameters of a DFB.

Types compatibility with address:
variable memory address I/0 address possible
BOOL %M (0x) %Q NO
BOOL %I (1x) %I NO
BOOL %IW (3x) %IW yes
BOOL %MW (4x) %QW yes
EBOOL %M %Q yes
EBOOL %I %I yes
EBOOL %IW %IW NO
EBOOL %MW %QW NO

Compatibility for DFB with In or Out pin:
variable DFB pin (In or Out) address possible
BOOL BOOL text yes
EBOOL BOOL text yes
BOOL EBOOL text yes
EBOOL EBOOL text yes

Compatibility for DFB IN/Out pin:
variable DFB I/O pin address possible
BOOL BOOL text yes
EBOOL BOOL text NO
BOOL EBOOL text NO
EBOOL, ARRAY OF EBOOL EBOOL, ARRAY OF EBOOL unlocated yes
EBOOL, ARRAY OF EBOOL EBOOL, ARRAY OF EBOOL located NO for Quantum only
Was this helpful?
What can we do to improve the information ?