We just posted the first video in a series of IQANdesign tutorials to

https://vimeo.com/iqan/channels

Part 1

IQANdesign tutorial part 1, adding modules and channels from IQAN on Vimeo.

Part 2

IQANdesign tutorial part 2, simulation from IQAN on Vimeo.

Part 3

IQANdesign tutorial part 3, Object List, from IQAN on Vimeo.

Highlighted features

New programming method: Qcode

Qcode is a text-based programming method available on all channels with function. For each function, it is possible to select whether to use Qcode or the classic method Object List.

Qcode makes it easier to implement more complex operations in fewer channels.

New channel type - Finite state machine

Improved state machine with transition conditions, this makes it easier to implement functions like sequence controls.

New component type - Comment

Comments can be placed anywhere in function groups.

New channel type - Array Channel

The array channel is used to store multiple values in a single channel. The stored values can be accessed in other functions by indexing the array. There are also special array functions that perform operations on all values in the array such as finding min, max or average.

Multiple instances open at the same time

Now possible to have multiple instances of IQANdesign open at the same time. Copy and paste works between instances.

Graphic measure on display

Line and bar graph display controls for IQAN-MD4. Used to draw a graph of a channel value over time.

When using an array channel the complete array is drawn as a graph:

Channel scope

Channels can now be made visible in other function groups than its own, either in sub function groups (protected) or the entire application (public). This reduces the need to create FGI's to access channels in other function groups. To make a channel available throughout the application, make it public. When using these as inputs, they will show up with a dashed line.

PDF viewer

It is now possible to add PDF files to project files for viewing on IQAN-MD4.

New module type - IQAN-SV

The IQAN-SV is an Ethernet camera which requires minimal configuration. More information will follow.

Improved decoding of J1939 PDU1 (DA)

Added property "Destination address (DA)" to JFIN/JFOUT. The new property is enabled when PGN is in PDU1 range. In previous version, this had to be calculated as part of the "PGN" property.

Resizable object group windows in function inspector

Resize the object groups to make Object List more visible.

New connection type: IQANconnect

A new way to connect remotely via Internet where you pay per connection. The IQANconnect service is available for beta testing, more information on this will follow.

For more details on the IQANdesign 4.00 news, see release notes.

Compatibility

IQANdesign 4.00 is fully compatible with project files created in version 3.

Upgrade

Use check for updates in IQANdesign 3 to download IQANdesign 4.00

A hint is to look through the examples and solution library files that install with version 4, you find them under:

C:\Users\<username>\Documents\IQAN Files\

these files have been updated to give examples of the new functionality.

Has there been any thought for creating a block the just decodes the DM1 messages and put them into an array or other object.  this could then be used to display the SPN, FMI, and occurrence without having to decode each message and display it.  This would be very useful based on the number of DM1 error code that need to be decoded.

  There are other software packages that have create block to handle this for both DM1 and DM2 messages.  They have incorporated an up/down scroll to scroll thru the faults held in a buffer.  You can also clear this buffer but would reload if the engine or other device sends another packet of faults.  It also handle all of the status lights that would need to displayed along with any flashing that would be required.

Hello,

It would be nice if CANopen and CANopen Safety was implemented in IQAN Design.

We see the need of CANopen Safety as most of the suppliers for components such as CAN sensors are using or are planing to use CANopen Safety as the CAN-protocol for their safety related components (ISO 13849).

Today J1939 and Generic is implemented in IQAN Design. It would be nice if there was J1939, CANopen, CANopen Safety and Generic.

Regards

Fredrik Forsberg

Is it possible to mount the display upside down so the plugs are at the bottom of the unit? It is for a MD4 7" display.

Thanks

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?

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?