Hi, release 4 of your dev environment adds IQAN connect as a communication service. This is very interesting as an alternative to Proemion. Where can I find more info on this service (how to register, cost, etc)?

Thanks!

Hi

I use a GPS (GARMIN 1020xs) on my product, for this function http://forum.iqan.se/topic/1063339-backlight-auto-adjuste/ I need to know the real time. By using the NMEA (= Canbus), I can read the GPS time, but it is impossible to change the time of IQAN master.

What do you think about this function ?

PS : there are a time synchronisation with the modem ? (cellular operation give time to a cellphone).

Regards

Would it be possible to add an extra drop down box to easily switch the logic block type? When sending safety signals between modules, I often copy and paste the APP OUT into the new module so i know what names I have used as the property name. This saves time when switching back to the other module application to see what the names are.

It would be much easier if I could copy the APP OUT and simply change them all to APP IN rather than having to create new APP IN's and insert the names into each one?

Could have a drop down box on every logic block type to change to any type of function? whether it be I/O / calculation / misc / interface etc?

There are many applications that require a variation in units. Currently if I want to display a pressure gauge, I would need to create a PSI pressure gauge, and a BAR pressure gauge. Then control the visibility properties of the gauge to display the desired gauge.

It would be helpful to tie an integer parameter to the "Min value" and "Max value" of the gauge control or bar control. By doing this it would also be necessary to change the "Tick count" value with an integer parameter. This way the programmer would only need to make one gauge and control the properties inside the "Display application" as opposed to multiple gauges.

Right now, in order for us to make diagnostic pages of inputs and outputs we have to create them manually by linking the outputs of our program to objects on the touchscreen, in small proyects it isn't much of a problem, but when we start to have multiple devices on a single proyect full of inputs and outputs, it starts to get tedious, we lose a lot of time in reviewing those screens to make sure all inputs and outputs are displayed.

As such, i think it would be great if we could have a new subcategory on the menu screen for the MD5 touchscreens were it automatically displayed the inputs and outputs we have configured, with the name that appears on the program aswell as it's value. 

I think this would reduce the probability of human error on the programmer's side, while also saving quite a lot of time in not having to create those pages ourselves.

I know this has probably been asked multiple times over the years, but we really need to have the possibility to downgrade and upgrade devices freely between versions.

With the recent changes on new MD5 HMI screens being shipped with 7.06 firmware from factory, i am now left with a big problem in having two different versions of multiple projects for vehicles currently in production. Which is, putting it mildly, an inconvenience, specially if i ever have to do maintenance on them or have the need for whatever reason to update the project.

I don't want to ask for the possibility to downgrade from the 7.06 firmware to older versions, since the time and money you would spend on developing it is probably not worth the effort. But i would like to humbly ask that moving forward, please, allow the possibility to downgrade and upgrade firmware versions freely from 7.06 onwards on all parker devices.

Thank you.

Lots of field service technicians are confused by the "Incompatible Version. File is too new, please update" message. We include a message in our software release notes if the IQAN Version is updated but the technicians don't always connect the dots that IQANRun needs to be updated when they get this message.

The message text should be improved to avoid confusion. One suggestion is the message could include the IQAN Version of the file they are trying to open and their current IQANRun version.

The message could also tell them to update IQANRun instead of just say "please update".

Can a scaling feature be added to IQANsimulate so that you can see the full display when simulating a portrait MD5-8 or MD5-10 on a standard 1980x1080 monitor? Below is a screen shot of an MD5-8 and MD5-10, both in portrait orientation and the bottom of the display is cut off when simulating.