We are experiencing an issue with several of our MD4-5. The issue is with any button on the MD4 whether they are parker system buttons or programed virtual digital in. Intermittently, the buttons tend to freeze therefore acting like a toggle when they are not. Please see below some points that I've noted.

1. The program is updated to its latest version of 6.05.
2. The cycle time of the MD4 during operation is 30ms.
3. The cycle utilization of the MD4 during operation is 20%.
4. The memory utilization is good.
5. The MD4 is located inside and operating at ambient temperature.

If I send a new simple program to any of these MD4, the issue will go away. I did notice, when I disable a certain amount of function groups within the program, the issue goes away. Therefore, I think its pointing to a program issue, but it seems strange to me because as mentioned above everything looks pretty good. Note: This is a multi-master system where the MD4-5 is the master. Any thoughts?

We are getting Log Errors on one of our machines. We get the same IQAN message 11 times. 1 of the 4 master controllers in our system happens to have 11 logs in it. So I'm assuming that is the culprit. We tried to pull logs from it and it was empty.

Any more info on this message? 

We have this same code running on hundreds of units and this is the only one with this issue. Hardware related ?

I created a safe password for a Login using the new Safe password request file. He loaded the safe password on the other end and the password was added to the password manager, but it did not allow him to login. When he entered the username in the login box it did not populate the password.

I'm a new user of IQANdesign. I mainly work with versions 5 and 6. Is it true that I cannot use the FOR, CASE and WHILE statements in Qcode?

Thanks in advance for your response.

Is there a way to insert comment tags in the interface?

MD4(2),MC43,MC41 - Currently using IQAN 5.04. Is it possible to not have the VREF Error message popup? 

We don't use the VREF's and none of the diagnostic channels are assigned to any of the VREF Channels, yet we still get errors associated with it. It is becoming an issue as machines are being repaired but they are completely functional (minus this nuisance alarm)

Hello,

Got few errors (related to different sensors, Can bus,...) with that blue background behind

Any idea what the background could mean? crash of the display?

usually the errors pop up but the normal/working screen is always at the background, I have not seen that shutdown message behind before

Br

/Adrien

I have two master modules, one on a fixed station and the other one on a mobile vehicle.

They are connected with the DIAG and MASTER busses through a CAN to ethernet adapter.

The ethernet link is then sent over the air using an industrial grade ethernet radio.

When I replace the radio with a cable, I can update the firmware of both masters using IQANDesign (via ethernet or CAN).

And then I remove the cable to run the application. I can connect using ethernet to one of the master and do some measurements using Measure groups.

Unfortunately I cannot update the multi-master firmware over the radio link, even though the radio bandwidth is not an issue (100 Mbps). My guess is this is due to a latency in either the radio link (when connecting using ethernet) or in the CAN to ethernet adapter when connecting with CAN. Is the firmware update procedure could be less strict on latency to allow firmware update in this case ?  

Best regards,

Martin

I have a customer who reported that several of their service engineers complained about the comma not being available in their Iqan go app keyboard.

The comma here should be used as a decimal separator (Dutch) for Real parameters in an adjust group.

Using a dot as a decimal separator yields an error