SwagBadge2022 Firmware

2023-03-12T20:44:32Z

Jonathan Oxer:

The preferred software environment for the SwagBadge is MicroPython. The badges have MicroPython installed as part of the testing process, but you may need to (re)install it to make sure you have a consistent environment.

The following sequence will fetch all the resources required including Aiko Engine, flash the badge with the correct version of MicroPython, and install the firmware.

mkdir SwagBadge2022 # Create a directory to keep everything in
cd SwagBadge2022 # Change into it
git clone git@github.com:geekscape/aiko_engine_mp.git # Get Aiko Engine
git clone git@github.com:geekscape/aiko_services.git # Get Aiko Services, which has fun examples
python3 -m venv aiko_env # Create a virtual Python environment for Aiko use
. aiko_env/bin/activate # Activate the venv just created
pip install esptool mpfshell # Install tools we need
python3.9 -m pip install --upgrade pip # To prevent it complaining every time!
cd aiko_engine_mp #
mkdir firmware # Create a directory to hold firmware

Download version v1.17 of the MicroPython binary for ESP32 from here: [https://micropython.org/download/esp32/ micropython.org/download/esp32/]

The SwagBadge 2022 currently requires microPython version 1.17.

Move the downloaded binary into the "firmware" directory that you created above.

Plug in your ESP32 device and make sure you can see it, e.g ls -l /dev/tty.* will show a serial device file like /dev/ttyUSB0 or /dev/tty.wchserial1410.

Export the serial port to an environment variable, so mpfshell can use it, e.g:

export AMPY_PORT=/dev/tty.wchserial11410

where the device is the one shown by the ls -l command above.

./scripts/flash_micropython.sh # Flash MicroPython onto the badge

SwagBadge2022 Firmware

2023-03-12T14:10:15Z

Jonathan Oxer:

The preferred software environment for the SwagBadge is MicroPython. The badges have MicroPython installed as part of the testing process, but you may need to (re)install it to make sure you have a consistent environment.

The following sequence will fetch all the resources required including Aiko Engine, flash the badge with the correct version of MicroPython, and install the firmware.

mkdir SwagBadge2022 # Create a directory to keep everything in
cd SwagBadge2022 # Change into it
git clone git@github.com:geekscape/aiko_engine_mp.git # Get Aiko Engine
git clone git@github.com:geekscape/aiko_services.git # Get Aiko Services, which has fun examples
python3 -m venv aiko_env # Create a virtual Python environment for Aiko use
. aiko_env/bin/activate # Activate the venv just created
pip install esptool mpfshell # Install tools we need
python3.9 -m pip install --upgrade pip # To prevent it complaining every time!
cd aiko_engine_mp #
mkdir firmware # Create a directory to hold firmware

Download version v1.17 of the MicroPython binary for ESP32 from here: [https://micropython.org/download/esp32/ micropython.org/download/esp32/]

The SwagBadge 2022 currently requires microPython version 1.17.

Move the downloaded binary into the "firmware" directory.

TODO: Continue from https://github.com/geekscape/aiko_engine_mp

Jonathan Oxer: Added link to OHMC2022

OHMC2021

2021-02-01T23:56:02Z

Jonathan Oxer:

All the Swagbadge shenanigans are at [[Swagbadge2021]]

= Presentations =

== Open Source FPGA Tooling, Our Journey from Resistance to Adoption ==
* Brian Faith and Tim Saxe
* https://lca2021.linux.org.au/schedule/presentation/110/
* https://www.youtube.com/watch?v=gjorwob1bzo

== We made a beautiful complete open-hardware computer, including keyboard and injection-moulded case ==
* Paul Gardner-Stephen and Martin Streit
* https://lca2021.linux.org.au/schedule/presentation/111/
* https://www.youtube.com/watch?v=_vorCvITSmA

Swagbadge2021 GettingStarted

2020-12-22T04:51:18Z

Jonathan Oxer: /* Getting the device on your wifi - wireless */

= Getting started with the Swagbadge =

== Support ==
* The [https://spectrum.chat/lca2021-swagbadge Swag Badge Spectrum chat] is a place where the badge team hangs out, ready to answer your questions.

== My package arrived in the mail, first steps. ==
* Your package should contain your badge! [insert photo here]
* Take off the protective cases to reveal the screens.
* Powering it up
** Insert a micro USB cable into the badge and connect the other end to a USB port on your computer or USB power source.
** A green light should glow on the rear of the board, and a title appear across the two screens.
* Turning it on and off again
** Plugging/unplugging it is fine. Usually the badge isn't running anything intensely enough that just unpowering it would cause a problem.
* On bootup, you should see:
** The OLED screens will display "Aiko" and a version number as a title
** It will also display something else to tell you to set up your wifi.

== Getting it on your network ==

'''Safety precautions we have provided'''

* When using any hardware ordered off the internet, you can't be quite certain what software might be present on it. Before shipping these badges to you, we reflashed a fresh copy of MicroPython onto the Lolin32.
* The framework running on the badge is Aiko, which is open source.
* The software on the badge is available on the CCHS repository, also all open source.
* The badges are designed to communicate over MQTT - a lightweight standard for messaging on IoT devices, but we are aware of privacy considerations: you don't want anybody able to control your badge from afar. The swagbadge protocol provides support for encrypted messages.

=== Getting the device on your wifi - wireless ===

* The first time you boot your device, it won't know how to talk to your network. If it can't detect a pre-existing set of network credentials, or connect to anything it knows about, it will establish a temporary access point and prompt you to navigate to it to enter your wifi details.
* ''Note: Your device can only talk to a 2.4GHz network: it is not compatible with 5GHz WiFi.''
* The screens on your badge will say: <code>Configure WiFi: aiko1234a12341234. Try http://192.168.4.1</code>
* Use your phone or computer to connect to the wifi network on the badge. Its name starts with <code>aiko</code> followed by some numbers/letters.
* Once you're connected to the badge, open a web browser to the IP address on the screens. Something like <code>http://192.168.4.1</code>
* You'll be prompted to enter your wifi SSID and wifi password.
* Once you've saved that, the badge will restart using the credentials you've provided and it will shut down its wifi access point.

Note: If you are using an Android device to link the badge to your WiFi, it will pop up a dialog to say you are switching to a network that doesn't have Internet access and ask if you want to switch back. Select "Keep" to stay on the badge's temporary access point.

=== Getting the device on your wifi - commandline with mpfshell ===

* If setting up via the wifi AP (access point) doesn't work, you can put a configuration file onto the badge.
* You'll need to start by getting [[Swagbadge2021_UpdatingSoftware|a copy of the aiko firmware, and installing mpfshell]]
* ''Note: Your device can only talk to a 2G network: it is not compatible with 5g.''
* Edit aiko_engine_mp/configuration/net.py and insert the details of your SSID and password.
* use mpfshell: <code>mpfshell -o COM3</code>
* <code>put configuration/net.py configuration/net.py</code>
* fire up repl to view the console log
* You can now restart your device
* On bootup it should now talk to your network and you can see it on the console log.

On bootup you should now see...

= Running pre-installed applications =
* Pre-installed things, how to access and run them.

= Extensions: Adding a SAO =
* provided by others
* build your own (linky here to our docs)

= Extensions: Updating the software framework =

Between when we ship the board and when it arrives, there might be some changes to the software framework (Aiko). Here's how to update it. Or perhaps you're interested in writing your own applications?

[[Swagbadge2021_UpdatingSoftware|Updating the Software]]

Swagbadge2021 GettingStarted

2020-12-21T04:29:27Z

Jonathan Oxer: /* Getting started with the Swagbadge */ Added support section

= Getting started with the Swagbadge =

== Support ==
* The [https://spectrum.chat/lca2021-swagbadge Swag Badge Spectrum chat] is a place where the badge team hangs out, ready to answer your questions.

== My package arrived in the mail, first steps. ==
* Your package should contain your badge! [insert photo here]
* Take off the protective cases to reveal the screens.
* Powering it up
** Insert a micro USB cable into the badge and connect the other end to a USB port on your computer or USB power source.
** A green light should glow on the rear of the board, and a title appear across the two screens.
* Turning it on and off again
** Plugging/unplugging it is fine. Usually the badge isn't running anything intensely enough that just unpowering it would cause a problem.
* On bootup, you should see:
** The OLED screens will display "Aiko" and a version number as a title
** It will also display something else to tell you to set up your wifi.

== Getting it on your network ==

'''Safety precautions we have provided'''

* When using any hardware ordered off the internet, you can't be quite certain what software might be present on it. Before shipping these badges to you, we reflashed a fresh copy of MicroPython onto the Lolin32.
* The framework running on the badge is Aiko, which is open source.
* The software on the badge is available on the CCHS repository, also all open source.
* The badges are designed to communicate over MQTT - a lightweight standard for messaging on IoT devices, but we are aware of privacy considerations: you don't want anybody able to control your badge from afar. The swagbadge protocol provides support for encrypted messages.

=== Getting the device on your wifi - wireless ===

* The first time you boot your device, it won't know how to talk to your network. If it can't detect a pre-existing set of network credentials, or connect to anything it knows about, it will establish a temporary access point and prompt you to navigate to it to enter your wifi details.
* ''Note: Your device can only talk to a 2G network: it is not compatible with 5g.''
* The screens on your badge will say: <code>Configure WiFi: aiko1234a12341234. Try http://192.168.4.1</code>
* Use your phone or computer to connect to the wifi network on the badge. Its name starts with <code>aiko</code> followed by some numbers/letters.
* Once you're connected to the badge, open a web browser to the IP address on the screens. Something like <code>http://192.168.4.1</code>
* You'll be prompted to enter your wifi SSID and wifi password.
* Once you've saved that, the badge will restart using the credentials you've provided and it will shut down its wifi access point.

=== Getting the device on your wifi - commandline with mpfshell ===

* If setting up via the wifi AP (access point) doesn't work, you can put a configuration file onto the badge.
* You'll need to start by getting [[Swagbadge2021_UpdatingSoftware|a copy of the aiko firmware, and installing mpfshell]]
* ''Note: Your device can only talk to a 2G network: it is not compatible with 5g.''
* Edit aiko_engine_mp/configuration/net.py and insert the details of your SSID and password.
* use mpfshell: <code>mpfshell -o COM3</code>
* <code>put configuration/net.py configuration/net.py</code>
* fire up repl to view the console log
* You can now restart your device
* On bootup it should now talk to your network and you can see it on the console log.

On bootup you should now see...

= Running pre-installed applications =
* Pre-installed things, how to access and run them.

= Extensions: Adding a SAO =
* provided by others
* build your own (linky here to our docs)

= Extensions: Updating the software framework =

Between when we ship the board and when it arrives, there might be some changes to the software framework (Aiko). Here's how to update it. Or perhaps you're interested in writing your own applications?

[[Swagbadge2021_UpdatingSoftware|Updating the Software]]

Swagbadge2021 GettingStarted

2020-12-21T04:27:57Z

Jonathan Oxer: /* My package arrived in the mail, first steps. */

= Getting started with the Swagbadge =

== My package arrived in the mail, first steps. ==
* Your package should contain your badge! [insert photo here]
* Take off the protective cases to reveal the screens.
* Powering it up
** Insert a micro USB cable into the badge and connect the other end to a USB port on your computer or USB power source.
** A green light should glow on the rear of the board, and a title appear across the two screens.
* Turning it on and off again
** Plugging/unplugging it is fine. Usually the badge isn't running anything intensely enough that just unpowering it would cause a problem.
* On bootup, you should see:
** The OLED screens will display "Aiko" and a version number as a title
** It will also display something else to tell you to set up your wifi.

== Getting it on your network ==

'''Safety precautions we have provided'''

* When using any hardware ordered off the internet, you can't be quite certain what software might be present on it. Before shipping these badges to you, we reflashed a fresh copy of MicroPython onto the Lolin32.
* The framework running on the badge is Aiko, which is open source.
* The software on the badge is available on the CCHS repository, also all open source.
* The badges are designed to communicate over MQTT - a lightweight standard for messaging on IoT devices, but we are aware of privacy considerations: you don't want anybody able to control your badge from afar. The swagbadge protocol provides support for encrypted messages.

=== Getting the device on your wifi - wireless ===

* The first time you boot your device, it won't know how to talk to your network. If it can't detect a pre-existing set of network credentials, or connect to anything it knows about, it will establish a temporary access point and prompt you to navigate to it to enter your wifi details.
* ''Note: Your device can only talk to a 2G network: it is not compatible with 5g.''
* The screens on your badge will say: <code>Configure WiFi: aiko1234a12341234. Try http://192.168.4.1</code>
* Use your phone or computer to connect to the wifi network on the badge. Its name starts with <code>aiko</code> followed by some numbers/letters.
* Once you're connected to the badge, open a web browser to the IP address on the screens. Something like <code>http://192.168.4.1</code>
* You'll be prompted to enter your wifi SSID and wifi password.
* Once you've saved that, the badge will restart using the credentials you've provided and it will shut down its wifi access point.

=== Getting the device on your wifi - commandline with mpfshell ===

* If setting up via the wifi AP (access point) doesn't work, you can put a configuration file onto the badge.
* You'll need to start by getting [[Swagbadge2021_UpdatingSoftware|a copy of the aiko firmware, and installing mpfshell]]
* ''Note: Your device can only talk to a 2G network: it is not compatible with 5g.''
* Edit aiko_engine_mp/configuration/net.py and insert the details of your SSID and password.
* use mpfshell: <code>mpfshell -o COM3</code>
* <code>put configuration/net.py configuration/net.py</code>
* fire up repl to view the console log
* You can now restart your device
* On bootup it should now talk to your network and you can see it on the console log.

On bootup you should now see...

= Running pre-installed applications =
* Pre-installed things, how to access and run them.

= Extensions: Adding a SAO =
* provided by others
* build your own (linky here to our docs)

= Extensions: Updating the software framework =

Between when we ship the board and when it arrives, there might be some changes to the software framework (Aiko). Here's how to update it. Or perhaps you're interested in writing your own applications?

[[Swagbadge2021_UpdatingSoftware|Updating the Software]]

SwagBadge2021

2020-12-21T04:25:56Z

Jonathan Oxer: /* Getting started */ Added link to Spectrum

= Swagbadge for [https://lca2021.linux.org.au LCA2021]: Welcome! =

⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    

   The Open Hardware Miniconf is ON for 2021! [https://linux.conf.au/programme/miniconfs/open-hardware/ Submit your talk proposals today]. Deadline is Dec 18th!
 
⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐    ⭐   

== Status, About us, Contact us ==
* '''[[SwagBadge2021 Status, blog and timeline]]: Read for regular project updates and history'''
* [https://twitter.com/swagbadge2021 Twitter @swagbadge]: Follow for project notifications. HashTags: ''#swagbadge, #lca2021''
* [https://diyodemag.com/columns/swagbadge_dagbadge_badge_ohmc_linux_conference DIYODE magazine issue 41, December 2020 article] on the Swagbadge

== Getting started ==
* [https://spectrum.chat/lca2021-swagbadge SwagBadge Spectrum chat]: Chat system where the SwagBadge team hang out to help you with your badge
* [[Swagbadge2021_Newcomers|Newcomers guide]]: Read our guide if you haven't done much hardware before and need more fundamentals before diving in
* [[Swagbadge2021_GettingStarted|Getting started guide: Swagbadge]]: Your Swagbadge has arrived. What next?
* [[Swagbadge2021_Dagbadge|Dagbadge]]: How to build and make your own!
* [[SwagBadge2021 FAQ]]: Frequently Asked Questions

== Resources ==
* [https://github.com/CCHS-Melbourne/Swag-Badge GitHub repository: #swagbadge hardware]
* [https://github.com/geekscape/aiko_engine_mp GitHub repository: Aiko Engine for microPython]: Not yet updated for #swagbadge

== Announcements ==

'''Today (2020-10-04), we are publicly announcing the [https://lca2021.linux.org.au LCA2021] #swagbadge project''' and beginning the process of opening up our hardware and software development processes. The next couple of weeks will be a bit of a spectator sport whilst we put in place mechanisms for technical collaboration and contributions. We warmly welcome you to join in, get an early start on LCA2021 and enjoy the ride ! '''We'll be listening for questions and feedback sent to [https://twitter.com/swagbadge2021 Twitter @swagbadge]'''

Note: Whilst this project is supported by [https://lca2021.linux.org.au LCA2021], the OHMC team are not an official part of the LCA2021 organizing committee. Of course, we'll be in close communication with them. Also, this project will be covered by a [https://lca2021.linux.org.au/attend/code-of-conduct Code Of Conduct] (perhaps with some hardware hacking caveats). The OHMC team supports and encourages inclusion and diversity in hardware / software hacking, please help us do better !

[[File:Swag badge render 2020-09-30.jpg|360px|LCA2021 swag badge 3D render 2020-09-30]] Recent 3D render 2020-09-30

----

=== LCA2021 #swagbadge announcement ===

A limited number of '''LCA2021 Swag Badge''' electronic badges will be produced for the [https://lca2021.linux.org.au on-line LCA2021] conference, which will be distributed to conference attendees. The LCA2021 Swag Badge is being specially developed and tailored for the conference.

* ''Note 0: This is just our current understanding of how the LCA2021 #swagbadge will be made available ... and is subject to change by LCA2021 organizing committee''
* ''Note 1: The #swagbadge will be only available to Australian participants, due to the cost and delay of shipping internationally''
* ''Note 2: If you are outside of Australia or miss out on a #swagbadge, then you might want to seriously consider acquiring a [[Swagbadge2021_Dagbadge|Dagbadge]]''
* ''Note 3: The Open Hardware Miniconf is ON! [https://linux.conf.au/programme/miniconfs/open-hardware/ Submit your talk proposals today]. Deadline is Dec 18th.''

No ordinary conference badge, this one is full of extensible, open hardware, ready to be loaded up with whatever software and custom hardware add-ons takes your fancy !

The Open Hardware Mini-Conference (OHMC) team are putting together a badge that will be:

* Approachable for newcomers, e.g runs Python and doesn't require any special IDE (for embedded device development)
* Custom-designed, super slick PCB
* Powered by an ESP32 which gives you Wi-Fi and Bluetooth connectivity
* Not one, but two delightful OLED screens
* ... which double as pressable buttons
* Ready for development with the latest [http://micropython.org microPython] installed
* Supported by an open-sourced embedded network framework, the [https://github.com/geekscape/aiko_engine_mp Aiko Engine for microPython]
* With a number of [[Swagbadge2021_SAO|SAO connectors]] so you can extend and add on your own hardware components

We aim to post the #swagbadges prior to Christmas so they will be available before [https://lca2021.linux.org.au on-line LCA2021] begins.

But wait, there's more ! In the spirit of LCA, we want the capabilities of the badge to be truly open. We'll be following up with more information about how you can join in to build out ideas for doing wonderful, magnificent, incredible... stuff ... '''<your idea here>''' ... using the [[Swagbadge2021_SAO|SAO connectors]].

Follow along and join in with the OHMC team as we prepare, plan, design and build your badges. We'll be posting regular updates here on this Wiki.

[[File:Swag badge mechanical 2020-09-30.jpg|360px|LCA2021 swag badge mechanical layout 2020-09-30]] Mechanical layout 2020-09-30

[[Swagbadge2021 Backstory]]

Sbstart

2020-12-15T00:59:13Z

Jonathan Oxer: Redirected page to Swagbadge2021 GettingStarted

#REDIRECT [[Swagbadge2021_GettingStarted]]

SBStart

2020-12-15T00:58:04Z

Jonathan Oxer: Redirected page to Swagbadge2021 GettingStarted

#REDIRECT [[Swagbadge2021_GettingStarted]]

SwagBadge2021 D.I.Y DagBadge

2020-10-17T11:13:04Z

Jonathan Oxer: /* DagBadge - the DIY SwagBadge2021 */

== DagBadge - the DIY SwagBadge2021 ==

[[Swagbadge2021|SwagBadge2021]] is the official electronic conference badge for the LCA2021 conference, but we don't want to limit participation to people who have the official board. So we've created DagBadge, the DIY electronic conference badge that you can build yourself from readily available parts.

=== Parts Required ===

You can adapt this design to suit the parts you have available. To follow our build guide, you will need:

* 1 x Lolin32 Lite (ESP32 development board)
* 2 x 0.96" 128x64 I2C OLED display modules
* 2 x tactile buttons
* 1 x breadboard
* Set of jumper wires

SwagBadge2021 D.I.Y DagBadge

2020-10-17T11:10:29Z

Jonathan Oxer: /* DagBadge - the DIY SwagBadge2021 */

== DagBadge - the DIY SwagBadge2021 ==

[[SwagBadge2021]] is the official electronic conference badge for the LCA2021 conference, but we don't want to limit participation to people who have the official board. So we've created DagBadge, the DIY electronic conference badge that you can build yourself from readily available parts.

=== Parts Required ===

You can adapt this design to suit the parts you have available. To follow our build guide, you will need:

* 1 x Lolin32 Lite (ESP32 development board)
* 2 x 0.96" 128x64 I2C OLED display modules
* 2 x tactile buttons
* 1 x breadboard
* Set of jumper wires

SwagBadge2021 D.I.Y DagBadge

2020-10-17T11:08:13Z

Jonathan Oxer: Created page

== DagBadge - the DIY SwagBadge2021 ==

SwagBadge2021 is the official electronic conference badge for the LCA2021 conference, but we don't want to limit participation to people who have the official board. So we've created DagBadge, the DIY electronic conference badge that you can build yourself from readily available parts.

=== Parts Required ===

You can adapt this design to suit the parts you have available. To follow our build guide, you will need:

* 1 x Lolin32 Lite (ESP32 development board)
* 2 x 0.96" 128x64 I2C OLED display modules
* 2 x tactile buttons
* 1 x breadboard
* Set of jumper wires

SwagBadge2021

2020-10-04T07:30:15Z

Jonathan Oxer: Removed reference to 300 units going to first registrants.

'''#swag-badge for [https://lca2021.linux.org.au LCA2021]: Communications and resources'''

* '''[[SwagBadge2021 Status, blog and timeline]]: Read for regular project updates and history'''
* [https://twitter.com/swagbadge2021 Twitter @swagbadge]: Follow for project notifications
* [https://github.com/CCHS-Melbourne/Swag-Badge GitHub repository: #swag-badge hardware]
* [https://github.com/geekscape/aiko_engine_mp GitHub repository: Aiko Engine for microPython]: Not yet updated for #swag-badge

'''Today (2020-10-04), we are publicly announcing the [https://lca2021.linux.org.au LCA2021] #swag-badge project (more details below)''' and beginning the process of opening up our hardware and software development processes. The next couple of weeks will be more of a spectator sport as we put in place mechanisms for technical collaboration and contributions. We warmly welcome you to join in, get an early start on LCA2021 and enjoy the ride ! '''We'll be listening for questions and feedback sent to [https://twitter.com/swagbadge2021 Twitter @swagbadge]'''

Note: Whilst this project is supported by [https://lca2021.linux.org.au LCA2021], the OHMC team are not an official part of the LCA2021 organizing committee. Of course, we'll be in close communication with them. Also, this project will be covered by a [https://lca2021.linux.org.au/attend/code-of-conduct Code Of Conduct] (perhaps with some hardware hacking caveats). The OHMC team supports and encourages inclusion and diversity in hardware / software hacking, please help us do better !

[[File:Swag badge render 2020-09-30.jpg|360px|LCA2021 swag badge 3D render 2020-09-30]] Recent 3D render 2020-09-30

----

'''LCA2021 #swag-badge announcement backstory story'''

'''Everything about 2020 has been turned upside-down and inside-out 🙃''' Feels like the last normal (and awesome) thing that happened was [https://lca2020.linux.org.au LCA2020]. Wow ... that was a good time 🎉

The Open Hardware Mini-Conference (OHMC) team was keenly looking forward to [https://lca2021.linux.org.au LCA2021]. We have very fond memories of the [http://www.openhardwareconf.org/wiki/AMC2013 Arduino MiniConf in 2013]. We did a road-trip from Melbourne, the LCA2013 venue at the [https://www.anu.edu.au ANU] was excellent and we were looking forward to visiting [https://en.wikipedia.org/wiki/Canberra Canberra] again. Sadly, LCA2021 was postponed 😢, but then went virtual 🤖 ... and then a surprising thing happened ... the LCA2021 organizing team reached out to us and asked if we'd like to consider a special project 😲

Melbourne was deep in CoVid-19 isolation 🤒 and the opportunity to start a new hardware project for our friends at LCA was just the shot-in-the-arm that we needed 💉 The LCA2021 organizing committee asked us to prepare a proposal for a [https://hackaday.com/2018/08/14/all-the-badges-of-def-con-26-vol-1 conference hardware badge] that could be manufactured and sent to a limited number (200) of LCA2021 attendees as part of the swag in time for the conference. So we did. They accepted ! '''And so the [https://github.com/CCHS-Melbourne/Swag-Badge #swag-badge] was conceived !!'''

We've been thinking about an [https://github.com/CCHS-Melbourne/Minimum-viable-badge LCA badge (well, more than just thinking !)] for years, perhaps going back to LCA2012 in Ballarat (another one of our favorites) and the [https://www.freetronics.com.au/products/leostick LeoStick swag].

Now, since it costs nothing to make additional copies of software ... the number of badges was bumped up to 300 🤖🤖🤖 ... (we anticipate some late nights assembling, flashing, packing and posting) 🙄 Not wanting anyone to miss out on the fun, [https://twitter.com/alecthegeek Alec] came up with the idea of the #dag-badge (a simple [https://en.wikipedia.org/wiki/Bill_of_materials BoM]) that anyone can order for themselves immediately and join in the fun, leading up to LCA2021 and beyond 🚀 The #dag-badge will be particularly important for anyone wishing to play along and contribute to the hardware (see [https://hackaday.com/2019/03/20/introducing-the-shitty-add-on-v1-69bis-standard SAO]) or the firmware, before we ship the actual #swag-badge.

Unfortunately, the traditional LCA Open Hardware Mini-Conference morning workshop assembly madness won't be happening this time, but maybe we can still switch it up and figure out a way to involve everyone and perhaps encourage both hardware and software collaboration and contributions. Something different from what we've always done before (which was hacking frantically in our respective caves until the morning of the OHMC). We're thinking something along the lines of ...

* Develop the #swag-badge hardware in the open ... we'll detail the journey, the highs 🎢 and lows 🤯 of delivering a hardware project

* Develop the #swag-badge software in the open ... encouraging collaboration and contributions 🧪💥

* Provide several [https://hackaday.com/2019/03/20/introducing-the-shitty-add-on-v1-69bis-standard SAO connectors] (power, [https://en.wikipedia.org/wiki/I%C2%B2C I2C] and a couple of [https://en.wikipedia.org/wiki/General-purpose_input/output GPIO] pins) ... so that you can create and share your own custom hardware add-ons to the #swag-badge

* Provide a simple "store" where people can upload and download simple application examples to share with others

[[File:Swag badge mechanical 2020-09-30.jpg|360px|LCA2021 swag badge mechanical layout 2020-09-30]] Mechanical layout 2020-09-30

----
'''LCA2021 #swag-badge announcement details'''

A limited number of '''LCA2021 Swag Badge''' electronic badges will be produced for the [https://lca2021.linux.org.au on-line LCA2021] conference, to be distributed to virtual attendees. The LCA2021 Swag Badge is being specially developed and tailored for the conference.

* ''Note 0: This is just our current understanding of how the LCA2021 #swag-badge will be made available ... and is subject to change by LCA2021 organizing committee''
* ''Note 1: The #swag-badge will be only available to Australian participants, due to the cost and delay of shipping internationally''
* ''Note 2: If you are outside of Australia or miss out on a #swag-badge, then you might want to seriously consider acquiring a #dag-badge (details soon)''
* ''Note 2.5: Sorry New Zealand, Australia 🐑 just isn't cool enough yet to be considered as part of New Zealand 🐑🐑🐑''
* ''Note 3: No ... '''LCA2021 registration isn't open yet''' ... but, we love your enthusiasm'' 😂
* ''Note 4: LCA2021 mini-conferences haven't been decided yet and we haven't received notification that there will be an OHMC2021''

No ordinary badge, this one is full of extensible, open hardware, ready to be loaded up with whatever software and custom hardware add-ons takes your fancy !

The Open Hardware Mini-Conference team are putting together a badge that will be:

* Approachable for newcomers, e.g runs Python and doesn't require any special IDE (for embedded device development)
* Custom-designed, super slick PCB
* Powered by an ESP32 which gives you Wi-Fi and Bluetooth connectivity
* Not one, but two delightful OLED screens
* ... which double as pressable buttons
* Ready for development with the latest [http://micropython.org microPython]
* Supported by an open-sourced embedded network framework, the [https://github.com/geekscape/aiko_engine_mp Aiko Engine for microPython]
* With a number of [https://hackaday.com/2019/03/20/introducing-the-shitty-add-on-v1-69bis-standard SAO connectors] so you can extend and add on your own hardware components

We aim to post the #swag-badges prior to Christmas so you'll have your badge before [https://lca2021.linux.org.au on-line LCA2021] even begins, and a stunning memento of your participation in the conference in 2021.

But wait, there's more ! In the true spirit of LCA, we want the capabilities of the badge to be truly open. We'll be following up with more information about how you can join in with other swaggerbadgers to build out ideas for doing wonderful, magnificent, incredible... stuff ... '''<your idea here>''' ... with the [https://hackaday.com/2019/03/20/introducing-the-shitty-add-on-v1-69bis-standard SAO connectors].

Follow along and join in with the OHMC team as we prepare, plan, design and build your badges. We'll be posting regular updates here on this Wiki.

[[File:Swag_badge_render_2020_09-02.png|200px|LCA2021 swag badge very first 3D render 2020-09-02]] Very first 3D render 2020-09-02
[[File:Swag badge pcb 2020-09-30.jpg|300px|LCA2021 swag badge PCB 2020-09-30]] Recent PCB 2020-09-30
[[File:Swag badge render 2020-10-01.jpg|360px|LCA2021 swag badge 3D render 2020-10-01]] Recent 3D render 2020-10-01

OHMC2020

2020-01-14T04:14:28Z

Jonathan Oxer: /* Schedule for the day */

Move over Cybertruck, in 2020 we're building self-driving DingoCars!

The Open Hardware MiniConf (OHMC) is a 1-day event that runs as a specialist stream within the [https://linux.conf.au linux.conf.au] conference.

Interest in Open Hardware is high among FOSS enthusiasts but there is also a barrier to entry with the perceived difficulty and dangers of dealing with hot soldering irons, unknown components and unfamiliar naming schemes. We use the assembly project as a stepping stone to help ease software developers into dealing with Open Hardware. Plenty of instructors will be on hand to assist with soldering and demystifying any questions around hardware assembly.

NO PRIOR HARDWARE EXPERIENCE REQUIRED! That is, after all, what this session is all about! To get the most out of this, some basic knowledge of Linux commands will be helpful. (ssh, running commands, navigating the filesystem)

Participants learn hardware skills by assembling their own electronic project which includes soldering and understanding how circuits work, as well as hearing interesting talks about various projects and techniques related to the morning project and to open hardware in general.

= Before the day =

== Registration and cost ==

STOP! Please read the information below before wildly clicking through to the application form!

To attend you '''must''' first register for the main conference, which provides the venue. The Open Hardware Miniconf is part of LCA as a specialist stream for conference attendees: it's not a stand-alone event. See [https://linux.conf.au/attend/tickets/ linux.conf.au/attend/tickets] for more information.

Places for the assembly session are strictly limited, so registration is required and there is a fee to cover the cost of materials. Even if you ticked the "Open Hardware MiniConf" box on the LCA registration form, you still need to apply for the miniconf separately if you wish to participate in the assembly session.

'''The registration process for the Open Hardware MiniConf is different this year compared to previous years.'''

Instead of a direct registration form, we’re using a 2-step process. This will help us avoid the registration rush that usually has the event sold out within a few hours.

This will also allow us to do a better job of balancing out the allocation of different types of tickets, including normal tickets, supporter tickets, and subsidised tickets, to encourage greater diversity. The result should be more fair than a simple race to the rego form like in previous years.

So take a deep breath, and relax. It’s not a race this year!

'''Step 1:''' Submit the application form using the link below. We’ll collect applications and then assign spots according to the different types of tickets.

'''Step 2:''' We’ll follow up this coming weekend to let you know if you have a ticket assigned. If you do, you’ll receive details of how to submit your payment and receive your ticket.

Please note that the application form includes a question about whether you identify as belonging to an under-represented group. The reason for this is to allow us to prioritise tickets for people who would otherwise not be well represented at the event, to improve the overall diversity.

Of course, this is a very difficult thing to define, and you may be wondering if this applies to you. We don’t want to be in a position of making a judgement call, so we’re leaving it up to your discretion.

The cost of the assembly session is AU$140, which includes all the parts required for you to build your own Perception Module and fit it onto a converted R/C car chassis to make a self-driving model car. Some subsidised places are also available for those who couldn’t otherwise afford to attend. The actual value of the parts provided is approximately AU$260, but thanks to a generous benefactor the cost has been kept low in order to allow more people to participate.

[https://forms.gle/2ZQv744b6ny7mXqh8 OHMC2020 Application Form]

All registered LCA attendees are welcome to come along and watch, or attend the talks, without additional registration.

== Where is it? ==

Tuesday January 14, [https://linux.conf.au/schedule/#tuesday Room 8].

== What to bring? ==
A laptop that has an SSH client.

== Want to present? ==

We have slots for 30 minute talks, as well as 5 minute lightning talks.

[https://linux.conf.au/programme/miniconfs/open-hardware/ Submit your talk proposal] on the LCA open hardware miniconf page.

Got something to share about your experiences with Open Hardware or Maker life? New to open hardware and want to tell us your achievements? An old hand and want to tell us your gritty stories of failures, successes and lessons learned? Not sure if your idea is suitable? Submit it anyway and we can talk with you about whether it'll fit in.

= Schedule for the day =

The miniconf is split into morning and afternoon sessions.

{|
| 10:40 - 12:20
| '''Assembly Workshop''' (registration required to participate, spectators also welcome)
|-
| 12:20 - 1:30
| Lunch
|-
| 1:30 - 1:55
| '''How the Perception Module hardware works''': John Spencer
|-
| 1:55 - 2:20
| '''Running Tensor Flow on the Perception Module''': Andy Gelme
|-
| 2:20 - 2:45
| '''Donkey Cars at Yarra Valley Tech School''': Matt Pattison
|-
| 2:45 - 3:10
| '''ESP32 memory management''': Marc Merlin
|-
| 3:10 - 3:50
| Afternoon Tea
|-
| 3:50 - 4:15
| '''IoT energy monitor using Linux capable host CPU''': Tishampati Dhar
|-
| 4:15 - 4:40
| '''WEMOS Minis are such a timesaver - or am I doing this wrong?''': Sven Dowedeit
|-
| 4:40 - 4:55
| '''Creating a Kubernetes cluster using LattePandas''': Brian May
|-
| 4:55 - 5:30
| '''Lighting Talks''' (5 minute blocks)
|}

== How the Perception Module hardware works ==
Presenter: John Spencer
Learn how the Dingo Cap works with a Raspberry Pi to provide power management and I/O capabilities for machine-learning projects.

== Perception Module software ==
Presenter: Andy Gelme
Run Tensor Flow on a Perception Module to control a self-driving model car.

== Donkey Cars at Yarra Valley Tech School ==
Presenter: Matt Pattison
Yarra Valley Tech School uses Donkey Cars to teach students about software and electronics.

== ESP32 memory management ==
Presenter: Marc Merlin
Microcontrollers such as the ESP32 present new challenges to developers who are accustomed to gigabytes of RAM and memory management handled by the OS.

== IoT energy monitor using Linux capable host CPU ==
Presenter: Tishampati Dhar
This talk discusses the design of a DIN Rail Energy Monitor with a Linux host processor. IoT systems are becoming a part of everyday life and some are built with little regard for security or privacy. As an electronics engineer I set out to design an IoT energy monitoring system that would be open-source and have openly reviewed firmware enabling users to audit the security and privacy features and possibly send data to their own IoT Storage platforms hosted within their private network. This talk also contains a deep dive in the linux kernel module for SPI drivers.

The initial iterations of the design used ESP8266 and then ESP32 as the host processor. The firmware has evolved from Arduino Wiring/C++ to Micropython. My recent efforts have been focused on transitioning a to full-linux capable host processor while delegating the real-time processing and energy computations to ASIC's and FPGA's with ADC extensions. The energy monitor specific code running on the Linux CPU is envisaged to be written in Python for ease of portability and iteration.

== WEMOS Minis are such a timesaver - or am I doing this wrong? ==
Presenter: Sven Dowedeit
I was roped into helping FollyGames, an emersive theatre and performance group, to build distributed actuators to add to their experiences. Initially, to rescue a performance at the Museum of Brisbane, using Raspberry Pi, audio and NFC, and then over time, adding neopixels, UHF RFID, buttons, motors, servos, and more.

In and attempt to head off the joys of last minute ideas, I've been leaning heavily on using WEMOS Minis and the shields that you can buy on AliExpress.

= Assembly Project: Perception Module and DingoCar =

Each year we help attendees build a project specially developed for the Open Hardware Miniconf.

The project for 2020 is the Perception Module, a flexible TensorFlow platform that you can build into your own machine-learning projects.

[[File:PerceptionModule-1.jpg|600px]]

It includes a Raspberry Pi 3B+, a camera, onboard power management, support for both NiMH and LiPo batteries, servo outputs, a 128x64 pixel OLED display, NeoPixel output, and connections for a sonar sensor.

The Perception Module is a direct descendent of the project from OHMC2019, with the brains of the Donkey Car encapsulated in a self-contained module that even has Lego-compatible holes to help you build it into your own projects.

[[File:PerceptionModule-2.jpg|600px]]

At the OHMC we will assemble our own Perception Modules and then fit them onto converted R/C cars to build the delightful DingoCar, a machine-learning self-driving car.

[[File:DingoCar.jpg|600px]]

DingoCar is a fun project but it's only one example of how you can use the Perception Module. After the event you can take your DingoCar and Perception Module home with you, and either continue to use them together or build other projects of your own around the Perception Module.

Some things are pre-built (a custom board to hook up to the Raspberry Pi that has connections for the camera, the servo motor for the engine and the steering) and we'll be attaching some components to the board using soldering, wiring, magic and luck.

The hardware kit includes:
* RC car chassis
* Raspberry Pi model 3+
* Raspberry Pi Camera
* Custom chassis parts for mounting
* Voltage regulator, PWM output controller, and other required parts

We'll then connect wirelessly to train the car by driving it around a track, then once the computer has processed this model data, we will unleash our DingoCars to drive themselves!

Yes, you will need your own laptop to participate in the assembly project to handle the training and control of your DingoCar. Setting some items up in advance will give you more time in the session for the hardware, and provide some relief to the conference wifi.

More information and instructions are available at:
* [[OHMC2020 Software instructions]]
* [[OHMC2020 Hardware instructions]]

= Credits =

OHMC is mostly run by Andy Gelme and Jon Oxer, with able assistance by their team of robots. 2020 also has the following human assistants: John Spencer, Andrew Nielson, Bob Powers and Nicola Nye. We also rely on a big team of helpers on the day who provide hands-on guidance to attendees, teaching assembly techniques and soldering, and answering questions, who include: Cary Dreelan, Matt Pattison, Mark Wolfe.

OHMC2020

2020-01-14T04:12:47Z

Jonathan Oxer: /* Schedule for the day */

Move over Cybertruck, in 2020 we're building self-driving DingoCars!

The Open Hardware MiniConf (OHMC) is a 1-day event that runs as a specialist stream within the [https://linux.conf.au linux.conf.au] conference.

Interest in Open Hardware is high among FOSS enthusiasts but there is also a barrier to entry with the perceived difficulty and dangers of dealing with hot soldering irons, unknown components and unfamiliar naming schemes. We use the assembly project as a stepping stone to help ease software developers into dealing with Open Hardware. Plenty of instructors will be on hand to assist with soldering and demystifying any questions around hardware assembly.

NO PRIOR HARDWARE EXPERIENCE REQUIRED! That is, after all, what this session is all about! To get the most out of this, some basic knowledge of Linux commands will be helpful. (ssh, running commands, navigating the filesystem)

Participants learn hardware skills by assembling their own electronic project which includes soldering and understanding how circuits work, as well as hearing interesting talks about various projects and techniques related to the morning project and to open hardware in general.

= Before the day =

== Registration and cost ==

STOP! Please read the information below before wildly clicking through to the application form!

To attend you '''must''' first register for the main conference, which provides the venue. The Open Hardware Miniconf is part of LCA as a specialist stream for conference attendees: it's not a stand-alone event. See [https://linux.conf.au/attend/tickets/ linux.conf.au/attend/tickets] for more information.

Places for the assembly session are strictly limited, so registration is required and there is a fee to cover the cost of materials. Even if you ticked the "Open Hardware MiniConf" box on the LCA registration form, you still need to apply for the miniconf separately if you wish to participate in the assembly session.

'''The registration process for the Open Hardware MiniConf is different this year compared to previous years.'''

Instead of a direct registration form, we’re using a 2-step process. This will help us avoid the registration rush that usually has the event sold out within a few hours.

This will also allow us to do a better job of balancing out the allocation of different types of tickets, including normal tickets, supporter tickets, and subsidised tickets, to encourage greater diversity. The result should be more fair than a simple race to the rego form like in previous years.

So take a deep breath, and relax. It’s not a race this year!

'''Step 1:''' Submit the application form using the link below. We’ll collect applications and then assign spots according to the different types of tickets.

'''Step 2:''' We’ll follow up this coming weekend to let you know if you have a ticket assigned. If you do, you’ll receive details of how to submit your payment and receive your ticket.

Please note that the application form includes a question about whether you identify as belonging to an under-represented group. The reason for this is to allow us to prioritise tickets for people who would otherwise not be well represented at the event, to improve the overall diversity.

Of course, this is a very difficult thing to define, and you may be wondering if this applies to you. We don’t want to be in a position of making a judgement call, so we’re leaving it up to your discretion.

The cost of the assembly session is AU$140, which includes all the parts required for you to build your own Perception Module and fit it onto a converted R/C car chassis to make a self-driving model car. Some subsidised places are also available for those who couldn’t otherwise afford to attend. The actual value of the parts provided is approximately AU$260, but thanks to a generous benefactor the cost has been kept low in order to allow more people to participate.

[https://forms.gle/2ZQv744b6ny7mXqh8 OHMC2020 Application Form]

All registered LCA attendees are welcome to come along and watch, or attend the talks, without additional registration.

== Where is it? ==

Tuesday January 14, [https://linux.conf.au/schedule/#tuesday Room 8].

== What to bring? ==
A laptop that has an SSH client.

== Want to present? ==

We have slots for 30 minute talks, as well as 5 minute lightning talks.

[https://linux.conf.au/programme/miniconfs/open-hardware/ Submit your talk proposal] on the LCA open hardware miniconf page.

Got something to share about your experiences with Open Hardware or Maker life? New to open hardware and want to tell us your achievements? An old hand and want to tell us your gritty stories of failures, successes and lessons learned? Not sure if your idea is suitable? Submit it anyway and we can talk with you about whether it'll fit in.

= Schedule for the day =

The miniconf is split into morning and afternoon sessions.

{|
| 10:40 - 12:20
| '''Assembly Workshop''' (registration required to participate, spectators also welcome)
|-
| 12:20 - 1:30
| Lunch
|-
| 1:30 - 1:55
| '''How the Perception Module hardware works''': John Spencer
|-
| 1:55 - 2:20
| '''Running Tensor Flow on the Perception Module''': Andy Gelme
|-
| 2:20 - 2:45
| '''Donkey Cars at Yarra Valley Tech School''': Matt Pattison
|-
| 2:45 - 3:10
| '''ESP32 memory management''': Marc Merlin
|-
| 3:10 - 3:50
| Afternoon Tea
|-
| 3:50 - 4:15
| '''IoT energy monitor using Linux capable host CPU''': Tishampati Dhar
|-
| 4:15 - 4:40
| '''WEMOS Minis are such a timesaver - or am I doing this wrong?''': Sven Dowedeit
|-
| 4:40 - 4:55
| '''Using LattePanda''': Brian May
|-
| 4:55 - 5:30
| '''Lighting Talks''' (5 minute blocks)
|}

== How the Perception Module hardware works ==
Presenter: John Spencer
Learn how the Dingo Cap works with a Raspberry Pi to provide power management and I/O capabilities for machine-learning projects.

== Perception Module software ==
Presenter: Andy Gelme
Run Tensor Flow on a Perception Module to control a self-driving model car.

== Donkey Cars at Yarra Valley Tech School ==
Presenter: Matt Pattison
Yarra Valley Tech School uses Donkey Cars to teach students about software and electronics.

== ESP32 memory management ==
Presenter: Marc Merlin
Microcontrollers such as the ESP32 present new challenges to developers who are accustomed to gigabytes of RAM and memory management handled by the OS.

== IoT energy monitor using Linux capable host CPU ==
Presenter: Tishampati Dhar
This talk discusses the design of a DIN Rail Energy Monitor with a Linux host processor. IoT systems are becoming a part of everyday life and some are built with little regard for security or privacy. As an electronics engineer I set out to design an IoT energy monitoring system that would be open-source and have openly reviewed firmware enabling users to audit the security and privacy features and possibly send data to their own IoT Storage platforms hosted within their private network. This talk also contains a deep dive in the linux kernel module for SPI drivers.

The initial iterations of the design used ESP8266 and then ESP32 as the host processor. The firmware has evolved from Arduino Wiring/C++ to Micropython. My recent efforts have been focused on transitioning a to full-linux capable host processor while delegating the real-time processing and energy computations to ASIC's and FPGA's with ADC extensions. The energy monitor specific code running on the Linux CPU is envisaged to be written in Python for ease of portability and iteration.

== WEMOS Minis are such a timesaver - or am I doing this wrong? ==
Presenter: Sven Dowedeit
I was roped into helping FollyGames, an emersive theatre and performance group, to build distributed actuators to add to their experiences. Initially, to rescue a performance at the Museum of Brisbane, using Raspberry Pi, audio and NFC, and then over time, adding neopixels, UHF RFID, buttons, motors, servos, and more.

In and attempt to head off the joys of last minute ideas, I've been leaning heavily on using WEMOS Minis and the shields that you can buy on AliExpress.

= Assembly Project: Perception Module and DingoCar =

Each year we help attendees build a project specially developed for the Open Hardware Miniconf.

The project for 2020 is the Perception Module, a flexible TensorFlow platform that you can build into your own machine-learning projects.

[[File:PerceptionModule-1.jpg|600px]]

It includes a Raspberry Pi 3B+, a camera, onboard power management, support for both NiMH and LiPo batteries, servo outputs, a 128x64 pixel OLED display, NeoPixel output, and connections for a sonar sensor.

The Perception Module is a direct descendent of the project from OHMC2019, with the brains of the Donkey Car encapsulated in a self-contained module that even has Lego-compatible holes to help you build it into your own projects.

[[File:PerceptionModule-2.jpg|600px]]

At the OHMC we will assemble our own Perception Modules and then fit them onto converted R/C cars to build the delightful DingoCar, a machine-learning self-driving car.

[[File:DingoCar.jpg|600px]]

DingoCar is a fun project but it's only one example of how you can use the Perception Module. After the event you can take your DingoCar and Perception Module home with you, and either continue to use them together or build other projects of your own around the Perception Module.

Some things are pre-built (a custom board to hook up to the Raspberry Pi that has connections for the camera, the servo motor for the engine and the steering) and we'll be attaching some components to the board using soldering, wiring, magic and luck.

The hardware kit includes:
* RC car chassis
* Raspberry Pi model 3+
* Raspberry Pi Camera
* Custom chassis parts for mounting
* Voltage regulator, PWM output controller, and other required parts

We'll then connect wirelessly to train the car by driving it around a track, then once the computer has processed this model data, we will unleash our DingoCars to drive themselves!

Yes, you will need your own laptop to participate in the assembly project to handle the training and control of your DingoCar. Setting some items up in advance will give you more time in the session for the hardware, and provide some relief to the conference wifi.

More information and instructions are available at:
* [[OHMC2020 Software instructions]]
* [[OHMC2020 Hardware instructions]]

= Credits =

OHMC is mostly run by Andy Gelme and Jon Oxer, with able assistance by their team of robots. 2020 also has the following human assistants: John Spencer, Andrew Nielson, Bob Powers and Nicola Nye. We also rely on a big team of helpers on the day who provide hands-on guidance to attendees, teaching assembly techniques and soldering, and answering questions, who include: Cary Dreelan, Matt Pattison, Mark Wolfe.