I have an application where I want to send text strings over CAN on a very occasional basis. A tool for handling extended outgoing CAN frames for this task would be very useful.

Please include an auto ASCII converter in the tool.

Part four of the IQANdesign tutorial is now available, this one is introducing some of the Qcode sytax:

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.

With the recent obsolescence of the MD4 modules, will the MD5 modules be able to be used as the sole master module and control machine functions in conjunction with expansion modules?

What are the risks of using the MD5 with expansion modules (XC43, LC5, XC23, etc.) to control machine functions without additional master modules?

I know another post implied that the main concern with not using the MD5 to control machine functions was the slower cycle time, but it appears that issue has somewhat been fixed with the lower minimum cycle time now listed at 20ms for the MD5. Is that no longer or less of a concern now?

We have had many bad experiences with multi-master systems, so I would like to avoid going back to an MC43 module, if at all possible. We've been using the MD4 modules with XC43 modules to control machine functions with very good success with a cycle time of 50ms, so the cycle time would not be an issue for us unless there are other limitations of the MD5 that make it unreliable for machine function control.

IQANdesign lets me use the MD5 as a direct replacement for the MD4 modules without any warnings about not using it in conjunction with expansion modules to control machine functions.

Hello,

I recently migrated to 7.05 IQAN suite from the 6 version. I noticed that the ability to export logs into XML has been removed. I just completed an automatic data load process that uses XML. I chose XML because it provided more metadata around which machine and when the information was being pulled. Can we get this functionality reinstated?

When connecting with IQANGo (or using remote assistance) by Bluetooth, the Machine ID is not showig in the machine list below "Select a machine..." menu. Only "Unknown", or "IQAN-G12" and a hexadecimal(?) code is showing for all machines. When there are multiple machines within Bluetooth range, this is very annoying. The Machine ID is only shown after tapping connect button. Same situation before/after pairing, or connecting to the same machine again. MD4-7 / MC43FS multi master system, IQAN G12 BT module.

IQAN design 4 had the feature of being able to right mouse click scroll to zoom in/out on the Qcode. This feature has disappeared with IQAN design 6 and 7. Was this an intentional deprecation?

Having the zoom feature on the channels is nice, but I do miss the Qcode zoom. Also running into an issue with using a laptop and additional monitors where it seems the resolution from the laptop is being applied to the Qcode on the additional monitor.  Additional monitor has higher resolution so my Qcode appears very small and I can't zoom in on it.
If I close the laptop and only use the additional monitors and open Design. The Qcode appears larger and this resolution is maintained when I open the laptop.