Your comments

The enabling of error checking on the VIN works in the same way as the outputs, it is only active when the channel is evaluated. You can use the same desing that Frank suggests for the outputs, by moving the VIN to a function group that can be enabled/disabled, you can disable the the VIN:s. When the VIN is disabled, it will have the value defined on the property error value.

In the example files that comes with IQANdesign, the Fork Lift examples shows how parameters can be used to enable/disable optional functions.

It depends on how high above 2.5A you are going.

The XC10 high-side DOUT:s are protected against both short to ground and over current.

If the DOUT is shorted to ground, it will switch off more or less instantly.

It the DOUT is overloaded, there is also an over-current protection. For the XC10 this protection is parts thermal, so it is difficult to know exactly when the output will switch off.

One thing to consider is that even the 2.5 A maximum current on the XC10 DOUT:s may be too high, if several adjacent DOUT:s are running 2.5 A each, that may be overheating the module too.

Is it ok if I move this ticket to the public part of the forum so that others can see it?

The question was posted as a private helpdesk ticket, do you mind if I move it to the public portion of the forum for a more open discussion?

When searching with Ctrl+F, have you tried using the F3 shortcut for Find again?

It does not present a list like you are asking for, but it jumps to the next component matching the search

One other aspect to consider is when sending a clone to a blank module, when the master module is empty it does not have any security levels yet, and it is not possible to log in. To send a clone in that case;

1. send the clone

2. log in at the correct access level

3. send the same clone again

As Ulrik and Kerry both mentioned, settings that the logged in user does not have access to will not be updated. One solution for this that has been discussed is to have a security level for "unrestricted clone", similar to the way there is a security level for send settings.

If the technician on site performing the send clone operations needs a higher access level, a workaround could be to embed the clone in a script file that does the login and the send clone operation.

Thank you for the feedback Eric, going with external terminations and configuring all IQAN modules to not use the internal termination could be a good option if one wants to have the option to check the terminations with the classic method of measuring resistance.

One possible drawback I can think of is when loading the software in a multi master system for the first time, on the production line. Before the master modules have an application, they will default terminate; so when adding a pair of external resistors in addition to this there might be too much load (depending on number of master modules).

As soon as the IQAN masters have had applications loaded in them, they have the properties for terminate yes/no from the last application saved, and will start up with this setting.

I am not sure, but I believe the following could have happened:

When you added the ISO image, you were probably using the quick method of going via the drop-down menu.

This method is quick, but it has the drawback that only one image per ISO symbol is added to the project file, and that there is no place where you can view and replace this image (other than looking at the image control using it).

If you then add the same ISO symbol in another display control using the same method, the original image will be replaced. If this new one happened to have properties making it invisible, e.g. the same color as the background, this would affect also the first image control. One does not see this immediately, the project file has to be closed and open to see the effect on the original ISO symbol.

An alternative approach that avoids this problem is to add the ISO 7000 symbols via an image group. That gives one image for each size and color variant you add to the project file.

I downloaded the application and tried it, and I can see what you mean. With the Line graph configured as scroll mode, the slider is not keeping up with the movement of the finger, it updates in steps.

With the line graph configured in scroll mode, the entire area of the line graph is redrawn continuously.

With the line graph configured in sweep mode, there are only the pixels at the sweep that needs to be redrawn, so this is much more efficient.

i saw the MD4 application was configured to run at 10 ms, so I tried setting it to 50 ms. In this small example it had no noticeable effect on the performance of the graphics, but in a full machine control application, the combination of cycle time and cycle utilzation for the application will impact the update rate on the graphics.