No, not at all. Most will just point out there are several ways to accomplish what the thread starter wants to do. Go with discrete components or just use a uC. The idea being to provide options. More than one way to get from point A to point B. The thread starter needs to find his own comfort zone as to making the box. Nobody is "harping" on using a uC but pointing out it's feasible as is going with discrete components.Here come the uC harpies…
Fixed.that video is private
Ummm . . . . . . .As you design this, remember that each line of Arduino code is about equal to one solder joint.
Ha - care to count? Post your design and I'll post the code. Likely, the code will need less lines than pins that need to be soldered in any logic chip solution. An Arduino is the right answer for this project.Ummm . . . . . . .
No.
ak
Don't know if you saw it but I have something similar in post #10..Of the discrete digital approaches discussed, I like the shift register the best. One CD4093 gate as the clock oscillator, one 8-bit and one 4-bit SIPO shift register, and the other three 4093 gates to manage the load and recycle.
But I like the LM391x idea better. I've never tried this, but it seems to me that a simple R-C ramp driving the LM3915 logarithmic bar graph device will produce linear bar movement, Looks good on paper. One LM3915, one LM393 dual comparator to manage the ramp and reset the ramp capacitor. Overall, around 50 soldered pins.
If you can't find a 3915, the same approach will work with a 3914 if you replace the R in the R-C ramp generator with a 1-transistor current source.
ak
I know. When I said I liked the 391x approach, I was referring to posts 9 and 10.Don't know if you saw it but I have something similar in post #10..
It isn't supposed to cycle automatically and continuously (not what the TS wants). You have to press the button to start the ramp. The TS will use a toggle switch in place of the button.I know. When I said I liked the 391x approach, I was referring to posts 9 and 10.
In #10, I don't see a feedback path to cause the circuit to cycle automatically for a continuously changing display.. Am I missing something?
ak
void setup(){
byte outputs[] = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13};
for (byte i=0; i<sizeof(outputs); i++){
pinMode(outputs[i], OUTPUT);
digitalWrite(outputs[i], HIGH);
}
pinMode(10, INPUT); //start
pinMode(12, INPUT); //reset
}
void loop(){
while (digitalRead(10) == 1){
delay(1);
}
for (int i=9; i>-1; i--){
digitalWrite(i, LOW);
delay(1000);
}
while (digitalRead(12) == 1){
delay(1);
}
for (int i=0; i<10; i++){
digitalWrite(i, HIGH);
}
}
NO! Not really. That is not even adequate for program files copied from an article.Ummm . . . . . . .
No.
ak
Oh, great - ratiional thought. Who the **** let you in here? Someone call the mods!Given the raging discrete vs. MCU controversy I hesitate to comment, but perhaps I can outrage both camps by suggesting WS2812 addressable LEDs. They have the advantage of requiring fewer pins, offering a very wide color palette, and enabling effects.
You are correct. I misinterpreted the description in post #4 as a continuous loop.It isn't supposed to cycle automatically and continuously (not what the TS wants). You have to press the button to start the ramp. The TS will use a toggle switch in place of the button.
by Jake Hertz
by Aaron Carman
by Duane Benson