From time to time on various pieces of our MDL2 equipped machines, we'll get get an "Overload" error on a COUT channel.
The COUT channel connects directly to a 350-650 mA valve solenoid that runs an engine cooling fan.
What exactly does "overload" mean in this context? If a COUT channel is basically a PWM output with current monitoring, how can the controller ever overload the output?
What are the specifics that the controller looks for to register an overload error on a COUT?
I'm in the process of upgrading a number systems using MDL2 modules and intend on using a MD4/XA2 combination in its place. Since this upgrade is largely due to the obsolescence of the MDL2 units I am concerned about the product line expected lifetime for the MD4s and XA2s. I remember that the MDL2s appeared to become obsolete rather suddenly, so are there any plans to make today's MD4 or XA2 modules obsolete in the next 5 years? 10 years? How would we find out when/if this status changes in the future?
Would it be possible for the IQAN patform software to be made high DPI aware by the Universal Windows Platform compatibility? At the moment, IQANdesign, IQANrun etc. scale incorrectly on multiple monitors setup.
I'm designing an IQAN program to control the test stand at my company. We have a set of seven types of valves that we will actuate using Deutsche Connectors attached to the sections, and potentiometers varying the output. The different valves that we will be testing require different PWM frequencies, so I went into the COut dropdown window and found the PWM Frequency property, which has a range of acceptable integer values from 25 to 335.
I wanted give the user the ability to select which valve was being used at the time, and change the frequency of COut, so that any deutsche connector could be used for any any valve. I started creating a nested set of timers to simulate a PWM duty cycle, but eventually I dropped it and settled for dedicated output ports for each valve, on the grounds that the better functionality wasn't significant enough to warrant the investment of time and energy.
However, the improvement would take almost no time or energy if I could simply set the PWM frequency of the COut pins to the value of a variable, rather than a constant. I can see no reason why this should not be possible, and it would make ideas like this one easier to implement.
It would be nice to be able to set some kind of power saving/idle mode for a module.
Meaning it could be in power saving mode with a very low cycle time and inactivated I/O's, waiting for a trigger event.
In our application this could be used as for e.g. a diesel heater timer. Then we could integrate the diesel heater to the iqan display.
Customer support service by UserEcho