Text formatting channel padding
There should be a way to set fields in the Text Formatting Channel to have padding with leading 0s. E.g. If set to be padded to 3 digits then 5 would be printed as "005". This is effectively the "Number of Decimals" filed, but in the other direction.
An application would be for a clock formatted string (e.g. for countdowns). currently, 0 hours, 5 minutes, 17 seconds would print as "0:5:7" instead of the desired "00:05:07".
For searching, this may be referred to as Padding, Leading Zeros, Leading 0s, Fixed Length Numbers, Number of Digits, or Significance.
Wireless can bus
Has anyone tried this between Iqan masters, like MD5 <-> MC42?https://www.ifm.com/fi/en/shared/productnews/2023/hmi/canwireless-effective-local-m2m-dialogue
Or is there some other wireless CAN-bus adapter that works in Iqan?
MD5 & MC4x Obsolete Connector
MD5
34576-0703 (Obsolete) - https://www.molex.com/en-us/products/part-detail/345760703
34576-1903 (Not Recommended For New Design = Going to be Obsoleted) - https://www.molex.com/en-us/products/part-detail/345761903
Code H version is also Obsolete. (34576-0803 & 34576-2003)
MC4x
34822-0013 (Not Recommended For New Design = Going to be Obsoleted) - https://www.molex.com/en-us/products/part-detail/348220013
34566-0103 (Obsolete) - https://www.molex.com/en-us/products/part-detail/345660103
Have you guys seen that the connectors that are used on the MD5's & MC4x are Obsolete, or going to become Obsolete soon. What is the long term plan for these connectors, as these were just released? Have you talked with Molex to support these longer?
Just trying to plan ahead, as we mfg harnesses to support these parts. And need to know if I need to buy and stock a lot of these so we don't run into supply issues.
Brief No Contact from 2x MD5 to MC43 on Equipment Start
We have a multi-master setup with MC43 headmaster, MC41, and 2 MD5 displays. On initial power up all modules are communicating normally without error. For a brief moment on engine start both MD5s report no contact to the MC43 and values from the CAN bus stop updating on both displays. First assumption was a voltage drop issue on the MC43 but we scoped power to ground at the MC43 during startup and we are well above the 9V minimum. We also ran a CAN trace on the bus to check for CAN errors but saw no issues there either (no CAN errors reported by anything on the IQAN side either other than the no contact error).
The no contact is transient, it appears to clear up almost immediately. There is no indication of no contact on either the MC43 or MC41 LEDs during this period. LEDs are displaying the normal running pattern. When the displays are frozen all of the control functions still work, but the display does not update to reflect our inputs.
The displays will resume updating values only if we transition to another user-created MD5 page and back. Until we go to another screen it will never resume updating values on the display. So far we have replicated on IQANdesign versions 7.05.19 and 7.05.27. Other than this specific issue everything is operating without problems.
Does anybody have any suggestions on potential causes or tests to narrow down the issue?
log Unknown component
I'm encountering a problem with the downloding of the log files in IQAN run 7.
when I select all log then it shows the component, but after I selected to get all records it will not show the component anymore, and it will only show : "Unknown component"
Before:

After:

Telematics
Telematics signal ID 19 data type real is showing up in our modem data stream as 0 when program is on a functioning machine. If the program is on our test bench that does not have any I/O, the value is exactly the value we would expect it to be. We have done lots of testing to narrow down the root cause. Our best understanding right now is that when the program is running on a real machine, the I/O is changing values. That seems to be the difference between the test bench and a real machine. Some of those I/O values are sent to display page items over the DIAG CAN from an MC43FS address tag of 0 to a display address tag 1. If we set up the display to never show a page on a real machine, signal ID 19 is the exact value we would expect it to be. Is this a known issue or has anyone else experienced something like this? We are using IQAN design 7.04.8.10088. We have also used IQAN design 7.05. The issue still exists.
Coping an external function removes adjustable item
When you copy and past an external function it will remove
Insert an external function (everything is correct)

I copy and paste it, to and another one. And the ability to now adjust this item is removed, and I cant not figure out any way to fix this. Other then deleting the whole group and adding it manually back.

Display Objects not updating position (Layer Issue)
Running the latest version of IQAN 7.05.27.10981, I am having a problem where buttons will not update location on simulate and the physical display.
In design it looks like this.

Simulate and if I program the display it looks like this.

If I delete the layer these items are on and add them to a new layer then everything is fixed.

iqan analyze screen zoom
Has anyone experienced an issue in IQAN Analyze where the screen font size is extremely small? If so, is there way to correct it? It's as if I zoomed out to 10% but there is no zoom feature that I can find.
Customer support service by UserEcho
