DrewTech MoongoosePro adapter, No J2534-libraries found

[KuusamoMart]

Compiled the April 16th source release as a 64 bit executable. under Windows 11. Was unable to locate the interface, however the J2534 Toolbox supplied by DrewTech can connect to the adapter and configure it. Recompiled the code as a debug version and it produces the error message "No J2534-libraries found". The 64 bit MongoosePro drivers are installed.
Note:
DrewTech do offer some sample code sources which is intended to permit DLL discovery by parsing registry settings to locate the DLLs.

[Comer352L]

FreeSSM parses the Windows registry for registered interfaces (as described in SAE-J2534 and DrewTech). If your interface isn't found, it most likely has not been registered properly by the interfaces installer. You say the "drivers" are 64bit ? Note that 1) the SAE-J2534 API is actually specified for 32bit + Windows only, everything else is out of scope 2) Windows maintains different registries for 32 and 64 bit applications I suspect you interface library is actually a 32bit library. To find out, build a 32bit application and check if it detects the interface. See README.TXT section 4.2.

[KuusamoMart]

So I rebuilt the application as 32 bit, this did detect the interface but it failed the interface test. I then rebuilt as a debug version, this was able to successfully pass the interface test. When I connected to the car, it was able to pull some information from the ECU, but it then gave a 'Failed to communicate' error. I tried connecting to each control unit, all of which failed to communicate correctly (ignore the TCU, the car is manual).
Log file attached.
FreeSSM_32_Bit_log.txt

[Comer352L]

So I rebuilt the application as 32 bit, this did detect the interface but it failed the interface test. I then rebuilt as a debug version, this was able to successfully pass the interface test.

There's no difference with regards to communication between release and debug builds.
The log indicates that there was a short interference on the ISO-14230 bus line, but that alone can't be the reason for your problem.
If it happens again, I suggest to check your interface/cable/wiring and create another log (that will hopefully contain the failing communication).

When I connected to the car, it was able to pull some information from the ECU, but it then gave a 'Failed to communicate' error.

The reason for this is that the ECU refuses to read the VIN.
The reason is still unknown and I will most likely not be able to fix this in the near future, so I decided to disable VIN reading for these ECUs.
Update to the latest code and communication should work.

I tried connecting to each control unit, all of which failed to communicate correctly (ignore the TCU, the car is manual). Log file attached.

That's expected. ABS and A/C controllers of your model are not supported.
Your car doesn't have a Cruise Control ECU (CC is integrated in the Engine ECU).

[Comer352L]

Which model and year is it ?

[KuusamoMart]

It's a UKDM Legacy Diesel 2010.
I'll go and log some more data and will check that I'm using the latest code sources.

[KuusamoMart]

Tried to build both release and debug versions from the latest sources. Release built correctly but debug failed to build. I will raise new issue for this.

[KuusamoMart]

Rebuilt from latest sources as of May 8th. Debug version built correctly (thanks!).
Captured several attempts to communicate with ECU, log file attached.
freessm_Subaru_Legacy_diesel_2010_log.txt

[Comer352L]

Fixed, try again.

[KuusamoMart]

That works in normal operation, but again only if I used debug build, the release build fails the interface test.
In test mode (fuse inserted in unmarked fuseholder on a BR/ BM), the interface test passes, but the connection to the ECU fails.
Log files for normal and test modes attached.
FreeSSM_debug_10-05-23_sources_Legacy_Diesel_2010_Normal.txt
FreeSSM_debug_10-05-23_sources_Legacy_Diesel_2010_Diag-mode.txt

[Comer352L]

Are actuator tests started automatically in test mode ? E.g. cooling fan goes ON-OFF-ON...  when ignition is switched on ? No idea at the moment why the interface test should fail in release mode but work in debug mode.

[KuusamoMart]

I do hear actuators going on and off, I need to see if the cooling fan is also operating.

[Comer352L]

Can you please try the attached patch and post me the debugging output ? Init will take +10s and don't expect the patch to fix the issue.

[Comer352L]

0001-DEBUGGING-PATCH-1.txt

[Rename from .txt to .patch]

[Comer352L]

Please ignore the previous patch and try this one instead:
0001-DEBUGGING-PATCH-1-V2.txt

[KuusamoMart]

OK, patch included with the 11th May build (hopefully). Ran with the diagnostic link installed in the fusebox and looged the output from debug.
FreeSSM_Patch_Suabru_Legacy_Diesel_2010_Diagnostic_mode_log.TXT

[Comer352L]

Looks like the patch wasn't applied properly.

Instead, reset your local repository and replace src/SSMprotocol2.cpp with the following file:
SSMprotocol2.txt
[NOTE: rename to .cpp]

[KuusamoMart]

Getting a build error when it starts processing SSMprotocol2.cpp, Looking at the SSMprotocol2.cpp source file in QT Creator, it gives the error "use of undeclared identifier 'sleep'" (all in lower case). Changed to 'Sleep', building now completes without error.
Tried to connect with the car in diagnostic mode, captured the log. Something I did notice was that, as soon as I try to connect to the Engine Control Unit, the actuator cycling stops immediately; repeating the test confirmed it was repeatable.
log.txt

[Comer352L]

Interesting log.
Please send me an email (see "About" section in the software).
Attaching zip-files here is nasty...

[KrisK63]

Any updates?