When updating our firmware programs on customer units from v6.08 to v7.05 remotely we can't accomplish this without asking something of the customer we really can't reliably expect from all of them.

They have iqango, connected via bluetooth.

Currently the only solution I have found is the following:

1) Remotely connected: using v6.08 install a blank program, power cycle

2) Email a v7.05 blank program to the customer, they use iqango to send it to the module, power cycle

3) Remotely connected: using v7.05 install the real program, power cycle

Attempting to remotely perform step 2 results in an immediate rejection of the remote connection.

This program is simply a single MC41

I've been using the CRC parameter in IQAN design for J1939 messages that require SPN 4206 (rolling counter) and SPN4207 (checksum). I can't find a configuration that works. I assumed that the "J1939 checksum" option was for SPN4207 but that doesn't seem to be the case (I just get checksum errors from the destination device). Am I missing something or is the CRC parameter not configurable for SPN 4207? I'm having to do it the long way around doing the calculation (it works but it's very messy). SPN4207 is a 4 bit checksum (as below), SPN4206 is a 4 bit rolling counter.

Checksum = 
(Byte1 + Byte2 + Byte3 + Byte4 + Byte5 + Byte6 + Byte7 + 
message counter & 0x0F + 
message ID low byte + message ID mid low byte + message ID mid high byte + message ID high byte)

Message Checksum = (((Checksum >> 6) & 0x03) + (Checksum >>3) + Checksum) & 0x07

Has anyone ever seen overload errors on all of the current output from an XC43 or have any idea what might be causing this?

This is an MD4-10 running on V 6.01.6 connected to a diesel engine on CAN A, XC43 on CAN C, and qty 2 LC5s on CAN D

This is an intermittent issue. Sometimes they will go a day without any errors while other times they see them every couple of hours or so.

This machine did have an alternator failure recently, so we initially thought it was a damaged XC43 module from possible voltage spikes from a failing alternator, so we replaced the XC43. The new XC43 worked for a day, but then the errors came back. All of the wiring looks good and we're told the new alternator is putting out a steady 27.5-28V.

I'm leaning towards replacing the MD4 and updating the firmware hoping that will fix it, but I'm kind of grasping at (expensive) straws at this point.

Description

Environment:

• MATLAB Version: R2025b
• IQAN Toolbox: IQAN Toolbox for Simulink 
• Operating System: Windows 11
• Target Hardware: [e.g., MC4x]

Issue Summary: While attempting to export a model using IQAN.export('ModelName'), the process fails immediately after the Model Advisor checks pass. The error occurs within the encrypted P-code file verifyAndExport.p.

Error Logs:

Matlab

### All checks passed!
Unrecognized method, property, or field 'class' for class 'Simulink.ConfigSet'.

Error in verifyAndExport
Error in IQAN.export (line 38)
      verifyAndExport(model, varargin{:});

Troubleshooting Performed:

1. Manual Check: Running cs = getActiveConfigSet(model); class(cs); in the command window returns 'Simulink.ConfigSet' correctly, confirming the model configuration is valid.
2. Path Check: Verified that class is not being shadowed by other functions; it points to the MATLAB built-in.
3. Root Cause: It appears verifyAndExport.p is attempting to access .class as a property of the Simulink.ConfigSet object (e.g., obj.class). In MATLAB R2025b, this syntax is no longer supported for this class, and the functional form class(obj) or isa() must be used instead.

Request: Since the source code is encrypted in verifyAndExport.p, I cannot apply a fix locally. Is there an updated toolbox version that supports the R2025b API, or a workaround to bypass this check during export?

Only first sections of the documentation are shown and there are no checkboxes to click to add more sections. Same project works well in 6.08 and 7.02.

Is there a workaround?

Hi,

Would anyone be able to provide me the download link of IQANdesign 7.05.25?

Thanks in advance!

7.05.27, MD5-8, G12

Whenever I connect via Bluetooth via laptop and try to measure it disconnects.

I can make modifications to the program but trying to measure is impossible.

How do I link the virtual digital input from MD5 display to the main MC43 controller?

I have problem getting my TSC1 work on volvo truck. Is here anybody that has gotten it to work and can give me some hints on how you have made it?

I have made it with 2 different J1939 with same source adress (thanks to this forum) because both want PGN230.

Volvo says that they have all the parameters activated that needs to be activated so it sounds that something is wrong on IQAN side.

I could not send the error report. IQAN Design 7.05.27.10982. Was adding a math channel to a function group and the software crashed with the following error message. Access violation at address 00000000018D6631 in module 'IQANdesign.exe' (offset 1406631). Read of address 0000000000000040. I reinstalled the software.