- Sun Jan 09, 2022 4:26 pm
#54624
Ardugauge 52 concept 1A.PNG (215 KiB) Viewed 3512 times
Ardugauge 52 concept 1B.PNG (265.83 KiB) Viewed 3512 times
Ardugauge 52 concept 1C.PNG (615.08 KiB) Viewed 3512 times
Recently I watched some videos on Speeduino YT being particularly interested in SpeedyKnock. You might also noticed my recent topic about my old prototype of universal gauge. Then I (re)spotted the topic of Ardugague by MielArrojado and it strikes me that what noisymime was trying to put together in here https://www.youtube.com/watch?v=vy3NvRq67BQ is in a big part a combined Ardugauge and my old project. So, I did a quick virtual mock-up based on my old design.
Cutting to the chase, here's a concept of a 52mm gauge with 128x64pxls OLED gauge and 25 RGB LEDs (neo pixels) on the circumference for "analogue" value displaying. It can reuse the code from Miel to serve as gauge showing data coming directly from Speeduino. Adding some conde can enable also the LEDs. Miel has used Arduino Nano but here I propose Micro Pro as it uses ATMega32U4 - the same as SpeedyKnock. It's not crucial to use same MCU but probably eases some stuff with USB transfer etc. Now, by adding TPIC8101 with bunch of passive components it can be used also as SpeedyKnock. One thing that is different is that I proposed I2C version of OLED (same as Ardugage, SpeedyKnock uses SPI) as it has less pins so it would have to be adopted in SpeedyKnock code. Also something requiring consideration is usage of Arduino module in terms of noise on analog path.
Perhaps it would be better to populate ATMega directly on main board but I would have to get some comments from noisymime on his experiences with TPIC.
As you can see it looks slightly Frankenstein like as there are 3 modules stuck to the main board - OLED, Arduino and DCDC converter. It's just cheaper this way ans saves space on the board. It might be even possible to put all soldered components on one side but that depends for example on how many capacitors are actually needed by neo pixels (I do not have much experience with those and data sheet stated 1uF for each).
I would love to hear your thoughts guys, especially from noisymime and Miel. I can make changes in PCB project quite quickly. I also have a concept for few 3D printed parts for mechanical structure and shaping ligh from LEDs.
Cutting to the chase, here's a concept of a 52mm gauge with 128x64pxls OLED gauge and 25 RGB LEDs (neo pixels) on the circumference for "analogue" value displaying. It can reuse the code from Miel to serve as gauge showing data coming directly from Speeduino. Adding some conde can enable also the LEDs. Miel has used Arduino Nano but here I propose Micro Pro as it uses ATMega32U4 - the same as SpeedyKnock. It's not crucial to use same MCU but probably eases some stuff with USB transfer etc. Now, by adding TPIC8101 with bunch of passive components it can be used also as SpeedyKnock. One thing that is different is that I proposed I2C version of OLED (same as Ardugage, SpeedyKnock uses SPI) as it has less pins so it would have to be adopted in SpeedyKnock code. Also something requiring consideration is usage of Arduino module in terms of noise on analog path.
Perhaps it would be better to populate ATMega directly on main board but I would have to get some comments from noisymime on his experiences with TPIC.
As you can see it looks slightly Frankenstein like as there are 3 modules stuck to the main board - OLED, Arduino and DCDC converter. It's just cheaper this way ans saves space on the board. It might be even possible to put all soldered components on one side but that depends for example on how many capacitors are actually needed by neo pixels (I do not have much experience with those and data sheet stated 1uF for each).
I would love to hear your thoughts guys, especially from noisymime and Miel. I can make changes in PCB project quite quickly. I also have a concept for few 3D printed parts for mechanical structure and shaping ligh from LEDs.
- By Kyleroberthammond
- By Piotr Pakulski
- By digmorepaka