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.
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...
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.
It is now possible to purchase licenses also for the developer tools IQANdesign and IQANscript on
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:
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.
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.
Are there any thoughts about integrating some kind of map app to the MD4?
Like google maps or something for navigation?
-Add a GPS device in the machine and then add some kind of map function in iqan design for the MD4.
-Connect a smartphone to the IQAN system and use the phones gps to show location in some kind of app on the MD4. Or maybe stream the phones map interface on the MD4.
Just some thoughts and ideas. Not high priority.
It is now possible to configure MD4 display pages for control with external buttons/encoders:
Activate/Navigate with Encoder or key Up/Down.
Interact with controls with key Enter, Slider and State selector will lock focus. Abort interaction (Slider and State selector) with key Escape/Menu.
Remove focus frame with key Escape.
Key interface is selected when using touch buttons, with external buttons/encoder, the spinner is used.
Property control of JFOUT and TSC1 source address
All master modules must be connected to diagnostic bus
Important problem solved
Triggered due to a touch chip communication problem, problem was introduced in 4.03. It is recommended to upgrade IQAN-MD4 applications to avoid this issue.
I have been working with IQAN Design 4 for a few months now and would just like to say that having the ability to change the channel scope to public was a much needed addition. Some programs can get fairly large and any attempt at organizing the logic ended up in multiple FGIs and ended up being even harder to follow. That being said, I was quite used to the Function group output shortcut, shift+ctrl+o. It would be nice if there were shortcuts for the other scope options as well, or pressing the shift+ctrl+o shortcut to toggle through the scope options would also be handy. As long as I'm asking, It would be great to change the scope of multiple channels at a time.
When the COUT regulator on an IQAN-MC2 or IQAN-XA2 is unable to deliver the commanded current, the COUT gets the status saturated.
Saturation happens when it becomes impossible to deliver the commanded current, this is when the supply voltage is too low, the coil resistance is too high, or the max current has been tuned too high.
The available supply voltage depends on the +BAT supply to the module, the internal voltage drop in the COUT, and also on the maximum pulse width, that varies with the dither frequency.
An example of when a saturation warning may be triggered is during cranking in a 24 V system, where it is usually possible to keep the IQAN system powered up. There, if a COUT is tuned close to the maximum current that can be driven through the coil during normal operation, if an output is kept on during cranking it would have the saturation warning.
The saturation status can be seen when measuring on the channel, for example in IQANdesign:
The COUT status can be seen when adjusting in IQANrun:
But the saturation warning also gets logged in the system log:
We have been getting some comments about the saturation warning, that it in some application just fills up the system log without providing much useful information for design or service.
Does anyone think that saturation warning in the log is useful?
Or that it should be removed?
Remove saturation logging
Keep saturation logging
Customer support service by UserEcho