For a long time we have been running into the limitation that the Program memory is too small for us. Is there also a view with the new MC4x to increase this in the future to 3Mb for example, this would help us enormously in adding functions that we are now forced to leave on the shelf.

We have experienced issues with two MD4-10 units where the touchscreens have become unresponsive. These master modules were being used on two different underground mining machines, operating in the same area of the mine with high levels of H₂S. Could there be a correlation between H₂S exposure and the touchscreens becoming unresponsive?

Good morning.  I have and MC43 and MD4 running on a machine that is programmed in 6.08.32.  I am getting random MC43 Vref B error codes along with the errors for the switches and transducers connected to that Vref.  

When I record a plot graph of the MC43 diagnostic channel attached to the Vref, input voltage, and the input voltages for all the sensors, I am not able to record any change in the voltages that would indicate a Vref issue.  Has anyone else ran into this issue?

We have a customer that requires a certain type of PPE glove to be used when operating MD5 HMI. The system we have planned is using 10" display but we don't currently have a unit here to trial, instead I have tried a MD5-5 with the certain glove type and it works OK. 

Is the 10" version just a scaled 5" and therefore I can assume as long as it works with the 5" it will be fine with the 10" version? I guess it depends if the same manufacture and screen tech is shared between the different modules?

We have a project that is to be used for the next 40 years. It is a functional safety system that utilises MC43FS. These modules will likely be superseded multiple times (probably due to enhancements in electronics etc) after the 20 years lifetime shown in the manual:

To guarantee functional safety, presumably its recommended we remove and replace the MC43FS after 20 years as described in the manual regardless if the module is working correctly? I'm trying to avoid re-assessing the system in 20 years time and fitting a safety controller available in 2045. Therefore I intend on having a brand new MC43FS available for when the system needs a replacement module in 2045.

Is the 20 years triggered as soon as the module is powered up, therefore we would need to clone the software only when we want to replace the module in 2045 (rather than installing software now and starting the 20 years timer)? Or has the module 20 years been triggered from manufacturing date on the serial number?

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

I have 2 different units both using MC2 DOUT to control a large solenoid. Both have flyback diodes installed correctly near the relay. After several years of use, both have the MELF resistor for that DOUT failed inside the module. How can i prevent this from happening to a new or repaired module? Fire a smaller relay to control the large solenoid? Add a capacitor to the DOUT line? Another diode inline on the DOUT line? 

 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.