I had an unnecessary state in a Finite state machine (state 15), so I deleted it. This resulted in all of the states > 15 to change to a state one lower (state 16-> state 15). But all of the functions that utilize this FSM did not change resulting in all of these functions being incorrect.

Updates for cyber security

This version introduces important updates preparing for IEC 62443 cyber security compliance on target modules.

Secure boot and secure update

IQAN-MD5, -MC4xFS, -MC4x, -XC4 firmware’s are now signed. 

Signed firmware is required for installing on modules produced with secure boot.

IQAN-MD5 displays, -MC4xFS-M24 and -MC4x-M24 controllers, and -XC4x-M24 expansions will be produced with secure boot starting in 2026. Modules produced with secure boot will thus have 7.06 as minimum version (changing from 7.02 on MD5 and 7.03 on C4x-M24)

IQAN-MD4 and original version of MC4xFS/MC4x/XC4x will continue to be produced with bootloaders supporting old versions. 

Major update of IQAN-MD5 firmware

MD5 firmware is restructured to strengthen cyber security and prepare for future improvements. When updating in the field, there are key points to be aware of.

• Upgrade of MD5 to 7.06 requires 7.05 in module.
• During update, all logs in the MD5 will be erased.
• After updating MD5 to 7.06, downgrade is not possible.

Message when attempting to send 7.06 to  MD5 with version 7.02-7.04. 

Message about major upgrade of MD5 module , before sending 7.06

Project file size (.idax) increased to ~75 MB, to handle the update from 7.05 to 7.06. Clone files are smaller, ~30 MB.

Clones taken from MD5 7.06 or newer can only be sent to module with 7.06 or newer.

Message when trying to use clone to upgrade to 7.06 

Other changes

IQAN-MD5 performance enhancements

• Reduced start-up time, time to show first display page reduced with ~1 second. 
• Minimum application cycle time is reduced from 50 to 20 ms. The recommendation to use locate machine control functions on MC4 controllers remain. 

Always send firmware before application

If an update is interrupted while sending firmware, the module is now able to restart with the old application, matching the old firmware. This reduces the risk of not having a working application if a version update is interrupted. As before the firmware is double stored, an IQAN module will always have a working firmware. 

More details in Release notes
Release notes - IQANdesign 7
Release notes - IQANsimulate 7
Release notes - IQANrun 7
Release notes - IQANscript 7

Hello, 

We are experiencing a user interface issue in Iqan Design 7.05.19.10562.

When editing a page on the display and scrolling in the Layers panel (for example towards the bottom), the main screen keeps scrolling along with it.
Even though the mouse cursor is positioned in the layer navigator, the display view continues to move.

This makes working quite difficult. Ideally, the scroll action should only affect the area where the mouse cursor is located, and the display view should remain in its current position.

Has anyone encountered this behavior before, or is there a setting to prevent the screen from scrolling together with the layer panel?

Thanks.

Application Migration From MD-4(7) to MD5(8).

1. How do I migrate a chunky application without having to lose connections to my I/O's that are present on separate Expansion modules but controlled by the head master MD4-(7) when I need to migrate the application from MD4-(7) to MD5-(8)?

2. How do I keep connections between adjustment groups, adjustment parameters, logs and Monitoring channels under the same transition?

3. Basically how can I completely migrate an application contained in an MD4-(7) screen to an MD5-(8) screen without loosing connections to other hardware in the System Layout if I am using a Variance file. 

The purpose is to have 2 selectable headmasters with complete application available on both.

I have a system with a MD4-5 display and a MC43 controller in 1qanDesign 7.04. 

Between these two the master/diagnostics bus is connected via a wireless can repeater.

This works perfectly fine when the connection is established via the wireless repeaters. However when the modules statrtup together with the display, the display is started faster than the display, which causes no connection to the mc43 to be established even when the can connection is online.

If during startup the connection is online, but connection is lost and re-established, everything works fine.

I have already tried making the MC43 optional, but this didn't work.

There seems to be some check in the startup that causes this behaviour?

Is there any way to avoid this?

Sometimes I find myself collaborating on a project with an engineer who is at a different location and have to test their program changes for them. It would be much easier to find a given channel or object that they are referring to if they could just give me an object number (which you can only find when doing a compare) for me to stick into the find window.

Can we get an item in the status bar next to the project name and version, which shows the number that would normally show up next to BEGIN or END in the project compare window?

I recently got an email notification that the MC/XC 4x series is being replaced by the M24 series controllers.

Is the non M24 series of controllers and expansion modules no longer available?

They claim to be compatible in form, fit, and function, but does the system have to be on IQANdesign V7.03 or higher to be able to swap a non M24 series controller with the new M24 controllers?

That is not ideal, as we have many systems out there with XC4x series expansion modules on V6-V7.02. Having to update master module programming to swap to the M24 series is not great and takes away one of the main advantages of the expansion modules (not having to update master module programming for field replacements). Especially since it can take a very long time to send projects that have different firmware than is on the master when using anything other than Ethernet.

It would be great, if you could create a function group/Sub items for a display page item (gauge/chart/Video feed, ect).  
Like for a gauge that you want to use on multiple pages.  
It would be nice if you can create a image that is x pixels by y.   
Do all of the controls and images for it, and then copy and paste that 1 item to multiple pages.   

Something like the Base page feature you have, but for smaller items to use in multiple places, so you only have to manage 1 version of it.