Currency: GBP
GBP USD EUR JPY AUD NOK CHF NZD CAD BTC
Conversions are estimates and updated daily.
You must be logged in to use your wishlist!

Interstate 75 &endash; Default Title

Enter the (LED) matrix with this all-in-one, USB-C powered controller for HUB75 panels. Read more...

  • Description
  • Reviews

Enter the (LED) matrix with this all-in-one, USB-C powered controller for HUB75 panels.

Interstate 75 is a RP2040-based driver board for HUB75-style LED matrices. It's designed to plug neatly into the back of a LED panel, and provides a quick and easy way to whip up some scrolling signage or an eye-catching LED display for sensor outputs.

Interstate 2040 is powered and programmable by USB-C. USB-C is capable of providing up to 3A of power which should be enough to power a single 64x64 (or smaller) panel, assuming you're not planning anything too eye-bleedingly bright. If you need more power than that (so you can chain multiple panels together, perhaps?) you can inject it into the screw terminals instead. There's also two useful buttons, a reset button and an onboard RGB LED.

We've also popped a QW/ST connector on there, to make it super easy to plug in Qwiic or STEMMA QT breakouts.

Features

  • Powered by RP2040 (Dual Arm Cortex M0+ running at up to 133Mhz with 264kB of SRAM)
  • 2MB of QSPI flash supporting XiP
  • Compatible with 32x32, 32x64 and 64x64 LED matrices.
  • Sturdy screw terminals for powering the LED panels.
  • USB-C connector for power and programming (3A max)
  • Qw/ST (Qwiic/STEMMA QT) connector
  • Reset, BOOT and a user button (the BOOT button can also be used as a user button)
  • RGB LED
  • Fully-assembled (no soldering required)
  • Measurements: approx 48.5 x 31 x 17mm (L x W x H, including connectors)
  • Schematic
  • C++/MicroPython libraries

LED matrix panels and cables are sold separately, check out the extras tab for some options!

Software

Because it's a RP2040 board, Interstate 75 is firmware agnostic! You can program it with C/C++, MicroPython or CircuitPython.

Our C++/MicroPython libraries contain some spiffy HUB75 drivers that use RP2040's PIO state machines and DMA to minimise CPU usage and maximise luscious, 10-bit gamma corrected colour depth.

You'll get best performance using C++, but if you're a beginner we'd recommend using our batteries included MicroPython build for ease of getting started.

You can also use CircuitPython on your Interstate 75! Because CircuitPython drivers are designed to work on a bunch of different microcontrollers you won't get the fancy RP2040-architecture specific tweaks that you'll find in our library, but you will get access to Adafruit's mighty DisplayIO library which makes it super easy to display all sorts of different kinds of text, draw shapes and display images.

Please note that some less-common varieties of 64x64 panels, like ones that use the FM6126A chip, are not currently supported in CircuitPython.

Connecting Breakouts

If your breakout has a QW/ST connector on board, you can plug it straight in with a JST-SH to JST-SH cable, or you can easily connect any of our I2C Breakout Garden breakouts with a JST-SH to JST-SH cable coupled with a Qw/ST to Breakout Garden adaptor.

You can find a list of which breakouts are currently compatible with our C++/MicroPython build in the most recent release notes.

We've also broken out a bunch of useful I2C pins, analog pins and debug pins along the side of the board so you can solder things like breakouts or analog potentiometers directly to them.

About RP2040

Raspberry Pi's RP2040 microcontroller is a dual core ARM Cortex M0+ running at up to 133Mhz. It bundles in 264kB of SRAM, 30 multifunction GPIO pins (including a four channel 12-bit ADC), a heap of standard peripherals (I2C, SPI, UART, PWM, clocks, etc), and USB support.

One very exciting feature of RP2040 is the programmable IOs which allow you to execute custom programs that can manipulate GPIO pins and transfer data between peripherals - they can offload tasks that require high data transfer rates or precise timing that traditionally would have required a lot of heavy lifting from the CPU.