Variant Program issue:

Facing 5 such errors in the program carried on from a variance program now to the idsx file. Unable to find the error upon double clicking the associated project check error line.

Type: Error | Code: Undefined reference | Component Type: Channel Subscriber | Component Name: Air Reel On IDC | Property: Channel

Tried manually looking out through the whole program to find where the channel subscriber is unable to look for these but have so far failed. Why isn't it showing the location upon double clicking the error line as it does with everything else in the project check dialog box.

Designing multiple graphics pages for a project and noticed if I accidently delete a line/graphic/text and hit the undo button, it resets back to system information page. Seems to only do it when re-instating a deleted item, rather than if you just edit an item. It also looses your zoomed profile on the display page screen you were on (if its set to 80% zoom for example) which is frustrating.

Appears to only do it on display pages, not in application logic. Iqan Design 7.04.

May not be a bug, but cant see why it would be beneficial to act like this?

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'm using a math channel to add a value stored in an adjustable integer parameter to the measured brightness value to control the backlight. I would like the ability to hide the backlight adjustment in the display preferences menu as this will cause confusion since customers familiar with the MD4 will go there to adjust the backlight, instead of the adjust group.

Or you could just add an ambient lighting adjust mode to the preferences screen so the operator can easilly chose how they want the backlight to operate. That'd probably be a better option.

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.