FA+
Shop
Build 4: The Challenge
14 years ago
General
Some journals are personal, and some journals are business related for Kinzart. For everything else, I don't care.
Build 3 is proving to be a migraine inducer like no other. I've been busy trying to remove the jittering bug on my eye blink modules, but to no avail.
To somewhat explain my progress notes, this is how they operate in a simple line.
Build -> Prototype -> Candidate -> Release
The build refers to the coding in the chips and increases with each major revision to that. Prototypes refer to the breadboards I export the builds to. The number for the prototype does not have to increase with each build (as build 1 worked fine on prototype 1 as much as build 2 did). Candidates refer to perf board versions of the breadboard designs. In this case, the one I posted on my FA so far is Candidate 1, Prototype 1, Build 2 (or v0.1.1.2). Release refers to actual market boards (printed PCBs, packaged with instructions, etc). So far I have not built 1 release board yet as I really want to fix the jitter bug first.
On Build 3, I origionally tried to control the power to the servos with a N2222 transistor by applying 5v to it when I want power to flow and take it away when I want to halt power. This would mean during the idle times, the servos would not be powered. With talks with friends, I've tried to instead control the PWM signals instead. This has worked partially, but for some odd reason, the ATTiny85 seems to be doing the OPPOSITE signals I want, but likewise with the transistor.
I seem to be getting 5v on my multimeter from the processor on the pin that is to control the transistor, but none when it's supposed to be sending a HIGH signal (5v). The issue is the actions of the transistor seem to state otherwise, so I'm at a near loss on understanding why that is the case. Either way, it does HEAVILY drop the jittering sound, but until I can truly control the transistor, it is still there, and the last thing I want is to have my first release a product to possibly cause frustration to either end user (the costume designer or the customer of the designer).
I'm curious about the use of capacitors, but I also know they tend to die out over time. The last thing I want is to have a module have a short lifespan, even though that would mean that more profits to me (i.e, people would have to buy replacement modules). I am a firm believer in "do it right the first time so you don't have to do it again." I'd rather be known for sturdy devices and have fewer sales than have to deal with replacing simple parts and sending modules.
Build 4 will focus on using a potentiometer to allow designers to adjust the angle the eyes close down. It will require a small screwdriver so that it won't accidentally be adjusted. I'm thinking about using the jumper to adjust which development mode the module is in by having the jumper inserted to activate 'open' mode (where the eyes remain open) and taking the jumper out and putting it back in before the module blinks again to activate 'closed' mode, where the module will close and stay closed. This will allow the designer to adjust the angle of the module's actions.
I hope to have more updates later on.
-Flame
BE SURE TO CLICK HERE FOR THE BLINK MODULE PICTURES AND HERE FOR THE YOUTUBE VIDEO!
To somewhat explain my progress notes, this is how they operate in a simple line.
Build -> Prototype -> Candidate -> Release
The build refers to the coding in the chips and increases with each major revision to that. Prototypes refer to the breadboards I export the builds to. The number for the prototype does not have to increase with each build (as build 1 worked fine on prototype 1 as much as build 2 did). Candidates refer to perf board versions of the breadboard designs. In this case, the one I posted on my FA so far is Candidate 1, Prototype 1, Build 2 (or v0.1.1.2). Release refers to actual market boards (printed PCBs, packaged with instructions, etc). So far I have not built 1 release board yet as I really want to fix the jitter bug first.
On Build 3, I origionally tried to control the power to the servos with a N2222 transistor by applying 5v to it when I want power to flow and take it away when I want to halt power. This would mean during the idle times, the servos would not be powered. With talks with friends, I've tried to instead control the PWM signals instead. This has worked partially, but for some odd reason, the ATTiny85 seems to be doing the OPPOSITE signals I want, but likewise with the transistor.
I seem to be getting 5v on my multimeter from the processor on the pin that is to control the transistor, but none when it's supposed to be sending a HIGH signal (5v). The issue is the actions of the transistor seem to state otherwise, so I'm at a near loss on understanding why that is the case. Either way, it does HEAVILY drop the jittering sound, but until I can truly control the transistor, it is still there, and the last thing I want is to have my first release a product to possibly cause frustration to either end user (the costume designer or the customer of the designer).
I'm curious about the use of capacitors, but I also know they tend to die out over time. The last thing I want is to have a module have a short lifespan, even though that would mean that more profits to me (i.e, people would have to buy replacement modules). I am a firm believer in "do it right the first time so you don't have to do it again." I'd rather be known for sturdy devices and have fewer sales than have to deal with replacing simple parts and sending modules.
Build 4 will focus on using a potentiometer to allow designers to adjust the angle the eyes close down. It will require a small screwdriver so that it won't accidentally be adjusted. I'm thinking about using the jumper to adjust which development mode the module is in by having the jumper inserted to activate 'open' mode (where the eyes remain open) and taking the jumper out and putting it back in before the module blinks again to activate 'closed' mode, where the module will close and stay closed. This will allow the designer to adjust the angle of the module's actions.
I hope to have more updates later on.
-Flame
BE SURE TO CLICK HERE FOR THE BLINK MODULE PICTURES AND HERE FOR THE YOUTUBE VIDEO!
