I have a problem with a system that uses APP in and out between three modules, one MD4, two MC3. I have found that one MC3 does not appear to be receiving APPIN's. When I monitor the modules in IQAN Run, all modules appear to be talking successfully. When I look at IQAN Design the APPIN's on the module that's faulting says Error, Timeout and its red not green. On the module that's sending the APPOUT, the function block APPOUT is green and OK. Its almost as if the modules are not starting at the same time and the timeout for the first APP in to be received is being reached?

Is there any way of finding out more information about this error?

The machine was working OK for some time and it just happened randomly and now im unable to recover the machine. We also have other machines running this software and same software version and it appears OK.

I have extended the 50ms cycle time to 100ms,on all three modules with no success. Is there any reason why this could have happened? Running Design 3.19.9.

It would be nice to be able to assign a State machine or parameter to a "Text Formatting Channel".

I have a situation where I have "Group A", 10 Text Parameters with with a state machine (10 states) assigned to it. And a "Group B" of 15 Text Parameters with a 15 state machine. I would like to use a Single Text formatting channel to Add Group A to B for certain situation.

Trying to display the text on the screen currently is painful.


Also on a separate note it would also be nice to be able to use a Text Formatting Channel in a Text Parameter.

Hello

It is possible to measure a frequency with a md4 ?

Thank

I have an application where I am using a gauge to display the position of a rotating object. I make the 12 o'clock position the 0° point. I noticed that as my input is rotating from clockwise, that the needle on the gauge rotates counter clockwise from 359° back to 0°.

It would be nice to have the gauge continue to rotate in a clockwise direction as my input crosses the 0° threshold.

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?

On modules which have two VREFs, can VREF error logs be updated so that they indicate which VREF has an issue? We've had instances where one of the two VREFs has an issue but you can't tell which one from the system logs. See below for an example of what the logs look like. 

This was from IQANrun 4, but it looks similar in newer versions of IQANrun.

We're adding separate event logs that record the voltage of the VREFs when an error is detected, but it could still be helpful if the system log indicated which VREF has an issue. 

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.

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. 

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?