The DTC simulation doesn't seem to be working correctly in version 7. When you change the value to a number above -1, you cannot go back to -1 to turn off the DTC. It will only go back to 0. 

I have a MD5-5 and MC41 in a system with a J1939 bus connected to both masters.  When I select an integer parameter channel to select between 250 and 500 kbps, it creates an error. The channel is located in an Initialization function group.  If I remove the connection of the J1939 bus from one of the master modules the error is not generated.  Is there a limitation to only being able to have one IQAN master connected?  I have tried this with 7.04 and 7.05 with the same result. In the pic below, if I hover over the red diamond it says "Speed not supported."

Hello,

just got that message on a MD3 screen, any idea the root cause ?

Br

/Adrien

Is there a way to create a Screen Saver on a display module (MD4 or MD5) ideally enable SS after xx minutes of inactivity and disable SS with a touch of the screen?

It would be nice if when parameters that are brought into the application from the built in J1939 database had their default property value set to 'Yes' for J1939 error check. All the J1939 database parameters are set to 'No' by default and need to be manually changed. If we were to manually drop a parameter using the orange 'Add' button, that default value is set to 'Yes' already.

J1939 Database

Manual Parameter added

Hello .  when I import a DBC file , it show this error, could you pls help me with it ?thank you ! 

We need a multimaster system that has (1 x MC43 and 1 x MD5) and (1 x MC43 & MD5) that exchange app in / out data when diagnostic and master bus is connected but continue to function with their own program using local IO when the systems are disconnected from each other. Each separate system has 1 x MC43 and 1 x MD5 display for viewing information inside the MC43. See system below showing the disconnection between the two separate systems:

The separate systems need to talk to each other using appin and appout, but still run separate control programs when disconnected.

Below is an extract from the IQAN user manual:

In this instance, I make the non headmaster optional in the settings so when the optional modules become disconnected from the headmaster, i get no errors in the headmaster and the headmaster. The headmaster continues to run its own application in a valid system state. 

In the optional module, when it disconnects from the headmaster, because the headmaster is not optional, will I get errors appear in system logs in addition to appin / appout for the timeout? I'm concerned it will log can bus module error state, the customer may be confused by these faults if it does this. Also this application will continue to run with its own local IO and control I have built into the application, so effectively becomes a standalone system that continues to run its logic even though its lost contact with the headmaster?

Any advice how I can handle the bus termination, as when we switch systems in and out, the bus configuration will change and we will loose termination at different points. Without the option to switch termination on and off unless the software is reloaded, I am unable to control this unless i switch relays on and off bringing in resistors at certain points on the bus. Maybe its easier to set up two separate applications that communicate when connected, can this be done with appin and appout in different application files?

hello guy, 
i am finding it difficult to program the can j1939 on the mc2/xa2 system. 
i want to expose some of the output of the mc2/xa2 on the canbus (j1939) in order to pick it up by another (external) module for data acquisition purposes.  I am having issue with the jfout module -  it seems i ve configured it right but i can see the module in red and is returning module not assigned error. 
I need help to get past this stage. 

There is definitely a repeatable problem with 7.05.  I have loaded 3 different programs with no changes other than updating to 7.05 from 7.04 and they all stopped after loading the two MD4's when it tried to load the first MC43 (we have two MD4's and 3 MC43's in all these machines).  Disconnected and no replay from the MC43.  I tried both IqanDesign 7.05 and IqanRun 7.05 with the same results.

this is the pulse captured from our gear speed sensor

and this is the freq measured from our iqanrun r7.

wonder why there is an unexpected spike freq.

and the unexpected freq is not always happen, but rarely happen, makes troubleshoot even more difficult.