Hello,

I need to drive relays on low side outputs on the XC-23 and MD4-5.  Do I need to use relays with included coil protection diodes or if the outputs of these modules are already internally protected ?

Thanks,

Guillaume

Hello,

I'm wandering if I could use two(2) or more low side outputs in parallel on the XC-23 to increase the carrying current capacity from 300mA to 600mA (2 outputs) or more.  I have a relay that I need to drive that needs more than 300mA.

Thanks,

Guillaume

I have a project that uses one MD3 and one XC10. The XC10 sits on its on Expansion Bus CAN line with no other devices except for the MD3. Occasionally, during startup the XC10 will report multiple address.

Currently we tell the customer to power cycle the machine if this comes up and it typically goes away. I am looking into automating this if possible. I have tried a few things and have not had any luck. Is there a way to do a forced reset either on the MD3 and/or XC10 to try and reset the error?

Right now, the XC10's V+ supply is behind a relay so I can cycle it power directly. Testing this method has also not panned out.

MD3 cycle time is at 10ms. I read on a different forum post that the XC10 can only go down to 20ms. Ideally, I want to keep the cycle time as low as possible because of how the machine operates. Would going to 20ms help with the multiple address issue?

Are there any othe XC10 limitations I should know about?

Is there anything else I can experiment with to try and resolve the multiple address without the user’s input?

Why do the XA2 and XC10 manuals call for adding clamping (flyback) diodes to digital outputs?

From what I can gather, the modules are equipped with their own internal clamping diodes. Why would those be disabled for digital outputs?

Thanks

Would any problems arise from supplying Parker Pulsar valves with a digital out signal instead of a PWM signal if proportionality is not desired? We're using an XA2.

Would a clamping diode be necessary in this configuration?

Why must a PWM output be wired as shown below in the XA2 manual?

When I've worked with mobile style PLC's in the past: It's just 1 pin for an output that delivers a PWM signal to a solenoid, then the other pole of the solenoid is wired to a common ground.

Why must there be three pins involved for this? Why shouldn't you wire one pole of the solenoids to a common ground (same potential as battery negative)?

Thanks in advance.

I have encountered a problem with DOUT on XA2 modules. We operate several Parker D1VW (NG6) valve, with multiple XA2 modules. Some DOUT (from different XA2) does not activate the magnet coil, although it looks completely correct when I'm connected to IQAN Design . DOUT = Tru.

We use valve contacts with zener diodes, it works on most DOUT otherwise. I had to change the output to PWM instead and then it works without a problem. Is there any problem with the XA2 modules, or are the Zener diodes that do not work against XA2?

Due to a voltage drop in the system, because of an electric fan switching on, all the voltage inputs give a low error.

The strange thing is that the voltage drop is not so big. it drops from 27 to 22 for only a sec due to the high start current of the fan.

Is this normal, I thought the modules could be used in 12 VDC system also. So the voltage drop should not be a problem.

regards,

Ed

We have a system with MD4 connected by master bus to MC3. We have a XC23 connected to the MC3 via expansion on different bus to master.

On ignition switch on the system appears fine and all outputs and inputs into XC23 are OK, during engine start there appears to be a dip in voltage which causes the XC23 module to show 3 red, 1 amber LED flash (can error / timeout). When we get this error flash, IQAN run says system health is OK under the XC23 and MC3 modules and IQAN design shows the outputs on XC23 going true and false as expected. XC23 module outputs however are non functional, the module is in error state and refusing to operate outputs whilst the LED flash sequence above is active.

There are no logs in the MC3 for failed communication with XC23.

Are there any recommendations for how to resolve this? Is this normal behaviour for a dip in voltage on XC23? All other modules appear to be unaffected by voltage dip, its almost as if XC23 does not recover and outputs are non functional even though IQAN design thinks they are? Would pulsing 'enable' property just after engine start re-enable the module in event of this error flash?

Running IQAN Design 4.07 with machine voltage 24V dipping to around 10/12V on startup.

We are having issues with a system that has 2 XC10's on the same expansion bus. This is the first system we used multiple XC10's and have been having issues since we got it online.The XC10's expansion bus is connected to a MC43.

Changing different settings seems to have some affect but I feel like no matter how we change settings this issue is still around it just might not popup as much.

We either get a multiple address error or a no contact error. When we get the no contact error if we look online the device is working however any outputs that were active are faulted and we need to cycle them to get it going. This seems normal for a no contact issue. We see these errors on startup and occasionally while running.

Here are settings I changed. When I changed them I cycle power 25 times to try to gauge where we need things set. The settings I played with are the MC43 cycle time, expansion bus divider, delaying and staggering the 'Enable' for the XC10's. And I recorded the occurrences of each message.

There is a pattern but I'm having a hard time decided where to set things. We currently have the system set with settings that didn't give us problems during the test, but during further testing we occasional see them.

20 ms MC43 

Expansion bus divider =  2(40mS)

Cycle util = 11% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000               

0 - No Contacts     

0 - XC10 Multiple addresses

10 ms MC43 

Expansion bus divider =  2(20mS) 

cycle util = 21% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

2 - XC10 -Multiple addresses

10 ms MC43 

Expansion bus divider =  2(20mS) 

cycle util = 21% 

XC10[0] Enable delay = 5000 

XC10[1] Enable delay = 0000             

0 - No Contacts     

2 - XC10 -Multiple addresses

10 ms MC43 

Expansion bus divider =  9(90mS) 

cycle util = 21% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

0 - XC10 -Multiple addresses

 5 ms MC43 

Expansion bus divider =  2(10mS) 

cycle util = 41% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

4 - XC10 -Multiple addresses

 5 ms MC43 

Expansion bus divider =  2(10mS) 

cycle util = 41% 

XC10[0] Enable delay = 5000 

XC10[1] Enable delay = 0000               

0 - No Contacts     

3 - XC10 -Multiple addresses

  5 ms MC43 

Expansion bus divider = 10(50mS) , 

cycle util = 41%  

XC10[0] Enable delay = 0000  

XC10[1] Enable delay = 0000                

1(1) - No Contacts     

0 - XC10 -Multiple addresses

5 ms MC43 

Expansion bus divider = 10(50mS) 

cycle util = 41% 

XC10[0] Enable delay = 4000 

XC10[1] Enable delay = 8000                

1(1)  - No Contacts     

0 - XC10 -Multiple addresses