All the displays, 4 made with neopixels and soldered by hand
Yeah, the 24x24 one took forever to lay out, glue and solder (6H+)
More than 2 years ago, I spent many hours writing an interrupt written driver for LED matrices that require fast line scanning while you setup the right rows, and even faster per color refreshes where you turn the color on and off depending on how bright you want each color component to be to yield different color mixes. This is explained in more details on my page on Driver for direct driving single to 3 color LED Matrices with software PWM.
Then came in Neopixels which can be individually addressed without fast row scanning, and the Adadfruit Neomatrix library. Those made creating color matrices much more trivial (except for the part where you have to actually build and solder that matrix):
2 row scanned matrices on the upper left, 7x7 neomatrix, another row scanned 32x16 Adafruit panel.
on the bottom row, self built 16x8 neomatrix, and another 12x12 neomatrix
I ended up taking my old Adafruit GFX demo I wrote fro my interrupt driven scan matrices, porting it to Neomatrix (which was trivial) and then extending it. You can find my MatrixGFXDemo code here,
Soon afer, I dug up my Adafruit 16X32 RGB LED Matrix Panel, setup an old Arduino Mega to control it and have enough RAM left to run some fun code (on an Uno memory would have been too tight), it turns out that thanks to Adafruit GFX support, it took very little time to get my same demo working on the RGB Panel.
Here is a video of the demo I wrote on all those different displays:
Here are some things the demo does:
Init displays the same 8x8 pattern as many times as it will fit
The code will then draw lines, rectangles and circles that match the size of the display:
If the display is at least 16x8, it will display the resolution in various ways appropriate to the display size:
Neither Arturo nor Johannes had gone to Heavenly this year, and it was about to close most of its lifts after this week, so Arturo offered a day trip there, which we both graciously accepted. We left around 05:30 and arrived by the nevada border by 09:30, parked, and took the gondola up because the connecting california lifts were already closed.
how's that cindaquil?
we actually stopped at mid station for a look, which I had never done :)
We then had to follow the sun and started down at stagecoach and went up to dipper as things got warmer, and eventually moved to sky express. The snow was spring snow, we had to avoid the ice in some places and sticky slush in others, but overall the snow was good on groomers and ok elsewhere. And for snow, there is lots of it.
lots of things were closed of course
Thanks to Arturo for getting us there, that was fun.
As explained on this page, I wrote a pretty extensive driver-set for an ESP32 based board with lots of IO, but hardly anyone has that board (fewer than 100 made), so I ported what I could of the code to the WROVER.
Sadly the WROVER lacks a touch screen, so you'll have to wire at least a rotary encoder or a joystick. In the demo above I also wired 2 neopixels and an IR receiver to mirror the hardware on the IoTuz.
Source code: https://github.com/marcmerlin/IoTuz
See this video for a demo:
It had been several years since I last went to Mammoth, and I was looking forward to finally going there with fresh powder. I carefully watched the forecast several days early including saturday when the storm was hitting the resort, to make sure that the top of the mountain would stay closed and I'd get fresh tracks the next day if I went.
I got up early (actually I woke up before my alarm) and by 04:45 started getting ready. Got to Palo Alto Airport at 05:15 and then started loading up the plane, parked the car, and got in the air by 06:00 for a beautiful easy flight:
By 07:15, I landed at KMMH, taxied to parking, found my rental car waiting for me on the tarmac (courtesy of Hertz), but sadly it was a 2 wheel drive with crappy tires (the front tires were not even M+S, they turned out to be crappy summer tires). Driving up to the resort, blowing past several chain control signs, took virtually all the driving skills I had. While I was barely able to drive up in the snow, I knew if I ever had to stop, it would be super unlikely that the car would get traction to restart at all (especially uphill), so I drove slowly with some distance with the car in front of me so I never had to stop when the traffic slowed down. Maybe in hindsight I should have gone to Eagle Lodge at much lower altitude, but powder-wise this was not a good idea, it was the wrong side of the resort and the top connecting lifts would be closed for a while. Yes, I should have had chains, but Hertz refuses to give or rent you chains because they're worried you may put them on wrong :(
Despite the driving challenges, I arrived at the main base around 08:15, had to find a far away parking spot and walk to the ticket counter to get my pass. I eventually got to the slopes around 08:40, which wasn't too bad.
snow all the way up to the base
the top of the mountain stayed closed until about 11:00
strangely, there was no line at the gondola
that's because everyone got out at mid station waiting for the top to open (that took 2H)
every other lift had 15mn+ lines
and more lines
while the gondola to the top wasn't open yet, but that's a lot of tracks down for a few ski patrol runs. Mmmh...
sadly, the 2ft of powder were pretty packed by the wind
line at the mid station gondola. It was better go to all the way back down and get it there
Gondola towards top of cloud nine had a bit of powder (only enough for one run though)
snow was good up high, but by 9000ft the powder quality went way down :-/
hike up the ridge to santiago bowl/hemlock bowl and chair 14
The next morning, driving up was easier, the road was mostly clear. I also only drove up to Mill's Café, which put me at the lifts I wanted and is actually easier to get back to, than the main lodge. Some people actually camped there:
The next morning was already spring skiing. Not bad, mostly no ice or slush, which is good, but virtually no powder left anywhere:
During those 2 days, I got some nice pictures of the surroundings:
airport I went to
looks nice to ride :)
this reminds me of heavenly]
On the way back, saw one of the Alaska planes bringing in a load of passengers:
good way to see the mountain
Mill's Café where I parked, and main lodge at the end of the road
I hiked up the hill to ski down that face a couple of times
Here is a 6mn clip showing the shoes and shirt if you'd like the details:
The problem with my shirt, though, is that the colors you see on the picture are actually due to broken traces, causing the colors you see. It's better than nothing, but not what I was trying to do, and no way to create streaming effects. This is of course where neopixels come in.
I'm not going to repeat the excellent Adafruit Neopixel Uberguide here, but I have a 3mn video clip showing a standard IR RGB LED controller, compared to a neopixel strip. It also shows how I use standard remote control servo cables to wire neopixels, and how to watch out for:
signal wire being in the center, so you must not feed 5V on the middle wire like you would with RC and servos
how if you have a neopixel strip that doesn't work right, you can only connect to the first LED, and you have to start cutting off LEDs from the strip one by one until you get to the first one that works
before you start cutting, make very sure you aren't connecting to the last LED (DO vs DI)
Why IR and Neopixels at the same time, is hard
So, the main point of this page is however to look into the issues of controlling Neopixels and receiving IR signals at the same time.
It's easy to listen for IR, and then change neopixels, leave them alone, and listen for IR again. It's hard (or near impossible on some chips) to actively update neopixel strips for animations and listen for IR commands at the same time.
Why? This video explains the issue:
What's going on is on low end arduino chips (328p, leonardo, or even AT mega and all other 16 bit AVRs), neopixels are controlled by stopping chip interrupts and sending a very precisely timed signal to the neopixels. If the timing is off just a little bit, the wrong colors get sent, or nothing works at all. This is why interrupts must be disabled
Now, there are actually many other addressable multicolor LED types. The nice ones are 4 wire and work via SPI, which allows the CPU to control the timing and the clock, removing this exact bit banging timing issue. The cheaper 3 wire ones have a set clock and require that the CPU sends a very precisely timed signal, usually done while disabling interrupts. See https://github.com/FastLED/FastLED/wiki/Overview
But since neopixel strips (aka WS2811/WS2812/WS2812B) is what I already had, I now had to deal with this precise timing issue. As you can guess, disabling interrupts causes issues with the IRRemote library because it has its on interrupt handler timer that also requires being run at a special timing, or it doesn't capture proper IR signals.
The end result is that you cannot disable interrupts and receive IR signals, and if you don't disable interrupts, the neopixel signal is unstable and the colors flicker (demonstrated int the video above).
So, unless you use some special hardware to drive neopixels strips on an AVR chip, concurrent IR + neopixels is just not going to work.
an arduino nano v3 running neopixel strips
my 328p arduiny chip (equivalent to arduino nano) and anti plug backwards toothpicks :)
because my 328p chip was unprogrammed, I had to figure out direct ISP programming pinout for it and I flashed a bootloader on it
Concurrent IR + Neopixels solution #1: be fast (Teensy 3.1)
a few chips for comparison (uno, leostick, nano v3, arduiny, and Teensy 3.1 in green)
Thanks to better FastLED hardware support, when I moved my code to a Teensy 3.1 32 bit ARM CPU, the CPU was fast enough that it had time to re-enable interrupts in the middle of updating neopixels. This in turns allowed the IR Remote interrupt handler to just barely run in between pixel updates, and capture IR codes. Success!
See this video for details:
The magic code that makes this work, is here: https://github.com/FastLED/FastLED/blob/master/platforms/arm/k20/clockless_arm_k20.h#L34 sei(); delayMicroseconds(WAIT_TIME); cli();
Thanks to this re-enabling of interrupts, things work.
So at this point, someone sensible would have declared victory. However, I felt bad wasting a Teensy 3.1 on something as simple as driving a single neopixel strip (it can drive 8 in parallel) and reading from an IR receiver, when it has around 32 I/O ports. This is why I checked if I could get this to work on ESP8266 chips which are even cheaper and have much fewer I/O pins (but add Wifi)
Concurrent IR + Neopixels solution #2: don't use the CPU for neopixels (ESP8266 (I2S) and ESP32 (RMT))
I had more 32bit chips, so I thought I would give them a try. I tried the ESP8266 and ESP32:
However in my tests, the IRremoteESP8266 library was maybe a little bit too slow and caused occasional visible neopixel glitching. This is where I found this interesting library: https://github.com/JoDaNl/esp8266_ws2812_i2s/ which manages to drive the neopixels without doing bit banging with interrupts disabled ((ab)-using the I2S hardware support). It's not a very fancy library in what it offers, but it works perfectly with interrupts enabled.
Same thing for ESP32. Actually ESP32 is even more difficult to get a perfect timing out of using bit-banging given that it's a dual core CPU running on top of an RTOS, and no matter how precise your code is, you just cannot guarantee that it'll run perfectly at the timing you need all the time. I did add ESP32 support to the Adafruit Neopixel library, but it only works most of the time, which isn't really good enough.
This where its built in RMT support comes in. It can generate 8 precise signal waves, which are perfect for neopixels, so this is the way to go to animate neopixels without disabling interrupts (making IR receiving trivial). IRremote was missing ESP32 receive support, but I added it recently, so it's all working.
Here's a video summary of ESP8266 and ESP32:
Software and Libraries
So, here's a summary of all the libraries I went through, 2 for IR, and 4 for Neopixels:
FastLED is a more complete library with better hardware support (both in pixels and CPUs): https://github.com/FastLED/FastLED . The big plus of this lib is that it support re-enabling interrupts on 32bit chips, allowing the IRremote ISR to run.
Instead of FastLED (which does work), on ESP8266 you can use https://github.com/JoDaNl/esp8266_ws2812_i2s/ . The support is bare, but uses an inventive (ab)use of the I2S subsystem (I2C for audio) to generate neopixel signals using an onboard co-processor unit without tying up the main CPU or requiring the disabling of interrupts.
On ESP32, FastLED isn't supported yet (I added support in Adafruit-Neopixel) but both require disabling interrupts at least temporarily and it's hard to do anything real time on a dual core ESP32 running on top of an RTOS. The good news however is that it has 8 RMT channels which are designed to handle precise signals like this without tying up the CPU. See this code that supports Neopixels with exact timing: https://github.com/MartyMacGyver/ESP32-Digital-RGB-LED-Drivers
I arrived a bit late on tuesday thanks to the Tesla supercharger being down. I had to drive around Folsom, and by then I was worried that Carson Spur would close, so I went around via South Lake Tahoe.
When I finally got to kirkwood, all the charging ports had ICE cars parked in front of them. Doh!
I Emailed vail about it, and thankfully they fixed that a day later:
The first day, I only got on the slopes just before 14:00, got a single ride on Cornice, and then it closed for lightening :( The snow was super wet and not run to ride though. Technically it was snowing, but it felt more like rain...
The next day, we had snow all day until 18:00, which fixed the crappy snow underneath. It was cold and very wet, but the snow was good. Back side opened by 13:30 adn was worth riding too. The wave didn't open though, which was great for the next day:
damn, that's a lot of snow in that drain under cornice
big rock skier's left of the wall, filled with snow
snow and snow and snow
backside, here we come
The 3rd day was finally the blue bird:
enough snow on the wall, you can get down anywhere
so many tracks, too many people :)
I went down eagle bowl, again, no one :)
the wave opened early in the morning
choose your way down :)
again, too many tracks :)
fawn ridge was beautiful
I lapped it 5 times and got fresh tracks each time
chute off the wall, snow had been blown off
By 14:00, the snow was however starting to turn. Somewhat slushy in places, and funny thing was other places had powder that was icing up (palisades), so I counted my blessings for all that snow with no crowds and went home:
While I was barely back from a ski trip and jetlagged in the wrong direction, my friend David (DJ Blur) encouraged me to come, for what was a great evening, starting with his own set. I was indeed tired that evening, but it was still worth the trip, great music.
After Silverton, it was time to go to Telluride. Telluride is about 10mn away as the crow flies, but more like 2H by road since you have to drive all the way around a bunch of peaks. While the snow the day or our travel didn't materialize much, or even the night before we went skiing, the day we did go skiing, it was there. That was along frigid temperatures (-20C wind chill). Even then, anything not north facing was pretty crappy under the fresh snow that wasn't deep enough, but by the end of day, we got enough new snow that things were pretty good. By mid afternoon, the sun came out, and it got warmer:
oops, I got stuck in a valley and had to walk out
the lift run looks nice
it's called the bad idea run because you get stuck without a slope at the bottom, so I went :)
The next day was sunny and we went for the left over fresh snow:
sadly, lift 15 wasn't that good when it opened, not deep enough
a bunch of nice EX runs
great view on the aircraft carrier style Telluride airport, highest commercial airport in the continental US
another nice tree run that ends up on a path and a road :)
Subaru blocked the access road for a bit while they were shooting a commercial with a drone
we went to the advanced group directly, the briefing was 'brief'
we didn't waste time climbing for 30mn from the lift for our first run
snow down looked good, but it wasn't that great the sun had already started baking it
silverton guides keep things tidy to use the snow as long as possible
each run got us back down to a road where a bus or van would come pick us up
while we were hiking up, some lucky folks got heli rides
The 2nd day, we were signed up for an all day heli tour. We ended up leaving late due to the avalanche danger being high, as well as very strong winds in the morning, making heli flying a bit more interesting. The first ride was damaged powder, but the last 5 runs we went to the next mountain across where the snow was still pristine and the north facing or tree protected snow was still in good shape:
your ride has arrived
our guide had a nice board, the church of snowboarding :)
the snow that day were really wanting to slide
The last 5 runs were pretty good considering, not awesome alpine from top to bottom due to the conditions, but still good and fun.
On the way back, I got a few shots of Silverton