IQANdesign 7.04 released

Faster startup of IQAN-MD5 modules

Application logic startup dropped from about 6 s to 3 s. 

Display pages now show after less than 6 s.

Reduced size of project files with IQAN-MD5

File size reduced from about 100 MB to 50 MB

More resolutions for SOME/IP cameras

Video controls for "SV" camera now support more resolutions. 

Note that cameras do not support all resolutions. The original IQAN-SV support previous resolutions and  1280x960.

SOME/IP cameras from other brands can be used as "SV" module since 6.08.32.

More changes and fixes

Release notes - IQANdesign 7

Release notes - IQANrun 7

Release notes - IQANsimulate 7

Release notes - IQANscript 7

I'm using an Modbus <-> CAN converter to get communication working between an MC41 and a Modbus device. The converter expects variable data lengths of the CAN frame it receives. It is not possible to add a variable parameter to the data length of a CAN frame is it? It doesn't understand bytes with 'ff' or '00', it wil be processed as data.

Hello,
I need a cyclic timer for raise a flag all 500 ms, setting by user by parameter.

The following code raise a flag all 520 ms:

It is not possible to have a cyclic timer directly ? if no, how to ?
Best Regards

I understand the additional error checking of HS+LS outputs. For some applications it would be simpler to be able to "dumb down" the output to be either HS or LS.

Is there a way to show a custom video on the MD5 screen? 

For example while powering up and shutting off the machine. 

It is possible to add an option in Project Check for retrieve the Expression not used in QCode ?

In my case, i consider that it is a bug because i cannot set correctly the result as expected

The size of a list can be optimized in KB or MB;
But the last items in the list should always be displayed as BYTES

we can have an internal digital channel, or an integer math channel, or a match channel...
Why not have array in each type?

IqanDesign 7.03

When 'Show all references' is not selected, only the forward side reference lines show up. 

Deactivation (on User Interface à System dialog boxes) can consider the dialog priority info. It can be implemented in different ways.

Deactivation should be an integer instead of {No, Yes}. The application can assign an integer channel to the Deactivation with the following logic:

• Deactivation = 0: equivalent to “No”
• Deactivation = 1: equivalent to “Yes” for all popups
• Deactivation = 2: equivalent to “Yes” for all popups with dialog priority level lower than the Information (so the deactivation is active only for Message)
• Deactivation = 3: equivalent to “Yes” for all popups with dialog priority level lower than the Confirmation (so the deactivation is active only for Message and Information)
• Deactivation = 4: equivalent to “Yes” for all popups with dialog priority level lower than the Warning
• Deactivation = 5: equivalent to “Yes” for all popups with dialog priority level lower than the Alarm
• Deactivation = 6: equivalent to “Yes” for all popups with dialog priority level lower than the Error
• Deactivation = 7: equivalent to “Yes” for all popups with dialog priority level lower than the Critical (so the deactivation is active for ALL except Critical)

This integer value can be connected an integer parameter (adjustable) on the Master display.

The idea is to delegate to our Service or dealer the possibility to decide from which severity level the driver acknowledge is mandatory.

Every customer/dealer wants to have a different approach.

If a subsystem raises a DTC with low severity level, the driver confirmation should be not required.

• i.e. to inform the driver that the required function is temporarily unavailable because an interlock is active:
• it should be visible until the function is requested or the interlock is active
• and the message should be hidden automatically. If we don’t close automatically, for the driver it is a source of distraction and the interaction to close the message is very annoying for our customers. If we don’t show the message to inform about the interlock, they claim because they don’t understand the reason of loss of functionality.

But if the DTC is critical for safety reasons or to avoid a component damage or if an analogue signal is disconnected/short to GND o Vbat, we MUST require a driver confirmation.

So, they can understand the seriousness of the situation and they call the service/maintenance to fix it.