G'day Josh - I am so pumped that you (and the Speeduino community) have really ramped up the activity in recent months - especially the 'Drop Bear' project as I have more than 4 cylinders in my future... Having been watching the project from the outside for many years, I am now starting on an implementation for a mates car. This has really opened my eyes to how inclusive and complete the Speeduino offering is, now I find myself looking for more projects to run another one!
Thanks again Josh for taking the time to go through the details, great insight into the options, pros and cons and vision for the future of the project. Thanks for keeping the non electronic genius users in mind.
HI Josh, Great stream unfortunately i didn't catch it live, Just a couple of thoughts on ST32F4, They support USB DFU (Device Firmware Update) and its fairly easy to setup on Windows and Linux and in our experience its almost as easy to use as the AVR 2560 system and requires no coded boot loader as its chip based rom code, the only thing is single button press to enter the rom or this could done over comms. Other thoughts would it not make sense to add a higher order active filter around the op amp circuit as your adding an the amp anyway. Other major differences between the 2560 and the other micro`s is ADC speed and resolution, i guess this would be more interesting to advanced functions like say Knock with internal tunable filtering. - Happy to take a side discussion if you want to chat about any of these items. Cheers Ben
Speaking only of the microcontroller specs and pricing, I think the MKE14F is one of best choices; 5v operation, 4kb of EEPROM, 168 Mhz, $2 in 10k quantity, -40 to 105 C operating temp. The MK64512 on the teensy has a badass internal voltage ref and 2x 16-bit ADCs, it is a shame that analog signals have to go through a voltage divider and an LM324 before it reaches the ADC.
I just discovered Speeduino and I’m thinking about making one for my 06 Mini Cooper. It has a DBW system. I think I can build a H bridge controller for the DBW. I have a strong automotive and electronics background. What are your thoughts? Also with the Teensy board, wouldn’t it be easier to supply the sensor with 3.3V instead of 5V? Instead of stepping down the 5V signal to 3.3v.
53:40 That switch statement makes me sad. :( Why not make a wizard that lets you select different things that you need for your engine, and then compile only what you need? If you only need 1 VE table, why use up the memory for any more? That would allow for a bigger map too (if memory is an issue for the board one selects).
"The outcome is still toast" Proper laughed out loud at that simple but bang on analogy!
Thanks again Josh, these sessions are so good!
G'day Josh - I am so pumped that you (and the Speeduino community) have really ramped up the activity in recent months - especially the 'Drop Bear' project as I have more than 4 cylinders in my future... Having been watching the project from the outside for many years, I am now starting on an implementation for a mates car. This has really opened my eyes to how inclusive and complete the Speeduino offering is, now I find myself looking for more projects to run another one!
Thanks again Josh for taking the time to go through the details, great insight into the options, pros and cons and vision for the future of the project. Thanks for keeping the non electronic genius users in mind.
HI Josh, Great stream unfortunately i didn't catch it live, Just a couple of thoughts on ST32F4, They support USB DFU (Device Firmware Update) and its fairly easy to setup on Windows and Linux and in our experience its almost as easy to use as the AVR 2560 system and requires no coded boot loader as its chip based rom code, the only thing is single button press to enter the rom or this could done over comms. Other thoughts would it not make sense to add a higher order active filter around the op amp circuit as your adding an the amp anyway. Other major differences between the 2560 and the other micro`s is ADC speed and resolution, i guess this would be more interesting to advanced functions like say Knock with internal tunable filtering. - Happy to take a side discussion if you want to chat about any of these items. Cheers Ben
FPGA + uC, the uC does the calculations, the FPGA does the timing critical parts and trigger decoding like the angular timer in pic16f1619 controller.
Speaking only of the microcontroller specs and pricing, I think the MKE14F is one of best choices; 5v operation, 4kb of EEPROM, 168 Mhz, $2 in 10k quantity, -40 to 105 C operating temp.
The MK64512 on the teensy has a badass internal voltage ref and 2x 16-bit ADCs, it is a shame that analog signals have to go through a voltage divider and an LM324 before it reaches the ADC.
Great video, thanks Josh
I would vote for STM32F4 series
I just discovered Speeduino and I’m thinking about making one for my 06 Mini Cooper. It has a DBW system. I think I can build a H bridge controller for the DBW. I have a strong automotive and electronics background. What are your thoughts? Also with the Teensy board, wouldn’t it be easier to supply the sensor with 3.3V instead of 5V? Instead of stepping down the 5V signal to 3.3v.
need to add support for h6 subaru trigger wheel frustrated its all i need to finish my build :(
53:40 That switch statement makes me sad. :( Why not make a wizard that lets you select different things that you need for your engine, and then compile only what you need? If you only need 1 VE table, why use up the memory for any more? That would allow for a bigger map too (if memory is an issue for the board one selects).
thanks much for all that work. 3000 view..such a shame