Since there are no DM1/DM2 blocks to send out 1 or more faults yet, (hint!), I'm trying to implement it myself, using Array blocks. It works, BUT:

- No Array support on MC3 (for safety reasons? why?)

- No looping or "Add" functions to construct the list dynamically

- Arrays are Float by nature. This is inaccurate for 32 bit UINT DTC codes. Would be nice to have a integer (and if doing it anyway, a boolean) variant

- Ability to fill/insert/operate an Array from another block ("adding itself to the list")

Biggest problem is the MC3, where more than 50% of the CPU is currently spend on sending out DM1 & 2 messages. Which is obviously way overkill, but I don't see ways to do it more efficiently with the available tools.

Is there a way to set the J1939 Source Address field in the TSC1 command to an Integer Parameter? That was we can install the same crane software on different truck chassis with different engines.
Cummins/PACCAR like to use SA 7 for TSC1 control. Detroit Diesel likes to use SA 231. It would be nice to allow the J1939 SA field to look at an integer parameter and adjust the code accordingly.

Ability to change TP channel value using Qcode like:

if VDIN-Choice1 = true then TP1 := "Your choice value is:" + MAC-value1 + " that is under the limit"

I have an application where I want to send text strings over CAN on a very occasional basis. A tool for handling extended outgoing CAN frames for this task would be very useful.

Please include an auto ASCII converter in the tool.

Part four of the IQANdesign tutorial is now available, this one is introducing some of the Qcode sytax:

There are many applications that require a variation in units. Currently if I want to display a pressure gauge, I would need to create a PSI pressure gauge, and a BAR pressure gauge. Then control the visibility properties of the gauge to display the desired gauge.

It would be helpful to tie an integer parameter to the "Min value" and "Max value" of the gauge control or bar control. By doing this it would also be necessary to change the "Tick count" value with an integer parameter. This way the programmer would only need to make one gauge and control the properties inside the "Display application" as opposed to multiple gauges.

If you store an integer composed of 8 or more digits, in many cases the stored value does not match the expected reference value. The discrepancy typically occurs in the least significant digits, which may be incorrectly stored or retrieved. However, the issue does not appear when the least significant digit is 0, in which case the value is handled correctly.

IQAN design 4 had the feature of being able to right mouse click scroll to zoom in/out on the Qcode. This feature has disappeared with IQAN design 6 and 7. Was this an intentional deprecation?

Having the zoom feature on the channels is nice, but I do miss the Qcode zoom. Also running into an issue with using a laptop and additional monitors where it seems the resolution from the laptop is being applied to the Qcode on the additional monitor.  Additional monitor has higher resolution so my Qcode appears very small and I can't zoom in on it.
If I close the laptop and only use the additional monitors and open Design. The Qcode appears larger and this resolution is maintained when I open the laptop.