03-11-2023, 09:55 PM
So far program changes on the MRCC have a couple of hiccups (there may be a bug that needs fixing, but it's easy to work around), however they are handled as follows:
The MRCC is supposed to listen on one channel of one port for PC messages targeting the MRCC, that port was initially Port 1 Ch 16. This seemed problematic in the sense that not everyone was expecting to use that functionality and the way it works it blocks those signals from being routed through to downstream devices from that channel of that port. So I asked Steve to disable these by default which he did, now if you want to use that function you need to enable it in the menu, and select a port and channel. Well it seems like while there is no selected port and channel at initialization, the PC messages are still being filtered out until you select a port and channel. It can be worked around by selecting a port and channel that you are not planning to use for PC messages (like Port 6 in Ch 16 for instance). Once that is done you should be able to pass PC messages on any other port and channel combination.
It's not a bad idea to update the FW to the current version if it's not been done for a while too, the instructions and link for that process is here:
https://conductivelabs.com/download/mrcc...re-update/
The MRCC is supposed to listen on one channel of one port for PC messages targeting the MRCC, that port was initially Port 1 Ch 16. This seemed problematic in the sense that not everyone was expecting to use that functionality and the way it works it blocks those signals from being routed through to downstream devices from that channel of that port. So I asked Steve to disable these by default which he did, now if you want to use that function you need to enable it in the menu, and select a port and channel. Well it seems like while there is no selected port and channel at initialization, the PC messages are still being filtered out until you select a port and channel. It can be worked around by selecting a port and channel that you are not planning to use for PC messages (like Port 6 in Ch 16 for instance). Once that is done you should be able to pass PC messages on any other port and channel combination.
It's not a bad idea to update the FW to the current version if it's not been done for a while too, the instructions and link for that process is here:
https://conductivelabs.com/download/mrcc...re-update/