It appears the fastest application cycle time on the MD5 currently is 50ms, which is 5x what it was on the MD4. Is this something that is planned to be improved in a future software or firmware release?

I need to be able to send out 10ms messages and it is just not possible from what I can tell on the the MD5 series.

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?

Hi folks,

Does anyone here have experience with controlling a Danfoss PVEM valve with IQAN?

Danfoss literature is rather scarce, and I am working with a legacy machine, and trying to upgrade the controllers.

What should the signal be going from the MC43 to the PVEM?

Thanks,

Hi Gustav,

We are experiencing issues with XC44 reporting no contact error and ID tag LED error.

Test bench system consists of the following:

1. MD4-10 (6.08.24.8051):
1. Adress tag 1
2. Can bus A – terminated
3. Can bus B – not used
4. Can bus C – not used
5. Can bus D – not used
2. XC44 module:
1. Address tag 2 (pin 4 and 20)
2. Can bus A – terminated
3. XC44 original harness on C1 and C2
4. No inputs, no outputs for testing purposes.
5. Tried different, known address tags
6. C1 pins have been verified.

Pushing the project to the MD4 has not fix the problem. We tried the same setup with IQAN 7 – same results.

Our field service started reporting same issues in the field where the XC44 is reporting no address tag errors.

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