So, I've read thru the comm. specs and we're golden. All looks like it will work ok, and is pretty darn close to expectations.
I'd optimized out one RES line and will have to put it back in as the data is encoded across both lines. I've already done that in the schematic but have to lay that track again on the board. It'll be fine even though it's getting pretty tight in some areas now.
Also, for the k16s; are there many raised components on the back of the board? IE will we be able to use a flat heatsink that is bigger than the total board footprint, got an old TEC waterblock I'd love to use!
The whole bottom has been kept clear. No parts. There is mask over most of the area but exposed pads 1cm x 1cm under each chip. See bottom mask in gerbers on github for exact size/location. Small thermal pads or, even better, copper pads (I've seen these real cheap on ebay) between large heat sink and board would make ideal heat conductors but also keep the heat sink slightly off the board. I'll be trying different things when the time comes. Bicknellski is arranging some heat sinks coming my way that we can source cheaply.
another question for that is the ce, rohs certificate and an invoice because without export/import in eu is a problem.
and if we can arrange a better quantity the price should be lower (but think if something is sold from a company the guarentee must be considered and so there is some profit for handle that)
Ya, I don't know about that EU certification stuff. It's a bare board that doesn't plug into the wall. It should be classifiable as exempt under some special use gear for development purposes or something. You guys in the EU will have to figure out what all that means, and if you're going to have hassles during import.
I do know that the assembler in Bkk says they build to RoHS compliance if need be. So maybe they know how to get stickers etc.
Hmmm. Let me guess - if you had to wait 6 months to get a sticker, you'd be ok with that...
I though of that, but if I bought all the parts and put together the board and flashed it, how would it get a different serial number? You would have to have a programming station that serializes the firmware when programming each part.
Why on earth would you want a serial # if you bought a board and assembled it yourself? You can just make up whatever number you like.
PS: i am not mentioning the fact that there might be other usb devices in the system and multiple instances of cgminer to be executd one for Icarus one for Klondike and so on. Having the option to assign unique name to each ttyUSb will save us a lot of trouble. the cgminer will be feed with -S/dev/TTY accordingly
If USB protocol has a place to stuff in a serial# when attaching then I can have the PIC supply that info so you can do udev rules or whatever. I was planning to put a serial# in the flash code anyway, only so it'll have some unique ID. It does just appear as a serial tty device.
Our chances are bigger there i guess
