<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://loftypremises.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://loftypremises.com/" rel="alternate" type="text/html" /><updated>2026-03-12T06:15:55+00:00</updated><id>https://loftypremises.com/feed.xml</id><title type="html">Lofty Premises</title><subtitle>A place for the self-complicating thoughts of Brett Hagman.</subtitle><author><name>Brett Hagman</name></author><entry><title type="html">Arduino IDE 1.8.0 - Yay?</title><link href="https://loftypremises.com/noise/2017/01/02/arduino-ide-1.8.0-yay/" rel="alternate" type="text/html" title="Arduino IDE 1.8.0 - Yay?" /><published>2017-01-02T13:00:00+00:00</published><updated>2017-01-02T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2017/01/02/arduino-ide-1.8.0-yay</id><content type="html" xml:base="https://loftypremises.com/noise/2017/01/02/arduino-ide-1.8.0-yay/"><![CDATA[<p>ICYMI - The “Arduinos” have begun to resolve their differences, and have attempted to start the process of merging the unnecessarily fractured software platform by releasing a new version of the Arduino IDE software<!--more--> - namely Arduino IDE 1.8.0.</p>

<p>arduino.org announcement: <a href="http://web.archive.org/web/20170807081415/http://www.arduino.org/blog/one-ide-for-all-arduino-boards">New IDE for all Arduino boards!</a> (archived version from archive.org)</p>

<p>arduino.cc announcement: <a href="https://blog.arduino.cc/2016/12/23/new-ide-for-all-arduino-boards/">NEW IDE FOR ALL ARDUINO BOARDS!</a></p>

<p>​It is a minor step in the right direction to removing some of the confusion surrounding all of the strangeness that both parties have exhibited over the last couple of years.  However, there is a long way to go.</p>

<p>Anyway, on December 23rd, 2016, the “Arduinos” released a somewhat-merged IDE.  (OK, so instead they compromised on a few things, and kept the “.CC” repository as the main repo.)</p>

<p>They bumped the version from 1.6.x (on the “.CC” side), and 1.7.x (on the “.ORG” side), to 1.8.0 – This should end the confusion about the software versions.  They also added support for both the “.CC” and “.ORG” hardware.</p>

<p>While this has been an interesting development in the Arduino ecosphere, there is still very little information on what is happening with the rest of the supposed merger.  Since the news of the settlement, there has been no other news, as far as I could find.  My only comment on this is that the involved parties need to be more open about what is happening with what was, at one time, an open source software project.</p>

<p><a href="http://hackaday.com/2016/10/01/arduino-vs-arduino-arduino-won/">Link to the Hackaday article on the settlement announcement</a></p>

<p>Because of my involvement with the software and hardware with the “Arduinos” and Wiring, I sincerely  hope that 2017 will be a significantly better year than the previous ones.</p>

