Main features for version 4.06

Add support for CRC check/generation for JFIN/JFOUT

The new channel type, CRC parameter channel, can be connected either to user defined channels for outgoing CAN (JFOUT and GFOUT) or to channels for incoming CAN frames (JFIN and GFIN)

This gives a functions for calculation of an additional checksum placed in the CAN message data field, and a message that can between 0 and 8 bits long.

The channel supports three different checksums:

CRC-8 as defined in SAE J1850, taken over both data field and identifier.

CRC-8 as defined in SAE J1850, taken over data field only.

J1939 defined 4-bit checksum, always combined with a 4-bit message counter.

The purpose of the CRC channel is to aid in the implementation of CAN communication to non-IQAN modules where these protocol features are used for risk reduction, for example the Parker EVM25 module.

IQAN-MD4 Menu system active error indication

The menu exit button in upper right corner will show message severity icon when there are active dialog messages to be seen on the display pages.

IQAN-MD4 Gray out disabled buttons when adjusting During adjust of FP, IP and TP, the buttons for menu back and menu exit are grayed out.

IQAN-MD4 Show active state on single adjust items The active state of FP, IP and DP channels is shown as text below the channel name.

Added support for Peak System USB-CAN adapter

Implemented for IQANdesign, IQANrun and IQANanalyze.

Important problems solved

There was a problem with upgrading to version 4.04 or 4.05 over USB for MD3 and MC2 modules containing older versions, more information in known problems. This is now solved.

For full release notes, see:

http://divapps.parker.com/divapps/iqan/Downloads/IQANdesign%204/ReleaseNotes4.06.12.htm

http://divapps.parker.com/divapps/iqan/Downloads/IQANrun%204/ReleaseNotes4.06.6.htm

http://divapps.parker.com/divapps/iqan/Downloads/IQANsimulate%204/ReleaseNotes4.06.10.htm

http://divapps.parker.com/divapps/iqan/Downloads/IQANanalyze%204/ReleaseNotes4.06.3.htm

Is in the future you expect to add the option to make us able to create a background and add forms to separate items and have some kind of box or forms like rectangle/circle/panel layout to make easier the graphical design.

Actually, the only way to obtain this is to build it with an external application and import this after. but if we have any modification to do, we have to re-edit this graphic and update it.

For big developpment this is acceptable, but for simple/quick project, this option can be very interesting. In the industrial type HMI, they use this concept. You still able to import, but you can design panel and other graphical add-ons to arrange your page.

Thanks!

Platform 4 - MD4

Is it possible to provide more information regarding CAN error reporting ?

For example "Critical CAN Error"

Can you information regarding the type of error that has been found ? For example

-Collisions

-Insufficient termination

-Error frames

-High utilisation

Summary: If the MD4 shuts down a CAN port due to a critical error then I just want to know exactly why.

4.04 IQAN Analyse - NI CAN Analyser.

The tool now reports CAN errors. Is there any more information available regarding the error frame encountered?

Is there a way to reorder the system list in IQAN Design? I would like to group like modules together, but I am unable to change the order.

Now that with the G11 and IQAN Run apps, it would be nice to have these modules in a logical order so the guy on the table can easily sort through all the modules.

IQAN offers a Serialnumber ModuleDiagnostics channel, but its in text format. As far as I know, you can't reformat/put that into a numeric channel, or on the CANbus.

What I would like to do, is sending over a unique hardware number (doesn't necessarily have to be the serial, just as long its "baked" into the IQAN somehow) over CAN. So another (non IQAN) unit notifies whenever hardware was replaced. Ideas?

I run a dedicated J1939 Bus to speak with the Vehicle CAN. I imagine most do it this way.

Now that I have to cover for the possibility of both 250kbs and 500kbs J1939 vehicle CAN buses, and do not want to have multiple versions of software floating around if I can help it (tried it, can be a bit of an unneeded mess), I am running out of CAN Buses on my MD3s.

The way it is now, I am planning on setting up 2 vehicle can buses, each with their own "engine", then pick which engine to enable in the settings (250kbs, 500kbs, or disabled). Unfortunately, that leaves me with a wasted Bus since I can not run both the 250 and the 500 to on the same physical CAN Bus pins. An empty Bus might even throw an error. I haven't tested it yet.

It would be nice to be able to select J1939 bus speed in the software settings or be able to disable the unused bus in the settings. Either would free up a bus on the MD3 so I wouldn't have to put absolutely everything else (Master, Expansion, Diagnostic, and J1939 components) all on the same physical bus.

It would be nice if we had control over the menu structure of the "System" and the "Functionality" tabs much like we do on the "Adjust groups" tab. I like to organize my programs so they are all as similar as possible for troubleshooting purposes.. if something ended up out of place it is usually not worth going through the process to reorganize..

IT WOULD BE NICE TO HAVE A STATE MACHINE OR STATE PARAMETER FEED INTO A VIN CHANNEL SAME AS IS CURRENTLY USED FOR COUT CHANNELS AS A MODE SELECTOR. ALSO IF THE UNIT COULD CHANGE WITH THIS WOULD BE VERY HELPFUL. WHEN CHANGING FROM ENGLISH TO METRIC PSI/BAR I WOULD LIKE TO JUST HAVE TWO SETS OF CALIBRATION AND SCALES THEN HAVING ALL OF THE MATH CHANNELS AND TEXT PARAMETERS TO SHOW THE PSI/BAR NEXT TO THE VALUE ON DISPLAY PAGES. I CURRENTLY HAVE 112 VOLTAGE IN PUTS AND WILL HAVE A HECK OF A TIME PUTTING IN ALL OF THE MATH CHANNELS AND VALUE CHANNELS JUST TO SHOW THIS AND CHANGING ALL OF THE FUNCTIONS THEY FEED INTO.

Hello, I have used MD3 module and have also flashed my program in the kit as per standard process. But unfortunately today am not able to flash my program in to the MD3 module.

it says error - "No handshake reply from master module Unknown"

Can some one help me the solve this?

Highlighted features

MD4: Support for rotating images Added new property Rotate on Image controls. Example usage, a wheel position indication for all-wheel-steering: Pixel size at font size properties In addition to the predefined font sizes (Tiny, Small, Medium, Large, Huge) it is now possible to enter the font size in pixels directly (as an integer). Implemented for label and value controls. Application documentation, add adjust items Included adjust items and parameters with limits in the auto generated project documentation. Remove logging of saturation warning Logging of the COUT saturation warning is now removed. COUT status will still indicate if the output is saturated (unable to drive the commanded current). IQAN-SV Add module info in menu system Information about an IQAN-SV camera can now be shown after it has been assigned by selecting the camera in the camera menu. For more info on feature updates and problems solved, see release notes