Your comments

I think that I found the reason for your problem. To improve performance when getting a clone IQANrun stores some resources in a cache. For example your cache may contain an exact copy of the images of the MD4. The problem is that the module address is not checked when determining if the cache version can be used. So when IQANrun is assembling the clone file it discovers that the module address of the image data differs and displays an error message that is bit cryptic.


You should be able to resolve this by clearing the cache. Empty the folder "C:\ProgramData\IQANrun 4\Firmware Cache" and try getting the clone again.


You're right, this error was introduced in IQANdesign 4.04. It will be solved in the next IQANdesign version (4.05) which is planned for released in the end of next week.

Q1: The format of the excel sheet is quite free. As a minimum it needs a column for SPN number and SPN name. This is used to create SPN channels. It may also contain a column for FMI and FMI names.

Once a file is selected a dialog is shown where you can select the columns to import. Header columns are ignored and the import starts with the first row that has a numeric value in the SPN column. The values that will be imported are highlighted in the import dialog.


The input field is initialized with the default value only the first time it is executed. The reason for this is to be able to go back in the script using the back button and keep the value. But as you have noticed the effect will also be that the value is kept when using a loop.


There is one way that the value could be cleared, but it will clear the value of all script actions. By using the script action "Clear script state" in the beginning of each loop everything will be reset. Depending on the script this may be acceptable or not.

What communication interface are you using? If you are using CAN, try to disconnect and connect the CAN adapter from the computer.


Does the MD3 seem to start as it should? You can try to start it in "safe mode" by holding the back button on the MD3 while switching on power. This will start the MD3 without loading the application.

Hi Kimmo,

If you don't have a 3.x version of IQANdesign, you can find these versions of IQANdesign here (follow the link in the bottom of the page for older versions and download the IQAN Creative Studio): http://divapps.parker.com/divapps/iqan/IQANstudios.html



Thanks for the files and description. Now I could reproduce it as well. It is probably related to that the "_" is also used to wrap a line in Qcode, i.e. if you want to continue the expression on the next line you can use the "_".


When you start writing the name of a channel containing "_" you can select it from the autocomplete list instead of typing the "_". Then it will be inserted correctly. Of course we have to solve this issue in the next IQANdesign version (I have added it as case 33064 in our issue tracking system).

We are not able to reproduce this error and have not seen it during our testing. Would it be possible to send the 4.02 project file to us so that we can investigate the reason for this? If you don't want to share your complete project, maybe you could export one of the function groups or channels with this problem from 4.02.


You can send the file using this link: https://iqan.sharefile.com/filedrop

It seems that comments that have a name show up in the auto-complete drop down menu. However if a comment is selected there will be a component mismatch error so the Qcode is not valid and cannot be sent to a master.


I have added this as a bug report so the comments will be filtered out in a future version.

When starting Ethernet communication the IQAN software begins with discovering modules on the same network. For this UDP port 8324 is used. The result is shown in the Ethernet connection dialog.


When selecting one of the discovered master modules UDP port 8325 is used to communicate with the module.


If you want to communicate with a master module that is not connected to the same router as your computer it will not show up as a discovered module. In this case you have to know the IP address of the master module and use the "Static modules" tab of the Ethernet connection dialog instead. When connecting to a master module using this way we use TCP on port 8323 instead. This makes it easier and more reliable to e.g. connect over a VPN connection. Note that this connection is considered to be a remote connection and will by default trigger a confirmation message on the MD4 before connecting.