johnridley: (555)
A couple of months ago I wrapped up physical packaging of the Duckon 20 blinkie kits, but I hadn't decided I was done with the firmware yet. Last night I sat down, tuned up a couple of the patterns, made one new one, then programmed and stickered 200 chips.

So that's in the bag.

Which, of course, means it's time to start thinking about the blinkie for Duckon 21.

Whew

Feb. 24th, 2011 10:03 pm
johnridley: (555)
194 kits packaged up, ready to go including spare parts. OK, I still need to program the controllers (those are not given out with the kits), but that won't take as long as putting these together did. This was 4 hours this evening.

There were 200 total, I built 6 as demos for Capricon.

johnridley: (555)
Everything showed up at once today. I got the blinkie boards and am quite happy with how they turned out, and both telescope equipment orders showed up today as well. Now I just have to see if I can get the telescope mounted on the dovetail rail and thence onto the mount.

I suppose if I'm snowed in tomorrow without internet service, I'll have something to do.
johnridley: (555)
Just got a ship notification from PCBCart! I was worried because Chinese Spring Festival starts next week and runs for 8 days, so if they didn't get it out today I might not have blinkies at Capricon. Now we'll see how long it takes DHL to get 200 boards from China to Chelsea.
johnridley: (555)
The board house sent me an email that they'd reviewed the order, found no problems and scheduled it for production. They say "delivery on Feb 10" - I don't know if that means they ship on the 10th or they expect me to have it on the 10th.

Normally they'd have it to me much sooner than that, most people seem to get their orders from them in 10 days worldwide, and that they pretty much always beat their estimates, but the Chinese spring festival is Feb 2-8, so I don't know. If they show up ON Feb 10, I will be able to solder together a few boards before packing for Capricon.

Oh well, they'll get here when they arrive. I do need to order up some other parts though, I originally only ordered enough parts for 100 kits.

EDIT: on lighter news, after hours of looking for someone who even HAD the LEDs that I want, it turns out that not only does DigiKey have them, but in 1000 quantity, they significantly undercut the Hong Kong/eBay sellers.
johnridley: (555)
I'm used to stuff from China, even in-stock stuff, taking 10 days to arrive. I'm seeing threads online that PCBCart delivers stuff in 10 days even though they have to make it first. Hopefully this is the case. I don't need most of them until June, but I'm supposed to have a few demos by Capricon to show off at the Duckon party.

Looks like I'm in just under the wire. They have a holiday Feb 2-8, and they say they knock off a couple of days before that, and won't be doing anything during that time. I should hopefully have my boards in hand before then.

Guess I'd better get moving on programming new patterns.
PCB rendering here )
johnridley: (555)
I did some final, niggling touch-up on the CAD files for the 2011 Duckon blinkie tonight. It's the first board I've ever sent out to have made, and the first board I've designed using CAD - in fact the first time I've used CAD for anything. I was pleasantly surprised at how trivial EagleCAD is to learn, and how pretty much impossible to screw up it makes board layout.

I've been through a bunch of tutorials on EagleCAD and been through design rule checks a dozen times and have everything cleaned up. It's a dirt simple board, but I'm nervous I've screwed something up. But I have a friend from work who's done boards before and he's looked at the Gerber files and assures me that it looks fine, and the prototype that I etched myself works fine.

I sent him a final copy, incorporating the last few nits that he had to pick, and assuming he doesn't come up with any show-stoppers, tomorrow I should be sending the files off to China to have the boards made. With luck there will be show-off boards at Capricon.

I guess I'd better get on eBay and order a whole crapload of LEDs now. And plastic bags to bag up the kits. Then at some point I'm going to have to write assembly instructions, but this is a damned simple blinkie so that should be easy enough.
johnridley: (555)
I haven't put together all the patterns for it yet, I have some ideas. The area around the chip is wretched because of the home-etched double-sided board; there's no feed-through so I had to disassemble an IC socket and solder the pins from both sides, which is really pretty difficult. I should buy some wire-wrap sockets to facilitate soldering on both sides. Either that or do all the chip stuff on the bottom and go to the other side with vias.

very short video behind the cut )
johnridley: (555)
I just had my first go at etching a circuit board in about 25 years. Last time I did it, I laid the board out on translucent grid paper using sticky pads and tape, and transferred to photosensitive boards.

This time I used Eagle CAD, and blue press-n-peel. I tried using a method that's been documented online, where you print onto cheap magazine paper and then dissolve that away in water. Screwed around for about 3 hours with that. I'm sure someone got it to work, but not me. It turns out I bought some press-n-peel blue transfer material about 12 years ago, and amazingly enough I actually stumbled upon it 2 days ago.

My printer (brother color laser) is really finicky about nonstandard paper, and wound up crunching my sheet of press-n-peel when it finally fed it; it took 5 tries to get it to pick it up. Finally I found a solution online, which is to print on plain paper, then cut out a piece of press-n-peel an inch or so larger than the pattern and tape it over the printed (centered) image on the paper (using the previous print as a location guide) then feed that piece of paper through again so the image is now printed on the press-n-peel. This also allows you to cut out and use only a small amount of press-n-peel. You must use masking tape, others will wreck the printer.

I etched using 1 part hydrochloric acid and 2 parts hydrogen peroxide. This worked great. In contrast to the traditional ferric chloride, this mixture does not stain everything it touches and it's fairly clear so you can watch progress more easily. The fumes are fairly irritating to the mucous membranes from what I've read, though not actually toxic as such. I just cracked a window and had no problems. Another advantage is that apparently this stuff can be refreshed by bubbling air through it; it becomes acid cupric chloride.

