Repository navigation
Releases
DMX Core Pico 2 USB Interface 1.0.19
The first release of the USB Interface firmware for the DMX Core Pico 2: a two-port
USB DMX interface.
- Enttec DMX USB Pro protocol, with two-port extensions: port A on labels 6 and
0x64, port B on label 0x65. Works with lighting software that supports the Enttec DMX
USB Pro or the DMXking ultraDMX, and with OLA on Linux. - Steady DMX output: the interface repeats the latest frame on its own, at the
output rate (1-40 frames per second, or 0 for as fast as the frame allows), whatever
the computer is doing. - DMX input on port A, sent to the computer every frame or on change only. When the
software that drove port A as an output stops (it closes the port, or the timeout
setting runs out), port A listens again. At most 40 received frames a second go to
the computer by default (the input rate setting; 0 sends every frame), always the
newest, so software such as QLC+ keeps up with fast consoles. - RDM on both ports: discovery, GET and SET. Port A works with RDM-capable software
such as OLA, through the Enttec protocol; port B through the second-port messages QLC+
uses; both ports work with the DMX Core configuration utility. DMX keeps going between
RDM requests. - Settings kept on the interface: port A's direction (output or input), output
rate, break and mark-after-break, full 512-channel frames, RDM on or off and the
spacing between requests, and what to send when the computer stops sending (stop, all
0 or all 255) after a timeout or when the software closes the port. - A serial port per DMX port (a setting): the interface shows up as two one-port
interfaces, so software that drives one port per interface, such as Lightkey, can use
both ports, each from its own universe. Port B can then also receive DMX. - Its own USB ID, 2E8A:1180, granted by Raspberry Pi, so lighting software can
recognize the interface by its USB ID. Builds up to 1.0.10 used the shared Raspberry
Pi Pico ID (2E8A:000A); after updating from one, the computer sees a new device and
assigns it a new serial (COM) port. - Updates without opening the case: software puts the interface into its boot loader
(label 1), and the new .uf2 is copied onto the drive that appears.
Install or update
Hold BOOTSEL while plugging the DMX Core Pico 2 into USB (or, from this firmware, send label 1 or run picotool reboot -u), and copy dmxcore-pico2-usb-interface-1.0.19.uf2 onto the RPI-RP2 drive. To go back to the Re-Mapper, copy its .uf2 the same way.
THIRD-PARTY-NOTICES.txt lists the open-source code in the firmware and its licenses.
DMX Core Pico 2 USB Interface 1.0.17
The first release of the USB Interface firmware for the DMX Core Pico 2: a two-port
USB DMX interface.
- Enttec DMX USB Pro protocol, with two-port extensions: port A on labels 6 and
0x64, port B on label 0x65. Works with lighting software that supports the Enttec DMX
USB Pro or the DMXking ultraDMX, and with OLA on Linux. - Steady DMX output: the interface repeats the latest frame on its own, at the
output rate (1-40 frames per second, or 0 for as fast as the frame allows), whatever
the computer is doing. - DMX input on port A, sent to the computer every frame or on change only.
- RDM on both ports: discovery, GET and SET. Port A works with RDM-capable software
such as OLA, through the Enttec protocol; port B through the second-port messages QLC+
uses; both ports work with the DMX Core configuration utility. DMX keeps going between
RDM requests. - Settings kept on the interface: port A's direction (output or input), output
rate, break and mark-after-break, full 512-channel frames, RDM on or off and the
spacing between requests, and what to send when the computer stops sending (stop, all
0 or all 255) after a timeout or when the software closes the port. - A serial port per DMX port (a setting): the interface shows up as two one-port
interfaces, so software that drives one port per interface, such as Lightkey, can use
both ports, each from its own universe. Port B can then also receive DMX. - Its own USB ID, 2E8A:1180, granted by Raspberry Pi, so lighting software can
recognize the interface by its USB ID. Builds up to 1.0.10 used the shared Raspberry
Pi Pico ID (2E8A:000A); after updating from one, the computer sees a new device and
assigns it a new serial (COM) port. - Updates without opening the case: software puts the interface into its boot loader
(label 1), and the new .uf2 is copied onto the drive that appears.
Install or update
Hold BOOTSEL while plugging the DMX Core Pico 2 into USB (or, from this firmware, send label 1 or run picotool reboot -u), and copy dmxcore-pico2-usb-interface-1.0.17.uf2 onto the RPI-RP2 drive. To go back to the Re-Mapper, copy its .uf2 the same way.
THIRD-PARTY-NOTICES.txt lists the open-source code in the firmware and its licenses.
DMX Core Pico 2 USB Interface 1.0.16
The first release of the USB Interface firmware for the DMX Core Pico 2: a two-port
USB DMX interface.
- Enttec DMX USB Pro protocol, with two-port extensions: port A on labels 6 and
0x64, port B on label 0x65. Works with lighting software that supports the Enttec DMX
USB Pro or the DMXking ultraDMX, and with OLA on Linux. - Steady DMX output: the interface repeats the latest frame on its own, at the
output rate (1-40 frames per second, or 0 for as fast as the frame allows), whatever
the computer is doing. - DMX input on port A, sent to the computer every frame or on change only.
- RDM on both ports: discovery, GET and SET. Port A works with RDM-capable software
such as OLA, through the Enttec protocol; port B through the second-port messages QLC+
uses; both ports work with the DMX Core configuration utility. DMX keeps going between
RDM requests. - Settings kept on the interface: port A's direction (output or input), output
rate, break and mark-after-break, full 512-channel frames, RDM on or off and the
spacing between requests, and what to send when the computer stops sending (stop, all
0 or all 255) after a timeout or when the software closes the port. - A serial port per DMX port (a setting): the interface shows up as two one-port
interfaces, so software that drives one port per interface, such as Lightkey, can use
both ports, each from its own universe. Port B can then also receive DMX. - Its own USB ID, 2E8A:1180, granted by Raspberry Pi, so lighting software can
recognize the interface by its USB ID. Builds up to 1.0.10 used the shared Raspberry
Pi Pico ID (2E8A:000A); after updating from one, the computer sees a new device and
assigns it a new serial (COM) port. - Updates without opening the case: software puts the interface into its boot loader
(label 1), and the new .uf2 is copied onto the drive that appears.
Install or update
Hold BOOTSEL while plugging the DMX Core Pico 2 into USB (or, from this firmware, send label 1 or run picotool reboot -u), and copy dmxcore-pico2-usb-interface-1.0.16.uf2 onto the RPI-RP2 drive. To go back to the Re-Mapper, copy its .uf2 the same way.
THIRD-PARTY-NOTICES.txt lists the open-source code in the firmware and its licenses.