Any of these still out there?, we're looking for one for a log harvestor. Also wondering if just the circuit board can be purchased.

Hello,

I am working with a Parker ECU (MC43FS), and I need to test for short to ground and short to battery faults on specific pins. Could you please provide detailed instructions or best practices for performing these tests safely? Specifically, I am interested in:

1. How to safely simulate a short to ground on the pin and verify the system's response.
2. How to simulate a short to battery and what actions I should take to test the system's reaction.
3. Any recommendations for multimeter settings or test equipment to use during these tests.
4. Expected behaviors or diagnostic codes (e.g., LED blink codes or error logs) that the ECU will produce during these failure scenarios.
5. Any precautions or potential risks I should be aware of during testing.

Thank you for your assistance!

Best regards,

Sayan Biswas

I received my first MD5 and am trying to flash it on the bench. There is no Ethernet hookup so I'm using a G12. It is taking forever and I'm only getting a couple percent done before the MD5 goes blank (after around 10 mins) and seemingly stops. My questions are, what is the fastest connection to flash a system with the MD5? If its CANbus, what is the hardware/ how do I wire it into the system. If its Ethernet, how do I wire that into the system. I have also tried to create a program utilizing an MD4 and MD5 to utilize the Ethernet and the program wont recognize the MD5. I heard the G12s are fast but there is no way it will work as the main programming connection considering the experience Ive had with them. 

XC43 does not have a 0-10V output. I need it for a command signal to another module. What is the best way to do this? PWM? COUT with resister? Thanks!

We have a project that requires control of multiple cylinders, each cylinder is connected to a double acting valve, 2 separate coils, one for each cylinder movement (in/out). These outputs must be safety in our application.

Reading the instruction manual for the DOUTs on MC43FS, it states we must use only one DOUT HS and one DOUT LS per output when its being used in a safety application, so the controller can switch the valve off by either side in event of a fault. Therefore I have concluded we can only have 5 DOUT safety per MC43FS. Or in other words, 2.5 cylinder valve controls.

Can I instead use COUT, and therefore each cylinder function can be driven by a complete COUT A? For example, i can technically connect 10 cylinders, in/out, i.e. 20 valves? I would have to ensure the current does not exceed the limitations of the groups, but does having the shared COUT + affect the safety aspect of a COUT? There is a note saying all COUTs are safety, and nothing about sharing pins like there is under DOUT so I guess I can overcome my issue of limited DOUTs for safety?

I guess if there was a function other than driving a component in a direction it would not be possible, as you can only drive a COUT in either + or - direction, i.e. not both if you has different valves to energise, which could be at the same time.

Also it explicitly states no diodes on a coil connected to COUT (I guess for regulation), does this still apply if I'm using COUTs digitally, ramping from 0-100% and 100-0%? Would the collapsing digital coil cause damage to the COUT driver?

Hello,

I have an odd issue, maybe power or ground reference related.

XC43 IQAN 6.08, sensors powered using the main 24VDC not regulated VREF.

When I start driving valves with the module the reported voltage from my VIN sensors drops by up to 5%.

It happens to all of them irrespective of the sensor type.

It also jumps around a ton.

This makes a huge difference on my 0-5800 0.5-4.5V sensors.

200+ PSI, not good for sensor accuracy.

Any ideas of what to try to fix?

Regards,

Hi, I'm looking to purchase a second-hand MD4 (and XC42) to replace our current control system. Has anyone got these in stock that could be shipped fairly quickly?

Thanks in advance!

I am working with a couple customers who are having "No Contact" Issues with XC43s installed to replace XA2s. 

When looking at the XC43 module itself, the error code is 1:2 (one red, 2 yellows).

I'm assuming the module is getting an errant input somewhere which is causing it to shut itself down.

I would like to better understand this error code better.  What causes an input error and under what circumstances does it cause the module to stop communicating with the master.

I am testing logic with a MC43 and using a PWM HS+LS output.

In the system we are using both sides of the output (+ and -) to drive two individual devices.

Both should never operate at the same time.

To simulate one of the device not operating, we unplug one of the solenoids.

With logic, this automatically causes the other side of the output to now function.

Basically, if the + side fails, it should switch to the - side and operate.

We are getting an open load error on the output with one of the solenoids unplugged and it does not allow us to operate the other solenoid on the PWM HS+LS output.

Is the output designed to shut off both sides if one side detects open load or should the other side work if one side detects open load?

As an example:

If the solenoid between C2:67 and C2:15 is unplugged, but the solenoid between C2:67 and C2:31 is plugged in and fully operational, should we be able to command it with an input signal of -100?