IQAN-G11 is now available to order. In combination with the IQANsync app and IQANconnect service this offers a very cost efficient remote diagnostic solution.

Detailed IQAN-G11 information available at: http://ph.parker.com/us/17616/en/iqan-g11-bluetooth-adapter

IQANsync app available for both iOS and android. Links to apps from http://www.iqan.se/store/ click on IQANsync

IQANconnect connections can be purchased from http://www.iqan.se/store/ click on IQANconnect.

User manual for IQANsync / IQANconnect:

User Manual IQANsync and IQAN-G11 HY33-8416-UM_UK.pdf

Is there any development in an (for example) LSL jostick with full detend/latching

So that the joystick stays in position.

We've had a couple occasions where this would be a great solution.

Marking MC/XC modules

is it possible to mark the modules with the type on the connector side.

if the module is mounted its not possible to see wich one it is

The new -M24 versions are now in serial production:

See updated catalogs:

IQAN-MC4x_brochure_HY33-8413-UK.pdf

IQAN-XC4x_brochure_MSG17-8417-UK.pdf

Requires IQANdesign version 7.03, see Version 7.03 released / Software / IQAN

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

The electrical diagrams for the MD5 that are published on the Parker website have an error, the +batt and -batt are reversed on those drawings. The MD5 instruction book is correct.

An MC4x evaluation board is now available to order, part number 20085169.

This board is meant to be used with all the MC4x units and will connect to C1.

It has all the I/O for C1 connector and can be used for testing everything on MC41 and MC42 and all I/O for C1 on MC43.

The kit includes the board and test cables.

i need more output io

but it looks like a big tear up

Has anyone had any success controlling valves that specify a low dither frequency below 71Hz with the XC4x current outputs?

We have a machine that is using a HAWE valve that specifies a dither frequency of 40-70Hz with 55Hz recommended. It also gives a range of dither amplitude of 20%-50%. The minimum frequency of the Cout channels on the XC4x modules is 71Hz. I'm sure 1Hz is not going to make a big difference if we set the frequency to 71Hz, but just wanted to see if anyone has had any similar experience or other recommendations. Just trying to avoid any possible stiction/hysteresis/chattering issues.