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.

Was the "Copy From Mode" feature removed from IQANrun7 or was this just moved somewhere else?

In IQANrun6 there are 3 options at the bottom of an adjust group, including "Reset Group", "Set Default" and "Copy From Mode" as shown below.

In IQANrun7 for the same adjust group I only see these two options in the menu.

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.

A release update to 7.02 is now available, IQANdesign 7.02.33

MD4

This version has a bug fix update for IQAN-MD4, we found and fixed an old issue where bursts of errors on CAN could lead to an MD4 watchdog reset. It is very unusual to be seeing this symptom even on machines with problematic CAN installations. But over the years there have been a number of events that can now be explained, and avoided by updating. 

MD5

MD5 update solving MD5-10 touch issues. 

See Release notes - IQANdesign 7 

Hello,

I am trying to run a Mitsubishi VFD that takes a current input of 4-20mA to change what hz the connected motor is running at. The VFD says it's not receiving a current command.

I see this excerpt in the manual:

Minimum current
There are several diagnostics methods that are active, one of these methods is based on
measuring current. The threshold for detection has been selected based on the
assumptions that currents below specified minimum current does not cause movement.
Error detection limits and delay
The COUT has two separate measurements of current, and is capable of detecting drift
faults on the closed loop control of the output. To avoid spurious trips, it is designed to
tolerate some deviation. The worst-case detection time for the most severe type of
faults are listed in the table below:
Since the MC4xFS COUT channels are grouped in pairs sharing an internal high-side
driver channel, shutdown of one COUT will cause shutdown of both COUT channels
in the pair. Restart conditions are controlled by the application.
Appendix B has detailed lists of failure modes focused on output wiring faults.
C4x-SMR-027:A Minimum current when using COUT
Safety related output functions controlled by COUT shall be designed so that
movement can only be activated if the output current is > 100 mA. 

Maybe I'm misunderstanding, but if the minimum current is 100mA, why does it let me set a COUT range of 4-20mA without throwing an error?