The programmable platform

ZC95: room for four channels and your own patterns.

The ZC95 is a distinct open project inspired by the MK312-BT. Its appeal lies in its control options as well as its hardware.

What changes your buying decision

The project documents four isolated channels, custom Lua patterns and remote access over Wi-Fi or serial. Audio input supports line-level or microphone operation. These features make the ZC95 worth investigating when your requirements go beyond selecting a built-in programme.

Customisation also creates questions to answer before buying. Which firmware is installed? How are patterns transferred? What documentation accompanies the finished device? A ready-made commercial unit and a self-built reference design can share a project name while offering different assembly, warranty and support arrangements.

MKI and MKII are different hardware generations

The MKII reference design combines boards into a smaller arrangement. It uses USB-C charging and a 26650 cell instead of the earlier 12 V sealed lead-acid battery concept. Output connectors change from 2.5 mm to 3.5 mm, and serial and audio connections become separate sockets.

These changes affect packing, charging and cable selection. They do not by themselves demonstrate a universal increase in output strength. If you already own an MKI, compare the manual and connector assignments before carrying accessories across to an MKII.

Treat wireless functions individually

Wi-Fi control, BLE button support and experimental streaming are different functions. They should not be compressed into a promise of universal Bluetooth-app control. Match your intended workflow to the relevant section of the project documentation, including any firmware requirement.

You can use the platform as a standalone device; custom code is an option, not a prerequisite for reading this guide. If Lua is central to your plans, investigate the pattern documentation before purchasing. Think about maintenance too: record the firmware version and keep a copy of the documentation for your build.

Where the ZC95 fits

Compare it with MK312-BT when the familiar 312 approach interests you but channel count or programmability could change your choice. Compare it with 2B when the software ecosystem matters more than the number of outputs.

View the STIM-SYSTEM ZC95 MKII build ↗. The history page explains the distinction between hardware generations and firmware milestones.