I recently ran into a scenario where I could not update the firmware on a module because my project file was IQAN 7.06 and the module was 7.04. The Module needed to be updated to 7.05 before it could be updated to 7.06.

This has never been an issue for me in the past. Usually the latest firmware would always load without having to load the intermediate firmwares. I simply created a blank project with the masters in the system at 7.05 and loaded it to 7.05, then loaded the project to 7.06. However this problem becomes much more difficult when issuing program changes to the field. I never released software to the field with 7.05, so the service technicians won't be able to update a system in this scenario.

I looked around in IQANRun and I didn't see any way to update the modules without a project file. Is there any way this can be done?

We need to implement a push button with a dual function, 

To achieve that, we would like to sense short press, long press, and the double or triple press of the push button,

Kindly let me know how to configure a push button in such a way

I'm using a CIN input to monitor a 4-20 mA signal. I have the Calibration set to {4000; 15000; 0; 137.5} Per the manual, the Error Value should result at the 'Illegal Value' point. For a Low Error, this occurs at 2 mA as expected. I assumed the Max input value to be 20 mA, and my Max value is set to 15 mA. The halfway point between them is 17.5 mA. For some reason the High Error condition is not happening. Am I using the wrong signal max value of 20 mA? If so, what should that value be?

In contrast, the Low and High Error points for a VIN are working exactly as expected when using a Vin Max of 5 Vdc.

I've found this to be true for both IQANsimulate and the actual hardware.

I'm using an MC43FS and IQANdesign 7.06.22.11482.

Is there a way to change values in adjust groups that are protected by user logins from iQAN Design after logging into the module using Design? I would have figured that once you logged in with Design (or Run) that the adjust group would appear in the system menu of the display module.

I'm working with Design 7.06 on a MD5.

When using the open with context menu option in windows explorer on an iQAN project file, iQAN Run opens, but it does not open the actual project file for viewing. You still have to open the project file using the open button in iQAN Run.

If I export an image group in iQAN 7.06.22, any images with a period in there name in iQAN will export without the period and anyting that follows the period. It does not matter if what follows is text or numbers.

Example: Image named "test-circle-5.2" will export as "test-circle-5"

The customer encountered a strange problem, they use the MEM channel to accumulate the total mileage. The system uses MD5 and MC43FS controllers, and the programs are also separate. The customer uses the same algorithm to perform operations in two separate controllers. In MD5, everything is normal and the total accumulated mileage has been increasing all the time. However, in MC43FS, once the values accumulate to 2048km, they will no longer increase. I use the IQANsimulate to monitor that MC43FS can also break through 2048km. 

The difference between the two programs lies in their different Cycle time. MD5 is 50ms, MC43FS is 10ms.

What could be the reasons for this problem?

Is there any intention of being able to convert text project files into Standard Project files? Or even better opening from a text file.

Saving a project file as a text file allows for revision control and diffs. Also this could allow for LLM assisted coding and troubleshooting.  

IQANrun does not limit output to minimum value when field is selected. When selecting a COUT to adjust the minimum, it states that the output is being limited to the minimum value, yet it is not limited. We have found a workaround by pressing "+" or "-" to change the set value first, then it will hold the minimum with full joystick throw. Previous versions did not have this problem. Up until we found this workaround, it became extremely difficult to set minimums properly. The only way was to use the maximum field to figure out the minimum, then copy it into the minimum field.