Hi,

I observed a bug on our machine.

If a sensor is detected in error, a defaut Error value is applied.

For us, this error value is 500 bar.

We made an Internal Digital Channel to detect if the value is egale to 500.

If true, the channel change to TRUE value.

But when the MC43 is a new one, the channel doesn't work.

As you can see on the picture, the channel value is 500, but the Internal Digital Channel is still FALSE :

Whereas the Qcode is simply :

If I just change the defaut error value to another in IQANRun, and set back to 500, the channel starts to work.

Did you already see that ?

The value tested comes from a filter channel, maybe that's the point, but it is strange that it's working if I change the value and set it back to the same defaut value :

We already observed something similar if we update a machine with a new soft on which one we change something on an existing variable. But here it's a new MC43.

IqanGo app have too small fonts for the values. If there would be large font mode, you could see important values more easily.

I recently encountered an error on a machine in the field where an MD4 will not boot up if it has 24 volts coming into C2 pin 1 or C2 pin 2.  MD4 is running IQAN Design 6.08.  Instead it will say "IQAN-MD4 Safe mode! Application no loaded Open or short circuit on ADDR pins."  I was able to replicate in a lab.  

We recently renewed our IQAN license and updated to the latest  version of design which is when this problem started.  As a test, I reflashed the exact same program except that it was written in IQAN design 6.02.  I did not encounter the same issue with IQAN 6.02 so I believe this problem was introduced in 6.08.  

Please review as we have machine in the field that have been running for a while that are using C2:1 and C2:2 as rocker switch inputs.  The MD4s will not boot while the rocker switch is in the ON position.  

Is there a programmatic way turn off a MD4 display but leave the controller and program running in the background?

Good morning,
I kindly ask for help regarding the following problem:
as soon as I start the engine, the system detects an "Abnormal update rate" error SPN639 FMI 9 and a warning SPN1235, FMI9. I want to clarify that after a while that the engine works, the RPM + and RPM- command does not work anymore until I switch it off and on again. All engine data are correctly displayed and managed. Can you help me please?
Thanks.

Best regards,
Lorenzo Simonetti

Is anyone using an ISO/other standard model for software quality control?

Thank you in advance for the feedback.

Is there a way to access the top level for the Adjust Groups in a project file; the menu page that shows a list of all the Adjust Groups?

We have an application that the customer would like to press a button (or something similar) and it would take the user directly to the Adjust Group menu.  The only way I can find to do something like this is setting up a button to take the user to a specific Adjust Group.  

This feature would allow the customer to better protect other menu items from users that do not need access to those items and at the same time allow access to the list of the Adjust Groups.  

When importing a program designed in a version of IQAN Design earlier than 6.08 all existing image libraries appear to be removed during the import.

The images previously added to the display pages still remain and function as normal, but the library images they are linked to appear to be removed and all library groups are absent.

Hello,
Is the following setup possible:
MC41 #1 with ID tag 0 connected on CAN A a to a J1939 bus
MC41 #2 also with ID tag 0 connected on CAN A a to the same J1939 bus

The MC41 would not use the 1939 bus to talk to each other but to our own ECU. From what I know I think this should be possible because I can specify a different J1939 address for each MC41.

Will this work or will I get errors because both MC41 have the same tag even though they are not communicating with each other?

The motivation behind this is that we would prefer if we can simply use a single type of ID tag in production.