New GUI

IQANrun 7 has an updated user interface, more similar to IQANgo. 

Online operations System, Logs, Measure and Adjust are on tabs at the top of the window. 

Send operations such as send to machine and get clone are available with one click on the main menu. 

When clicking connect or selecting an operation that requires connection, a connect dialog is shown. The tab for last used interface is selected as default. 

Single adjust such as function parameters can be adjusted directly when entering the adjust group, giving better overview when adjusting. Click on value to type in or use +- buttons. 

Adjust items with multiple values E.g. COUT is presented in a more compact form. 

New and improved adjust view

Application viewer in a separate Window

Other features 

IQANconnect free

Remote connections no longer require a separate IQANconnect license.

Inform of firmware update

IQANrun now shows confirmation dialog informing of firmware update. 

In a multi-master system, the version info shown is for the address 0 headmaster.

See also Release notes - IQANrun 7

Compatibility

IQANrun 6 compatibility

• IQANrun 6 can be used with version 7 systems; online operations as well as send application and get clone. IQANrun 7 is necessary for view project.

IQANrun 7 compatibility

• Support file operations down to version 3.
• CAN adapters need 64-bit support
• Minimum OS version Windows 10

Does somebody knows if it is possible to change the colour of for  example a bar graph by a variable.
Now yo have to choose a fixed colour.

I want to change the colour if the input value is above a adjustable setpoint.

The way program it now is to have two bar graph with different colours, and use the visible input to select the color.

Maybe a idea for a next release???

I really would like a lookup table for text. I have a list of errorcodes, now we only give the error number. This is not very clear to the user. So if we get an error code, I would like to be able to display a text to let the user know what the problem is. Because this list is very long, it would be very helpfull to have it in a lookup table where we can import a list. It is mentioned before, but I think it is not an any developpers list.

Idea : Table to manage error code / Software / IQAN

I think it would be a good idea if there were three modes of operation for the run mode button.  The first is the current mode where the animations of the gauges and lamps occurs.  The second would be an off position where all lamp controls show the on image, all gauges move to the max position, and all bar/arc controls move to the max position.  And last would be an off position where all lamps controls show the off image, all gauges move to the min position, and all bar/arc controls move to the min position.

This would be useful for verifying the layout of the display interface without having to invoke the simulation step. 

Also, it would be useful if IQANdesign could remember the visibility setting in the project.  If i toggle the visibility off for a layer, group or control and save the project, IQANdesign will remember that setting until i change it.  Function in the simulator and on the hardware could remain unchanged.

This would be helpful so that controls that are positioned on top of each other didnt need to be toggled visible / invisible every time a project is opened.

It would be really helpful to be able to add a help text to adjust items.

This would ensure technicians/users have relevant instructions about what they are adjusting on screen.

The items with help text could show in a pop-up like when editing text parameters or in fullscreen like when adjusting input channels.

Would it be possible to implement free Comment Fields on the System layout page, the same way as it is implemented on the FG pages

Would be nice if you could use an integer parameter to set the window size of
a moving average.

I'm in the process of upgrading a number systems using MDL2 modules and intend on using a MD4/XA2 combination in its place. Since this upgrade is largely due to the obsolescence of the MDL2 units I am concerned about the product line expected lifetime for the MD4s and XA2s. I remember that the MDL2s appeared to become obsolete rather suddenly, so are there any plans to make today's MD4 or XA2 modules obsolete in the next 5 years? 10 years? How would we find out when/if this status changes in the future?

We work with NMEA 2000 devices and have had a great deal of issues with the dynamic Source Address nature of the standard. On startup the devices will jockey for Source Addresses and, depending on what's powered on or connected at the time, the Source Address scheme will be different.

We've made due so far with GFINs and using an ajust parameter for the Source Address to build the Identifier, but this requires one of two things to reconnect to a module: 1) blindly cycle through addresses until we find the right one, 2) connect a CAN analyzer to the bus and find the right address. Also, GFINs don't allow for the "Don't Care" option for priority that JFINs offer, which has also been a problem with manufacturers using different default values.

What I'm proposing is kind of the best of both worlds, where we can have the Identifier flexibility of the GFIN, but with the wildcard capability of the JFIN. That, or native NMEA 2000 support...