https://iomixer.com/forums/ Wed, 04 Nov 2026 20:00:45 +0000 MyBB https://iomixer.com/forums/showthread.php?tid=409 Sun, 18 Oct 2026 01:13:02 +0000 iforce2d]]> https://iomixer.com/forums/showthread.php?tid=409
This requires a browser that supports WebSerial API, you can see details on browser support here: 
https://developer.mozilla.org/en-US/docs...patibility

As well as being much more convenient than the relay server (both for usage and developing/maintaining!), the performance also feels a bit faster.

The best experience seems to be with Chrome based browsers. With Chrome, any devices you've connected to previously will be automatically reconnected when the page is reloaded, and the device previously used for each document will be reactivated. Firefox requires manually reconnecting every time...

Note that the bootloader is recognized as a different device to the normal firmware, so when the browser encounters each bootloader for the first time you'll need to connect to the device manually.

Other changes:

- devices can be renamed to more easily differentiate them (default name is the serial number)
- when keyboard focus is not on an input element, number keys 1-9 can be used as hotkeys to select the content of the right-hand panel
- after adding a new node it will be automatically selected (this is so that with hotkey 1 the properties of the new node can be quickly edited)
- the 'range' property of 'tweak number' node now takes a string input like "3-7" to define the slider extents as absolute numbers rather than a relative window around the 'value'
- finally minified and bundled JavaScript files, bringing HTTP requests required for initial page load from 220+ to about 26
- many various improvements and fixes

This update required touching a LOT of code, so some problems are likely to come up here and there. Please let me know if something seems to be not working properly.]]>
This requires a browser that supports WebSerial API, you can see details on browser support here: 
https://developer.mozilla.org/en-US/docs...patibility

As well as being much more convenient than the relay server (both for usage and developing/maintaining!), the performance also feels a bit faster.

The best experience seems to be with Chrome based browsers. With Chrome, any devices you've connected to previously will be automatically reconnected when the page is reloaded, and the device previously used for each document will be reactivated. Firefox requires manually reconnecting every time...

Note that the bootloader is recognized as a different device to the normal firmware, so when the browser encounters each bootloader for the first time you'll need to connect to the device manually.

Other changes:

- devices can be renamed to more easily differentiate them (default name is the serial number)
- when keyboard focus is not on an input element, number keys 1-9 can be used as hotkeys to select the content of the right-hand panel
- after adding a new node it will be automatically selected (this is so that with hotkey 1 the properties of the new node can be quickly edited)
- the 'range' property of 'tweak number' node now takes a string input like "3-7" to define the slider extents as absolute numbers rather than a relative window around the 'value'
- finally minified and bundled JavaScript files, bringing HTTP requests required for initial page load from 220+ to about 26
- many various improvements and fixes

This update required touching a LOT of code, so some problems are likely to come up here and there. Please let me know if something seems to be not working properly.]]> https://iomixer.com/forums/showthread.php?tid=408 Tue, 22 Sep 2026 03:13:33 +0000 iforce2d]]> https://iomixer.com/forums/showthread.php?tid=408
https://iomixer.com/logstream


  Selection_1526.png (Size: 267.51 KB / Downloads: 2)

The inputs (coming from iomixer 'Log output' nodes) are updated in real-time and displayed as numbers, UI elements and on a graph. Outputs (received by the iomixer as 'Log input' nodes) can be controlled in real-time. 

But the main purpose of the page is to allow more complex behaviors via scripting. You can write a script in JavaScript to get and set values of nodes at up to 50Hz for 32 values each way. There is a code editor with compile error highlighting. All regular features of JavaScript are available plus a few custom functions related to the interaction with iomixer. For now the goal was to have a highly interactive mini-IDE kinda thing, but it could be tidied up a bit into an API of sorts if people want to make their own more custom dashboard/control panel.]]>
https://iomixer.com/logstream


  Selection_1526.png (Size: 267.51 KB / Downloads: 2)

The inputs (coming from iomixer 'Log output' nodes) are updated in real-time and displayed as numbers, UI elements and on a graph. Outputs (received by the iomixer as 'Log input' nodes) can be controlled in real-time. 

