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?

Hello,

I have a question regarding coils for proportional valves controlled by uni- or bidirectional COUT outputs:

As of now, we are using the coil "Sun Hydraulics 770-924" for some of our proportional valves. That coil includes a TVS-diode:

That contradicts the (somewhat loose?) statement in the MC4x Instruction book:

I understand that there is some kind of diode solution internally in the MC4x for COUT's. Does that solution make the coil's diode solution redundant?

Some information regarding the coil:

The coil _appears_ to work just fine in our application but I haven't checked it with an oscilloscope during operation to see what is actually going on. Maybe the TVS-diode in the coil is never active? 

In short:
Is it OK to use this coil or does it, in some way, interfere with functionality? Or should I interpret the Instruction Book strictly and use a coil with no diodes at all?

I thought that with your knowledge of the MC43's internal hardware perhaps you could shine some light on the matter?

Much appreciated,
Christopher Fridstaden

Controller: IQAN-MC43, Connector C1, Pin 12 (IN_34, pull-up type frequency input)

Issue: I'm feeding a 200 Hz, ~60% duty cycle open-collector signal into pin 12, using the module's internal pull-up (per manual: 1.5 kΩ to internal 5V, 10 nF) with no external resistor. Instead of a clean square wave, the signal reads as a sawtooth that never reaches 0V - high sits around 4.6V, low only drops to ~4.3V.

I've confirmed pin 12 floats at 4.6V unloaded, and leakage from my circuit is negligible. Tried several pull-up configurations externally; sink current into the pin stays very low (~0.2-0.5 mA) regardless.

Questions:

1. Is 1.5 kΩ/10 nF correct for this input type?

2. What sink current is needed to reliably trigger a logic-low on this pin?

3. Any recommended interfacing for low-current-sinking sources on these inputs?

Thanks for any guidance.

I have a project where we want to drive some hydrostatic pumps with current outputs on an MC4x controller, but the pump manufacturer's recommended control characteristics aren't available with the MC4x. This project had been working using an MD3 and several XT2 expansion modules, but these are both obsolete. 

The pump manufacturer recommends 35 Hz, but the MC4x only has 71 Hz and higher available. (the pump manufacturer also recommends the dither amplitude be set 125 mA, and that is no longer controllable at all)

So my question is:

1. Is there a way to make this work with 71 Hz? Is setting the frequency to just over double recommended going to work?

My CAN bus operates with approximately 2 V on CAN_L and 3 V on CAN_H during normal communication. I would like to ensure that the TVS diode remains inactive during normal operation and provides protection only during overvoltage or surge conditions.If this device is not suitable, please suggest an alternative TVS diode that is recommended for CAN bus protection and compatible with these operating voltage levels.Awaiting your feedback.

We have several machines with the MD3 + XA2 + XS2 architecture; the MD3 is no longer available to purchase, and we need to provide our customers with a compatible solution when their MD3s break down.

I have checked that in IqanDesign 7 I can create the following configuration: MD5-5 + XA2 + XS2. If we create an updated software, adapting the electrical connection, will this architecture be compatible with the systems currently in operation without changing the slave modules?

We have an MD5-10 display that transitions from the current display page to a black screen and then returns to the display page again. Seems to be about 2-3 seconds showing the display page and then about 0.5 seconds black. The issue does not appear to be program related because it has the problem even when you are in menu mode. We have noticed that turning the brightness down < 80% seems to make the issue go away.

Part number: 20085203

Serial number: 2444230031

Is there any known problem here?

Hello,

I am working on a hydraulic control system based on MD5 and MC43. The main control logic runs in MC43, while MD5 handles non-safety UI functions.

To ensure safe operation, I implemented a simple heartbeat between MD5 and MC43:

Setup:

• Heartbeat: digital signal toggling TRUE/FALSE every ~100 ms in MD5
• Transmitted via J1939 to MC43
• MC43 monitors time since last change
• System cycle time: 50 ms
• Safety action: if no change for >500 ms, MC43 disables outputs
• Logging is active on both MD5 and MC43

Problem:

The heartbeat signal is periodically lost or appears frozen for short periods (typically 100–3000 ms, sometimes longer), triggering safety shutdowns.

Test setup (minimal system):

• Only MD5 and MC43 connected
• 30 cm CAN cable
• Two 120Ω termination resistors at both ends
• No other CAN nodes
• Minimal application: only one J1939 message + heartbeat logic
• No HMI logic or additional communication

The issue still occurs in this simplified configuration.

Tests performed:

• Different CAN speeds (including 250k / 500k/1000)
• J1939 and generic CAN communication modes
• Same behavior observed across configurations
• No communication errors reported in internal Parker logs

Question:

Has anyone observed similar intermittent J1939 communication drops between MD5 and MC43 under otherwise stable conditions?

Hi, I have a MD4 display and it does not recognize the ID tag anymore. Already did a update to the last firmware but without results. Any suggestions?