987673 - Create device specific cradles for Eideticker harness

Status: RESOLVED WONTFIX

(Powertool Graveyard :: Hardware, defect, P3)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Currently the Eideticker harness is constructed using LEGO [1], which works well but is a little excessive when holding the device in place. It requires essentially building a frame for the device to slot into, whilst still allowing access to the hardware buttons and camera lens. It also means that the frame must be partially deconstructed in order to perform maintenance tasks on the device.

When trying out the battery harness created by Jonathan Hylands, I thought it would be relatively easy to tweak this for connecting to the LEGO harness. After speaking with Jonathan on IRC, he suggested that as we only need a solid mount point (we don't need the power monitoring for Eideticker) we could instead create a simple 3D printed cradle for each device.

The devices that we will need to mount for Eideticker are:
inari, hamachi, tarako, flame

Requirements:
* Device screen must be 100% unobstructed.
* Access to the USB port so we can keep the device plugged in whilst in the cradle.
* A LEGO compatible base, so we can connect the cradle to a LEGO 'podium'.
* Leave the hardware buttons and camera lens accessible.

Considering that some devices have the power cable attach at the top/side, this could have the effect of pulling slightly on the device. For these, it would be great if the cradle could be firm enough to resist this.

Looking at the devices I have to hand, I think a 2x8 compatible LEGO base [2] would give us the stability we need. For devices where the power cable attaches to the bottom, we could leave the middle 2x2 free, which should still give us a strong enough bond, but also allow us to accommodate the cable.

[1] http://blargon7.com/2013/09/building-a-harness-for-eideticker-with-lego/
[2] http://brickset.com/parts/300726

Comment 2

[Dave Hunt [:davehunt] [he/him] ⌚BST]

:glob It looks like we have a undesirable attachment. I've made it obsolete, but could you remove it entirely? Is there a procedure for reporting bugzilla spam?

Comment 3

[Dave Hylands [:dhylands]]

I reported on #developers and gerv disabled the account that added the attachment.

Comment 4

[:glob ✱]

The content of attachment 8412652 [details] has been deleted for the following reason:

spam

Comment 5

[:glob ✱]

(In reply to Dave Hunt (:davehunt) from comment #2)
> :glob It looks like we have a undesirable attachment. I've made it obsolete,
> but could you remove it entirely? Is there a procedure for reporting
> bugzilla spam?

deleted.

with regards to process, file a bug in the bugzilla.mozilla.org::administration component, or if it's urgent #bmo on irc is the best channel.

Comment 6

[Sylvestre Ledru [:Sylvestre]]

This project isn't maintained anymore.