Not a bug

IQANrun's imposed COUT limitation when adjusting Min current remains on controller after lost connection.

Johan Palm 11 months ago in IQANrun updated by Gustav Widén (System support) 10 months ago 1

When adjusting the minimum output current of a COUT, IQANrun imposes a limitation on the COUT equal to the set minimum current.

If the controller drops the application, without a graceful disconnect, e.g. if you do not first disconnect IQANrun before you connect with IQANdesign, then the imposed limitation on the COUT remains. This can cause a lot of confusion if you are unaware of this functionality.

It would be preferable if a dropped connection immediately removes the current limitation on the COUT.

Not a bug

I can confirm that this is how the min-current limitation works, it stays effective also if connection is lost.

It is not a bug, staying with the limitation is in our opinion the most predictable choice of action in case of an error. A realistic scenario could for example be if the diagnostic CAN bus is cut wile adjusting.

I think the main point that is good to be aware of is that there can only have one diagnostic session running at a time. 

If you are connected with IQANrun and for example start a measurement in IQANdesign, IQANrun is abruptly disconnected.