Hello,

When I try to sumit a new topic at this forum and I change the header in the Submit new topic form, the fields to fill in the descripion disappear and the suggested topics appear. There is no possibility to return to the form, only cancel is an option.

You can start over again for describe your problem. This is very annoying

Kind regard

Laura

Question, How can I read the raw value of current-loop in value in using QCode?

Hello, 

I was used to sometimes have 2 generic buses, one with 11bits ID and the other one with 29bits ID, on a same CAN bus.

But with the 7.0 version, This seems not possible anymore.

Is this deliberate (Why?) or is this a bug?

Thanks, 

Rich

IQANgo version 7.00 is now available. 

Measure 

Measurement can be saved as CSV.
Status is now visible at the bottom of the graph (as in IQANrun).

Now possible to change min, max and color for graph items.

Adjust

While adjusting min current, the output will be limited to the adjusted value (same as MD4 and IQANrun)
Adjust view more similar to IQANrun 7.

New user manual

User manual available here.

I like a option to resize the channels. One thing to add would be a setting to set a default size for the channels. I find myself resizing all of my new channels. Would be nice if they were placed the size I want them.

Hello,

I have reviewed the forums and have seen some comments from around 2 years ago stating that the diagnostics over CAN for the MD4 units using IQANdesign require 250kbps baud rate. Is that still the case or can we use a bus network at 500 kbps? Thanks.

I have an existing design I have inherited which has 3 connected J1939 Canbus networks. Network 1 connects between an engine ECU and a MC2 Controller, Network 2 connects the MC2 and a MD4 Screen and Network 3 connects between the Controller, screen, and all our other CAN Devices; Radio, etc.

What is the point of Network 2, when they are already connected through Network 3? Is it because of it being a "Multi-Master" Device?

Thanks for the help!

Hi

Is there a way to duplicate the IQANdesign windows, to work on two functions group side by side ?

Similar to Microsoft Excel, if you use it, you can open two or more windows and put each one on differents screens.

Some software has this possibility.

It would be good for IqanDesign  !

Could it be possible to show the other languages in Iqan Design without having to flash it to the machine? It would be nice to know if the text fits while in the design process or, in my current situation, take a screenshot of the other language screen for purposes of making the operators manual.

I've been having some very strange issues today with XC43 "System mismatch" errors on a system with an MD4-7 and XC43. We're on IQANdesign 6.01.6. There's 1 XC43 with address 1 on CAN-C. When I load this program on new MD4-7 and XC43 I get the XC43 "System mismatch" error and the XC43 has internal state "Failed 306". The amber LED continuously blinks very quickly.

When I move the XC43 to CAN-A or CAN-B and reload the program, everything works. I then move the XC43 back to CAN-C, reload the program, and everything works.

Having the XC43 on CAN-D seems to result in the same "System mismatch" error.

We've used this same program and these same modules on many other machines without this issue, so looking closer at the MD4-7-T1E2 modules I was testing with, it seems like something changed with the modules with 2023 manufacture dates (2302040070 is the earliest SN that I experienced this issue with). All our modules that are later than 2208040660 don't seem to load the firmware onto the XC43 on CAN-C or CAN-D or something. 2208040660 and earlier have no problem operating the XC43 on CAN-C.

Did something change in the CAN-C and CAN-D ports on the MD4-7 suddenly sometime after SN: 2208040660 that they can no longer load firmware onto expansion modules? Or am I doing something wrong?

This could become a fairly serious issue with replacing XC43 modules in the field in the future. If CAN-C and CAN-D can't load firmware on the modules, we'd need to either reprogram the existing system or make sure the firmware is updated before it ships out. This isn't always easily done and kind of defeats the major advantage of expansion modules (forward/reverse compatibility without reprogramming). And if we can't use CAN-C/D for expansion modules, it severely limits their usefulness, since we're already advised not to use these buses for the diagnostic bus.