How-to
Exposing M340 EBOOL variables to Vijeo Designer Basic
Short answer
Vijeo Designer Basic can only tag the variable types its M340 driver lists, so an EBOOL that is absent cannot be selected. Copy the signal in the PLC program to a BOOL located at a %M bit, or import it by name, and point the HMI tag at the mapped variable. For operator commands the HMI writes a dedicated BOOL command bit that PLC logic consumes, never the EBOOL itself.
On this page
An EBOOL that the M340 driver's type list in Vijeo Designer Basic 1.2 does not offer cannot be tagged directly, and no setting in the HMI project adds a type the driver does not carry. The fix is one mapping in the PLC program: copy the EBOOL signal to a BOOL and point the HMI tag at the BOOL. For a status indication, that single assignment is the whole job. For an operator command, the HMI writes a dedicated BOOL command bit and the PLC logic consumes it, so no HMI write ever lands on an edge-sensitive EBOOL. Both directions, the addressing choice, a packing example for sixteen signals, and the proof tests are below.
Why the type list stops short of EBOOL #
The PLC's type set is wider than what an HMI driver transfers, and the variable-type list you see when adding the tag shows only the transferable subset. EBOOL is Unity Pro's boolean with edge memory: it records transitions so the edge-detection function blocks can act on it. BOOL is the plain on/off level an HMI actually displays.
Drivers drop Unity types they cannot carry, and the drop is documented behavior, not an anomaly. Vijeo Designer does not support Unity Date and Time (DT) types, and the New Variables From Equipment dialog box leaves out DT types along with any type that contains one as an element. Treat the absent EBOOL entry the same way: a boundary of the driver's type list, not a corrupted installation. Picking a neighbouring type does not create a mapping either — a tag whose type does not match the PLC variable reads wrong values, the same PLC-to-HMI boundary behind why an HMI writes the wrong PLC value above 9. For commissioning, read how forcing treats BOOL and EBOOL differently in Unity Pro before you force either type.
Decide the direction before you map #
Two cases, configured differently:
- Status, PLC to HMI. The panel only reads. One copy assignment per scan is enough, and the tag stays read-only.
- Command, HMI to PLC. The panel writes. Give the write its own BOOL command tag, and let PLC logic act on the rising edge, apply the machine's interlocks, and drive the EBOOL output. The HMI never writes the EBOOL itself: its edge memory belongs to the PLC's edge detection, not to an operator press.
Status gets a copy, commands get a consumed command bit. Nothing else holds up.
Map the signal in the M340 program #
- Open the application in Unity Pro or Control Expert, and in the Data Editor create the HMI-facing variable: type BOOL, located at a free %M bit — %M16 in this example. The Data Editor is also the tool for realtime read/write access to PLC data while you commission.
- Copy the source signal every scan with one assignment. With the existing source
Pump_Runningdeclared EBOOL and the newHMI_Pump_Statusdeclared BOOL := FALSE, the whole status mapping is:
(* illustrative names; one status copy per scan *)
HMI_Pump_Status := Pump_Running;
- For the command direction, create a second BOOL (for example
HMI_Pump_Cmdat another %M bit) and add logic that acts on its rising edge, applies the permissive conditions, sets or resets the output command, then resets the command bit so a held write cannot repeat the action. - Analyse and build the Unity project, download it, and confirm both new variables appear online.
Point the Vijeo Designer Basic tag at the mapped variable #
- With the M340 driver configured and the controller connection proven, add the variable and read the type list the driver offers in this installation. Select BOOL, the exact match for the mapped PLC variable.
- Address the located bit exactly as the Data Editor defines it. Bit addressing is what produces invalid bit address errors when adding HMI tags, so the %M reference must match the PLC project character for character.
- Set access deliberately: read-only for the status tag, read/write only for the command tag.
- If your project standard forbids located data, import the unlocated variable by name through the New Variables From Equipment dialog box instead of typing an address, and confirm the BOOL appears in that list.
- Build the HMI project and clear any unresolved-variable or type diagnostics before drawing objects.
Worked example: sixteen signals in one word #
Sixteen conveyor statuses held as EBOOL variables do not need sixteen tags. Copy each EBOOL to its BOOL, then pack the BOOLs into one INT word, with bit n carrying conveyor n + 1 at weight 2^n. One tag replaces sixteen.
| Conveyor | Bit | Weight |
|---|---|---|
| 1 | 0 | 2^0 = 1 |
| 4 | 3 | 2^3 = 8 |
| 8 | 7 | 2^7 = 128 |
With conveyors 1, 4 and 8 running and the rest stopped, the word reads 1 + 8 + 128 = 137. The panel shows 137 on one INT tag, and each lamp decodes its own bit: 137 AND 1 = 1 (conveyor 1 on), 137 AND 8 = 8 (conveyor 4 on), 137 AND 128 = 128 (conveyor 8 on), 137 AND 2 = 0 (conveyor 2 off). Below about eight signals, individual BOOL tags are easier to read and animate; at sixteen, packing wins on tag count and polling.
Prove the mapping before the screen goes live #
- Go online and open the Data Editor's variable list with the source EBOOL, the mapped BOOL and the packed word side by side, using its realtime read/write access.
- In a safe machine state, write the source EBOOL and confirm the copy follows on the next scan; set conveyors 1, 4 and 8 and confirm the word shows 137.
- On the panel, confirm the object follows the mapped variable, not a stale value.
- For the command path, press once and confirm the PLC consumed exactly one edge, the output changed, and the status came back before you call it done.
- Split the failure paths: every tag on the driver stale at once points at the controller connection; one tag reading nonsense points at its type or address. Rehearse the screens first, the way testing HMI simulation against a live PLC describes, before touching the running machine.
One safety note, where it belongs: an HMI write arrives with no interlocks, so the interlocks live in the PLC logic that consumes the command bit, and the command path is proven in a machine state where the commanded motion is safe.
The decision, case by case #
- One status signal: one BOOL at a %M bit, a read-only tag, one assignment per scan.
- One operator command: one BOOL command tag, read/write, edged and interlocked in the PLC; the EBOOL stays internal to the PLC.
- Sixteen or more status bits: pack into INT words, one tag per sixteen signals — 137 means conveyors 1, 4 and 8 in the example above.
- Projects that forbid located data: import the unlocated BOOL by name through the New Variables From Equipment dialog box and confirm it is listed before configuring the tag.
Questions asked
Is the missing EBOOL type a fault in my Vijeo Designer Basic installation?
No. The list shows only the types the driver transfers, and Vijeo Designer is documented to drop Unity types it cannot carry: Date and Time types, and any type containing one, never appear in the New Variables From Equipment dialog box. An absent EBOOL entry is the same boundary, not a corrupted project or a bad install.
Should the mapped BOOL be located at a %M bit or imported by name?
Locate it at a %M bit when you want to type the address straight into the driver tag: no import step, and the tag survives HMI project rebuilds. Import by name only when the project standard forbids located data; the import lists the Unity Pro variables whose types the driver supports, so confirm the BOOL appears there before configuring the tag.
Can the HMI write the mapped BOOL and reach the EBOOL output?
Only through logic you write. The status copy runs one way, EBOOL to BOOL, so a write to it changes the display and nothing else. For operator commands, add a separate BOOL command tag and PLC logic that accepts each write once, applies the interlocks, and drives the EBOOL output.
How many signals should I pack into a word before it is worth it?
Below about eight signals, one BOOL tag per signal is easier to read and animate. At sixteen it is one INT tag instead of sixteen: three running conveyors on bits 0, 3 and 7 read 1 + 8 + 128 = 137. The arithmetic is the test, because you decode the same bits back out of the word.
Does a stale tag mean the type mapping failed?
Not necessarily. A type or address error usually shows at build time or as one tag reading wrong values, while a failed controller connection leaves every tag on that driver stale at once. Check the connection first, then the tag's type and address, and treat the two as separate failure paths.