We have recently found a big problem when attempting to update an MD5 screens over CANbus or G12’s. 

The firmware will start to send and get roughly 30% complete before the screen goes blank and dark. 

Design shows to still be sending the file but the screen is unresponsive. You can power cycle after this crash and it will show no program message. 

The only way to fix this seems to be with Ethernet connection.  We have had 3 Md5’s now with this same issue and becoming a major problem, as several customers have relied on G12 update support on the field.

In the current iteration of the iQAN software, when a dialog for undefined DM1 SPNs appears on the MD4, it is limited to only showing 3 SPM/FMI values. If there are any more, at the end of the last shown FMI it will display "...".

Techs in the field who are doing an initial assessment on a machine tend to not understand that there are more faults active, that they can't see without going to the module status page in the system menu. Could we perhaps get a "more" button they can press to directly open this page when more than 3 faults are present?

Hello,

I find the Propagate Outputs feature to be extremely useful. It would be beneficial to allow function group inputs to be propagated as well. I tend to use nested function groups quite often to keep my programs clean and easy to follow, and as a result I will typically have the same function group input repeated in order to pass information along. This feature would not be useful if that data being passed through each function group was being used in each one, but I often find myself passing data through function groups without using it in any of the intermediate function groups. For these cases, being able to propagate inputs would be extremely helpful.

The below example should help clarify what I mean. This is a part of an external function I am creating to control a CANOpen device. To make this external function as generic as possible, I have created this COB-ID generator module that will combine a user defined Node ID with a predefined TPDO/RPDO. This nested function group is the only part of the program that interacts with the FC NODE ID & NFLS NODE ID function group inputs. These FGIs would not need to be in place if propagating inputs was implemented. The middle picture shows what is inside the COB-ID GENERATOR function group, and the last picture shows the main external function group.

I am working on a project with four variants. When I click the Run button in IqanDesign, the simulator only works on one of them.

On the other variants, when I click Run, it checks the project and the following window appears, making it impossible to continue:

Hello, I have a engine control project that I use the same base program but I swap from a Diesel engine to Natural gas.  The Diesel uses Source address 0 and the Natural Gas uses 39. I have a MD4 and MC43FS. I have variant programs as it changes they control function between the Diesel and the Gas. That works good but i have to manually change the source address each time I upload. It would be good if we could in the initialization use a variant that would select the appropriate source address. Maybe there is already another way to do this? Or if we could set some CAN messages to accept from any source address.   

In the Object List area, the And/Or/Latching drop down is scrollable when the mouse is hovering over it. I've unintentionally changed this a couple times now while scrolling through my object list and it's the kind of thing that's real easy to miss. I don't see any way to disable this in settings, anyone else having any issues with this?

Is it possible to obtain information on when the operator is touching any point on the display in an MD4-10 display?

I recently updated to V 7.05 and I was able to update the initial system i was testing on with no issues but when i went to go update another system my MD4 would take the new program but the MC43 will not. I have tried power cycling and have had no luck. I then decided to bench test with another Md4 and a MC43 and i had the same issue. The screen takes the program but the MC43 will not connect. I questioned the program itself and made a blank program with the two devices just to confirm and same result. The First time programming both modules take the program and then after that only the MD4 will and i get the incomplete system error.  Note this was all using ethernet

Normally i would just revert back to CAN programming to try to just do the MC43 by itself  but with the V 7.05 i can not get my peak adaptor to connect anymore. I updated the drivers to 64 bit and confirmed in my PCAN view I'm running 64. but I get a no uniCAN error. I then tried to go back to my 6.08 software to test and now it wont work there either as it gives me a communication error and wont connect. It had worked for the last several years until I updated my Peak to 64 bit

Some assistance on both communications would be appreciated.

I am using IQANDesign 7.05 and if I use the component navigator on a CAN Frame IN or OUT (Generic or J1939) there is a letter designated to the frame.

I thought this must have been linked to the calculation order of the frames assigned to a given module but that doesn't appear to be correct because it skips letters (i.e. not all modules have A, some skip other letters). It is also not a reference to the CAN network (A through E on an MC43) that the module is connected to because there are letters like V and W.

What does this component in the navigator mean?

Is there a way to measure the display brightness that is set in the preferences menu? I have a system with 2 MD4s, and I would like any display brightness setting set on one display to be set on the other. Could we perhaps get a module diagnostic channel for this?