Recent content by Alexia

I am considering "slim" models later with just the most popular interfaces. The GPIO is for items such as air conditioning request and analog output for older transmission controllers that need a TPS signal.(Or even just an analog gauge.) I have a lot of experimenting and coding to do!

I do have a steel enclosure I designed for this that will eventually be modified for the production boards. For this small batch of five development boards I am going to just 3D print some enclosures. As you said, there is too much feature creep, so I have already designed a new PCB that is...

They are here and I took a few minutes to solder on the through hole parts to board #1! I will be bringing these boards online over the next few weeks.

The fabrication company just sent me a picture of board number one! There are two issues with the solder mask that do not affect the board functionality that I will have to correct for production boards. Once they arrive I will make any repairs and assemble the through hole parts.

I did manage to reduce the size somewhat. Now I need to get a lot of sleep and do more rounds of checks before sending it off for manufacturing. The SD card slot was rotated 180º the wrong way and I almost did not notice.

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

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

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

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

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.

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.

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...

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...

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.

I have prototype hardware that I am using to add more supported vehicle buses. I am working on GMLAN and Chrysler PCI Bus right now(Finishing up a LS swap in my Wrangler.)