0
Under review

Run fault PID 90131 bluescreen crash

nick_namsep 1 week ago in Master modules / MD4 updated by Gustav Widén (System support) 2 days ago 1

Hello,

I am currently working on a machine that uses an IQAN system with an MD4. For some context: it’s a mobile hydraulic machine driven by a diesel engine. I’m running into an issue that I haven’t been able to pinpoint to a specific cause, and I’m wondering if anyone recognizes this error code or has ideas on what I could try next.

The error code I get is:

Run fault PID 90131 TID 14 Signal 11 Code 0


The situation is as follows. When I start the machine, everything initializes fine. The whole IQAN system comes up normally, the UI works, and I can operate the control system without any issues. When I give the signal to start the engine, it works in two steps:


First, the engine ECU is powered up. Then the ECU sends an OK signal back, after which I need to trigger the start again to actually crank the engine.


The ECU and the IQAN system communicate over CAN. However, as soon as I give the first start signal and the ECU powers up, the MD4 immediately goes into a blue screen and completely locks up. Nothing responds anymore, and I can’t recover from the error without completely disconnecting the system and doing a full reset.

As far as I can see, there’s nothing useful written in the logs that I can trace back to the blue screen—only the information shown on the display itself.

I’ve been trying to diagnose this for a while now, but I’m not sure what could be causing the fault in the first place. The only thing I could find online was a post mentioning CAN bus overload, but I don’t really see how that would apply here.


At this point I’m mainly looking for ideas on what could cause this error, or where I should start with further diagnosis. Any ideas are welcome.

0

Are Diodes or TVS required when using a COUT for On/Off control (NOT Proportional)

Mark Bevington 3 weeks ago updated by Tim Reen 3 weeks ago 1

Hi,

We are converting a machine that had MC2's, XA2's, XS2's & MC3's to use MC43's or XC43's. There were not enough DOUT's when the application was originally written, so COUT's were used and driven from either 0% to 100%, or from 100% to 0%.  There is no proportional control used.  The command input to the COUT is either 0% or 100% can instantaneously switch  from either OFF to ON, or ON to OFF at a 10 mS system cycle time. See below for an example of the code. Are TVS, or Diodes, required across the COUT to protect the outputs from instantaneous changes??   

Image 5210

0
Answered

G12 No contact at diagnostic bus speed of 500/2000kbps

Jesus 3 weeks ago in Gateways / G11/G12 updated by Gustav Widén (System support) 3 weeks ago 5

I am trying to change the speed on the diagnostic bus between an MD5-8 screen and a G12, but it only works at speeds of 250 or 500 kbps. 

At speeds of 500/2000 kbps, I get the error message ‘No contact G1x’.

According to the G12 instructions, it should be able to support this speed.

Image 5208

0
Answered

Relay on XC43 HSDOUT caused Open Load error

Shen Yang 4 weeks ago in Expansion modules / XC4x updated by Gustav Widén (System support) 4 weeks ago 1

We've used the 24V DC relay (datasheet is attached) on a XC43 High Side DOUT, but it doesn't seem to like the relay and show us a Open Load error. Could you please help us understand why this happened? Is there anything we need to pay attention to when using relay?Section-1_35_2018.pdf

0

Error during startup on XC44

Jesus 1 month ago in Expansion modules / XC4x updated 2 days ago 2

Good afternoon,

I have a system that uses an MD4-5 as the master and several XCx modules as extension módules. One of the XC44 modules randomly fails to connect when I power up the system, and the LEDs indicate the following error:

"R4:3 3:1:7 Startup check. Expected after update of XC4x to FS capable version."

This error is random; it may not appear for a week or it may appear several times on the same day.

I have checked the wiring and it is correct, as is the battery voltage.

0

Problem using Current CIN sensors

A DOMS 1 month ago in Master modules / MC4x updated by Gustav Widén (System support) 3 weeks ago 1

Hi,

I need some help.

I have trouble using CIN sensors.

I have no problem with any others sensor types, but with almost all current sensors (4-20mA), I get an error with the signal (24mA) after some use.

But not all the time.


For exemple, here I have some undesired spikes while measuring.

