After an application update this message box with a white dot appeared on the MD4 and the screen was completely locked up. No touch areas reacted. 

After a power cycle everything works fine but i thought I should let you know anyways.

The ChannelName in the Array Channel is correct in the external function. 
When imported as an external function the ChannelName is changed to "Undefined" in the Qcode.

When simulating, as seen in the figure, the Array channel returns the correct value.

Using IQANdesign 6.01

JN2100 documentation

Hello everyone, 

I am trying to connect an inclination sensor from IFM (JN2100, see documentation attached) to a MC43. But for now, I didn't manage to have a connection to receive the data.

I want to receive the data from TPDO1 (X value longitudinal and Y value lateral) and I am not sure which identifier I should put on the generic frame in to get these data. 

Can someone please help me ? 

Thanks in advance,

can I put an XA2 and an XC43 on the same bus? The only reason I ask is because the XC adds the HS Exp bus. 

We are seeing an overlapping video message on an MD4-7 where there are no overlapping items, just 2 video feeds side by side and within the screen boundaries. Everything seems to work OK but the message keeps coming up and is an annoyance. 

What could the issue be?

I am running into a weird bug with design 6.02, where if I try to execute a check project, nothing happens. If I do it in 5.07 it works as designed. 

I have tried all of the things I could to try to figure out if it was my system, but all information seems to indicate this is a bug. 

IQAN Design 6.02.10.5706

Windows 10 Enterprise

     Version 10.0.17763

     OS Build 17763.1282

     64 bit

I am more than happy to share any other information needed to get this resolved. I am at the tail end of a big project, and not being able to run this is going to hurt. 

It would be nice to have the ability to add momentary input for MC module applications that could be accessed through IQAN Run. The goal would be to have a way to initiate service routines when a display module is not present.

Allowing VDINs or adding a reset to digital parameters would do the trick.

Question on ISO11783. It defines a paged protocol with some of the messages 17 bytes long. How do I interpret these messages? 

My options in Design are either paged protocol(8 Byte each page) or multipacket.  If paged how do I look at a 17 byte message? If mulipacket how do I look at multiple message on the same PGN with info on the same bytes as one another?

Hi , I am having issues while integrating from different project to a single project, Right now I am exporting from one project and importing to another, Is there any other way for doing integration?

Many of our systems use a master module (MD4, MD3, or MC43) and I've noticed that a lot of our designs specify a terminating address/ID tag to be used on these master modules. Will this mean that all CAN buses will be always be terminated internally, or can you still configure the internal terminations in IQANdesign?

For CAN buses that are configured to be internally terminated in IQANdesign, will using a terminating address tag in conjunction "double-terminte" this bus?