https://blog.usedbytes.com/posts/ Recent content in Posts on usedbytes:Blog Hugo -- gohugo.io Sat, 07 Jan 2023 00:00:00 +0000 https://blog.usedbytes.com/2023/01/astro-slide-early-impressions/ Sat, 07 Jan 2023 00:00:00 +0000 https://blog.usedbytes.com/2023/01/astro-slide-early-impressions/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- Earlier this week, on the 3rd January 2023, a nearly 3-year saga entered it’s next phase: I finally received the Astro Slide 5G Transformer I backed on Indiegogo back in May 2020. The original estimated delivery date was March 2021, so it’s been A While. https://blog.usedbytes.com/2022/08/screenmachine-flm-images/ Thu, 11 Aug 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/08/screenmachine-flm-images/ When I visited recently, my Dad gave me a challenge: He handed me a box of 3.5" floppy disks1, which hold lots of images of minerals from an electron microscope. The challenge: Turn the images into something viewable with a modern computer. I don’t have any computers with a floppy drive, though I do have a bunch of floppy drives not in computers ¯\_(ツ)_/¯. I did think my 11-year-old desktop had a floppy connector on the motherboard, but alas not. https://blog.usedbytes.com/2022/06/3d-printed-terrain-models-using-os-open-data/ Tue, 28 Jun 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/06/3d-printed-terrain-models-using-os-open-data/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- Images on this page contains OS data © Crown Copyright (2021), used under the Open Government License Some years ago, in 2018, a relative of mine mentioned in passing that they’d quite like a 3D model of the area where they live, as it’s geographically complex and hard to get a sense for from ground level. https://blog.usedbytes.com/2022/06/m0o-shepherds-pi/ Mon, 13 Jun 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/06/m0o-shepherds-pi/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- The last of the three “prescribed” challenges is Shepherd’s Pi. In this challenge there are 6 sheep which need herding into a pen, and 3 wolves which must not be “killed” (knocked over). Challenge Decisions I started out hoping to do all three challenges autonomously, but when it came down to it I’ve had to complete Shepherd’s Pi via remote control. https://blog.usedbytes.com/2022/06/m0o-natures-bounty/ Sun, 12 Jun 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/06/m0o-natures-bounty/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- After tackling Hungry Cattle, Nature’s Bounty is next on the hit-list. Lots of videos/pictures in this post, because I think it helps a lot with explaining how it all works. The challenge is pretty daunting: The robot must find an apple tree, and pick 12 apples from it, three times in a row, in 5 minutes or less. https://blog.usedbytes.com/2022/06/m0o-hungry-cattle/ Sat, 11 Jun 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/06/m0o-hungry-cattle/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- Hungry Cattle is probably the easiest of the three main Pi Wars challenges to do autonomously and so is the one I chose to tackle first. The basic premise is delivering “cattle feed” (rice) to three troughs, placed at known positions within the arena. https://blog.usedbytes.com/2022/05/m0o-computer-vision/ Sun, 29 May 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/05/m0o-computer-vision/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- To be able to locate the different game pieces in the Pi Wars challenges M0o+ has a very basic camera. M0o+ is using a Pico for all the processing, so there’s really no chance of porting OpenCV to it. https://blog.usedbytes.com/2022/05/m0o-software-overview/ Sun, 15 May 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/05/m0o-software-overview/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- I’ve written a number of posts now about different “building blocks” which make up M0o+: The bootloader The network/bluetooth interface The chassis The camera The boom, parts 1, 2, and 3. There’s one crucial element missing from that list, which is needed to turn a collection of parts into an actual functioning robot than can compete in Pi Wars: The Software. https://blog.usedbytes.com/2022/05/m0o-boom-part-3/ Sun, 08 May 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/05/m0o-boom-part-3/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- Last time, I derived the Forward Kinematics for the boom on M0o+. If you haven’t read the first two posts, then this one won’t make much sense (and I don’t want to repeat myself 😄): https://blog.usedbytes.com/2022/04/m0o-boom-part-2/ Sat, 02 Apr 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/04/m0o-boom-part-2/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- This post is the second in a trilogy detailing the boom on my Pi Wars 2022 robot M0o+. In the last post, I wrote about the mechanical and electronic design. In this middle post, I’ll be describing the equations which let me find out where the end of the boom is, and next time will go into the equations which let me control where the end of the boom is. https://blog.usedbytes.com/2022/03/m0o-boom-part-1/ Mon, 28 Mar 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/03/m0o-boom-part-1/ So clearly there are some issues to work out, but this was bit-banged from an OV7670 on a Pico. PIO next. #raspberrypi #PiWars pic.twitter.com/yJFQFhU9Xk — Brian Starkey (@usedbytes) September 14, 2021 [M0o+](https://blog.usedbytes.com/tags/m0o+/) -- My Pi Wars at Home 2022 robot M0o+ is intended to resemble a telehandler (long-reach forklift). Image credit: Jacquesbotha, CC BY-SA 4.0, via Wikimedia Commons. A fairly crucial part of a telehandler - the thing that makes it a telehandler, really - is it’s boom, which the forks (or other tools) are attached to and can lift and extend. https://blog.usedbytes.com/2022/02/pico-pio-camera/ Sat, 19 Feb 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/02/pico-pio-camera/ This is a lengthy post which goes into lots of detail. The tl;dr is that the code is here: https://github.com/usedbytes/camera-pico-ov7670 In this post I’ll describe how I went about connecting an OV7670 camera module to the Raspberry Pi Pico that drive’s my Pi Wars at Home 2022 ‘bot M0o+. It’s all wrapped up in a separate library which should be easy-ish to incorporate in other projects. Trying to get this camera working was the very first thing I did, as a sort of Pico “feasibility study” to decide if entering a Pico-based robot was practical. https://blog.usedbytes.com/2022/01/m0o-s-chassis/ Sun, 23 Jan 2022 00:00:00 +0000 https://blog.usedbytes.com/2022/01/m0o-s-chassis/ M0o+ is my Raspberry Pi Pico-based robot entry for Pi Wars at Home 2022. This post details what I’ve settled on for the basic chassis of the robot. Rebound As I wrote in my initial post for the project, I had originally hoped to re-purpose an ancient RC car chassis to be the basis of my robot. Sadly, it became apparent that all of the things which made it so much fun as an RC car when I was a child, made it almost entirely unsuitable for Pi Wars. https://blog.usedbytes.com/2021/12/esp32-wifi/bluetooth-bridge/ Sun, 26 Dec 2021 00:00:00 +0000 https://blog.usedbytes.com/2021/12/esp32-wifi/bluetooth-bridge/ M0o+ is my Raspberry Pi Pico-based robot entry for Pi Wars at Home 2022. A Pi Wars robot needs to be remote-controllable, and network connectivity is extremely useful for telemetry, debugging etc. As the Pico doesn’t natively have any kind of wireless connectivity, I’m using an ESP32 to provide that functionality. It connects to a bluetooth gamepad, relaying controller input to the Pico, and acts as a WiFi access point to provide network connectivity. https://blog.usedbytes.com/2021/12/pico-serial-bootloader/ Wed, 01 Dec 2021 00:00:00 +0000 https://blog.usedbytes.com/2021/12/pico-serial-bootloader/ My Pi Wars 2022 entry, M0o+, is powered by a Raspberry Pi Pico, which itself is powered by the RP2040 chip. The RP2040 has a built-in boot ROM with a USB bootloader, which allows the chip to show up as a USB flash drive for uploading code. This is usually a very convenient interface, making it extremely quick and simple to upload code to the device. However, in a Pi Wars robot, I don’t want to have to bring the Pico back to my computer and plug it in to iterate on the code - I see it as essential to be able to download new code to the robot wirelessly without needing to touch it. https://blog.usedbytes.com/2021/11/m0o-pi-wars-at-home-2022/ Sun, 14 Nov 2021 00:00:00 +0000 https://blog.usedbytes.com/2021/11/m0o-pi-wars-at-home-2022/ Pi Wars (at home) 2022 is upon us, and after taking 2020 “off”, I’ve had an application accepted for the competition. I’ll be blogging about my progress here the same way I did for 2019 and Mini Mouse. The “in person” 2020 competition was postponed on account of the Covid-19 pandemic, and hasn’t yet taken place. In 2020, an “at home” competition took place, with competitors submitting videos for each challenge. https://blog.usedbytes.com/2021/01/m5stack-core2-early-impressions/ Sat, 16 Jan 2021 11:13:08 +0000 https://blog.usedbytes.com/2021/01/m5stack-core2-early-impressions/ Just after Christmas I ordered an M5Stack Core2 (referred to as M5Core2 in many places) on a bit of a whim. I’ve been annoyed about my lack of a self-contained rapid-prototyping platform, and the M5 hardware looks pretty good, and appears popular online. Historically I’ve used original Mbed LPC1768 boards which I’ve collected over time. However the “old” online compiler platform for Mbed is more-or-less unsupported now, and last time I tried the newer mbed-cli system, I had a lot of trouble setting it up. https://blog.usedbytes.com/2020/11/un-replaceable-belling-oven-switch-replacement/ Wed, 25 Nov 2020 20:35:09 +0000 https://blog.usedbytes.com/2020/11/un-replaceable-belling-oven-switch-replacement/ One Sunday evening around the end of October, our dinner just wasn’t cooking properly. The cause: despite heating initially, the oven wasn’t holding temperature. Now this particular cooker - a Belling Platinum db3 - is pretty old. I don’t know exactly how old, but it’s old enough that none of the spare parts suppliers recognise it as a model; and the most similar manual I can find online has a copyright date of 2002, so I assume it’s in the region of 20 years. https://blog.usedbytes.com/2020/06/failsafe-pi-dual-boot-with-gpio/ Sat, 06 Jun 2020 22:12:52 +0100 https://blog.usedbytes.com/2020/06/failsafe-pi-dual-boot-with-gpio/ tl;dr Add this to /boot/config.txt: # Set GPIO 26 to pull-up gpio=26=pu # If GPIO 26 is high, the kernel, dtb and cmdline will be taken from /boot/other/ [gpio26=1] # Note the trailing slash is important os_prefix=other/ The background I’ve been keen for quite some time on using Arm powered machines for as much as I can. Back in 2012 I bought the first Samsung Chromebook which used a dual-core Cortex-A15 Samsung Exynos chip. https://blog.usedbytes.com/2020/04/reverse-engineering-keyboard-firmware-with-ghidra-part-4-conclusion/ Wed, 29 Apr 2020 19:53:36 +0100 https://blog.usedbytes.com/2020/04/reverse-engineering-keyboard-firmware-with-ghidra-part-4-conclusion/ This post has been a bit delayed for noe reason in particular (except perhaps fatigue with the project). It brings the Ducky reverse engineering adventure (mainly) to a close. At the end of Part 3, all of the pieces were in place, but I still wasn’t able to flash my own modified firmware to the keyboard because of a pesky failing CRC check. What I did know, was that after sending the CRCCheck() command, the keyboard responded with a 16-bit value. https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-3/ Sat, 28 Mar 2020 10:18:10 +0000 https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-3/ In which we succeed, and fail - and take a break to play through Half-Life: Alyx At the end of Part 2, we’d found and extracted the “firmware blob”, which is the data that the updater sends over USB to the keyboard. The problem is that the data doesn’t look anything like Arm Cortex-M3 code. 00000000: 84be c2c7 450a 0879 6c0a d553 51ce 1efc ....E..yl..SQ... 00000010: fe5b e848 e9c1 3c77 3b74 48b7 768c cbd9 . https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-2/ Fri, 13 Mar 2020 20:36:08 +0000 https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-2/ Last time, in Part 1, we found out the super-secret XOR key for the Ducky One firmware updater and used it to obtain its file header describing the firmware version and keyboard layout. The next missing piece to find is the size of the firmware image, which will tell us which part of the .exe file contains the firmware. To find out where to look, we need to go back to the xx_get_fw function, which takes the firmware size as a parameter: https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-1/ Wed, 04 Mar 2020 20:43:08 +0000 https://blog.usedbytes.com/2020/03/reverse-engineering-keyboard-firmware-with-ghidra-part-1/ In March 2019, the NSA (yes, that NSA) released a reverse engineering tool called Ghidra. This is pretty cool, as it’s relatively easy to use, pretty powerful, and free as in both speech and beer (compared to the similar and popular IDA Pro which is not). Around a year earlier, I’d “upgraded” my non-backlit Ducky One TKL keyboard to a backlit one: The non-backlit version is identical to the backlit version, they just don’t install the LEDs. https://blog.usedbytes.com/2019/11/run-at-startup-without-rc.local/ Sun, 24 Nov 2019 16:13:28 +0000 https://blog.usedbytes.com/2019/11/run-at-startup-without-rc.local/ A question that comes up quite frequently in Pi Wars circles is “how do I make my robot program run at start-up?” Someone asked me that directly at the Pi Wars Miniconference - and I gave the same answer I always do: “Use systemd”. In itself, that not a very useful answer, because systemd is a large and varied project with lots of tools and functionality. It’s just a bit too complex to describe over voice without context. https://blog.usedbytes.com/2019/06/google-home-headphone-jack/ Sun, 09 Jun 2019 15:36:04 +0100 https://blog.usedbytes.com/2019/06/google-home-headphone-jack/ In my living room, I have a pair of reasonably nice speakers (rescued from a skip) connected to an amplifier salvaged out of an old pair of Dell PC speakers. That setup actually sounds pretty good, but doesn’t see much use. It’s a pain to plug something into them: either you plug them into the TV and have to have the TV on, or you plug your phone in and have to keep walking over there. https://blog.usedbytes.com/2019/06/making-jewellery/ Mon, 03 Jun 2019 20:26:51 +0100 https://blog.usedbytes.com/2019/06/making-jewellery/ Towards the end of 2018, I got engaged (woop!), but that’s not really what this post is about. This post is about the ring. The ring is designed in OpenSCAD and printed/cast in 14K gold by Shapeways. In the process of designing it, I learnt a whole host of new tricks in OpenSCAD which I wanted to share1. All of this design work was done in secret, mostly under the guise of “working on my PiWars robot”. https://blog.usedbytes.com/2019/03/pi-wars-post-mortem/ Sun, 31 Mar 2019 20:20:41 +0100 https://blog.usedbytes.com/2019/03/pi-wars-post-mortem/ Pi Wars happened! It’s over! I can start doing something else with my life! I had an awesome time at Pi Wars today and yesterday, with Mini Mouse performing pretty solid attempts at all of the challenges. I ran into a few hiccups on some challenges, but far outperformed my expectations on others. Overall, I placed 3rd in my category, and am really happy to have been awarded first place for this blog, and Artistic Merit (for being “beautiful on both the inside and the outside” - thanks Rachel :-) https://blog.usedbytes.com/2019/03/pre-competition-status-report/ Thu, 28 Mar 2019 20:58:21 +0000 https://blog.usedbytes.com/2019/03/pre-competition-status-report/ With two days to go until competition day (only one day for schools and clubs!), I thought I’d capture the status of Mini Mouse, for posterity and for something to compare against in a Post-Competition Post-Mortem. I’m quite happy with where I’ve got to. The autonomous challenges are all working mostly reliably in practice runs, and the performance seems to be competitive. Of course there’s no guarantee that it’ll perform “on the day”, but I’ve done all I can at this point! https://blog.usedbytes.com/2019/03/battery-discharge-profile/ Sat, 16 Mar 2019 22:16:03 +0000 https://blog.usedbytes.com/2019/03/battery-discharge-profile/ Earlier, on the PiWars Discord, we were having a spirited discussion about the discharge profile of lithium batteries, disagreeing about the relationship between cell voltage and remaining charge level. I’ve never actually checked this for myself before, so I thought I’d run a little experiment to see. When fully charged, a lithium polymer (LiPo) cell should be at 4.2 Volts. The “nominal” voltage for a LiPo cell is 3.7 V, and figures for the “minimum” recommended discharge level vary - but quoted figures range from 2. https://blog.usedbytes.com/2019/03/autonomous-challenge-hubble/ Wed, 13 Mar 2019 16:15:56 -0700 https://blog.usedbytes.com/2019/03/autonomous-challenge-hubble/ The Hubble Telescope Nebula Challenge (previously Somewhere Over the Rainbow) is one of the autonomous challenges, requiring the robot to visit the four corners of a square arena, starting from the centre. In each corner, there’s a coloured board - and for maximum points the robot must visit the corners in an order specified by their colours (Red, then Blue, Yellow and finally Green), as quickly as possible. My overall strategy for this challenge is to spin on the spot at the starting position, to identify where each colour is. https://blog.usedbytes.com/2019/03/setbacks/ Fri, 08 Mar 2019 18:20:44 +0000 https://blog.usedbytes.com/2019/03/setbacks/ Three weeks ago, I got a basic implementation of The Hubble Telescope Nebula Challenge working, which made Mini Mouse’s code “feature complete” from the point of view of entering all of the autonomous challenges. Honestly, I was pretty darn happy. All three challenges were working well enough to be “competitive”, and with more than a month to go until the competition, all that was left was optimisation. So, I spent a week doing rapid-fire blog posts . https://blog.usedbytes.com/2019/02/mini-mouses-armament/ Wed, 20 Feb 2019 20:37:14 +0000 https://blog.usedbytes.com/2019/02/mini-mouses-armament/ Now, irrespective of personal views on arming robots, unfortunately one of the Pi Wars challenges requires1 that we weaponise them. For Space Invaders we have to be able to knock down as many targets as we can (up to 5) from 1-1.5 metres away. Plan A This challenge has caused me a great deal of head scratching as I sought out the right option for projectile launchers for Mini Mouse. For Bot Matrix the plan was dual-wield repeating rubber band guns - so that was my starting point for Mini Mouse too. https://blog.usedbytes.com/2019/02/edge-detection/ Tue, 19 Feb 2019 20:23:05 +0000 https://blog.usedbytes.com/2019/02/edge-detection/ Identifying edges is one of the key “features” of the human vision system. Our brains have evolved to identify edges and it’s one of the things which lets us pick out different objects in the world. If we want to teach our computers to see, Edge Detection is one of the key tools needed to reach that goal (at least, according to “classical” methods. Things change with Deep Learning). Unfortunately, edge detection can be a difficult problem to solve in software. https://blog.usedbytes.com/2019/02/autonomous-challenge-blast-off/ Sun, 17 Feb 2019 19:52:08 +0000 https://blog.usedbytes.com/2019/02/autonomous-challenge-blast-off/ Blast Off: the Straight-ish Line Speed Test is, to my mind, the easiest of the three autonomous challenges in this year’s competition. As such, it’s the one which I started working on first. The task is to get from one end of the course to the other as quickly as possible. There’s effectively two feasible options: Follow the walls Follow the white line Given that I don’t have any side-facing sensors to follow the walls, to me the easiest option looked like following the white line. https://blog.usedbytes.com/2019/02/mini-mouses-software/ Sun, 17 Feb 2019 11:43:26 +0000 https://blog.usedbytes.com/2019/02/mini-mouses-software/ Before I dive in to details on individual challenge implementations, I thought it would be sensible to describe how the software on Mini Mouse sits together. Some of this information is duplicated in We’re in, but there’s more detail here, and things have evolved since then. The diagrams on this page are created with graphviz (or more correctly, dot), which doesn’t give the prettiest of drawings, but does stop me wasting time obsessing over layout. https://blog.usedbytes.com/2019/02/final-hardware/ Sat, 16 Feb 2019 22:03:44 +0000 https://blog.usedbytes.com/2019/02/final-hardware/ It’s been a few frantic months of robot building between my last post and now, a decent portion of it being focussed on finalising the chassis. Since around September I’ve had my prototype chassis working, which has given me a great test-bed for software implementation testing and debugging the hardware design. There were three main (known/intentional) limitations with the prototype chassis, borne out of a need to get it built and tested before I could finalize some of the details. https://blog.usedbytes.com/2018/10/quite-robust-thresholding/ Sat, 27 Oct 2018 16:55:59 +0100 https://blog.usedbytes.com/2018/10/quite-robust-thresholding/ Today, I’m detailing the method I’m using to threshold images for line detection. Also included are some hard-learned lessons about premature optimisation and the importance of re-evaluating your decisions frequently! Image thresholding is the process of taking an image, and converting it into a two-color (just black and white, no grey) image. This is useful for lots of image processing algorithms - like edge or blob detection. My initial focus here has been on implementing a white line detector for the “Blast Off” challenge. https://blog.usedbytes.com/2018/10/were-in/ Sat, 06 Oct 2018 11:09:04 +0100 https://blog.usedbytes.com/2018/10/were-in/ So last weekend Mike and Tim sent out the confirmations for Pi Wars entries, and Mini Mouse made the cut! We’re going to Pi Wars! Doug on the Discord suggested the idea of sharing successful applications for people to look at to see if they can improve their chances next time - so here’s mine in case it’s useful. It’s been a little over a month since my last post, but I have moved things forward a bit in that time. https://blog.usedbytes.com/2018/08/pcbs/ Sun, 26 Aug 2018 10:11:04 +0100 https://blog.usedbytes.com/2018/08/pcbs/ For Mini Mouse, I’ve designed two PCBs - one for motor drivers, and one for the power supply/control circuitry. These were my first boards using the open-source KiCad suite of EDA tools, having previously been an EAGLE user. I got the boards made at dirtypcbs.com, panelising the two boards into a single 5x5 square. This is the third set of boards I’ve made with dirtypcbs, and I’ve always been very pleased with them. https://blog.usedbytes.com/2018/08/power/ Sun, 26 Aug 2018 09:50:46 +0100 https://blog.usedbytes.com/2018/08/power/ Every robot needs power, generally at two or more voltages - one “high” voltage directly from the battery to feed the power hungry motors, and one “logic” voltage to drive the electronics. The motor voltage needs to be able to provide high current, and the logic voltage needs to be relatively “clean” to avoid messing up the electronics with excessive noise or voltage drops. Mini Mouse uses a 3S LiPo battery, which means it’s quite important not to over-discharge the battery, as that might damage the cells (and could even result in fire). https://blog.usedbytes.com/2018/06/motors/ Sun, 03 Jun 2018 14:55:44 +0100 https://blog.usedbytes.com/2018/06/motors/ Motors were the first thing I worked on selecting at the start of the development process. Given the space constraints I’m working with, motors would be a critical component which would inform the design of the rest of the robot. Stepper vs Brushed DC In Bot Matrix I had DC motors with hall-effect encoders on the back. I used the encoders to implement closed-loop control for motor speed, and for odometry for dead reckoning. https://blog.usedbytes.com/2018/04/mini-mouse/ Mon, 30 Apr 2018 19:47:31 +0100 https://blog.usedbytes.com/2018/04/mini-mouse/ In the past 12 months, I built Bot Matrix, aiming for PiWars 2018 (though unfortunately I wasn’t selected as a competitor). It was the first chassis I built from scratch, and I learnt a lot in the process! Bot Matrix was large (on the limits of the PiWars size allowance), and used pretty large motors and drivers. This year’s project is a little bit different - I always fancied building a robot in a computer mouse and so that’s what I’m going for.