Would be great if the DM1 messages from the "DM1 out" also sends Occurrence Count.

As it is now it always sends 127 which makes the DM1 messages in IQAN Connect portal not work as desired.

Seems to be the norm these days is to have a "Dark Mode" version of the program. Is IQANdesign going to be moving that direction?

We are working on a project which includes machine vision. In order to communicate between TPU and MD4 we are limited by MD4 to CAN bus only. Are there any plans of expanding C3 and/or C4 communication capabilities?

Using 6.06 I have that when I try to enter a PIN Code the machine masks the number selected with astrisck. Is there anyway to change this so the number is not masked?

Some people have shaky fingers and they have difficulty entering the correct code number.

Is there any way of recalling fault/warning messages via VDIN without a need of restarting the system?

Hello All,

While working on a project for the past couple of months I had used a couple of different passwords for full access, limited access, and some other functionalities. Since they are automatically saved to the database I never had any issues with this up until I wanted to migrate the software to a different computer. I ended up exporting and importing the code into a new project with a new project ID and linking all the interfaces back resolving my password problem. 

To prevent people from having to do the same in the future I would like to suggest a feature where you can do a password recovery. This could be linked to an IQAN design license, the project ID, or a company e-mail account, whichever is more convenient. What do you guys think about such a feature?

Kind regards,

Roy den Drijver

Is it possible to make the position of the controls dynamic (X and Y)? We use one software version for different customers. Depending on the application some gauges and buttons are visible, and some not. It would be nice if we could shuffle some objects to fit it all better together. I think it would be enough if this feature is enabled for groups. That would be great!

Similar to this:

MD4 Display Page - Dynamic Graphic Objects - Dynamic XY … / Software / IQAN

Hi there.  Really like the new DM01 / Log folder reading in the FW6.06.10 just released.  Also the shortcut function to read DM01/2 is a great addition.  This comment is the same for the Log folder access and viewing.  

Only additional comment is that there is a difference between the DM01 and the Log folder when the message is longer than the space on the screen.  In the Log folder, the log description + value text is shown at the bottom (great) and automatially shrunk to fit (and centred it looks).  So long text descriptins and values are supported well.

BUT the DM01 does not do this.  If the DM01 has fairly long txt for the FMI description, then when this FMI text is shown at the bottom of the screen, the text is truncated and not shrunk to fit.  It would make sense to have the Log folder and the DM01 react the same way if the text does not fit the space at the bottom.  Make sense?

Thanks

Julian

I have a question about the length of J1939 when the data is less than 8 bytes.

IQAN seems to set automatically the data length to 8 bytes, no matter what the DBC files contains.  

But, for example, when a PGN is set to 4 bytes by a manufacturer, the communication fails.

Is there a way to set the proper value of the DLC in IQAN when the data length is less than 8 bytes on J1939 CAN bus?

The past year (since Februari or so), we've been experiencing a lot more CAN related issues than in previous years. Usually BUS-ERRORs (so the safety module will lock down). It happens sporadic, it has been extremely hard to reproduce, but it happens on quite a lot machines, a few times a week in some cases. Machines with different software, different engines (FPT, Scania), different programs, different wiring. So they must have something in common that makes this happen.

I suspect it's "just" somewhere in the wires/terminators or other external factors that may reduce the bus health in general. But, what strikes me it started to happen on somewhat older machines, after updates. Some MC4x modules went from IQAN 5.03 to IQAN 6.xx, and it seems that CAN problems started there as well.

Could it be that the problem was always there, but that IQANs have a more strict check (less tolerance) since a specific firmware version?

Couldn't find it in the release notes, other than that several new CAN features (high speed, FD) have been added. A bit off topic, but in the same fashion we just updated a very early MC43 with a new program, and suddenly there is a VREF error that didn't occur before the update. Again, I guess the error was always there, but slipped through somehow in the older firmware?

For the info:

* We use 250 kbps

* Faults happen on the primary CAN-bus (about 4 MC IQANS, a display, an Engine)

* Usually the Safety Module will lock down, while the others continue to talk

* Networks are often a mixture of firmware versions (IQAN 5.03, IQAN 6.00.49, and more recent IQAN versions) - depending which modules got updated