The etch isn't perfect, but I learned a lot and hopefully the next time it'll go better. Double sided is a real pain this way. I probably should drill a couple of holes in blank areas of the board in opposite corners and print fiduciaries on the board to line them up properly.

johnridley: (555)
So, I've been testing my blinkie prototype for Duckon 2011. I'm switching to coin cell batteries (CR2032) because honestly these days they're cheaper than four LR44s, and they have the same power capacity, is more compact and you can easily buy holders for them that are easily soldered on.

I chose a really low power microcontroller and put some nod in the firmware to power savings, and wanted to let the prototype run until it killed a battery.

This could take a while. So far it's been running for 32 hours, and though it's not as bright as when the battery was fresh, it's still going fine. It ran very bright for probably a good 18 hours.

Edit: 60 hours and it's still running, though dimming noticeably. For some reason the green is dimmer than the red.
johnridley: (Default)
I have the blinkie for 2011 about ready to start laying out board for. The circuit (little that it is) is confirmed working, I'm pretty much done with the software, I have a few patterns in it. I'm currently running a runtime test; since this is a new CPU and a new battery, I want to make sure that the runtime is reasonable before laying out the board, and certainly before paying to have some made.

The blue car seems to have gotten a broken headlamp lens somewhere, and since they're both rather yellow and tired looking, and it's only a little more to get both than to get one, I ordered up a new set on eBay. $80, and installation is about 5 minutes for each. I was going to try to polish them up anyway as the yellowing lenses have been reducing output, so I suppose this is the lazy man's way out.

The 15" telescope goes back in the van this afternoon, and tomorrow around lunchtime I drive to Toledo to deliver it to the buyer. In the spring I *might* decide to pick up a new scope, much more modest and portable, and a modest 3 or 4 eyepiece set, and limit myself to the moon and planets. But only if the mood takes me, and at this point it doesn't feel like it will.
blinkie video behind cut )
johnridley: (555)
This was goal #3 in getting this blinkie up and running. This was the last significant hurdle as far as the software is concerned. Now I just need to develop some nifty patterns. I may add one more thing, which is a simple pushbutton for on/off and modes, rather than just an on/off switch. Depends on how the patterns go.

I was kind of dreading this step because interrupts on this chip was one thing I knew nothing about, and I must admit I was dragging my feet on getting to it, but I finally decided I'd better get moving. I was tearing my hair out for about an hour because the compiler kept optimizing out all my pattern generation code. Finally I realized that I had to define the values as volatile, and it started right up.

Of course the board needs to be laid out but I have a friend who will help with that (I don't know the CAD software used and he's done a ton of this stuff). I also need to determine how long it will run off a CR2032 battery (I did test that it DOES run off one today) - and also I need to see if I can decrease the duty cycle of the LEDs without a lot of difference in brightness - that will increase battery life.

Depending on battery life, I may have multiple options. Two AAA cells on the back would run it for quite a long time but would be too heavy for earrings, OK for a necklace.

CR2032s in quantity are QUITE cheap, on the order of 12 cents, but I don't know what my runtime would be with them. A single CR2032 has very nearly the same energy as the four LR44s that the previous blinkies have been using (3v x 225mAH = .675 watt hours, vs 6v x 120mAH = .72 mAH) but it's a lot smaller and lighter and both the battery and the holder are cheaper.

johnridley: (555)
The charlieplexing code is now 100% working. I'm getting some ghosting but that's a circuitry problem and I suspect that it actually has to do with the prototyping board that I'm using. Next time I work on this, I'm going to take the chip off and put it directly on the board and see if the ghosting remains. If it does I have some head scratching to do because my code is pretty much identical to other code I've seen online.

I'm going to order up some Tiny85 chips - I ordered Tiny13s because that's what I'm familiar with, but the Tiny85 is the same chip with 8x as much RAM, which means probably 20x more patterns (lots of the first chunk of RAM will be taken by just the basic code, not pattern code). The difference is only 25 cents ($1.33 versus $1.08). Total parts for this unit may be as low as $3, though the board will probably cost a couple of bucks.
johnridley: (555)
I have a preliminary charlieplex display driver written, and it mostly works. One line is not being driven properly, so there's some little bug in it somewhere. Fairly promising though. I'm writing this in C so it's a hell of a lot quicker and easier to program - so far it's only about 50 lines of code. It isn't doing patterns yet. Those aren't hard but they're time consuming.

The code isn't interrupt driven yet, I want to do that so that I can totally ignore display timing and write code that does nothing but worry about pattern timing. Totally separating the two will make things easier to program.

I also have to learn about sleep mode and prove the concept of using a single pushbutton switch and deep sleep mode as a substitute for "off" mode.

I may have something in rough prototype (still on breadboards and development boards) at Windy.

Once I get it on stand-alone breadboards, I need to try to do some current measurements and see how long it runs off various batteries, then I can think about starting to lay it out.

I also need to decide whether to try to make it reprogrammable in circuit.
johnridley: (555)
I fixed the wiring bug that I had in the basic charlieplexed prototype that I put together over the weekend. The wiring is confirmed OK. I also drew some charts by hand to make sure I understood what was going on.

Then I got the STK500 development board powered up and a ATTiny13 chip installed and jumpered properly, and wrote a 4 line test program to just blink the first 5 LEDs on and off.

The major issues are:
- figure out how to do deep sleep mode and how to wake from it with a switch on an input
- build an interrupt driven charlieplex display driver.

These are really the only two issues. Doing the patterns and stuff on top of this will be pretty trivial.

Then I need to learn how to use Eagle CAD to lay out the board. I do know a couple of guys at work that have done that before though so I have a resource.

July 2025

S M T W T F S
  12345
6789101112
13141516171819
20212223 242526
2728293031  

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 28th, 2025 06:11 am
Powered by Dreamwidth Studios