We have a new machine where this has happened a few times now.

Suddenly the image on the screen will freeze and stop updating.

It seems to be repeatable by using the joystick encoder at a particular screen.

We are using "External button control" to select sliders and buttons on the screen by turning the encoder.

The way to repeat the problem:

Select a slider with the encoder

Click a button on the screen which hides that slider.

Exit and enter the menu page in question

Turn the slider

Of note is also that one of the sliders never hide, even though it's "visible" object is false.

I can send the file if you like.

After a few seconds of pressing the screen it resets to the boot image and gets stuck there.

Even though the screen is stuck at boot image, MD4 and XC42 are running like normal in background.

It is possible to start and stop the diesel engine with the J1939 joystick.

It is possible to connect with iQANdesign and iQANrun to take measurements

Cycle time is 23%

CAN utilization is low.

No errors in log file.

Power cycle gets everything back to normal.

So when I export my complete generic CAN database, by going to the Generic CAN module, selecting everything with ctrl A and then going File-->Export-->Export CAN Database, it will export the .dbc however it is missing every 32 bit offset parameter in any paged protocol Generic Frame ins, other than in the 0 page. This does not occur if I just select a single Generic Frame In channel and export it. Any help or potential work arounds would be appreciated. Thanks

How can I use a gauge in IQANscript 6. The button to add this function is not responding and in the manual I cannot find any further conditions for adding this function.

I have a system where I have an MD4-5 connected to an MC43 in a multi-master system, using both APPIN/APPOUT and J1939 messages between them.

I have implemented a FINITE STATE MACHINE in the MD4-5 master, and send the representative code to an identical mock-up of FSM in the MC43 (with all the same links).

For some reason I have cases where the MC43 system will either revert back from one state (4) to 0 and then back again (very briefly). At other times, I can see on my screen a J1939 (or APPIN) message (since I've tried it both ways), where the input number is 6, but the FSM in the MC43 will stay at 5 and not change to 6. What is also strange is that there is no path from 4 to 0 in my FSM design (though I suspect the default value on a CAN error, even with the master bus, is 0).

I am running IQANDesign 6.02.7.5650 (and hope to get an update if our new license code arrives)

We are using a cellular modem to allow our MD4 to connect to IQAN connect. While attempting to update the system using remote connect on IQAN Run the process will hang after updating the MD4.

It is possible to open the application logic in Iqan run with a lower security user level than I want.

This user level has to update a project, but is not allowed to open the application logic. 

Do I miss anything, and how do I have to do this, or is this really possible that everyone with a security level password can see the application logic in Iqan run?

Kind regards, Laura

After I send the project the screen goes blue and shows text below. I take out one of the larger function blocks and then it works. 

Hi all, 

I am trying to find some material like videos or manuals for the CANopen protocol to guide and help me program MD4 master display controller module using IQAN design. I understand the CANopen protocol but not really sure how to set up Transmit and Receive PDO / SDO in the IQAN design since there is no option to import the .eds files directly like the .dbc files. 

All I am trying to do is send some commands to my node from Master and later monitor the status of my node using TX/RX PDOs.

I really appreciate any help or guidance towards CANopen. I am not able to find any existing documentations. 

Thanks

Experienced a visual bug on two out of three object lists when selecting an ECNT channel. Disappears when clicking on each bugged object list area.

Initially the object lists looks like this:

When clicking on the "Decreasing" area the visual bugged object C disappears.

When further marking the "Resetting" area the visual bugged objects B and C disappears.

The increasing area is not bugged in this example.

Keep getting system mismatch error with Internal State: Failed 106 on a XC44 with a MC43 master and can find very little information as to what this means. It might have to do with us having multiple XC43 and XC44 modules in the project with different pinouts/configuration, which are then enabled and disabled using digital adjust parameters, as when I enable certain ones I don't get the error and then other ones I do. If I get a new module it will not complain after the initial upload, but as soon as I update it again, the error returns and does not go away. Any help with this issue or more info on what this error means, would be much appreciated. Thanks