CAN bus to CCD bus Protocol Translator(Chrysler PCM Simulator)

[Alexia]

Originally Posted by Palani

That sounds great! How are you liking the TDI? I considered that option but there aren't any junkyards here on the Big Island where I live to pull parts from so a crate engine seemed more do-able despite the upfront cost. The Cummins has been great, just working out a couple kinks with fan controllers and ac lines, etc. Normal engine swap speed bumps.

Is your set-up based on the Teensy chip you and Alexia were discussing? I've never played with anything like this before so I'll be recruiting a friend of mine from the industry that deals with programmable hardware regularly. I'm looking forward to seeing your setup. In the meantime, would you mind providing a basic parts list so I can get things on order? Thanks in advance!

For CAN bus to CCD bus:
Teensy 3.2
2x CAN bus transceivers - I used the TJA1050 chip to do write only for the CCD bus.
Power supply - I used a single voltage regulator to power the Teensy.

[Palani]

Originally Posted by Alexia

For CAN bus to CCD bus:
Teensy 3.2
2x CAN bus transceivers - I used the TJA1050 chip to do write only for the CCD bus.
Power supply - I used a single voltage regulator to power the Teensy.

Thanks so much!

[xeroOTG]

Originally Posted by Palani

That sounds great! How are you liking the TDI? I considered that option but there aren't any junkyards here on the Big Island where I live to pull parts from so a crate engine seemed more do-able despite the upfront cost. The Cummins has been great, just working out a couple kinks with fan controllers and ac lines, etc. Normal engine swap speed bumps.



Is your set-up based on the Teensy chip you and Alexia were discussing? I've never played with anything like this before so I'll be recruiting a friend of mine from the industry that deals with programmable hardware regularly. I'm looking forward to seeing your setup. In the meantime, would you mind providing a basic parts list so I can get things on order? Thanks in advance!

I actually just started my swap and drove it for the first time last week. I love it! I have a bad turbo that I need to replace before it goes back into drivable status, but I'm definitely loving the torque. I already have a couple other VW's so it made sense for me and when I started the Cummins wasn't out yet. I've got a super detailed write-up on tdiclub, but most of the same content is in my build thread here, minus a month or so of weekends.

I actually derived from the route Alexia started with. I'm using a stm32f4xx running micropython because python has a smaller learning curve than C/C++ for people that aren't in the firmware business (I am... But I wanted to try it out). My other gripe is the teensy 3.2 is based on the k20, which is dated at this point. NPX does not recommend the k20 for new designs. I don't think the teensy 3.2 is going anywhere because China is pumping out counterfeit boards, but still. I wanted the mbed sdk for the k20 and could no longer get it from npx's tool, mcuxpresso. They really are pushing the k26 for new designs.

I'm doing a dual CAN design, and using a j1709 chip for the CCD side cause I can read the bus as well as transmit. Doesn't matter in the long run, but avoids bus collisions. Either board will do what you need. I'm too busy with my day job to fab and sell boards, so why not just share them with the Jeep community?

Sent from my Pixel 2 using Tapatalk

[Alexia]

I only use Teensy 3.2 for my prototyping phases since it speeds up the process and I have them laying around.(Granted, it ends up staying in all of my dumb around the house projects.) I will probably moved to the Teensy 3.6 with the K66 eventually once I run out.

The alpha hardware sample I have in hand is entirely different. This really is something I should have completed a couple years ago, but life has got in the way.

[Alexia]

I have a "finished" schematic that I have handed off to an electrical engineer and work should start soon on creating a "final" PCB since my personal PCB designs are garbage.(There is always feature creep!) I am 100% free of a job until the end of October so I am making this my job to get this created and out there.

So far:
* 2x CAN Bus
* Single Wire CAN (Low Speed) Bus
* CCD Bus
* ISO9141 K and L Bus
* J1850 Bus
* 5v DAC for simulating engine health sensor output
* 12v DAC for simulating engine health sensor output
* SD Card slot for data logging
* QSPI 32Mbit Flash for additional code storage(CircuitPython support)
* JTAG/SWD 10 pin connector
* USB port for end user configuration and flashing

[John(XJ)Jeep]

I'm doing an LS swap 04 Intrepid soon. Will this help in that? I'd like to keep it factory body and run MS3 goldbox. Or is the CCD bus different in this vehicle from jeeps?

[Alexia]

Originally Posted by John(XJ)Jeep

I'm doing an LS swap 04 Intrepid soon. Will this help in that? I'd like to keep it factory body and run MS3 goldbox. Or is the CCD bus different in this vehicle from jeeps?

Megasquirt is not something I plan to support at the moment. It uses an active polling protocol instead of a protocol that is always broadcasting like every other OEM protocol.

[John(XJ)Jeep]

OK well, maybe one of the GM dashes will be close enough to get into the car lol.

[Alexia]

I am back now with Chrysler PCI bus support. The format for the individual pieces of data is similar to CCD, but the protocol for how the data is presented is slightly different.

[Alexia]

The message identifier for speed is eluding me, but I have all the other gauges working.

[Alexia]

I have a PCB design rough draft in hand for the Translator Gateway Module that will power the instrument cluster eventually.

[kastein]

EAGLE is some good PCB design software. Looks like that board could be a little smaller but not too much, maybe 50% reduction. What connectors are those?

[Alexia]

Originally Posted by kastein

EAGLE is some good PCB design software. Looks like that board could be a little smaller but not too much, maybe 50% reduction. What connectors are those?

Some of the blank area is there for future expansion and still be able to use the same enclosure. Having a JTAG connector out there all alone is a bit silly. :P

Molex Mini50

[Cummins90]

Would you have any use for blank JTEC electrical headers with this project

[Alexia]

Originally Posted by Cummins90

Would you have any use for blank JTEC electrical headers with this project

Nope, all of this is intended to be spliced in.