[OpenTRV-dev] Current rough to-do list top
Bo Herrmannsen
EMAIL ADDRESS HIDDEN
Mon Oct 21 12:07:49 BST 2013
would it be wrong to have case as an task in opentrv calendar running from
last night until weekend?
just to show the world what we work on... can be extended if need be
-----Oprindelig meddelelse-----
From: Damon Hart-Davis
Sent: Monday, October 21, 2013 1:05 PM
To: Bruno Girin
Cc: Damon Hart-Davis ; Closed list for developer discussions ; Bo
Herrmannsen
Subject: Re: Current rough to-do list top
Getting a full OpenTRV box first pass kinda sorta ready this coming weekend
would be in gloriously good time! Gives us lots of elbow room for
iteration.
Rgds
Damon
PS. Just 3D printed a set of 'Roman' pan-pipes for my daughters school
project, and they sort of work! I am flabbergasted! B^>
PPS. Have family birthday on Sunday but Saturday potential free on my side!
On 20 Oct 2013, at 20:56, Bruno Girin wrote:
> Damon,
>
> That's fine. I have a DD1 PCB. I'll check Bo's PDF to see if I have enough
> info in there. What I suggest we do then is that I create the box as per
> the dimensions in the PDF and as soon as we have a real PCB, we do a test
> print. As you saw last time, it is really easy to iterate if we need to
> change something.
>
> The one thing I may not be able to work out from the PDF is the variation
> between versions (e.g. USB vs batteries) but I can still start and we can
> validate the design once we have the first PCB.
>
> In this case, when would be a good deadline for you to have a first
> version? Bearing in mind that I have lots of evening events this week, I
> may struggle to have anything ready before the weekend: would that work?
>
> Bruno
>
>
>
> On 20 October 2013 20:47, Damon Hart-Davis <EMAIL ADDRESS HIDDEN> wrote:
> Hi Bruno,
>
> (Mark: could you help manage the detailed logistics of this box + PCB
> mechanicals/fab part?)
>
> We can't put one of the real new REV1 PCBs in your hands for at least 3
> weeks. And there will be the Bo and PMS variants which will probably be
> slightly different in various parameters unless we are super-careful.
>
> We do need to try to have the box as near ready as possible by the time we
> do have the PCBs so that we can assemble complete units without delay.
>
> However, if Bo can confirm that the REV1 size, shape and mounting-hole
> locations are exactly as per DD1, then I think you may already have one of
> those (or I can give you one).
>
> We can probably assume for now that component height on the SMD side is no
> worse than the DD1 populated board too, and there is only the FDTI
> connector, AVR (possibly socketed), LED and LDR (IIRC) above the board.
>
> The micro USB is below the board if used, I believe.
>
> We'll need to deal with buttons. We don't have to use the Maplin ones and
> could try to find shallower devices to minimise case volume. (At a pinch
> for future revisions we could consider side acting ones mounted on the PCB
> for example.)
>
> Maybe if we get you an accurate series of high-red PNGs you could work
> from them for micro USB cutout placement, etc?
>
> I'm happy to try to do a box design session on whatever terms suit you.
>
> Rgds
>
> Damon
>
> On 20 Oct 2013, at 20:18, Bruno Girin wrote:
>
> >
> >
> >
> > On 20 October 2013 19:35, Damon Hart-Davis <EMAIL ADDRESS HIDDEN> wrote:
> > * BOM and how to deal with LDR, LED, AVR, RFM23, reg (link?)?
> >
> > * Batteries vs USB supply count?
> >
> > * ENIG finish
> >
> > * Preallocation of initial runs to users and DHD R&D bench
> >
> > * Run numbers (20 iTEAD/Bo, 30 PMS)?
> >
> > * Box OpenSCAD/STL including fudge factors for 'overprint'.
> >
> > Fudge factor won't be too difficult. I'll do that sometime during the
> > week. For the box, the best way would be to have a box design session
> > with a real PCB and a pair of callipers.
> >
> >
> >
> > * AVR/RFM RX code
> >
> > * Power-on-self-test code suitable for Bo and PMS to use also.
> >
> >
> >
> >
> > --
> > Bruno
> > Visit my weblog: http://brunogirin.blogspot.com
>
>
>
>
> --
> Bruno
> Visit my weblog: http://brunogirin.blogspot.com
More information about the OpenTRV-dev
mailing list