The new -M24 versions are now in serial production:

See updated catalogs:

IQAN-MC4x_brochure_HY33-8413-UK.pdf

IQAN-XC4x_brochure_MSG17-8417-UK.pdf

Requires IQANdesign version 7.03, see Version 7.03 released / Software / IQAN

Hello,

We are experiencing faults across multiple machines with LC5 levers.

The fault presents intermittently as a no contact error, and requires a power cycle to resolve.

The LC5 status light shows a fast blink pattern of 2 yellow, 15 red, then approx 30s of high frequency red blinks. See attached videos (split into 2 parts due to size restrictions). 

The MC43 in the system shows an R3:1 no contact error blink sequence. Please note that the LC5 is connected to our MC43 via an expansion bus connected with CAN-A. Our application cycle time is 20 ms.

The bus CAN-A contains 3 other devices. When the fault occurs, the other devices on CAN-A continue to transmit/receive CAN messages.

So far we have tried:

1. Checking canbus termination: 56 ohms

2. Increasing the polling cycle time from default to 80 ms. 

3. Checking CAN bus utilization. Busload after the of the fault was measured at

approx 36%.

We have also tried to replicate the fault by manually disconnecting power/can from the LC5, with no success.

Can anyone provide more information on the causes and possible solutions for this error?

lc5-fast-blink-SN-421040085-2of2.mp4
lc5-fast-blink-SN-421040085-1of2.mp4

Thanks in advance for any assistance.

Rhys Nicholls

The electrical diagrams for the MD5 that are published on the Parker website have an error, the +batt and -batt are reversed on those drawings. The MD5 instruction book is correct.

i need more output io

but it looks like a big tear up

Has anyone had any success controlling valves that specify a low dither frequency below 71Hz with the XC4x current outputs?

We have a machine that is using a HAWE valve that specifies a dither frequency of 40-70Hz with 55Hz recommended. It also gives a range of dither amplitude of 20%-50%. The minimum frequency of the Cout channels on the XC4x modules is 71Hz. I'm sure 1Hz is not going to make a big difference if we set the frequency to 71Hz, but just wanted to see if anyone has had any similar experience or other recommendations. Just trying to avoid any possible stiction/hysteresis/chattering issues.

It's recently come to my attention that the final order for new XA2 and XS2 modules is this month (January, 2024). This blindsided us, since we never received any warning for this. We were instructed to move to the newer XC expansion modules, but never given a date of when production of these would be discontinued. There was a Parker notice sent out in April, but this never made it to us as an OEM/end user, so now we're scrambling to figure out a strategy for service and replacement of the hundreds of modules we have in the field, if there's any issues in the future. There's not a great way to replace these, especially in systems that use an MD3, since the XC series is only compatible with IQANDesign 6.00+ and the MD3s aren't supported in those newer versions. These MD3 systems will likely require a full controls overhaul due to one faulty module.

Can Parker please post these notices publicly somewhere where end users/OEMs can see these directly from Parker?

Or is there a mailing list that we could sign up for to receive these notices?

Solely relying on vendors to filter out and forward important notices such as this to end users/OEMs is clearly not sufficient.

I'm hoping someone might be able to chime in if they have seen something similar before.

I'm driving two contactors (they close at different times) off the MC41. The contactors at peak draw 3.9A for about 75ms. When the contactors close, a very short time later, the MC41 enters a critical fault. The flashing lights (4R, 1Y, 12Y, 3Y, 1Y, 2Y) seems to indicate there is a 'watchdog' fault. Looking at my CPU/RAM usage and cycle usage, we are not even using 1% capacity. Is it possible this overcurrent condition could trigger this particular fault?

As well, I can't seem to find any information on what the 12Y is supposed to mean? "R4:1 n:3:1:2" which would be the "n" in the manual. What would the 12th part of the software mean?

Say you have a brand new XC43. The firmware installed from factory is 1.0 (I think). How many times will the firmware update before reaching the current version of 1.03?

Also, the XC4x SIC module status lists a value of 140 as Firmware update. From the documentation that means the firmware update failed. Are there any other status values pertaining to the firmware? 

What are the different values possible in the system info "InternalState" and is this channel accessible in the project?

Hi!

Previously we used MC2 in a project. Now changed master module in the program to MC43.

We have a DIY test board (large resistors with LED for indication) to double check if the machine sends signal to valves etc.

Using COUT channels...so connectors come in pairs. With MC2 if one of the connectors wasn't connected to a load it would display "open load" error when machine would send a signal to a valve that isn' t connected, but connected one would work when output is signal is given. (no open load error when joystick is in neutral)

Now with MC43- both COUT pair connectors have to be connected for it not to display "open load" error..even when joystick is in neutral position.

Is this because MC43 diagnoses itself differently than MC2 or is there something to be changed in the program?

Hi, I have an issue with intermittent MC43 COUT overload errors on one of our machines.

Status is OK and operates well in most conditions, but will randomly report overload (even when that function is not requested).

I have tested the solenoids, plugs, and wiring harnesses within this circuit and all looks ok.

COUT circuit C1:16, 41, 57.

Is there anything else I should check to see what might be going wrong?