Will the XC43 (when paired with the MC43FS) inputs to be allowed for use in Functional Safety Marked Function Groups in a future version of IqanDesign?

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.

Say you have a brand new XC43. The firmware installed from factory is 1.0 (I think). How many times will the firmware update before reaching the current version of 1.03?

Also, the XC4x SIC module status lists a value of 140 as Firmware update. From the documentation that means the firmware update failed. Are there any other status values pertaining to the firmware? 

What are the different values possible in the system info "InternalState" and is this channel accessible in the project?

We are experiencing a problem with the HS+LS outputs on an XC44 module connected to an MC43 as the master running IQAN 6.07. Pin C1:46 as the HS and pin C1:41 as the LS.

The outputs are being used to activate a solenoid. The circuit was wired to run through a relay latched by system estop, with a diode placed across the solenoid to protect the outputs as in the documentation.

This circuit is able to latch and unlatch the solenoid with no problems, and this was repeatable many times. However when the system estop is pressed for the first time and the relay unlatches and breaks the circuit there is no error. When the relay is energized and the circuit is connected again, when the output is turned on a message is displayed reporting that the LS pin is overloaded. This message then triggers on either side of the estop from that point on. Key cycle is able to "reset" to the first estop cycle. This behavior happened ~9/10 times the cycle was repeated. There were some occasions where the error did not trigger.

The overcurrent error will only trigger when the output is requested, the estop relay can be re-energized connecting the circuit and no overcurrent is reported. 

Current measurements were taken on the HS+LS wire to investigate. The current on this wire never approaches or exceeds the listed 2.5A. This is the only load on that pin grouping, the other 3 LS pins were not used.

 Current_results.pdf

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,

Where can I read about when to use terminated address tag or not? E.g. 0T and 0 tag? When prototyping discrete resistors may be useful but will it work with just a resistor of correct value? Please advise.

Hello,

I have an odd issue, maybe power or ground reference related.

XC43 IQAN 6.08, sensors powered using the main 24VDC not regulated VREF.

When I start driving valves with the module the reported voltage from my VIN sensors drops by up to 5%.

It happens to all of them irrespective of the sensor type.

It also jumps around a ton.

This makes a huge difference on my 0-5800 0.5-4.5V sensors.

200+ PSI, not good for sensor accuracy.

Any ideas of what to try to fix?

Regards,

I am working with a couple customers who are having "No Contact" Issues with XC43s installed to replace XA2s. 

When looking at the XC43 module itself, the error code is 1:2 (one red, 2 yellows).

I'm assuming the module is getting an errant input somewhere which is causing it to shut itself down.

I would like to better understand this error code better.  What causes an input error and under what circumstances does it cause the module to stop communicating with the master.

Good morning, we have had a problem with an XC44 expansion module, when we connect more than 5 solenoid valves to the DOUT-(HS) outputs, during the initialisation process, the module is protected and goes into state: SSP (Safe Shutdown Path) with the blink code: R4:2 1:1:1.

The electrical installation has been checked several times and everything is OK and all the clamp diodes are installed properly.

If we start with the solenoids disconnected and when the initialisation process has passed we connect them, everything works correctly.

We have tried to replace the module and it didn't work either.

We have finally had to add several relays to control the solenoids so that the module starts correctly, but this solution involves a lot of tedious extra work.

How do I upgrade the firmware for my xc42?