Spikes are very short so I can't read +24mA in IQAN but I think if there was longer, I would have 24mA, so more than my scaled value at 20mA

Image 5198

For this exemple, the value come back to a good value quickly, but sometime it stays in error ~= 24mA

Have you ever had similar problem ?

Do you have some advises ?

I can't use Vref+5V because my sensors can be supplyed between 8-32Vdc.

The sensors used are made with 3 wires : +24V / 0V / Signal

So the wire 0V is connected to the 0V of the battery, but on every machine, the 0V of the battery is conencted to the chassis of the machine.

Iin the manual it is recommanded to do not connect the 0V to the chassis. It's not possible on mobile machine.

Image 5199

So we tried to connect the 0V to the VREF- but it's doesn't work obviously.

Is there a way to have a VREF for sensors that supply about 10Vdc ?

Hope someone has some experiences that can help us to understand this problem with current sensors !

0

MC42FS Error code R4:2 1:1:3 I/O startup test failed

Gijs van Beek 2 months ago in Master modules / MC4x updated by Gustav Widén (System support) 4 weeks ago 1

Got the R4:2 1:1:3 I/O startup test failed error on a MC42FS module.

Even when I only put power (24v external power supply) and a address tag on it.
Tried to put an empty program on the controller. The controller is installing the program but when it restarts it keeps coming back with the same error.

Is there anything I can try to fix this?

0

XC43 multiple DOUT overloads

Petteri 2 months ago in Expansion modules / XC4x updated 2 months ago 0

We are having a problem with XC43 giving overload errors in multiple DOUT's at the same time.

Construction of the application is MD4 + 2xMC43 + 3xXC43, running with IQANdesign 6.08.

Problem is only in one of those XC43's. We use those DOUT's to control two different kind of solenoids, connected as shown below:

Image 5164

Fault codes are occurring only in:

  • C2:29 (load 0,83 A), C2:13 (0,83 A), C2:30 (1,29 A) and C2:14 (1,29 A) overload simultaneously
    • If you activate only one of these DOUT LS's, every one of those are giving fault code
  • C1:58 (1,29 A) and C1:42 (1,29 A) overload simultaneously
    • If you activate only one of these DOUT LS's, both of those are giving fault code
  • C1:60 (1,29 A) and C1:44 (1,29 A) overload simultaneously
    • If you activate only one of these DOUT LS's, both of those are giving fault code

Sometimes you can drive a day without having any fault codes, sometimes fault codes appear at the first activation at the morning. Even when the machine is standing still, only ignition on and you are activating those solenoids, it can be that you can activate those 50 times without problem and then suddenly the next activation gives you the fault codes.

We have replaced that XC43 with the other one installed in the same machine, still giving the fault codes. The original XC43 didn't give any fault codes when installed to another location. We have checked and measured all the wires, not shorted to the ground or to each others. Measured the coils, everyone has the correct resistance. Replaced all the diodes at the solenoids' connectors, no change. We have dozens of machines with exactly same construction and none of those are having the similar problem.

Any ideas how we should proceed with the troubleshooting? Thanks!

0
Answered

Molex Connector part numbers

Doug Coutlee 6 months ago updated by Gustav Widén (System support) 3 months ago 1

Molex has indicated that the MX123 connector series are scheduled for end of life. These connectors are used on all of the MC4 and XC4 series modules. Does Parker have any information on potential future compatible replacement parts?

Answer

The supplier have decided to change part numbers on all of their harness connectors used in the MX123 connector family due to an improvement in Wire Dress Cover retention. The replacements have no change in form, fit or function.

This will affect following parts that we recommend using for IQAN-_C4_ family and also the IQAN-MD5 family:

Part numbers change:

IQAN-_C4_:

66-P connector 34822-0013 -> 216741-0001
73-P connector 34566-0103 -> 216739-0001

Dress cover       34565-0003 -> 34565-0005

IQAN-MD5:

56-P connector 34576-0703 -> 216742-0001
56-P connector 34576-1903 -> 216742-0007

Dress cover       34575-0003 -> 34575-0005

We will update our documentation to reflect this change.