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.

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.  

An XC43 sent a COUT error to the MD4 display, which is the master module in the CAN bus network. However, the error was not logged in the MD4 log. Any idea why this might be happening?

Hi,

I want to create an External Function that will contain a JFIN. 
When I will import the External Function, I would like to be able to vary the PGN property of the JFIN.
At the moment, it seems that the PGN property of the JFIN can only accept integer number, it cannot accept an integer coming from a channel.
If I insert the External Function in my project, I will not be able to change the PGN property of the JFIN because it will be locked. And I do not want to change it to the same PGN value for all the occurences of the External Function.
I would like the PGN to be a FGI to the External Function.

My use case is that I want to control Hawe PSx CAN valves where they have a different PGN for each valve section. It would be neatly integrated inside an External Function so I could reuse it for all the different valve sections I have in my project.

Any workaround?

Thank you and have a good day!

Description

Hi,

I would like to ask about the best way to update a program on a machine that already has an existing IQAN application installed, especially in cases where some parameters have been modified from their default values.

If we upload a new program with the same project ID:

• Will it overwrite the existing settings (i.e., reset parameters to default)?
• Or will the current parameter values be preserved?

I want to make sure we avoid unintentionally resetting user-defined or tuned parameters during an update.

Thanks in advance!