Highlighted updates

New gateway module IQAN-G11 added

The IQAN CAN bus to bluetooth dongle IQAN-G11 added in IQANdesign. More information will follow when hardware and apps are released.

Qcode improvements

Show most sever error as status on row.

Improve Qcode auto-completion.

Include Qcode instructions in channel hint when Qcode is selected

Camera

Added module for Generic camera as alternative to IQAN-SV.

Functionality similar to IQANdesign 3.x

Show unit on scaled max and scaled min

For VIN, PWMIN, FIN, DFIN, PCNT and DPCNT

Also added unit to reset value for MEM, TMR. PCNT, DPCNT

New solution library examples

Added IQANdesign example files for:

• Start button NO NC (both project file .ids4 and simulation file .isa4)
• J1939 Fluid Property Sensor (FPS)
• J1939 particle counter IPDR (iCount)

Added IQANscript example files for:

• Get system info and clone (.iss4 script file, installs with IQANscript

Highlighted features

Signal generator

It is now possible to control the value of a simulation item using a signal generator. The signal generator contains a table with time/value pairs.

Import of measure file creates simulation items for each channel in the measure file that can be simulated (inputs). Values from the measure file are also imported so that you can play back a measured scenario.

Interface to other simulation software

ActiveX support implemented. Makes it possible to read and set values from external software, e.g. Microsoft Excel. There is an example file for this under the examples folder.

Remember input values and settings between simulations without having to save

Simulations can be manually saved as .isa4 files. There is also an automatically saved simulation, that stores the input values and all the settings between the simulations. When launching IQANsimulate, there is an option to select whether to use a saved simulation file or create a new one.

Keyboard shortcut for small input changes

In the simulation group view the arrows are used to select channel. Ctrl+arrows are used to change the value of the selected track bar. Added shift+ctrl+arrows to change values in raw value steps of 1 (smallest step available).

Possible to add channels to simulation group while simulating

"Set value" function more accessible

For more details, see release notes.

It would be fantastic to have a script to import .DBC files that would generate automatically the GFIN/JFIN GFOUT/JFOUT as well as the associated JPIN/GPIN JPOUT/GPOUT. That would literally save be weeks of typing and may mistakes!

Hi,

I'm currently migrating a fairly large program from older IQAN hardware to the current.

The workspace for large programs is awful to use; can we get some kind of update to make this less frustrating?

I have multiple large function groups (30+ inputs) and there is no way to lay them out that makes it easy to read.

And can we also get some more tools other than comments to organize the software?

With all the FS changes and multi master systems likely becoming more common can we get some tools to help manage multi master systems?

It would be good if I could reference MCXX unit states and display them on my MD5 HMI and have it auto populate.

Thanks,

A

I like the solutions where you can drag and drop them into programs. Is it possible to drop in my own custom solutions? I think this would increase my productivity?

We have many machines running a range of firmware versions, we need to ensure we prepare program updates containing the same firmware as already exists on the machine, purely due too the bad experiences when updating firmware remotely.

I assumed IQANLauncher would open the correct version of IQANDesign (If the application version is installed) when a program is double clicked, but we have found this not always the case.
There doesnt seem to be any documentation on this program that I can find, can we get info on its intended purpose and use.

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