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.

Is there any plan to add string compares or other string functions to IQAN yet?

I run into this wall somewhat regularly as our machines get more complex. Adding even simple comparison to strings would be useful. The problem I am trying to solve right now is that I have no way to compare a string to know if it has changed.

Alternatively, if there was some channel status on a text parameter to know if it was updated, that would be useful as well.

I did read through Gustav's thread about string functions here: String functions / Software / IQAN

Doesn't seem there has been much advancement on this topic and those string functions wouldn't accomplish what I am looking to do.

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 

Does Parker IQAN team has any plan/interest to implement CAN-FD (Flexible Data Rate) capability in the future ? 

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?

The USB interfaces page mention Kvaser Leaf as being a supposed USB to CAN interface, but is the Kvaser BlackBird v2 (https://kvaser.com/product/kvaser-blackbird-v2/) fully supported as well?  I have one that I can get to work with IQANanalyze but it can't find a master module to connect with when used in Design.  It is recognized as an interface under Tools>Options>Communication as a CAN adapter but I an error message when trying to connect (see screenshots below)

Sometimes using a dual object as a limiter on a dual direction math it does not store the value entered. Not sure if its the same on other functions.

Enter value into Out 1 then hit down key rather than return key and the value fails to store although appears to be saved in the property section.

Enter value into Out 2 then hit up key the value fails to store.

Clicking off the channel in the main workspace and then reselecting it shows it has not remembered the value you entered in property section, and instead goes with the value shown at the bottom of the page.

I had multiple instances where I thought I entered a value and found it had not stored correctly, but seems intermittent, made worse if you key down to Out 1 (to enter a value) from the 'input' selected (highlighted) first rather than using the mouse.

IQAN Design 7.02.

It would be a nice addition to the MD5 family if we had option to upload/update programs via onboard USB port. Rather than relaying on proper cell coverage we could simply email the file and have the end user push an update via the USB port. It appears to me that most of other controllers have that feature build in. 

When ever I call the variable name in a table "%TIME%" seems like I am bot getting the data when ever the script is running in IQANrun. Can someone tell me how can I get the variables to be read when running the script in IQANrun?

Is there a way to log decimal numbers in the event log? The values I have now are stored as whole numbers with ".00" after even through the actual channel they were reading has decimals. For example, a channel value of 5.4 is logged as 5.00.