I am still unable to reply to previous posts with the same error being reported as before when I attempt.. 

In reply to Gustav's comment on this post: XC44 HS+LS Overcurrent Follow Up / Hardware / IQAN

"Ok, the disabling of the function group explain at least a part of the behavior you see.

When disabling the FG, the DOUT deactivate. Diagnostics is still running, so when disabled all checks for output off are running. In IQANdesign you will only see channel status disabled though.

At what events do you disable? Only before cutting the highside externaly?

Or also during normal deactivation of the output?"

The function group is only disabled on Estop. Before an estop event the output functioned as normal, the estop being triggered starts the overcurrent issue. 

Original post: XC44 HS+LS Overcurrent / Hardware / IQAN

What is the XC43 COUT open load threshold when the COUT is off?

I'm having an issue where the PWM outputs jump in voltage to battery voltage seemingly randomly and with no change in the displayed output on IQAN run. Anyone know what is going on?

We had a XC42 where we use a hall effect analog device that was mapped to pin 8 and configured as an analog input. The device was connected to Vref A so uses a supply voltage of +5v and provides 0.5-4.5v thru 180 deg of rotation. We first started to see it only indicating from 2.5-4.5v and then eventually we got fixed values that fluctuated based on if the hall effect magnet was present or not. After some trouble shooting we removed the wire from pin at a connector and were getting a fixed voltage of around 4v at pin 8. With this removed the magnet rotated gave us 0.5-4.5v at the output of the sensor.

A data sheet of the sensor is attached. Model # is RTP180LVNAA

We ended up remapping the input to pin 52 and it all worked fine again.

It almost seems like the pull up resistor in the channel was "turned on"???Honeywell RTP Sensor

I've noticed that the following XC43 pins appear inaccessible via IQANdesign:

C1:61

C1:62

C1:63

C1:64

C2:69

C2:70

C2:71

C2:72

Is this by design or am I missing something? They're listed as PWMOUTs or High Side DOUTs in the manual.

IQANdesign 6.04.5.5888

I have not checked the other XC4x modules.

Working on a project in which 2 XC43 modules are not supplied with power until the MD4 commands a safety relay contactor closed.

I've worked through almost all the bugs, but I'm getting a VREF A error as soon as the XC43 modules enable. I've tried leaving up to a 30 second delay after powering the XC43 modules to enable them, but the error still pops up for one cycle and then shows up on screen (Watching in a measure group, VREF starts at 0V for one or so cycles, then goes right to 5V). All the sensors read fine, just have the error at system start.

Is there any way to delay how long it takes for the VREF error to show

On the XC4x serie there are multiple Vref+ and Vref- and on both C1 and C2 

Are these interaly connected in the module? 

Or are they seperate from eachother and serve only dedicated Vin's?

Best Regards Ed

I'm using the expansion module XC43 to control valves, usually, I use Cout to control proportional valves but I run out of current output pins " I have 13 valves" I'm wondering if I can use PWM OUT HS to control D1FBE01HC0NJJ3 " Proportional directional valves in general " also L90LS, P70? Because it seems for me that PWM is only to control pulsar valves that have some frequency working value.  

Our usual setup is an MD4 with an XC4X expansion module. But we end up using an MC4X because we need the CANBus available on the master module. It would be nice if the expansion module provided access to additional CANBus the same way it provides access to its IO.