More journals fixed

Author: dannystaple

Diff for: content/2018/04/2018-04-01-piwars-bot-build-notes.md

@@ -12,7 +12,7 @@ This was disturbing.
 
 I was researching stuff on motor stall currents, and brushing up my physics - what had I missed? The robot could fail only seconds in, or a while in.
 
-After checking on twitter, and then reading the piconzero docs - it turns out that older pi raspbian images had i2c stability issues. So I started a dist-upgrade on it. This seemed like a great plan...
+After checking on social media, and then reading the piconzero docs - it turns out that older pi raspbian images had i2c stability issues. So I started a dist-upgrade on it. This seemed like a great plan...
 
 Bad news  then - I knocked out the power cable (external wall power) while doing the update!
 
@@ -248,7 +248,7 @@ Left track 0 Right track 0
 What does this mean? Wait - 2.0.4?
 
 Now using the controller example from <https://approxeng.github.io/approxeng.input/examples/show_controls.html> - and the axis are weird.
-Time to talk on twitter.
+Time to talk with other robot builders.
 
 Trying to remove "pi" from the "input" group. Then log out, back in and try again. No - nothing.
 Try a reboot. Without the pad - input shows only "mice".
@@ -269,7 +269,7 @@ crw-rw---- 1 root input 13,  0 Apr  1 15:23 js0
 crw-rw---- 1 root input 13, 63 Apr  1 15:22 mice
 ```
 
-I spoke on twitter to the approx_eng guy. With Helena's help - and used `evtest` - which shows event sources and allpws you to look at them.
+I spoke to the approx_eng guy. With Helena's help - and used `evtest` - which shows event sources and allows you to look at them.
 
 This showed nothing when not in the input group, and 2 event sources when in the group.
 

Diff for: content/2018/04/2018-04-06-piwars-fixing-sensors.md

@@ -39,7 +39,7 @@ It was a dependency of the `skittlebot` class in the code.
 
 ## Multiple sensors
 
-This is going to get interesting. I had a chat with @4tronix on twitter and asked for some ideas for using multiple distance sensors with the PiConZero.
+This is going to get interesting. I had a chat with @4tronix and asked for some ideas for using multiple distance sensors with the PiConZero.
 The PiConZero itself wouldn't be able to, but additional GPIO boards could. So the options are:
 
 * creating a shim to attach to sensors.

Diff for: content/2018/04/2018-04-18-piwars-robot-panic-sets-in.md

@@ -0,0 +1,51 @@
+---
+title: Piwars 2018 Robot - Panic Sets In
+date: 2018-04-18
+tags: [robot building, piwars, opencv, electronics, power, raspberry pi robotics project, raspberry pi opencv project, python, raspberry pi camera]
+---
+As we realise how close we are to going to the event, panic Sets In. 2 days before we leave! Our robot should be ready for the 22nd of April - not everything works!
+
+We have a task list, but it's too far from realistic. this is a mix of things we've done, and what we were hoping to do. We have a lot of work to do.
+
+* Finish the code conversion to the method for HC-04 used in the piconzero library. - done
+* Finish assembling the motors. - done
+* Test each distance sensor in it's enclosure on the Tester made with the microview - ensure there isn't any weird values.
+    * Check that that breadboard is wired correctly. -done
+    * Left - done
+    * Right - done
+    * Front - done
+    * Conclusion - the 3d printed cases are not a problem.
+    * Try three together on multiple microviews. - nah - lets not.
+    * Fix the distance code - the GpioZero is the wrong way to do it for now - done.
+* Test the motors with keypad drive. - done
+* Test the distance code again.
+* Find out why the lights aren't working - get them working.
+    * Use a microview with some code to test that first strip and connector
+    * Replace that connector if I need it.
+    * Now try to get at least one light under pi control, can I use my logic analyser to see if anything is coming out on that SPI output bus I made?
+* Finish the MENU module - and blend it with drive - so menu is Manual Drive and launch auto.
+* Write the sysv/systemd script to launch this as user Pi when powered up.
+* Make the rainbow module - give it the sequence of colour hues - test with skittles.
+        * It is the hue divided by 2 to fit in the range.
+    * Find the hue for red - range -15 - 15,
+    * hue range green - 45 - 75
+    * hue range blue  - 80 - 145
+    * hue range yellow - 20 - 40
+    * Create code to go through the sequence: red, blue, yellow, green
+        * Drive up.
+        * Pull back.
+        * Next
+        * When done - exit back to drive.
+    * Test it.
+* Test the avoid module - see how I can branch it for fast straight line.
+* Make a simple maze - use cardboard in the house.
+* Test the robot with a simple maze test.
+* Play robot skittles with the kids.
+
+* PACK!
+    * Screwdrivers
+    * Cables + crimps?
+    * laptop
+    * Batteries (charger?)
+
+The next update will be after the event, a debrief.

Diff for: content/2020/03/2020-03-01-kicad-part-for-explorer-hat-pro.md

@@ -1,5 +1,5 @@
 ---
-date: '2020-03-01'
+date: 2020-03-01
 description: Explorer Hat Pro Part For Kicad
 layout: post
 tags:
@@ -8,7 +8,7 @@ tags:
 - raspberry pi projects
 - raspberry pi 3 projects
 - piwars
-- robot
+- robot building
 - kicad
 title: 'Piwars 2020: Kicad Part For the Pimoroni Explorer Hat Pro'
 ---
@@ -27,4 +27,4 @@ Download the files below:
 * [explorerhatpro.lib](/assets/kicad-library-parts/explorerhatpro.lib)
 * [explorerhatpro.dcm](/assets/kicad-library-parts/explorerhatpro.dcm)
 
-![Nerf Gun On the Robot](https://pbs.twimg.com/media/ERVTiHkU8AER8cU?format=jpg&name=large){.class="img-responsive"}
+{% img_responsive "content/2020/03/nerf-turret-on-bangers-robot.JPG", "Nerf Gun On the Robot" %}