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

IQANdesign 6 released

For an introduction to IQANdesign 6, see: http://solutions.parker.com/IQAN.

Main features

Integration of Matlab/Simulink blocks

IQANdesign 6 introduces a feature for integrating Simulink models; With the IQAN toolbox for the Mathworks software Simulink, a designer can generate blocks from a Simulink model of a controller, and integrate this in an IQAN-MC4x 
application.

More information about the IQAN Simulink toolbox is found on the IQAN store, here. 

Implemented for IQAN-MC41, -MC42 and -MC43, the feature is not yet implemented in MC4xFS.

J1939 improvements

Multi-packet and text support on JFIN/JFOUT

It is now possible to use JFIN/JFOUT for handling both incoming and outgoing J1939 messages where the PG data length is longer than 8 bytes, multi-packet messages.

Text is supported by new channels TPIN/TPOUT, removing the need for the previous JTOUT channel:

Add Blinking Lamp status to MDGN:s for J1939 DM1 decoding, controlled by property Enable lamp flash on DM1 in a channel.

Improved support for J1939 Component ID and Software ID, can now be controlled by properties on a master module.

New expansion modules: XC41/XC42/XC43/XC44

The IQAN-XC4x is a new series of expansion modules based on the MC4x hardware.

The modules have similar I/O capability as the corresponding MC4x, and support both classic CAN and CAN FD. 

It is planned to certify the XC4x-series for functional safety, however, this is not yet done in 6.00.

New expansion bus type for higher speeds

New expansion modules XC4x have support for higher speeds, both classic CAN up to 500 kbit/s and CAN FD,  with 500 kbps as nominal bit rate and 2000 kbps as bit rate for the data field. 

Speed is selected on the bus and automatically detected by the XC4x. 

CAN FD is supported on MC4x and MC4xFS, on buses A to C

When this bus type is combined with classic expansion modules such as XC21, classic CAN with the lower speed 250 kbit/s must be used.

Remove modules no longer recommended for new design

IQANdesign 6 only includes the most modern target products. Following modules are no longer recommended for new designs, and are not carried over to IQANdesign 6:

IQAN-MC2

IQAN-MC3, IQAN-MC31

IQAN-MD3

IQAN-XA2. IQAN-XS2

IQAN-XC10

IQAN-G2/G3

XR radio

These modules will instead continue to be supported in the 5.x branch.

Other features

Measure function group utilization

When measuring, the function group header now shows utilization for that group. The value includes all channels and lower level function groups of the group.

COUT: Control "bidirectional" property with channel

Implemented

SV camera mirror in run-time

Moved properties for flip/mirror/bitrate/HDR from the camera to video control. This means that individual video controls can have different settings. Useful e.g. for setting a lower bitrate on display pages showing multiple camera images.

Move property "Connect to IQANconnect" to master

As this property only applies for connection to the IQANconnect server via the Ethernet port (not to G11/GT), moved from group property "Connectivity" on Security node to master module. Renamed group property "IP address" to "Ethernet".

Some 6.00 updates that will also come in the 5.05 release:

• Implement full circle mode on the gauge control
• Support external ESC key in PDF reader
• Various bug fixes.

Version 6.00 is available on check for updates and on IQAN store (https://www.iqan.se/store/downloads.html).

Also, see

Release notes IQANdesign

Release notes IQANrun

Release notes IQANsimulate

Release notes IQANanalyze

Release notes IQANscript

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?