Okay, so... This project stalled again right after I got the engine running and drove it last time.
Complete:
S60 Engine and XC90 Transmission installed
Driveshafts installed
Exhaust more or less functional (needs moar shielding)
Car starts every time. Runs a little rich but idles great,
ECM is communicating with the RealDash
TODO:
TCM and ECM are NOT communicating (because I haven't taught the EMU how to speak Volvo yet...)
Interior is still sitting in a bedroom floor
Bumper for wrong YM car, but... I have the Maxton Design widebody kit for it
Wheels... Wheels need to be done with body kit otherwise
---
So, I made an "about face" on the OEM ECM after trying to decipher the CAN captures that I have. There are soo many messages in the CAN frames that do not start on byte boundaries. Then there are single bit flags and a litany of other challenges to overcome like scaling, etc. I have worked out about 30% of it for sure and another 30% of it is likely. The XC90 apparently uses 27 unique CAN-IDs. Maybe one more for a trailer module but I haven't confirmed that. There are six for the ECM that carry runtime data; four for the TCM and one each for security/immobilizer data (Again, not confirmed but I am PRETTY sure at this point). Those six ECM frames are what I need to recreate before I can actually call this car "swapped".
So in the interest of science and to move the guessing closer to zero, I have begun building a stim for the ECM. I will can (re)wire it into the vehicle CAN and hopefully be able to at least figure out the torque reduction data so that the transmission will stop trying to break shit when I shift to reverse (one of the known times that there is a torque reduction request).
I am actually writing this post pretty much for the explicit purpose of sharing knowledge about the Ardu-Stim project at
https://github.com/speeduino/Ardu-Stim.
First off, if you are uninitiated, this is a project for creating a simulated Crank/Cam signal for bench testing the Speeduino ECM.
It was a pretty trivial task to clone, compile and load the Arduino project. It is pretty straight forward as long as you have experience with the Arduino Dev environment.
The front end however... has not been updated in some time. I was completely unable to get it to load on my RPI4 desktop running Kali. There is an appimage available but it simply fails. So, I try to load it on the windows desktop. Nada. Open the Dev Console on the browser and start reading the logs.
Okay. Switch strategy. This is a standalone app designed to run in a container. I mean, I get it because thats what the Debian binary was offered as. But looking at the source downloaded with the Ardu-Stim git repo, you'd think this is a web app.
Anyway, install Node.js for windows. Install npm and the electron serial library for node. Compile, debug, inspect. Wash, rinse, repeat.
Then, you have to build a map for your crank correlation to the cam signal.
That is where I am at:
Back to it...
