I wish it was easier to handle Text formatting. 

Text parameter channel (TP) do not have channels as inputs, which makes it difficult. For example if I want to display a numerical value if the sensor is connected and "not connected" if it is not connected, this is impossible (atleast I can't find out how to do it).

Is there a reason for this. I want to display text or a value or a text, I have to hide the one not shown.

Hi,

I'm using: 

but I have the following Communication menu:

I'm missing the Bluetooth option.

I have uninstalled and re-installed with the same results. What else can I try?

anyone seen this?

I have a weird situation on an MD4 whereby a VDIN button programmed as a momentary button is latching on?

The visibility and enable for the button are both controlled from an IDC channel in turn enabled when a VIN input measuring a position with a tight +/- tolerance added is in tolerance. If the input goes outside the tolerance the VDIN should go invisible and be disabled. There is the possibility the user positions the associated drive to a position just inside the tolerance band and then with a little noise/flicker on the input signal it is possible for the VDIN to effectively be switched on and off rapidly- if it gets into this situation, it seems to latch on- the button itself seems to be off (no yellow background as seen when pushed normally) but in iqan design it is definitely on. Pressing the button makes no difference either way- it remains 'on' The only way to reset it is via a hard reset (power recycle). This is obviously unacceptable and potentially not good.

i have no idea if this is firmware related or what but am interested if others have seen similar and what can be the cause

thanks

Why do I get a project check warning about this? I do have G11 and a GT module on the same diagnostics bus but why is this a problem?

I recently tried to export a dbc file that contained a multipacket JFIN with dynamic TPINs. The exported file does not include the TPINs.Export dbc test.idsx

When adding a J1939 image from the library in the latest version of IQANdesign, it no longer allows you to customize the image size.  It adds the images as 50x50, which is much larger than I want.

I have a MDL2 i normally program it with my other laptop that has 3.19 iqan design on it, I would like to download it on another laptop and program the MDL2. Where can i download version 3.19?

Hello, 

I have imported a J1939 message with a multiplexor starting on bit 13. I was used to have 1  message by multiplexor value (in my previous importations)  but I only have 1 message with the data of the last multiplexor value. Nevertheless, the Multiplexor seems to be detected:

Hello, 

Yesterday, I tried to import a J1939 dbc but I had an issue. I have 2 IDs,  CEFD1EF and DEFD1EF, with the PGN EF00 and 1EF00. When I try to import these 2 messages, I get a random result: I sometimes obtain 2 messages with the data mixed on eachother, or 1 message with the data of the 2 messages, and the PGN read by Iqan Design is always EF00 (61184). 

The work around I found is to import the messages with PGN 1EF00 and change the PGN imported from 61184 to 126720, then import the message with PGN EF00.

I concluded that the DP bit is not read or not correctly imported. In your opinion, is that an importation bug or a bad DBC configuration?

Recently had the same issue with 2 different customers who have been running the same system for 5+ years. 

The systems have an MD4 and 3 MC3s.   

After a partial touchscreen failure the customer replaced the original MD4 (running a program written in IQAN design 3) with a new MD4 and flashed the whole system with an updated program written in Design 5.07.  

After flashing, everything worked for a few days and then one of the MC3s had a No Contact error.  I had them swap two MC3 modules around and reflash and the MC3s received the program with no issues over the CAN network but the No Contact message remained.  I had the customer check the indicator flash codes on the modules and the 2 units that could still talk with the MD4 were flashing 3 reds and an amber (no contact), but the MC3 that couldn't be communicated with was flashing steady amber (status ok).

I then had them unplug the C2, C3, and C4 connectors to the MC3 causing the issue and the No Contact went away.  I had them plug in the C2 and C3 connectors and everything was still working fine (besides open load errors from the outputs on C4 connector).  When the C4 was plugged in the No Contact returned.  

The system uses Digital Out/Returns on C4 pins 13/14, 15/16, & 17/18 to control relays.  Once they unplugged the wiring from those 6 pins the problem was resolved.  The functions run by those relays are not critical to the operation of the system so customer is leaving unplugged.

As I said, this is the 2nd time this has happened recently.  The first time I chocked it up to a wiring fluke but now that it's happened twice and both soon after a screen replacement/firmware update I'm starting to connect the dots and thinking there may be a bug in IQAN design 5 which is causing this issue.