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.

Hi,

Our transmission manufacturer uses a 2-pin magnetoresistive (MR) speed sensor.  The output is 7 mA for low signal and 14 mA for high signal.

The frequency range would be 0-1500 Hz.

Given that FIN is looking for <1V low and >4V high on an XC43, we can't condition the signal with a simple current-sense resistor.

Do you have any suggestions on how to integrate this type of sensor into a XC43 module?

Recently we encountering "No Contact Error" in our system,  but we found out that the cause of the problem is when the XA2 unit temperature goes to 42-46 degree it creates no contact error, but my question is, why it is happening if the operating temperature of the XA2 is up to 70 degree Celsius. I check on Diagnostic, Voltage are okay, Status okay, Address okay, only that the temperature is high.

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?