Shrimping It at Cambridge

By -

Make your own Arduino clone

I've just come back from a Shrimping workshop at the /dev/winter conference in Cambridge.

I've run quite a few of these workshops now, and they have all been fun. Participants build the Shrimp, a low-cost Arduino clone on a breadboard, and start learning to program it using the Arduino IDE.

The Shrimp was developed by the Makers of Morecambe. The Morecambe Maker I've met is Cefn Hoile; he maintains the website and provides kits at an unbeatable price.

...and what to do next

Several of the workshop participants asked for advice about what to do next. There's a huge amount of information about Arduino techniques, libraries, shields and projects, but that's a problem in itself. Where do you start?

One option is to take the free Life After Blink e-course I put together for people who'd attended my Shrimping It! workshops. It's a series of online lessons, along with a google groups support group.

At some stage I will probably turn that into a low-cost ebook and/or a course on Udemy, but for now the on-line version is available, and free.

You'll need

  • about £10 worth of components (details in the course)
  • a computer running the Arduino IDE (under Windows, Linux or OS/X)
  • either a Shrimp or a commercial Arduino.
Sign up here. 






Comments

  1. Anonymous26 January 2015 at 10:30

    I do quite like the idea of the shrimp but I've been using the Arduino Micro for my solutions so far. I do notice that the prices for the Shrimp has gone right down so I may switch now.

    ReplyDelete

Post a Comment

Popular posts from this blog

Controlling a Raspberry Pi Pico remotely using PySerial

By -
Image
Update : I'm using thie code below in another project, and found that I had not correctly fixed the reported bug. The new version passes automated tests, and I am pretty sure it works OK. I have changed the name of the class to Talker  since it can both send and receive information. Apologies to all concerned for the bug! Introduction You can use a Raspberry Pi Pico as a powerful peripheral to a host - a Raspberry Pi, a Jetson Nano, a laptop or workstation. In this article you'll see how to interact with a Pico running MicroPython or CircuitPython by writing some Python code that runs on the host. The software is easy to use. It enables you to send a Python statement to the Pico and read the results. The statement can be any valid MicroPython code. Setting up the host and the Pico For this article I've used a Raspberry Pi as the host, but any computer running Windows, Linux or Mac OS will do so long as it has Python 3.5 or later installed. In particular, you can use this t...
Read more

Five steps to connect Jetson Nano and Arduino

By -
Image
Yesterday's post showed how to link a micro:bit to the Jetson Nano. One of the members of the (unofficial) NVIDIA Jetson Nano group on Facebook asked about connecting an Arduino to the Jetson. Here's a simple recipe for getting data from the Arduino to the Jetson Nano. It should work on all the Jetson models, not just the Nano, but I only have Nanos to hand. On request, I've added a recipe at the end of this post which sends data from the Jetson Nano to the Arduino; it turns the default LED on the Arduino on or off. The recipe for sending data from the Arduino to the Jetson has just 5 stages: Program the Arduino. (I used the ASCIITable example). Connect the Arduino to the Jetson using a USB connector Install pyserial on the Jetson Download a three-line Python script Run the script.   Programming the Arduino I used an Arduino Uno, and checked it on a verteran Duemilanove (above), but any Arduino should work. You'll need to do this step usi...
Read more

Raspberry Pi Pico project 2 - MCP3008

By -
Image
This post show you how to drive the MCP3008 8-channel ADC using a Raspberry Pi Pico. I'll start with a personally embarrassing and annoyingly relevant story. I'll also tell you about a minor 'gotcha' when using SPI on the Pico, and how you can avoid it. Finally, I've include the code and fritzing diagram I used to test the interface. First, the story. Back in 2012, when the Raspberry Pi was fresh and new, I was running a startup called Quick2Wire.  We made add-on boards for the Pi. Just before Christmas we sent out our first batch of boards to a small army of beta-testers. The beta boards didn't work. Somehow a single trace on the pcb had got deleted and one of the GPIO pins was isolated. The boards were still usable and it wasn't too hard to solder in a jumper wire to replace the missing trace, but it was very embarrassing. It wasn't just that we'd shipped boards with a defect. The really annoying thing was that I'd set up an  automated loop-bac...
Read more