shrimpingit / projects Goto Github PK

Although V-USB's firmware-only USB implementation (as used in the Conductive Keyboard build) is shared via GPL, they also ask that project details are shared with an image etc. When project information is complete, we should submit this information to them.

There could be a benefit to moving the 9-pin header inwards for all builds. Need to check if there's any exception to this. Currently the Memory Game and Conductive Keyboard builds all benefit from access to the extra pins from the outside. Might be a trend.

On the plus side, by doing this extra step in the build, learners get to find out that components can be moved horizontally for convenience without changing the circuit. On the negative side, there's a variation compared to Blink which could introduce problems (especially since the reset pull-up resistor also needs to be moved and might be replaced incorrectly). This could be handled in the instructions, by suggesting a Blink verification after moving the components?

Benefits:

• Builds have fewer variations compared to the Blink circuit
• Reset button actually more accessible/usable in protected build

Costs

• Protected Shrimp
  • some clear space either to the left or the right of the header is needed for the button
  • the capacitor positioning for crystal caps and decoupling caps could be a blocker
• Vector Graphics
  • a lot of rework will be needed, especially to handle re-routing of Rainbow cables.

To copy/paste a Tact switch a 'Reset Button' layer was made visible which should be hidden again for the Alarmclock project. No reset button is required (and on its own it's not fully wired to be functional anyway).

There is a 'Requires:' aside on the Alarmclock Kit cover which goes over the bounding box, which makes cutting the covers from A4 (with Blink on the back) a bit problematic.

File at https://github.com/ShrimpingIt/projects/blob/master/vector/alarmclock/kit.svg

Yellow has been assigned to 'Data' more consistently, meaning a switch of the wire colour for the Serial Wakeup line, as well as for the I2C line. Eventually this colour convention will continue with LED clock too. The text build instructions for each build needs to be updated to match.

Thanks to @benjaminwohl

Could use Binary to simply light up a fixed text/image sequence, this is a simple development from Blink plus a for loop (which could also be illustrated by e.g. a Larson scanner).

Currently the Conductive Keyboard build has a suggestion to remove a pin from a header.

This should ideally not be necessary, and instead a horizontal move of the header should be suggested as there is space to simply reposition it.

Potentially, this horizontal move should be proposed as an initial step, meaning the 'bonus pullup' is no longer a special case to be handled, and can be added along with all the other left-hand pullups. It's feasible to try and normalise this header-move also for the Memory Game?

All builds incorporating LEDs should have LED orientation clarified.

Status check...

There is a 2.2kOhm resistor as part of the Conductive Keyboard build, which should be a pull-up for the white wire D+ not the green wire D-.

It would also be a good idea to use 'highlighting' of some sort instead of the male pin headers to show the locations of active points where MakeyMakey keys can go, which makes it flexible to wire them in different ways (e.g. with long jumpers stuck into bananas or with conductive tape).

Additionally the programming header should be moved across like in the Memory Game build to make it easier to wire pull-ups.

Consequently, the build diagram needs to be updated.

Currently the Alarmclock kit graphic doesn't draw attention to the fact it's quite useful to have a battery pack for running a clock project for a long time. Could use the 'suggested' aside already in use on other vector graphics.

add call to player.silence() at end of loop() to turn off sound when 1min alarm time has elapsed

It's feasible to add Arduino pin numbers to the diagrams for reference, instead of the chip image, making it easier for learners to relate the software pin numbers to the hardware.

1. A quick reaction game...
   https://www.raspberrypi.org/learning/quick-reaction-game/worksheet/
2. A set of 'QI' quiz buzzers with a different tune triggered by each button.

The Fritzing rail assignments may conflict with recent breadboards we've seen. Should document and decide which way to jump.

Currently, the Memory Game and POV are architected to assume you will turn them on and off manually, and consequently it's easy to run batteries flat. It might be useful to incorporate the low power behaviour prototyped in the AlarmClock, relying on an interrupt from a button (or tilt-switch in the case of the POV) and optionally serial to wake.

If the Piezo resistor (control wire) is attached to a PWM-capable pin on the left hand side of the chip instead, it means it's easier to wire the LCD module which uses all 5 pins down the lower right hand side of the chip, whilst still keeping Alarm clock functionality.