I have problem using encoder for external display control (MD4-7). When using version 6.05.19.6064 everthing work fine.

With version 6.06.10.7344, the encoder(highlight square)  select some images instead of the button is supose to select.

In a similar vein as what was done with Custom re-usable function group.  It would be nice to have the same for graphic objects.

We think consistency in a visual interface is critical to a well perceived information.  For that matter, now that we can group images it would be very good if we could create library of standard object we can re-use though out a project or even across project or to display group of similar information. for example:

A lighted fault button:

or a pattern of repeating information:

Then modification of the master would apply to all.  This would apply strictly to the object graphic options, Color, Size relative position.  Each object group instance then can be associated with is own variables set.

Likewise and I had posted something like it to create within a project a set of "My colors"  so we can keep color consistency a bit easier than what we do now.

Idea: The ability to build in a redundant Master module. Installed so that they share state information over the diagnostic bus and automatically switchover if there is a failure. 

The redundant module would disable CAN and physical outputs until swapping over.

Will IQANdesign corporate license allow me to use IQANrun as well?

Thank you 

We require display pages that have a White back ground due to visibility issues in the sun. The Bar frames are white and do not allow yo to change the color like other bars that are offered.

Other Bars change

It is impossible to find this errors, see attached.

I have imported the components from another project writed with IQAN5.08 and I have deleted unused componetns and parts of software unused

We have a CAN Open sensor that has 2 sensor outputs under index 6020 subindex 1 and subindex 2. I get ambiguous identifiers which usually we resolve using page protocols but these are normally different index numbers so straightforward to configure.

How do i configure paged protocols when they have the same index of 6020? (only the subindex differentiates each output).

Shown in the picture the counter selected has 2 increasing single object arguments driven by directly by the 2 digital inputs, shown above the box. This is recording actual inputs from our machine, the digital in is not capable of being latched in the program nor in the increasing object. On the resetting side the Stop input is reading correctly. The single was deleted and a new one was added, with the same result. The new single was deleted and dual set up oppsite of the resetting was added, with the same result where both read 100. Design 6.06.10.7344

In order to move forward with the machine, the Stop single was deleted as I found it was redundant for what I was accomplishing. 

Apologies for the grainy picture as I had troubles with the screen shot on the computer.

Not sure if this is by design or a bug. 

for a lamp object, when I select Image library we have a choice of default images:

But when I select the same for the OFF Image the Image library appear to be empty:

Is this intentional?

We would like to be able to trigger the log page of a non display log (MC43) use a text button action in the MD4. Currently one action available for the text button is to trigger a log located in the MD4, but it does not allow triggering a log in another master. We utilize this function to allow the user to quickly review historical data for important machine events. For instance, when we winterize the machine, we log that it was winterized. We also log when the machine is de-winterized (water is sensed in the system again). The winterization page has a history button that allows the user to see each event. In our multi-master system, the winterization function is handled by the MC43, so the log is in the MC43. So, my history button does not function. The only solution I can see is to send winterization event status to the MD4 using a CAN message and move the log to the MD4. 

Alternatively, you could add a show trigger to the log. I would have to pass the VDIN to the MC43 via a CAN message and then use this to show the log page.