<p>So, happy new year!  Is this a step in the right direction?</p>]]></content><author><name>Brett Hagman</name></author><category term="arduino" /><summary type="html"><![CDATA[ICYMI - The “Arduinos” have begun to resolve their differences, and have attempted to start the process of merging the unnecessarily fractured software platform by releasing a new version of the Arduino IDE software]]></summary></entry><entry><title type="html">Halloween 2016</title><link href="https://loftypremises.com/noise/2016/11/02/halloween-2016/" rel="alternate" type="text/html" title="Halloween 2016" /><published>2016-11-02T13:00:00+00:00</published><updated>2016-11-02T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2016/11/02/halloween-2016</id><content type="html" xml:base="https://loftypremises.com/noise/2016/11/02/halloween-2016/"><![CDATA[<p>Here are some shots from this year’s Halloween setup.</p>

<p><a href="/assets/images/halloween2016/img-20161031-201118_orig.jpg" class="text-center">
<img src="/assets/images/halloween2016/img-20161031-201118_orig.jpg" style="width: 80%; padding: 20px;" />
</a></p>

<p><a href="/assets/images/halloween2016/img-20161031-201150_orig.jpg" class="text-center">
<img src="/assets/images/halloween2016/img-20161031-201150_orig.jpg" style="width: 80%; padding: 20px;" />
</a></p>

<div style="margin:0 auto; width: 80%; padding: 20px;">
  <div class="ytcontainer"><iframe class="yt" frameborder="0" allowfullscreen="" src="https://www.youtube.com/embed/qGPNVI2UZKs"></iframe></div>
</div>

<p>The big pumpkin plays music and has an animated face.  It currently has 4 different songs to which it sings.</p>

<p>There is a motion sensor that triggers the show over an RF link.</p>

<p>Here is a short breakdown of how it works:</p>

<p><strong>Pumpkin Player</strong>: uses a Wiring S board, a Rogue Robotics rMP3 Playback Shield, an nRF24L01+ radio, and a hand built LED driver board to control the LEDs.</p>

<p><strong>Motion Sensor</strong>: uses a Wiring S board, a PIR module (from Seeed Studio, IIRC), and an nRF24L01+ radio.</p>

<p><strong>Remote Control and Display</strong>: uses a Rogue Robotics Rapscallion board, and an nRF24L01+ radio.</p>

<p>The Pumpkin Player receives messages from both the Motion Sensor and the Remote Control.  It plays music using the rMP3 and changes the facial expressions to match the music.  The facial expressions are stored as an accompanying lyrics file for the current song being played.  The rMP3 plays the music, and the Wiring S reads the lyrics file at the same time to get the expressions.</p>

<p>The Motion Sensor sends messages to both the Pumpkin Player and the Remote Control.  It uses a typical PIR sensor module.</p>

<p>The Remote Control receives messages from the Motion Sensor.  If the Motion Sensor is triggered, then the RGB LED on the Rapscallion flashes (and a tone on a speaker is played, if a speaker is connected).  Playback can be started and stopped using the buttons on the Rapscallion.</p>

<p>Wheeeee!  Another fun Halloween.</p>]]></content><author><name>Brett Hagman</name></author><category term="halloween" /><category term="arduino" /><category term="timewasted" /><category term="wiring" /><summary type="html"><![CDATA[Here are some shots from this year’s Halloween setup.]]></summary></entry><entry><title type="html">WXM Grey Cup Sign Project</title><link href="https://loftypremises.com/noise/2016/08/24/wxm-grey-cup-sign-project/" rel="alternate" type="text/html" title="WXM Grey Cup Sign Project" /><published>2016-08-24T13:00:00+00:00</published><updated>2016-08-24T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2016/08/24/wxm-grey-cup-sign-project</id><content type="html" xml:base="https://loftypremises.com/noise/2016/08/24/wxm-grey-cup-sign-project/"><![CDATA[<p>Brent Marshall from Wright XM poked me a while back to help him out on a project for the CFL.</p>

<p>They wanted a huge interactive sign for the kickoff the next season. Wright XM definitely stepped up to the plate (um… yeah, wrong sports metaphor).</p>

<p>The sign consisted of 8 characters (<code class="language-plaintext highlighter-rouge">#GREYCUP</code>), and each letter was internally lit using addressable LEDs.</p>

<p>Brent needed a bit of help with the interaction between all of the letters.  He already had all of the high level interaction done (e.g. scraping Twitter for the hashtags to update the letter colours, etc.).  So, he called upon me to help with the low level stuff.</p>

<p>I used an old trick of using a single microcontroller as the master that would send simple serial messages with an embedded address. There was no data acking/error correction employed, as we only had a single transmitter, and no way to multiplex the incoming data from the slaves. RS232 was used in this case, since we didn’t have time/resources to switch over to RS422 or such, and we were well under 20m cable runs.</p>

<p>It worked quite well, despite a few cabling issues here and there, and in the end, I think Wright XM’s clients were happy.</p>

<p>Here is a video that Wright XM produced after the project to demonstrate what was done.</p>

<div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/151176817?title=0&amp;byline=0&amp;portrait=0" style="position:absolute;top:0;left:0;width:100%;height:100%;" frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen=""></iframe></div>
<script src="https://player.vimeo.com/api/player.js"></script>

<p>And here’s a shot of me working on the sign:</p>

<p><a href="/assets/images/wxmgreycupsign/werkinondaeee.webp">
<img src="/assets/images/wxmgreycupsign/werkinondaeee.webp" style="width:50%;" />
</a></p>]]></content><author><name>Brett Hagman</name></author><category term="blinkylights" /><summary type="html"><![CDATA[Brent Marshall from Wright XM poked me a while back to help him out on a project for the CFL.]]></summary></entry><entry><title type="html">Look Who Turned Thirty This Year</title><link href="https://loftypremises.com/noise/2014/11/09/look-who-turned-thirty-this-year/" rel="alternate" type="text/html" title="Look Who Turned Thirty This Year" /><published>2014-11-09T13:00:00+00:00</published><updated>2014-11-09T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2014/11/09/look-who-turned-thirty-this-year</id><content type="html" xml:base="https://loftypremises.com/noise/2014/11/09/look-who-turned-thirty-this-year/"><![CDATA[<p>By far the most interesting thing, for me at least, that turned thirty this year, is Brøderbund’s desktop publishing package <a href="https://archive.org/details/The_Print_Shop_1984_Broderbund">The Print Shop</a>.</p>

<p>Taken from <a href="http://archive.org/">Archive.org</a>:</p>

<blockquote>
  <p>The Print Shop is a basic desktop publishing software package developed in the early 1980s by Brøderbund. It was unique in that it provided libraries of clip-art and templates through a simple interface to build signs, posters and banners with household dot-matrix printers. Over the years the software has been updated to accommodate changing file formats and printer technologies.</p>

  <p>The original version was for the Apple II and created signs, cards, banners, and letterheads. Designed by David Balsam and programmed by Martin Kahn, it became one of the most popular Apple II titles of all time. Versions for the IBM PC, Commodore 64, and Atari 8-bit computers followed, as did a variant for the Apple IIGS. These versions were published in Europe by Ariolasoft.</p>

  <p>The software became very popular. In 1988 Brøderbund announced that it had sold more than one million copies, and that sales of The Print Shop comprised 4% of the entire United States software market in 1987.</p>
</blockquote>

<p>Ah… to think of the countless hours wasted in front of the ubiquitous Apple II series of computers, and others, by people around the world.</p>

<p>In honour of The Print Shop turning thirty, I could think of no better way to show my appreciation than to show everyone (especially the latest generation), the best part of printing something with The Print Shop:</p>

<p><a href="/assets/images/printshop-thinking.gif" class="text-center">
<img src="/assets/images/printshop-thinking.gif" style="width: 80%; padding: 20px;" />
</a></p>

<p>Cheers.</p>

<p>And happy birthday, The Print Shop!</p>]]></content><author><name>Brett Hagman</name></author><category term="apple" /><category term="nostalgia" /><summary type="html"><![CDATA[By far the most interesting thing, for me at least, that turned thirty this year, is Brøderbund’s desktop publishing package The Print Shop.]]></summary></entry><entry><title type="html">Low Frequencies on Arbitrary Pins</title><link href="https://loftypremises.com/noise/2014/07/23/low-frequencies-on-arbitrary-pins/" rel="alternate" type="text/html" title="Low Frequencies on Arbitrary Pins" /><published>2014-07-23T13:00:00+00:00</published><updated>2014-07-23T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2014/07/23/low-frequencies-on-arbitrary-pins</id><content type="html" xml:base="https://loftypremises.com/noise/2014/07/23/low-frequencies-on-arbitrary-pins/"><![CDATA[<p>I’ve had a few people ask me how to produce low frequencies on an arbitrary Arduino/Wiring pin. They have found that the tone() function (the same applies to the Tone library) can not produce frequencies below ~30 Hz.</p>

<p>The thing is that when you’re toggling a pin at that frequency, it is essentially an eon between pin toggles (from the microcontroller’s perspective).</p>

<p>So my suggestion is to add non-blocking code in your main loop to handle the flips, just as long as you don’t tie up the main loop with too much other time-consuming code.</p>

<!--script src="https://gist.github.com/bhagman/0baae0c8f37ee37f0f61.js"></script-->
<noscript><pre>400: Invalid request</pre></noscript>
<script src="https://gist.github.com/0baae0c8f37ee37f0f61.js"> </script>

<p>Here is a capture of the frequency output from a <a href="http://www.roguerobotics.com/products/electronics/wiring/wirings">Wiring S</a>:</p>

<p><a href="/assets/images/lowfreqscopecap.png">
<img src="/assets/images/lowfreqscopecap.png" style="" />
</a></p>]]></content><author><name>Brett Hagman</name></author><category term="arduino" /><category term="code" /><category term="gist" /><category term="wiring" /><summary type="html"><![CDATA[I’ve had a few people ask me how to produce low frequencies on an arbitrary Arduino/Wiring pin. They have found that the tone() function (the same applies to the Tone library) can not produce frequencies below ~30 Hz.]]></summary></entry><entry><title type="html">Pung</title><link href="https://loftypremises.com/noise/2014/01/22/pung/" rel="alternate" type="text/html" title="Pung" /><published>2014-01-22T13:00:00+00:00</published><updated>2014-01-22T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2014/01/22/pung</id><content type="html" xml:base="https://loftypremises.com/noise/2014/01/22/pung/"><![CDATA[<p>So, if one pings (yes, <a href="http://dictionary.reference.com/browse/ping">it’s now a  ”verb”</a>) something or someone, they are said to be contacting something/someone with the intent of receiving an immediate response to ascertain their presence.</p>

<p>To be clear, I’m OK with the new verb.  However, I’m a little uneasy with the past tense of some of the new slang words that are entering the common vernacular.</p>

<p>So, does the past tense of “ping” get conjugated to “pinged”, which, unfortunately, should be pronounced like “hinged”, but people say “ping’d”?  Or should it be “pung”, much like “sung” or “hung”?</p>

<p>I think I’m going to start using “pung”.  That’s just the way I roll.</p>

<p>“My boss just pung me.”</p>

<p>“I pung Google, before I <a href="http://dictionary.reference.com/browse/google">googled</a> ’pung’.”</p>

<p>It will definitely catch on, I’m sure.</p>

<p>(For extra credit, what should be the past tense of using Microsoft’s Bing search engine?  I assume that some people still use <a href="http://news.yahoo.com/microsoft-admits-campaign-turn-bing-verb-massive-flop-234514035.html">“bing” as a verb</a>…)</p>

<p><strong>Update:</strong>
So, after discussing this with a student (thanks Andre!), it might be a bit more complex than just “pung.”  We may have to have “pang” for the past tense, and “pung” for the past participle.  Examples forthcoming.</p>

<ul>
  <li><em>I pang you.</em></li>
  <li><em>You were pung by me.</em></li>
  <li><em>Donald pang the server.</em></li>
  <li><em>The server was pung by Donald.</em></li>
  <li><em>She pings all the servers he has pung.</em></li>
</ul>]]></content><author><name>Brett Hagman</name></author><category term="flotsam" /><category term="grammar" /><category term="pedantic" /><summary type="html"><![CDATA[So, if one pings (yes, it’s now a  ”verb”) something or someone, they are said to be contacting something/someone with the intent of receiving an immediate response to ascertain their presence. To be clear, I’m OK with the new verb.  However, I’m a little uneasy with the past tense of some of the new slang words that are entering the common vernacular. So, does the past tense of “ping” get conjugated to “pinged”, which, unfortunately, should be pronounced like “hinged”, but people say “ping’d”?  Or should it be “pung”, much like “sung” or “hung”? I think I’m going to start using “pung”.  That’s just the way I roll. “My boss just pung me.” “I pung Google, before I googled ’pung’.” It will definitely catch on, I’m sure. (For extra credit, what should be the past tense of using Microsoft’s Bing search engine?  I assume that some people still use “bing” as a verb…) Update: So, after discussing this with a student (thanks Andre!), it might be a bit more complex than just “pung.”  We may have to have “pang” for the past tense, and “pung” for the past participle.  Examples forthcoming. I pang you. You were pung by me. Donald pang the server. The server was pung by Donald. She pings all the servers he has pung.]]></summary></entry><entry><title type="html">Down in Boston</title><link href="https://loftypremises.com/noise/2013/09/06/down-in-boston/" rel="alternate" type="text/html" title="Down in Boston" /><published>2013-09-06T13:00:00+00:00</published><updated>2013-09-06T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2013/09/06/down-in-boston</id><content type="html" xml:base="https://loftypremises.com/noise/2013/09/06/down-in-boston/"><![CDATA[<p>Down in Boston to meet up with Alex and Hernando for the 2013 Open Hardware Summit.
Hernando will be participating in a panel discussion on forking and attribution.</p>]]></content><author><name>Brett Hagman</name></author><category term="wiring" /><summary type="html"><![CDATA[Down in Boston to meet up with Alex and Hernando for the 2013 Open Hardware Summit. Hernando will be participating in a panel discussion on forking and attribution.]]></summary></entry><entry><title type="html">Wiring++ and New Libraries</title><link href="https://loftypremises.com/noise/2013/08/23/wiring-and-new-libraries/" rel="alternate" type="text/html" title="Wiring++ and New Libraries" /><published>2013-08-23T13:00:00+00:00</published><updated>2013-08-23T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2013/08/23/wiring-and-new-libraries</id><content type="html" xml:base="https://loftypremises.com/noise/2013/08/23/wiring-and-new-libraries/"><![CDATA[<p>Hernando, Alex, Robert (of <a href="http://energia.nu/">Energia</a>), Ed (and Amon &amp; Collin of <a href="http://modk.it/">Modkit</a>), and I have been working as hard as we can during our spare time to bring out the new Wiring++ we demonstrated at Maker Faire San Mateo earlier this year.</p>

<p>Ed (from Modkit) is the one that came up with the idea for running threads and events in the background.  Alex has added some of his wizardry to the mix as well.</p>

<p>Hernando and Robert have put in some brilliant work on the new build process.</p>

<p>I’ve been working with Alex on some new libraries as well as a “base library” that people can use to build their own libraries.  More on that coming in the next few months.</p>]]></content><author><name>Brett Hagman</name></author><category term="wiring" /><summary type="html"><![CDATA[Hernando, Alex, Robert (of Energia), Ed (and Amon &amp; Collin of Modkit), and I have been working as hard as we can during our spare time to bring out the new Wiring++ we demonstrated at Maker Faire San Mateo earlier this year.]]></summary></entry><entry><title type="html">Google Interactive Doodle Disease</title><link href="https://loftypremises.com/noise/2013/08/22/google-interactive-doodle-disease/" rel="alternate" type="text/html" title="Google Interactive Doodle Disease" /><published>2013-08-22T13:00:00+00:00</published><updated>2013-08-22T13:00:00+00:00</updated><id>https://loftypremises.com/noise/2013/08/22/google-interactive-doodle-disease</id><content type="html" xml:base="https://loftypremises.com/noise/2013/08/22/google-interactive-doodle-disease/"><![CDATA[<p><a href="/assets/images/GIDD.jpg">
<img src="/assets/images/GIDD.jpg" style="" />
</a></p>

<p>A.k.a Shiny Ball Syndrome, Google Interactive Doodle (GID) Disease (GIDD) causes the user to immediately interact with the doodle upon opening a new window to search for, invariably, something much more important.  The unsuspecting victim will “play” with the doodle and within 2 minutes, will have completely forgotten what they came to search for.</p>

<p>One possible solution/workaround/vaccination: Use 150% of your will power to avoid playing with the GID upon first appearance and type your search string as fast as you possibly can into the search box, but don’t press the “Search” button until you’ve completely satiated your inner child’s desire to play with the completely useless, yet infinitely entertaining toy presented for your distraction.  WARNING: You may accidentally press on a part of the GID which will cause the doodle’s “related search” - this may cause your search string to be wiped out!</p>

<p>I hope this helps you. Unfortunately for me, I’m extremely susceptible to GID Disease.  I can no longer count how many searches I’ve lost (as well as how many brain cells along with them).</p>

<p><strong>[Update 2018-06-07]</strong>: I’m not alone! At least one other person feels similarly, and went as far as creating <a href="https://grantwinney.com/how-to-hide-google-doodles-in-chrome/">a browser extension</a> to hide the GID.</p>]]></content><author><name>Brett Hagman</name></author><category term="google" /><category term="flotsam" /><category term="timewasted" /><summary type="html"><![CDATA[]]></summary></entry></feed>