Left unconnected it would be pulled down, always reporting logical 0, CAN message receive timing out after 1 second. In his case it seems it always report 1, which means either a connection to wrong signal or burnt IO pin maybe?
Vida CEM swapping
-
vtl
- Posts: 4727
- Joined: 16 August 2012
- Year and Model: 2005 XC70
- Location: Boston
- Has thanked: 114 times
- Been thanked: 606 times
Re: Vida CEM swapping
I bought https://www.skpang.co.uk/products/teens ... ceae&_ss=r
And follewed can wires from schematics that was in github page..
And follewed can wires from schematics that was in github page..
-
vtl
- Posts: 4727
- Joined: 16 August 2012
- Year and Model: 2005 XC70
- Location: Boston
- Has thanked: 114 times
- Been thanked: 606 times
Check your wiring once again. If all looks good, you may have burnt the line in chip. Move pin 4 to other digital IO pin and reflect it in the code: https://github.com/vtl/volvo-cem-cracke ... er.ino#L35
- RickHaleParker
- Posts: 7129
- Joined: 25 May 2015
- Year and Model: See Signature below.
- Location: Kansas
- Has thanked: 8 times
- Been thanked: 958 times
The Teensy 3.3V line is right next to CRX1 ...... one pin position off perhaps. That would tie Latency detect high.
⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
- RickHaleParker
- Posts: 7129
- Joined: 25 May 2015
- Year and Model: See Signature below.
- Location: Kansas
- Has thanked: 8 times
- Been thanked: 958 times
One of the early schematics had a omission in it.
Post the one you used so we can check it or download the latest and compare it to what you used.
⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
-
swinokur
- Posts: 14
- Joined: 5 September 2021
- Year and Model: 2013 C30 Polestar
- Location: San Francisco
- Has thanked: 2 times
Hi there,
I've just gotten back from my first attempt to crack the CEM on my 2013 C30, sadly I didn't succeed on my first two tries!
I'm hoping someone here has some suggestions on what to do next:
- I built the hardware based on the schematic just downloaded from: https://raw.githubusercontent.com/vtl/v ... ematic.png
-- I used two "waveshare" canbus transceiver boards:
https://www.waveshare.com/sn65hvd230-can-board.htm
https://www.waveshare.com/w/upload/c/c5 ... ematic.pdf
-- and an OBDII cable from amazon. (Yep, I checked that I had the right pins using a meter)
- To power the teensy I used a powered USB hub between the laptop and the device: https://www.newark.com/cypress-semicond ... dp/19M6485 (yep, exactly this object)
-This was done in the car, with a battery tender attached to the car.
- As seems to be indicated, I connected the Teensy and turned the ignition to P2 within a couple seconds of attaching the Teensy to power.
I tried a run with all of the defaults, using the build from July 20th that is on github.
After that first run was not successful, based on some of the reading in this thread I un-commented line 1031 (// set_arm_clock (180000000);) and tried again.
This was also not successful.
I've attached logs of both runs.
Let me know if there's more information to provide - and what other tricks folks have done to get this to pop?
thanks!
I've just gotten back from my first attempt to crack the CEM on my 2013 C30, sadly I didn't succeed on my first two tries!
I'm hoping someone here has some suggestions on what to do next:
- I built the hardware based on the schematic just downloaded from: https://raw.githubusercontent.com/vtl/v ... ematic.png
-- I used two "waveshare" canbus transceiver boards:
https://www.waveshare.com/sn65hvd230-can-board.htm
https://www.waveshare.com/w/upload/c/c5 ... ematic.pdf
-- and an OBDII cable from amazon. (Yep, I checked that I had the right pins using a meter)
- To power the teensy I used a powered USB hub between the laptop and the device: https://www.newark.com/cypress-semicond ... dp/19M6485 (yep, exactly this object)
-This was done in the car, with a battery tender attached to the car.
- As seems to be indicated, I connected the Teensy and turned the ignition to P2 within a couple seconds of attaching the Teensy to power.
I tried a run with all of the defaults, using the build from July 20th that is on github.
After that first run was not successful, based on some of the reading in this thread I un-commented line 1031 (// set_arm_clock (180000000);) and tried again.
This was also not successful.
I've attached logs of both runs.
Let me know if there's more information to provide - and what other tricks folks have done to get this to pop?
thanks!
- Attachments
-
TyCommander-9903900-Teensy-180Mhz-Run 2.txt- (56.11 KiB) Downloaded 93 times
-
TyCommander-9903900-Teensy-600Mhz-Run 1.txt- (55.64 KiB) Downloaded 94 times
-
swinokur
- Posts: 14
- Joined: 5 September 2021
- Year and Model: 2013 C30 Polestar
- Location: San Francisco
- Has thanked: 2 times
I think all C30s are P1?
Based on the part number reported by the software (31327215) it would be this part https://www.volvopartswebstore.com/prod ... 27215.html -- which appears to be the same ECU as all the rest.
-
swinokur
- Posts: 14
- Joined: 5 September 2021
- Year and Model: 2013 C30 Polestar
- Location: San Francisco
- Has thanked: 2 times
After reading more of this thread, I found the strong suggestion to not power the teensy with USB power and switched over to a buck transformer that I had in a parts bin: https://en.cosel.co.jp/product/powersup ... /SUS61205/ (5v 1.2A output, 12V input). I connected it to the OBD II pins 16 and 4. (I wasn't sure if pin 4 or pin 5 was more appropriate or mattered, but one other design I saw in the thread used Pin 4, so that's what I settled on.)
Then I tried some more runs.
Run 3 was done with the default settings.
Run 4 was done with Samples = 30, 180Mhz clock, and LAT_ONLY commented out.
Then I read some more in this thread, and saw that some people called for the removal of the terminating resistors on the CAN transceivers. I removed those resistors and tried again.
Run 5 was the same settings as Run 4. (Samples = 30, 180Mhz clock, and LAT_ONLY commented out)
Run 6 was was back to 600Mhz, with Samples = 30 and LAT_ONLY back to default.
At this point I'm imagining that my CAN bus transceivers might be to blame, being the 'inexpensive' amazon/china type.
I suppose it could also be my wiring - between the teensy and the transceivers they're 4" breadboard .100 pin female to female connection wires.
(I'm fairly adept at soldering, if it is just easier to pull the silly thing out of the car and pull the data off the chips with a programmer or adapter, let me know if there's a guide to that somewhere.)
thanks!
Then I tried some more runs.
Run 3 was done with the default settings.
Run 4 was done with Samples = 30, 180Mhz clock, and LAT_ONLY commented out.
Then I read some more in this thread, and saw that some people called for the removal of the terminating resistors on the CAN transceivers. I removed those resistors and tried again.
Run 5 was the same settings as Run 4. (Samples = 30, 180Mhz clock, and LAT_ONLY commented out)
Run 6 was was back to 600Mhz, with Samples = 30 and LAT_ONLY back to default.
At this point I'm imagining that my CAN bus transceivers might be to blame, being the 'inexpensive' amazon/china type.
I suppose it could also be my wiring - between the teensy and the transceivers they're 4" breadboard .100 pin female to female connection wires.
(I'm fairly adept at soldering, if it is just easier to pull the silly thing out of the car and pull the data off the chips with a programmer or adapter, let me know if there's a guide to that somewhere.)
thanks!
- Attachments
-
TyCommander-9903900-Teensy-180Mhz-Run4-Samples30-Lin-Buck.txt- (65.11 KiB) Downloaded 82 times
-
TyCommander-9903900-Teensy-600Mhz-Run3-Buck.txt- (66.15 KiB) Downloaded 86 times
-
TyCommander-9903900-Teensy-600mhz-Run6-S30-buck-no120.txt- (67.76 KiB) Downloaded 87 times
-
TyCommander-9903900-Teensy-180mhz-Run5-S30-Lin-buck-no120.txt- (55.74 KiB) Downloaded 80 times
- RickHaleParker
- Posts: 7129
- Joined: 25 May 2015
- Year and Model: See Signature below.
- Location: Kansas
- Has thanked: 8 times
- Been thanked: 958 times
All C30s are P1. However there been clues that later P1s have a different shuffle order.
PIN shuffle order: 0 1 2 3 4 5 works on some P1s.
VTL has more the one shuffle order in the code but I am not sure if he has more then one shuffle order for the P1. I think he was looking for a cutoff point at one time but never found one.
Last edited by RickHaleParker on 05 Sep 2021, 22:24, edited 2 times in total.
⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙⸙
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD. Yamaha V8 conversion
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
-
- Similar Topics
- Replies
- Views
- Last post
-
- 1 Replies
- 6431 Views
-
Last post by RickHaleParker
-
- 5 Replies
- 8699 Views
-
Last post by forumoto






