Hi, today we have silver and red reference lines. Furthermore we have the possibility to show all or only the lines from a component. When I select a component, the associated lines are highlighted a little bit with a thicker line. But it is still hard to see, if you got a mesh like I have here below.
Wouldn't it be nice if we add a third colour to highlight the lines of the selected component?
Currently its not possible to have J1939 & Generic on the same line... why not? As long as the bitcount (29) and KBPS are the same...
The thing is, I need some tricks from both systems. J1939 allows to handle engine messages more easily, and also allows to use the Page Mask byte(s), so the same PGN can be defined multiple times and split ways. But J1939 JFOUT does not allow to change the PGN programmatically, which is needed in this particular case in order to make a reusable library.
Generic JPOUTS do allow a dynamic messageID's, but don't bring the other benefits...
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?
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.
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.
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.
Customer support service by UserEcho