But the main purpose of the page is to allow more complex behaviors via scripting. You can write a script in JavaScript to get and set values of nodes at up to 50Hz for 32 values each way. There is a code editor with compile error highlighting. All regular features of JavaScript are available plus a few custom functions related to the interaction with iomixer. For now the goal was to have a highly interactive mini-IDE kinda thing, but it could be tidied up a bit into an API of sorts if people want to make their own more custom dashboard/control panel.]]> https://iomixer.com/forums/showthread.php?tid=407 Tue, 22 Sep 2026 02:34:13 +0000 iforce2d]]> https://iomixer.com/forums/showthread.php?tid=407 https://iomixer.com/releases/firmware/v0.1.6

Changes:
- improved speed of 'Upload+write' by about 10x
- 'Memory used' value changed to 'Untouched memory', with better measurement (actual stack - heap margin)
- Log input node: value type 'Field' option separated into float/color/int32 options
- serial number in USB descriptor now includes suffix like -C, -CG, -CM to differentiate same device running with different USB class (VCP, VCP+gamepad, VCP+midi etc). This helps Windows to apply the correct device drivers after switching between USB classes.
- separate builds for different RAM specs (previously the F103RE boards with 64kb were only utilizing 48kb)

I have removed the 'xperimental' section which was only being updated sporadically, and will now include the 8MHz and blue-pill builds in the main folder as a matter of course.

Firmware files will now be named in more detail to reflect their content, eg. iomixer-512kb-64kb-12MHz-0.1.6.bin

Bootloader files rarely change so have been removed from the per-firmware release folders, will be kept separately at: https://iomixer.com/releases/firmware/bootloader

The 'both' files are no longer being provided. These were just a concatenation of the bootloader and main firmware that is convenient when you're flashing a whole bunch of boards at the same time.]]> https://iomixer.com/releases/firmware/v0.1.6

Changes:
- improved speed of 'Upload+write' by about 10x
- 'Memory used' value changed to 'Untouched memory', with better measurement (actual stack - heap margin)
- Log input node: value type 'Field' option separated into float/color/int32 options
- serial number in USB descriptor now includes suffix like -C, -CG, -CM to differentiate same device running with different USB class (VCP, VCP+gamepad, VCP+midi etc). This helps Windows to apply the correct device drivers after switching between USB classes.
- separate builds for different RAM specs (previously the F103RE boards with 64kb were only utilizing 48kb)

I have removed the 'xperimental' section which was only being updated sporadically, and will now include the 8MHz and blue-pill builds in the main folder as a matter of course.

Firmware files will now be named in more detail to reflect their content, eg. iomixer-512kb-64kb-12MHz-0.1.6.bin

Bootloader files rarely change so have been removed from the per-firmware release folders, will be kept separately at: https://iomixer.com/releases/firmware/bootloader

The 'both' files are no longer being provided. These were just a concatenation of the bootloader and main firmware that is convenient when you're flashing a whole bunch of boards at the same time.]]> https://iomixer.com/forums/showthread.php?tid=40 Fri, 31 Jul 2026 03:35:08 +0000 devin]]> https://iomixer.com/forums/showthread.php?tid=40 IOMixer HAT boards.
Project links:

• IOMixer HAT for STM32F103RCT6 Generic Board: https://oshwlab.com/devfisher/project_cojnqego
  
• IOMixer HAT for STM32F103RCT6 FK103M2 Board: https://oshwlab.com/devfisher/project_lxiegdql
  

These adapter boards let you use inexpensive STM32 development boards with the IOMixer ecosystem while remaining compatible with the IOMixer Configurator.

The goal of this project is to provide an alternative hardware platform for IOMixer using available STM32 development boards. The boards are designed for DIY assembly using commonly available through-hole components. The project pages include full details, including assembly information and design files.

I also have a small number of extra PCBs that I'd be happy to send to anyone in the USA who is interested in building one. They will be available on a first-come, first-served basis, so if you'd like one, send me a DM.

