We have a machine that has sporadic nuisance open load errors on a function controlled by a unidirectional current output (COUT-G) on an MC43. Since this happens with some frequency, I suspect we are right up against the limit of the open load detection threshold. They test out well in assembly, but any increase in resistance occurring in the field might be setting it over the edge of the error threshold.

How can I calculate at what load resistance, commanded current, and supply voltage an open load error will occur?

This function is controlled with a Parker CCP024H 1/2" super coil with nominal resistance at room temperature of 30.30 ohms. Machine runs on 24V (around 28V when alternator charging). Maximum commanded current is set to 600mA.

Are the current out channels on an MC43 suitable for dishing out a 4-20 ma signal? It would be controlling a VFD.

I know the current out channels are typically used to control valves and used in the hundreds of milliamp range. 

We are using a MC43 and using PWM and COUT channels. What we have noticed is when a PWM HS output is shorted to ground, one of our COUT outputs goes into overload. In our case, C2:51 was shorted to ground but C2:67/C2:15 had the overload error. 

Hello,

ID-tag 4 to 7 does not exist for Molex MX123.

We use 4,5 and 7 today and have to re crimp those ID-Tags for MX123.

When do you plan to offer ID-Tags 4 to 7 for MX123?

Regards

Fredrik Forsberg  

IQAN Design refers to CAN bus on the MC4X as A, B, C etc, manual (under installation) refers to it as numbers 1, 2, 3 etc. Although its obvious to work out, its better for us if its one designation across the board to avoid confusion when cross referencing documents.

We are using a MD4-7 and x2 MC41's on some of our machines (we actually wanted to use only x1 MC42 for these jobs but we are still waiting for the parts to arrive and have deadlines to meet so we are just using what we have available to get the job done)

But last night we started testing the machine and went through all of the procedures and functionality when all of a sudden an error appeared on the display telling me that one of the MC41 controller lost comms, but the other one was still fine and giving readings... So the 1st thing we tried to resolve this was typically switching the machine off and on, but this time there was no CAN comms at all.

We went though the wiring harness and made sure that everything was correct and the wiring was all good, so we then went and replaced both these controllers with new MC41's we had in stock, we plugged it in uploaded the software and the system was happy again with the new controllers and it is still working fine at this moment... So I took the 2 faulty MC41's to my office and connected it all together to try and diagnose the issue. 

Each time I tried uploading software (using IQANDESIGN 5.01 via ethernet) it kept on warning me about the incomplete system and that only the MD4-7 will be updated.

Eventually we switched from CAN-A to CAN-B only on the MC41's. but upon each attempt to upload the software, the same "incomplete system" warning appeared. 

So I just left it for a while and a few minutes later decided to just try again uploading once more. Well it worked all of a sudden and that is also a big problem, because I didn't change anything where I could say " there, that was the problem".

This is worrying us a bit, because we have no idea why this happened in the first place and secondly these machines are going to the middle of Africa... So this sort of thing must not happen at all!

I have only been using MD4's and MD3's with XA2's in the past without any problems at all, these are our first machines using the MC4x family and this is also the 1st time that I encountered any issues like this on IQAN.

Have anyone else experienced this before?  I have no idea why it failed or why it started to work again and this is definitely not the correct answer to give the person asking this question when there are deadlines to meet.

The other thing to mention also is the LED's on the controllers which blinked bright yellow 3 times then blinked dimmed yellow 3 times while it was not communicating. which also does not correspond with these fault codes in the manual. There was no RED LED blinking at all. 

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.

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 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?

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