It would be nice to be able to select from a range of label sizes on the gauges - similar to 'tiny, small, medium', etc for the regular label sizes.  When I have to make a gauge small in size the default text can overlap, causing me to hide the default labels and make separate smaller labels at each marker tick.  

Hope that makes sense.

I open a measure with IQANRun 6.0 for study my waves, and do some modifications if necessary in IQANDesign 7.0 as following

The IQANDesign shall be able to disconnect only if IQAN Run is connected in order to download software. not closing my opened measure in IQAN Run.

It is very unconfortable to reopen measure again, and redo few operations in order to retrieve my selected signals, etc..

The store value of finite state machine object is not working in a specific way :
- store value is Yes

- function containing the finite state machine can be disable : in my case, it is disable at startup during at least 1500 ms.

But in this specific way, the memorized object works fine !

How to get the bus load of CAN bus ?

Expected -2 result for (-16.80 div 10) operation;

Expected -1 result for (-13.60 div 10) operation;

Noticed the coloured progress bar on sending from Design 7.04.8 appears to be 100% complete but graphically just over halfway:

Not a major problem, just reporting visual bug!

I love the Finite State Machine. Great to see such an excellent feature added to the program after being away from IQAN for 11 years.

That being said, here are two possible improvements for the Finite State Machine:

1. The addition of Delay on to the arrows.

Justification: I find myself adding alot of internal digital channels outside of the Finite State Machine that are looking for the machine to be in a specific state number so long before turning true. Adding this and possibly the Delay off would make the code in the Finite State Machine more readable and explainable.

2. The addition of being able to set a debug on a state in the Finite State Machine:

     Justification: The states can zoom through things so quickly that the only way to trap a bug would be to set a trigger to hold the Finite State Machine in that state. The alternative is to add all the exterior channels that contribute to the logic in a measure group and then work on analyzing what happens.

     Implementation: The ability to set a debug flag on that state. Then as that state is about to be exited because an exiting arrow has turned true, the state would be held. The debug flag wouldn't persist between power cycles of the evaluating master module and debug flags cannot be communicated when sending a project. I know that this could be a touchy subject for IQAN because nothing else in the program allows you to pause the execution of blocks in real time. But I would like to make the argument that Finite State Machines tend to be used for supervisory or sequencing logic of actions on machines and staying in one of these states as long as the underlying safety checks are being performed in conventional channel blocks, this wouldn't pose a risk to life or machine.

GPIN Startup value can be not null and/or incoherence value for a boolean as following : we save in memory the 100st values of one object in array, and we can see at first cycle, a value of <3> for a boolean !

Having issues installing IQANdesign 7 software. When our local IT admins are installing this software, it is not actually installing it on the C drive. Is there a way to change the install location? 

We are planning a project with 6 x MD5 displays and 6 x MC43FS modules, is there a limit that the diagnostic bus and master bus will take before it overloads? These modules are connected all together for both diagnostic and master bus. Conscious of initial start-up bursts and also general running bandwidth consumption.