I have an issue where there are four identical sensors on CAN-D of a MC43.  It has worked without any problems for about a year.  Currently, we are constantly seeing a "Timeout" for all of the sensors on this bus.  There are no other devices on the bus except the four sensors and the MC43.  If we use IQANanalyze, we can see the information from the sensors on the bus, but again, the MC43 shows a timeout for all the sensor JFIN channels.  If we physically unplug the harness from the MC43 and connect it to a MC43 in test box, the MC43 will recognize the sensor CAN frames.  We tried swapping out the original MC43 with the test box MC43 and re-programmed to the machine project file and the test box MC43 does not recognize the sensor CAN frames.  We have an identical setup on CAN-C using the same type of sensors and do not have an issue with reading those CAN frames.  We are using IQANdesign 5.07 and it is in a system with 2-MD4's, 2-MC43's and 1-MC43-FS.  What may be causing this issue?

Hi,

The application has two languages; English (UK) and English (US).

A math channel's unit is set up with multiple language properties; m (meter) for English (UK) and inch for English (US).

A value control is used to display the value and unit of the math channel.

The problem is that the displayed unit does not immediately change from m to inch when I change the language from English (UK) to English (US); I need to restart the simulation for the change to take effect.

Is this intentional?

English (UK):

English (US) without restart:

English (US) after restart:

The display page value control:

The math channel:

Tested with IQANdesign and IQANsimulate 6.08.

I have noticed that a conditional message can display another channel value. This is handy especially when using the message to notify the user that a parameter is out of spec. I am using an interactive channel for the same purpose but it does not appear to be able to display a value from another channel in the same way. Is there a way to do this?

I have seen a few radio receiver models that have IQAN as an option for control (instead of J1939 or CANopen). Has anyone done this? How is this implemented? Explain to me whats going on.

I am programming currently an application where a touch screen is not accepted at all. I use a external J1939 Button and Encoder control. Page changes and changing values in the screen etc. are working now perfectly, this part of HMI I can Programm. But some HMI Dialoges are created automatically be the firmware of the IQAN system e.g.: short circuit on pin...... 

How can I like a my external signal to your firmware dialog???

Thanks

Hello guys, is there any document that lists all these statuses

stAddrClaimError

stAddress

stAlienOnline

stCalcOverflow

stCAN

stChecksumError

stCriticalError

stDiffCheckError

stDisabled

stDivByZero

stError

stFirmwareUpdate

stHighAlarm

stHighError

stHighSupply

stHighTemp

stHighUtilization

stInputError

stInternalError

stInvalidLogRecord

stInvalidArg

stJ1939Error

stJ1939NotAvailable

stLocked

stLogFull

stLogRecycling

stLowAlarm

stLowError

stLowSupply

stMultiAddress

stNegSqRoot

stNoContact

stNoSIMCard

stNoStatus

stNotEvaluated

stOK

stOpenLoad

stOutOfRange

stOverload

stPINCodeError

stPinConflict

stReserved

stRTC

stSaturated

stStartBlock

stSystemMismatch

stTimeout

stVREFError

stWarning

Hi,

I am sending a multi packet J1939 message as shown below with a priority 6. I am using MC41 as master. For some reason TP packets are braodbcast the priority is being changed to 7 from 6. See snapshot of the data log showing identifier 1CECFF7F instead 18ECFF7F. As a result my request from MC41 is being ignored by the Vehicle controller.

I have manually broadcast 18ECFF7F and 18EBFF7F using Busmaster and it works OK. however when I manually transmit

1CECFF7Fand 1CEBFF7F vehicle controller ignores TP packet.

I am not sure if this is a bug or I am doing something wrong appreciate if you can point me in the right direction.

Thanks,

Jag

We are an electronic repair/service company. We have 7pcs of XA2 modules in that are faulty and need repair. I have an MD3 screen available. What version Iqan develop software do I need to write a little test application so that I can turn outputs ON and OFF to test the XA2 modules?

Is there anyway to add the MD3 support for IQAN 6.0+. I see in the release notes item 49995 this was done for the XA2 and XS2 as legacy modules. We still use the MD3 in our current production but we are interested in bug fix item 50457. 

According to the documentation, the system will use the top left pixel to define the background of the start-up screen. 

I have a JPG image 800x182 used on an MD4-7 with white background.  When booting up the screen shows 2 large back bar above and below.  Normal?

Since this not matching the documentation I list that as a bug.