+6
Completed

Version 5 I/O Display

Joe 2 years ago in IQANdesign • updated by Ulrik Zakariasson (Software development) 2 years ago 13

Showing the pin connections on the module screen in Version 5 is really nice.  However, not showing all of the available I/O makes it difficult to see how pins are shared between different channel types. For example, you may not realize that you could simply move a DOUT to a different channel assignment (i.e. DOUT:F rather than DOUT:I) to allow for an additional COUT that shares a pin assignment with DOUT:I (ref XA2 module).  Is it possible to have the option to show all the I/O like before, but keep the pin connections displayed?


+6
Completed

MC4x pin descriptions

Rick 3 years ago in IQANdesign • updated by Gustav Widén (System support) 12 months ago 2

Adapting the MC4x modules on our first machines now, we had quite a struggle with the various pin characteristics (DIN Pull-up / Down, A15/17 suitable for relays on the MC3, et cetera). Such details can be found in the Specs of course, but it would be quicker & easier if we can see such details in IQAN Design, for example in the bottom-right corner when clicking an in- or output pin.

+6
Completed

Have Function Group Input names default to match the name of the respective input channel

Forrest 3 years ago in IQANdesign • updated by Ulrik Zakariasson (Software development) 1 year ago 4

I am doing a bunch with functional groups in the latest project to clean things up a bit, and it is annoying to have to individually name/rename each of the FGIs, especially when I change the name of the source and then "have to" rename it again in every Funtional Group where it shows up.
Maybe have a box to check to override the default name strategy for the times someone might want another name used.

+6

New IQAN-MD4 demo pages

The latest IQANdesign versions include some new demo pages for the IQAN-MD4-7. The pages are built on the Fork Lift application example, and illustrate some useful techniques, like working with transparency.

Fork Lift, "Industrial" theme:




Fork Lift, "High Tech" theme:


Fork Lift, "Classic" theme:


The pages were made by an industrial designer. He worked in Illustrator/Photoshop to make the graphical design elements, and then used them to build the HMI in IQANdesign. He offers his services to IQAN users, we can provide the contact details.

These are the files:
My Documents\IQAN Files\Examples\Fork lift\Fork lift.ida3
My Documents\IQAN Files\Examples\Fork lift\Classic.ids3
My Documents\IQAN Files\Examples\Fork lift\HighTech.ids3

Classic and HighTech use the same application as in Fork lift, but with different look and feel. They are stripped project files, but can be opened in IQANdesign in the same way as a normal ida3 file. Just select the correct file type in the open dialog, or double-click the file in Windows Explorer.


+6
Completed

Diagnostic Entries for application

David Freeman 4 years ago in IQANdesign • updated by Ulrik Zakariasson (Software development) 3 years ago 5
Currently the only way to populate the diagnostics in an application is to create an spn for each diagnostic. In some applications we have 500-600 diagnostics. Is the a way we could populate and spn table with a spreadsheet or txt file
+5

JFIN Source Address flexibility or GFIN Identifier wildcards

Vincent Thiele 12 months ago in IQANdesign • updated by Florent Mirieu de Labarre 8 months ago 6

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...

+5

Any plan to support importing EDS file?

Frank GUO 1 year ago in IQANdesign 0

Is there any plan to add importing EDS file into IQAN?

+5

COUT Adjust Channel Naming

Dave R 1 year ago in IQANdesign • updated by JamesV 10 months ago 3

Would like to be able to setup COUT adjust items with different names based on the channels Mode Selection. We use COUT's to run different functions based on machine setup and it would make it less confusing if the adjust channel could be named more specific to the setup instead of a generic name or a really long channel name with each function in the name. Sort of like how measure channels can have different names for the same measured channel.

+5

IQANdesign and IQANscript available on IQAN store

Gustav Widén (System support) 1 year ago in IQANdesign • updated 1 year ago 0



It is now possible to purchase licenses also for the developer tools IQANdesign and  IQANscript on

IQAN store.

Previously it was only possible to get the licenses for  IQANrun and IQANconnect via the store, the licenses for the developer tools were ordered in the same way as hardware and shipped in boxes.


Since version 5, the tools IQANsimulate and IQANanalyze are free.

The PC tools that require licenses are:

  • IQANdesign
  • IQANscript
  • IQANrun



We are also rolling out a new IQANdesign upgrade subscription, to help drive the development of new and improved functionality for IQAN software. For more details, see the new IQAN software updates and licensing FAQ


The IQAN store also introduces a feature for retrieval of licenses bought via the store, and a way of updating existing licenses via the store.

+5

Make log data available to the application and display pages

Gary Posey 2 years ago in IQANdesign • updated by Gustav Widén (System support) 2 years ago 0

It would be a nice feature to make log data available to the application and display pages. For example, I like to use the logs to contain machine hours. This can include, engine hours, pump hours, motor hrs, valve hrs, fan hrs, filter dirty hrs, low grease hrs, number of starts, etc... Logs are good for storing the data, visible when you get the clone file c/w logs, with nice reset features.   However, this data is currently unavailable for use within the application control logics and display pages. Its current nice to see all of the machine hours in a common log group, but it would be nice to also display some select logs on the programmed pages for operator quick reference. As for use in the application, this data can be used to trigger conditioning message or have other functions.


An alternative solution to display machine hours on the log group and display pages would be to use timers in addition logs. However, these additional timers would result in duplicate and parallel logic to the logs, and is no perfect solution.