Vida CEM swapping

[RickHaleParker]

July 4th fireworks!

Got my PT V2.0 assembled. It is not reading the CEM Part numbers. Would it get that far if it was not communicating on the CANL or CANH ? A little more verbose so we can confirm that and that is happening would be handy for us non-coders.

[vtl]

Comment/remove autodetect?

[RickHaleParker]

Comment/remove autodetect?

Dead in the water right now. Downloaded your latest master sketch .... it will not compile and upload to the Teensy 4.0.

Arduino: 1.8.13 (Windows 10), TD: 1.53, Board: "Teensy 4.0, Serial, 600 MHz, Faster, US English"

E:\Sketches\VTL\volvo-cem-cracker-master\volvo-cem-cracker-master\volvo-cem-cracker\volvo-cem-cracker.ino:16:30: warning: "/*" within comment [-Wcomment]

#define LAT_ONLY /* choose candidates by latency only (vs latency/standard deviation) */

^

E:\Sketches\VTL\volvo-cem-cracker-master\volvo-cem-cracker-master\volvo-cem-cracker\volvo-cem-cracker.ino:12:1: error: 'st' does not name a type

st is brute-forced */

^

Multiple libraries were found for "FlexCAN_T4.h"

Used: C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\FlexCAN_T4

Not used: C:\Users\RickP\OneDrive\Documents\Arduino\libraries\FlexCAN_T4-master

Error compiling for board Teensy 4.0.



This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

[RickHaleParker]

Got the master to compile. Commented out #define CEM_PN_AUTODETECT. No change.
This is a CEM-L on the bench.

Why is the CEM_PN_AUTODETECT still running when it is not defined

Perhaps if PN = 0 then prop the user to enter the CEM part number or CEM type in the serial terminal. Instead of giving up.

[urosm]

I tried cracker on 2004 V70 and 2005 V70. Both D5.

This schematic I used:

The 2004 V70 is a CEM-B. The side attack does not work on a CEM-B.
The 2005 V70 is a CEM-L. The side attack does works on the CEM-L.

Schematic is good.

If you are cracking in-car. the battery needs to be in good health and fully charged. A CEM may stop responding to the carcker if the voltage is low.

Did you cut the trace between V-USB and V-IN on the back of the Teensy 4.0?

How about some pictures of your CEM cracker. So we can look for possible problems.

Yes, I cut the trace between V-USB and V-IN.

Here is a photo of the board:


Here are photos of the interface:

[RickHaleParker]

Yes, I cut the trace between V-USB and V-IN.

You have a Red wire running from the Teensy V-IN to J1 V-USB. That is the same as not cutting the trace. You also have Teensy grounded to the USB port. Remove the Red and Black wires fron J1. Plug the interface into the OBD2 port. The Tennsy will power off U4.

[ricked]

need some help with V50 CEM 30728906 on bench

What year is it? I've heard 2010+ don't want to crack.

i know what the error was... CEM is dead, after 4 runs of the cracker i did try to read it with xprog and carprog both cant connect to mcu.

owner did jump start the car with cables reversed

[vtl]

Got the master to compile. Commented out #define CEM_PN_AUTODETECT. No change.
This is a CEM-L on the bench.

Why is the CEM_PN_AUTODETECT still running when it is not defined

It's not running, the code sends everything to programming mode and then tries to read the part number as a CAN connectivity test.

[vtl]

owner did jump start the car with cables reversed

[vtl]

This is a CEM-L on the bench.

Start with the CEM being powered off. Press the reset button on Teensy, wait for "Sending blah-blah", sharply apply the power to the CEM. You have about 20 ms from the CEM's on-the-bench start to send the programming mode messages, otherwise it goes into a sleeping/idle mode.