We are happy to announce that IQANdesign 5 is released, bringing in powerful features for team collaboration and a brand new look!
Main feature updates
New system layout
The system layout grid view has been replaced by free positioning of the modules and buses.
Tool bars and context menus are replaced by an Add button in all views where you can add components. The Add button has additional features such as component search and hints.
Dynamic block diagrams
Block diagrams now only shows pins that have channels assigned. Also other improvements such as pins showed separately for multi-pin channels and multiple categories for some I/O types, e.g. HS/LS categories for digital outputs.
Solution library added that lets you add ready-made solutions to your applications from the Add button.
A new concept that allows you to place application logic in a file external to the project file where it is used. By doing that, you can reuse code in multiple projects, and also make it possible for two or more persons to work on the same project simultaneously.
Instances of the external function in the main project file can be automatically updated when the function in the external file is updated.
Move image and line controls in runtime
It is now possible to control X and Y positions of images and lines using channels. This will allow you to do simple on-screen animations.
MC4x: CAN routing
CAN routing adds a new concept of rules and exceptions to simplify routing of CAN frames between CAN ports on MC4 modules.
Check for updates on version 4 will direct you to any upcoming maintenance updates on that version, for downloading version 5, use these links:
IQANdesign 5 demo video
For more details, see:
In IQAN, we have had the feature for reading of DM1 for ages, and DM2 reading since version 3, but reading other PGN:s that are sent as J1939 multi-packet is more tricky.
I come across more and more applications with requests for reading other PGN:s with > 8 bytes.
With a bit of knowlege and time, it is possible for an IQANdesign user to implement reading of BAM and TP.DT using JFIN channels, but it comes at the expense of overriding the DM1/DM2 reading features.
With a more integrated feature for J1939 multi packet, using e.g. a JFIN with length > 8 byte, requests such as these could be solved more easily:
With version 5.02 we added two features for outgoing multi-packet (DM1 and text), now might be a good time to develop incoming multi-packet further?
I think it would be useful to be able to take the description text from the CAN bus, VRef, etc or add free text to the List view of a master module:
This would allow for clearer definition when sending to a wire harness builder or for troubleshooting.
Would it be possible to add a SIC that holds the filename used to program the system and also timestamp of the file?
It would help us a lot to keep track of versions, specials and machines.
I know there is Version under Project Properties but it happen to often it don't get updated.
Version 5.02 of IQANdesign, IQANsimulate, IQANrun and IQANscript are now released on check for updates. These are the highlights:
DBC -file import
On the tools menu, there is a new CAN database feature for .DBC file import. After importing a DBC it is easy to automatically generate JFIN/JPIN, JFOUT//JPOUT, GFIN/GPIN and GFOUT/GPOUT channels from the database.
A J1939 library is included in the CAN database menu in IQANdesign. It gives easy access to creating channels with the standardized PGN and SPN numbers and names. Note that timeouts and transmit rates needs to be set manually.
There is now a built-in function for generating outgoing DM1 messages based on channel status. Drag the channels to the DM1 out container and set a unique SPN number for each.
The length of the outgoing message is determined by number of channels with a warning or error status. FMI is set based on the channel status.
New channel type: JTOUT
The J1939 text output channel is used to send text to an external system. It supports multi-packet when text length > 8 bytes.
Support for J1939 address claim
Forces IQAN master modules to claim their J1939 address before starting other J1939 communication. Enabled by a property on the J1939 bus.
Support for J1939 Time/Date
External systems can now set the date and time in a master module using J1939 TDA. Enabled with property on master module.
A Connect button with a drop-down for selecting the communication interface has been added to the IQANrun start page.
The IQANrun multimeter button brings up a free floating window where it is possible to make a new measure group on the fly.
Channels can be added from the existing measure groups, and also the module block diagrams and application view if this is visible.
More IQANdesign features
IQAN expansion bus
The use of IQAN expansions in systems with short cycle times is improved by two small changes. Property 'Sample rate divider' is clarified by changing it into "Polling cycle time", and an estimated CAN bus utilization project check is added for expansion buses.
Property to disable undercurrent detect on Digital out HS+LS added.
Zoom support in page editor
Makes it possible to zoom in and out in the display page editor.
For more details see release notes and IQANdesign 5.02 user manual.
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...
Customer support service by UserEcho