On IQANDesign version 6.02, I am experiencing a consistent crash when trying to copy a group of display objects. It does not crash with small groups of controls that do not require input channels (line, label). But if I try to copy a small group of a label and an LED, the program crashes every time. 

Issue with channel order, ver 6.02

Steps to recreate problem:

1) Create 3 signals

2) Set "Internal digital 1" as output

2) Set "Internal digital 3" as output

3) Set "Internal digital 2" as output

Then compare the Calculation Order to the Function Group order.

To resolve this issue, you need to go make a change to the order, then change it back.  Then all will be correct.

Just loaded some software into a new build machine and got the following blue screen on the system.

The other modules (2 x MC3) are fine, all have OK status in IQAN Run, but the display boots for around 1 second then i get a blue screen, any ideas on what may be the issue and why?

How can i get it out of this blue screen loop as it crashes before i get a chance to reinstall software to see if thats the issue?

Thanks.

Hi everyone,

When I put a simple line on a display page, if I choose a gradient for color, in Iqan Design I see correctly the gradient but when I simulate, only one color on my line.

How can I use it? I try with linear bar but the result is not like I want.

Thank you everybody and Byebye

I am having trouble communicating with a Peterbilt that has a PACCAR/DAF MX11 engine. I am using 4.07 software.
Is there any chance my communication problems might be on the IQAN side?

Just for my curiosity.

When I am setting up the gauges and what nots for the display. I notice that for the display on the MD4 I can see and display all of the sensors on any of the masters without doing a APPOUT/IN or JFIN. This tells me that those values are always being transmitted between the masters. But, if I want to use the same data values into an Application logic circuit on another master then I have to do a APPOUT/IN or JFIN. If all this data is circulating on the master or diagnostic bus anyway, why do we have to transit it again for use in the application logic? I'm building a multi master system with one md4 and two mc43.

Can I pack multiple signals / parameters into the APP OUT parameter so as to send more infomration in one message?  Then unpack it on the other side. For example, if I have a lot f digital signals I want to share arround multiple MC43 modules, sending only one APP OUT is far more sensible than making multiple APP OUT's ?  Kind of like a J1939 PGN with SPNs inside.

In the main menu is the Preferences tab, can I add functions there for example a different display mode option.

Like choose another display mode between classic and new.

Is it possible for one MD4 to have multiple J1939 SA addresses? For example one SA (SA=0 or 1) to communicate to another MD4( SA=39) and another SA (SA=49) to communicate to engine and transmission?

At a given cycle time, is it possible to determine if a J1939 CAN frame has just been received? I am aware CAN frame blocks return a boolean indicating if their frame is new or not. However I believe this only works if the CAN frame has an enabled time out. Is it possible not to have a time out and still be able to determine if a CAN frame is new or not?

My goal is to not implement a time out, yet still be able to distinguish a CAN frame that has not been updated for a while from a CAN frame that is continuously being updated with identical values.

Thanks,