A nested subroutine code structure lends itself well to the light saber project.
By Julian
Youtuber, shed dweller, solar charge controller aficionado
Good morning all…
Youtuber, shed dweller, solar charge controller aficionado
This site uses Akismet to reduce spam. Learn how your comment data is processed.
When are you going to do this again we haven't seen the completed result
O_O'''
This might make a good POV wand, now there's a programming challenge.
Youtube.. The only place where you can get away with flipping the finger when explaining stuff 😀
Love your channel, very informative and inspiring. You make me do lots of funny stuff with electronics 🙂
That light saber is far to slow. Studies estimate the speed of the light saber extend time to be in the order of 100ms to 150ms. Hmmmm – all this coding / work for 100ms of entertainment. You should have used an arduino – decimated your lines of code decimated your dev time and decimated your extend time.
The Force is strong in this one.
I don't understand PIC coding and all those syntax's and what Jullian does with the PIC. can someone help me with some tutorials where I can learn it from scratch?
Why use hexadecimal (0x20) for the led counter? Can't you just use a decimal constant (32)?
Julian, use the red leds you must and join the dark side 😉
Thank you Julian, you've completely reminded me of my assembly days, the instinct to critique your code is overwhelming!.
You said it yourself though… 50k subroutine calls with two free nops in every call, certainly not optimized!
hi julien could you try to control b3603 or b3606 from arduino either via serial or directly so then you could make a better bench psu
That's why almost all programming languages allow you to comment your code.