One thing to be aware of: a small hardware modification is required to support the IOMixer bootloader button. It's a simple change, and I'll explain what's required if you contact me about a board.

I'd love to hear any feedback or suggestions!

  hats.jpg (Size: 479.35 KB / Downloads: 1) ]]> IOMixer HAT boards.
Project links:

• IOMixer HAT for STM32F103RCT6 Generic Board: https://oshwlab.com/devfisher/project_cojnqego
  
• IOMixer HAT for STM32F103RCT6 FK103M2 Board: https://oshwlab.com/devfisher/project_lxiegdql
  

These adapter boards let you use inexpensive STM32 development boards with the IOMixer ecosystem while remaining compatible with the IOMixer Configurator.

The goal of this project is to provide an alternative hardware platform for IOMixer using available STM32 development boards. The boards are designed for DIY assembly using commonly available through-hole components. The project pages include full details, including assembly information and design files.

I also have a small number of extra PCBs that I'd be happy to send to anyone in the USA who is interested in building one. They will be available on a first-come, first-served basis, so if you'd like one, send me a DM.

One thing to be aware of: a small hardware modification is required to support the IOMixer bootloader button. It's a simple change, and I'll explain what's required if you contact me about a board.

I'd love to hear any feedback or suggestions!

  hats.jpg (Size: 479.35 KB / Downloads: 1) ]]> https://iomixer.com/forums/showthread.php?tid=19 Wed, 13 May 2026 19:58:52 +0000 devin]]> https://iomixer.com/forums/showthread.php?tid=19
See the configuration below, as simple as I could make. I can see the onboard led change when I press the user key button on my board. I can also see the live values reflect what I expect.

What I know:

• Seem to only have issues with Linux (have successfully run it on windows) 
  
• Can see the midi device on Linux ( list in terminal 'amidi -l' and can see the device on https://hardwaretester.com/midi )
  
• Cannot see any events on the bus
  

What I have tried:

• Have tried both channel 0 and channel 1
  
• Have tried a few indexes
  

Maybe it is some Linux permission issue? Not sure.

Running:
Board: Homemade FrankenBoard based on this dev board: https://stm32-base.org/boards/STM32F103R...103M2-V1.0
Bootloader: xperimental/8MHz 1.5
Firmware: xperimental/8MHz/ 1.5

  Screenshot_20260513_134806.png (Size: 107.74 KB / Downloads: 3) ]]>
See the configuration below, as simple as I could make. I can see the onboard led change when I press the user key button on my board. I can also see the live values reflect what I expect.

What I know:

• Seem to only have issues with Linux (have successfully run it on windows) 
  
• Can see the midi device on Linux ( list in terminal 'amidi -l' and can see the device on https://hardwaretester.com/midi )
  
• Cannot see any events on the bus
  

What I have tried:

• Have tried both channel 0 and channel 1
  
• Have tried a few indexes
  

Maybe it is some Linux permission issue? Not sure.

Running:
Board: Homemade FrankenBoard based on this dev board: https://stm32-base.org/boards/STM32F103R...103M2-V1.0
Bootloader: xperimental/8MHz 1.5
Firmware: xperimental/8MHz/ 1.5

  Screenshot_20260513_134806.png (Size: 107.74 KB / Downloads: 3) ]]> https://iomixer.com/forums/showthread.php?tid=2 Mon, 18 Nov 2024 05:43:32 +0000 Kermets]]> https://iomixer.com/forums/showthread.php?tid=2
using waterfox which is the same as FF

Cheers Brett

  com 13.jpg (Size: 314.53 KB / Downloads: 5) ]]>
using waterfox which is the same as FF

Cheers Brett

  com 13.jpg (Size: 314.53 KB / Downloads: 5) ]]> https://iomixer.com/forums/showthread.php?tid=1 Thu, 31 Oct 2024 17:08:53 +0000 mdroberts1243]]> https://iomixer.com/forums/showthread.php?tid=1
Is Remora ( or equivalent ) supported for LinuxCNC?]]>
Is Remora ( or equivalent ) supported for LinuxCNC?]]>