We have a requirement to have multiple XC43 modules remotely to the master MC43FS module. Its likely they will all be powered from separate power supplies and they wont supply the same 0V for batt -ve.

Is this likely to be a problem in terms of interference etc?

IQAN Tech Support,

We are looking for help with troubleshooting our "IQAN Controller, Master Unit, IQAN - MC43" Safety Controller. It is getting inputs from two Temposonics tank-level sensors in our electronic water-level system, models GB Series & RF 5^th Gen input sensors. The IQAN controller is PN 20085113.

We are receiving a potential difference (voltage output) of 0.39 V from Output pin to System Ground when measured with a multimeter; however the programming software indicates that the output should be 0 V. Our known inputs and outputs are below:

• The tank level sensors are bottomed-out, as there is no water in the tank.
• With no water in the tank, the IQAN is programmed to output 0% Du Cycle, yielding 0.0 gallons on the display - but there is a .39V measured.
• The lowest water level reading that the sensors could output is 120 gallons, but should read 0.0 gallons below that.
• We are needing help troubleshooting and establishing / calibrating our 0.0 baseline

Questions: 

1. Why is a voltage being read at the output, when the program is indicating that it should be zero? 

2. Can we create a code or loop in the program to circumvent the small output voltage?

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

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?

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?

Is the MC4X PWM Input able to monitor frequency ranges outside of it's normal function like 1000 Hz and if so what would the effects be with the resolution of the readings from the MC4X?