<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[iomixer forums - All Forums]]></title>
		<link>https://iomixer.com/forums/</link>
		<description><![CDATA[iomixer forums - https://iomixer.com/forums]]></description>
		<pubDate>Thu, 15 Oct 2026 14:17:04 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA['Logstream' utility]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=408</link>
			<pubDate>Tue, 22 Sep 2026 03:13:33 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=1">iforce2d</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=408</guid>
			<description><![CDATA[I made a page that uses WebSerial to read and write values from the 'Log output' and 'Log input' nodes. This requires a USB-serial adapter and UART pins on the iomixer (not the regular USB connection). <br />
<br />
<a href="https://iomixer.com/logstream" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/logstream</a><br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=10" target="_blank" title="">Selection_1526.png</a> (Size: 267.51 KB / Downloads: 1)
<!-- end: postbit_attachments_attachment --><br />
<br />
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. <br />
<br />
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.]]></description>
			<content:encoded><![CDATA[I made a page that uses WebSerial to read and write values from the 'Log output' and 'Log input' nodes. This requires a USB-serial adapter and UART pins on the iomixer (not the regular USB connection). <br />
<br />
<a href="https://iomixer.com/logstream" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/logstream</a><br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=10" target="_blank" title="">Selection_1526.png</a> (Size: 267.51 KB / Downloads: 1)
<!-- end: postbit_attachments_attachment --><br />
<br />
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. <br />
<br />
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.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Firmware release v0.1.6]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=407</link>
			<pubDate>Tue, 22 Sep 2026 02:34:13 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=1">iforce2d</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=407</guid>
			<description><![CDATA[Download here: <a href="https://iomixer.com/releases/firmware/v0.1.6" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/releases/firmware/v0.1.6</a><br />
<br />
Changes:<br />
- improved speed of 'Upload+write' by about 10x<br />
- 'Memory used' value changed to 'Untouched memory', with better measurement (actual stack - heap margin)<br />
- Log input node: value type 'Field' option separated into float/color/int32 options<br />
- 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.<br />
- separate builds for different RAM specs (previously the F103RE boards with 64kb were only utilizing 48kb)<br />
<br />
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.<br />
<br />
Firmware files will now be named in more detail to reflect their content, eg. iomixer-512kb-64kb-12MHz-0.1.6.bin<br />
<br />
Bootloader files rarely change so have been removed from the per-firmware release folders, will be kept separately at: <a href="https://iomixer.com/releases/firmware/bootloader" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/releases/firmware/bootloader</a><br />
<br />
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.]]></description>
			<content:encoded><![CDATA[Download here: <a href="https://iomixer.com/releases/firmware/v0.1.6" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/releases/firmware/v0.1.6</a><br />
<br />
Changes:<br />
- improved speed of 'Upload+write' by about 10x<br />
- 'Memory used' value changed to 'Untouched memory', with better measurement (actual stack - heap margin)<br />
- Log input node: value type 'Field' option separated into float/color/int32 options<br />
- 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.<br />
- separate builds for different RAM specs (previously the F103RE boards with 64kb were only utilizing 48kb)<br />
<br />
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.<br />
<br />
Firmware files will now be named in more detail to reflect their content, eg. iomixer-512kb-64kb-12MHz-0.1.6.bin<br />
<br />
Bootloader files rarely change so have been removed from the per-firmware release folders, will be kept separately at: <a href="https://iomixer.com/releases/firmware/bootloader" target="_blank" rel="noopener" class="mycode_url">https://iomixer.com/releases/firmware/bootloader</a><br />
<br />
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.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[iomixer hats]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=40</link>
			<pubDate>Fri, 31 Jul 2026 03:35:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=46">devin</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=40</guid>
			<description><![CDATA[I've published the project pages for my <span style="font-weight: bold;" class="mycode_b">IOMixer HAT</span> boards.<br />
Project links:<ul class="mycode_list"><li>IOMixer HAT for STM32F103RCT6 Generic Board: <a href="https://oshwlab.com/devfisher/project_cojnqego" target="_blank" rel="noopener" class="mycode_url">https://oshwlab.com/devfisher/project_cojnqego</a><br />
</li>
<li>IOMixer HAT for STM32F103RCT6 FK103M2 Board: <a href="https://oshwlab.com/devfisher/project_lxiegdql" target="_blank" rel="noopener" class="mycode_url">https://oshwlab.com/devfisher/project_lxiegdql</a><br />
</li>
</ul>
<br />
These adapter boards let you use inexpensive STM32 development boards with the IOMixer ecosystem while remaining compatible with the IOMixer Configurator.<br />
<br />
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.<br />
<br />
I also have a small number of extra PCBs that I'd be happy to send to anyone in the <span style="font-weight: bold;" class="mycode_b">USA</span> who is interested in building one. They will be available on a <span style="font-weight: bold;" class="mycode_b">first-come, first-served</span> basis, so if you'd like one, send me a DM.<br />
<br />
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.<br />
<br />
I'd love to hear any feedback or suggestions!<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=9" target="_blank" title="">hats.jpg</a> (Size: 479.35 KB / Downloads: 1)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[I've published the project pages for my <span style="font-weight: bold;" class="mycode_b">IOMixer HAT</span> boards.<br />
Project links:<ul class="mycode_list"><li>IOMixer HAT for STM32F103RCT6 Generic Board: <a href="https://oshwlab.com/devfisher/project_cojnqego" target="_blank" rel="noopener" class="mycode_url">https://oshwlab.com/devfisher/project_cojnqego</a><br />
</li>
<li>IOMixer HAT for STM32F103RCT6 FK103M2 Board: <a href="https://oshwlab.com/devfisher/project_lxiegdql" target="_blank" rel="noopener" class="mycode_url">https://oshwlab.com/devfisher/project_lxiegdql</a><br />
</li>
</ul>
<br />
These adapter boards let you use inexpensive STM32 development boards with the IOMixer ecosystem while remaining compatible with the IOMixer Configurator.<br />
<br />
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.<br />
<br />
I also have a small number of extra PCBs that I'd be happy to send to anyone in the <span style="font-weight: bold;" class="mycode_b">USA</span> who is interested in building one. They will be available on a <span style="font-weight: bold;" class="mycode_b">first-come, first-served</span> basis, so if you'd like one, send me a DM.<br />
<br />
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.<br />
<br />
I'd love to hear any feedback or suggestions!<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=9" target="_blank" title="">hats.jpg</a> (Size: 479.35 KB / Downloads: 1)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Midi Out issue on linux]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=19</link>
			<pubDate>Wed, 13 May 2026 19:58:52 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=46">devin</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=19</guid>
			<description><![CDATA[I'm running into an issue with midi out support.<br />
<br />
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.<br />
<br />
What I know:<ul class="mycode_list"><li>Seem to only have issues with Linux (have successfully run it on windows) <br />
</li>
<li>Can see the midi device on Linux ( list in terminal 'amidi -l' and can see the device on <a href="https://hardwaretester.com/midi" target="_blank" rel="noopener" class="mycode_url">https://hardwaretester.com/midi</a> )<br />
</li>
<li>Cannot see any events on the bus<br />
</li>
</ul>
<br />
What I have tried:<ul class="mycode_list"><li>Have tried both channel 0 and channel 1<br />
</li>
<li>Have tried a few indexes<br />
</li>
</ul>
<br />
Maybe it is some Linux permission issue? Not sure.<br />
<br />
Running:<br />
Board: Homemade FrankenBoard based on this dev board: <a href="https://stm32-base.org/boards/STM32F103RCT6-FK103M2-V1.0" target="_blank" rel="noopener" class="mycode_url">https://stm32-base.org/boards/STM32F103R...103M2-V1.0</a><br />
Bootloader: xperimental/8MHz 1.5<br />
Firmware: xperimental/8MHz/ 1.5<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=8" target="_blank" title="">Screenshot_20260513_134806.png</a> (Size: 107.74 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[I'm running into an issue with midi out support.<br />
<br />
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.<br />
<br />
What I know:<ul class="mycode_list"><li>Seem to only have issues with Linux (have successfully run it on windows) <br />
</li>
<li>Can see the midi device on Linux ( list in terminal 'amidi -l' and can see the device on <a href="https://hardwaretester.com/midi" target="_blank" rel="noopener" class="mycode_url">https://hardwaretester.com/midi</a> )<br />
</li>
<li>Cannot see any events on the bus<br />
</li>
</ul>
<br />
What I have tried:<ul class="mycode_list"><li>Have tried both channel 0 and channel 1<br />
</li>
<li>Have tried a few indexes<br />
</li>
</ul>
<br />
Maybe it is some Linux permission issue? Not sure.<br />
<br />
Running:<br />
Board: Homemade FrankenBoard based on this dev board: <a href="https://stm32-base.org/boards/STM32F103RCT6-FK103M2-V1.0" target="_blank" rel="noopener" class="mycode_url">https://stm32-base.org/boards/STM32F103R...103M2-V1.0</a><br />
Bootloader: xperimental/8MHz 1.5<br />
Firmware: xperimental/8MHz/ 1.5<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=8" target="_blank" title="">Screenshot_20260513_134806.png</a> (Size: 107.74 KB / Downloads: 3)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Cant tick Com port]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=2</link>
			<pubDate>Mon, 18 Nov 2024 05:43:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=25">Kermets</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=2</guid>
			<description><![CDATA[Hay there Chris, Im not able to tick the port 13 box on left looks like its greyed out ?<br />
<br />
using waterfox which is the same as FF<br />
<br />
Cheers Brett<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=2" target="_blank" title="">com 13.jpg</a> (Size: 314.53 KB / Downloads: 5)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[Hay there Chris, Im not able to tick the port 13 box on left looks like its greyed out ?<br />
<br />
using waterfox which is the same as FF<br />
<br />
Cheers Brett<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://iomixer.com/forums/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=2" target="_blank" title="">com 13.jpg</a> (Size: 314.53 KB / Downloads: 5)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Supporting Remora?]]></title>
			<link>https://iomixer.com/forums/showthread.php?tid=1</link>
			<pubDate>Thu, 31 Oct 2024 17:08:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://iomixer.com/forums/member.php?action=profile&uid=23">mdroberts1243</a>]]></dc:creator>
			<guid isPermaLink="false">https://iomixer.com/forums/showthread.php?tid=1</guid>
			<description><![CDATA[Hi,<br />
<br />
Is Remora ( or equivalent ) supported for LinuxCNC?]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
Is Remora ( or equivalent ) supported for LinuxCNC?]]></content:encoded>
		</item>
	</channel>
</rss>