Liberate the Liberty
This WILL BE what the future of engine swaps looks like....
Last edited by Jimbo1367; Sep 10, 2019 at 09:07 AM. Reason: Autocorrect
The Best V8 Stories One Small Block at Time
Probably the biggest thing that's kept me from doing much else with the hardware designs was that the main processor the module runs on(it uses 3 processors total) does not yet have bit locking enabled to prevent someone from reading the program back out of the processor. Now that may seem petty but I've dealt with that once and have no intentions of letting it happen again. There are other processors I could probably use that I'm able to lock right now but nothing nearly as powerful as what I've been using. I don't know exactly how much processing power it would take to keep everything working the way it is right now since the 4 that I've used throughout development are pretty hard to compare.
Using a 16mhz processor was beyond laggy unless you were only doing one or 2 gauges.
Using an 84mhz processor it greatly improved and I could drive all 4 gauges with minimal lag but warning lights were out of the question as they took to much overhead to deal with.
Overclocking the 84mhz processor to 120mhz took care of the gauge lag but adding in control of the warning lights started to make things lag again.
The processor I'm currently using runs at 600mhz and is able to processor data similar to how a dual core CPU works and is able to flat out smash though anything I throw at it with out ever skipping a beat.....and this is the processor that I'm not currently able to lock out from dumping the code off it.
So I would either need to find another processor that was capable of executing code similar to a dual core or I would need to find something significantly faster then a 120mhz chip to use.
Since both the Jeep and Ls computers are both VERY slow protocols by the time the conversion module has read data from the LS computer enough time has past that the data read is already on the edge of lagging so by the time that data is formatted and converted to work with the Jeeps data bus and then transmitted onto the Jeeps bus that by the time the Jeeps cluster/bcm have processed the data it's been long enough that you can clearly tell the data is no longer being displayed in real time. The only way I was able to "make up" for the lack of speed on both sides of the data bus was by throwing a very large processor in the conversion module at the situation. If either the Ls computer of the Jeep was using CAN this would be an whole different situation and processor speed wouldn't be nearly as crucial....and before anyone says something. NO, there is not any version of this that works CAN, I'm just pointing out the fact that these data buses are extremely slow and the reason this has been difficult with out running into any type of lag.
great work I imagine a lot of BMWswaps could use this CAN conversion











