Hey there!

I'm using a MD3 and a MC31 on my application. I'm transfering the application through an USB-to-CAN interface (KVASER - LEAF LIGHT). I'm using the same cable to transfer the application simultaneously to MD3 and MC31. The transfer completes greatly, I can even use the Measure feature on IQANDesign to get signals from them both. But, between them, the MD3 can't see the MC31 (No contact error), as well as MC31 can't see the MD3. Can anyone help me? I can send pictures of the connection and the error that is occurring.

I have a new windows 11 PC, I support many legacy IQAN systems and install all versions of IQAN design on my Laptop. I cannot communicate with systems via USB. 

carefully read this article "https://forum.iqan.se/knowledge-bases/2/articles/236-usb-no-valid-license-or-incorrect-version"  and i do indeed have the correct driver. but in device manager  I get this error.

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

I have the identical set up on my old laptop and it has the identical driver but with no error

any suggestions on how to fix this?

I already lowered angle and still goes over preset angle. What other setting can cause it to go over.

Hello,

Does an MD3 require an ID Tag if it's being used in a single module network? The only other module on the CAN network is a non-IQAN J1939 module (engine ecu.) This is how we communicate with the engine. The machine did not have an ID tag when it was built back in 2010 and we recently replaced the MD3 because the screen was too dark to read. We had some problems opening the original ida file because it was an old beta version. So we had to pull a clone file from the existing MD3 and saved it as an ida3 before sending it to a new replacement MD3. After installing the new MD3 the 'Wrong IdTag!' error appears. I've searched this forum for answers but can't seem to find this particular case. Is there a new address requirement for MD3's that was not the case back in 2010? Did saving the file from ida to ida3 cause this problem?

We have a customer with a MD3 that sometimes works fine and other times just displays this error message. Its running a IQAN Version 2 program.

+AT+IPR?$dAT+IPR?$D

We will replace the display, just curious what is going on.

Thanks

I just had an error show up on my MD3 today which says New MD3 VREF error. Value 0.5V

I was told some months ago, the the MD3 would be obsoleted sooner rather than later, but I have not seen anything further on this.

Any idea how far out is the timeline on obsoleting the MD3?