Your comments

The PWM out channel has value type Integer and unit %, so for monitoring the commanded pulse with the resolution is limited.

Also, the Min MR and Max MR are set as integer values in percentage.

But the value type on the input channel is real, and the result you get after scaling is the actual pulse width resolution specified in the instruction book appendix A , this is a much better resolution, see for example IQAN-MC3 or IQAN-MC43.

Here in the case of the IQAN-MC3, the PWMOUT resolution is specified as 1 microsecond.


The question was posted as a private ticket, but since it is a very general question and the printscreen is just an example I took the liberty of moving it to the public portion of the forum, I hope you don't mind.

Another comment is that for the IQAN-MC3, there are very few reasons to configure the output as open control PWM, for this module it is almost always better to configure the pins as COUT.

No, the IQAN-MD3 has limited hardware resources and runs a very compact firmware, it does not have the capacity to show pdf files.

To view pdf files on the master display, you will need to use the IQAN-MD4.

What you can do is to use the result from the IMGS channel to trigger the MD4 display page external button controls, this will let you enter the main menu in the menu system. See attached example

IMSG button to menu.ids4

But there is no shortcut to bring up individual adjust items from this part of the application, that could be a good feature addition.

The output error detection differs between different IQAN modules.

All modules have some protection for overload situations like short to ground on the output, but It is not all modules that have diagnostics reporting of this error, and not all modules have detection in the off state.

IQAN-MC3 is a module that can detect SCG of the highside when the PWM out is off. But it has had this since the module was introduced in 2.50, and there is very little reason to use an MC3 output as open PWM instead of COUT.

What type of module is this happening on? The IQAN-XC10? It has PWM outputs with various diagnostic reporting of faults when the output is on, but should not be reporting this when the module is off.

One possibility is that the overload occurred when the output was on. The output remains in the error status until it has had a zero command and then gets activated again.

But this does not really match the symptom you are describing, that you had to get to 90% duty cycle before the error went away.

We have not scheduled any functional safety training for 2017 yet, but if there is more interest I am sure it can be arranged.

(next scheduled training in Sweden is IQAN Creative Studio 4, held on the 21st -23rd of March)

That is right, with current version there is no way of forcing the keypad to appear when triggering the showing function on the PCC.

I think that some method of forcing the keypad style dialog to appear could be a useful addition, it seems to be quite common to use a function to trigger the PCC dialog, so there are probably other users who would like to see this feature also.

Good to hear that the small angle approximation worked here.

Just to clarify the resolution for the sin() function for anyone else, this is the description in the IQANdesign user manual:

Operand resolution for trigonometric operators is at least 0.1°.

Result resolution is at least 3 decimals.

The keypad style is actually used also when the PIN code is implemented using the PCC channel.

The tricky thing is that there is no property to control if the spinner or the keypad shows up, instead this is selected automatically based on the last input.

If there was an external button control activating the PIN (as it would have to be on e.g. an MD4-5-T0), then the spinner shows up, if there was a touch input, one instead gets the keypad.

In the attached application, one touch button is assigned to open a PCC protected adjust item directly, this gives the result that the keypad is seen.

PIN code example PCC from display page.ids4

Another button triggers a VDIN that in turn s used in the PCC channel function. When the PCC is triggered by its own function, it has no way to know that the showing action was the result of a touch input. We chose the spinner as that works both with external button control and the touch interface.

To force the keypad to show up when it is the PCC function triggering it, a new property or perhaps a variant of the Qshow function that takes this as an argument would be needed.

A coil for a hydraulic valve is an inductive load, so it would not have an inrush current in the same way as e.g. an incandescent light bulb.

I believe it is the other reason, that the output is being cycled on and off. The XC10 does not have nearly as accurate current measurement as the IQAN modules that have COUT:s, e.g. the XA2 or MC43.

To compensate for this limitation in current measurement, the XC10 has been designed with a much longer detection delay, about one second. Normally this should reduce the chances of having a false error, but I am guessing that the rapid change in command interferes with the detection in this case.

The IQAN-XC10 has properties for disabling under current reporting when the output is on (would be seen as open load), but it is not possible to switch off the error detection for over current.