Restored all the code that was commented out for ready for real canbus testing. Still need to stop the watchdog timer running when in wifi mode. The watchdog reboots everything if it does not see can messages in 10 seconds. This was as during cranking the voltage dropped and the canbus receiver became unstable.This isn’t likely now but the first prototype has no capacitors in the power supply.   Added a webpage button to check canbus driver status along with stats on queued packets and errors.   Fixed a mistake displaying the flash colour in webpage.   soldered some light sensors to wire and add heat shrink to keep it tidy ready for when needed.   The case I have spare has a couple of metal blocks in it that need to be removed. The early ones the glue was easy to remove, the current ones seem to have melted plastic not glue. It doesn’t dissolve and won’t melt before the case does if the blocks are heated. Guess to save cost they melt other products that fail QA and use them as glue. This one just happens to have been from higher melting point plastic product.  I ordered the other model with the battery to see if it has the metal blocks as well.  

Well it’s 1am and fixed all the current issues. Added the colour option for when it flashes which should have worked already but I had a read 16 bits in the 32 bit read code from a copy paste. Code to make canbus speed adjustable added, though the option was in web portal already. Started to add some formula options, default is STI but have Porsche and GR Yaris. Different model use different byte orders and modifiers to get rpm. Eg sti is just byte6 and byte5 joined to make 16bit number Porsche uses two bytes joined divided by 4. Which in binary jist removes the last two digits making it 14 bits. Yaris may use two bytes joined multiples by 0.8    I still have to figure out how to do the formulas while running, I may have a seperate function for each, then when it boots that function gets set as the canbus interrupt handler. It saves having a switch if bunch of if statements in the code that would run every can message. makes the code larger in storage, but faster in the most critical part.   Canbus code all needs a testing as the current chip has power off and listen only mode pins that can be controlled. Old version didn’t have this. But the old chip can be used on the new board if needed. Once it all updated and running it’ll need a complete rewrite as the Esp32 has new release of its core code to 5.5 which has all new canbus functions.

Found and fixed an issue with the RGB LEDs control dropping out. This was due to the pin used this time. The full incase build was pin 26, current test rig was pin 2 and now pin 4. There may have been an issue with power as the LEDs that show the wifi password are white and full brightness so draw 3x more current than when acting as a shift light. They also get toasty warm when full white compared to ambient when showing typical colours.   Finally added a test led function for the custom colour set. Once set in the web interface you can click a button to show those colours love on the display. Since you can only set half the LEDs color as it mirrors each side, when testing it uses the whole display with every other LED blank so it’s easier to interpret color and work out which number each one is.

That’s true, the plugs can vary quite a bit depending on the models and years of the vehicles. Having the donor vehicle's loom definitely makes a big difference, especially when you’re dealing with any complex connections. I agree—getting your hands on the wiring diagrams for both vehicles is a must. It’ll save you a lot of time and guesswork. Zotabet Casino website offers players an engaging online gambling experience with its diverse game selection and user-friendly interface. Once you have those, it’s mostly about matching up the corresponding wires and ensuring everything is properly secured and insulated. Just take your time, double-check everything, and it should work out fine!

Old post. But logging the twin turbo the ECV on my bh5 has control on the boost of primary at high duty cycle of the primary boost control , I'm remapping my ECU at the moment, but logging this setup is very different to what people think or think they know