(09-08-2025, 12:10 PM)XORadmin Wrote: This looks a bit like either cable / connection issues or a hardware issue (maybe power). It's surely not related to the latest Firmware Release candidate.
In general, never hotplug any of the expanders (or change the channel).
Try to isolate the issue to a specific cable or expander. If it gets detected on multiple NSA then there is something wrong for sure. That could lead of course then to the individual ports not working properly.
I'll connnect the CV16 directly to NS, check cables/connections, try if that works normally on all NSA ports and do the same for the Trigger16.
I'm not hotplugging anything, but thanks for the heads up!
(09-08-2025, 01:09 PM)DriesG Wrote:(09-08-2025, 12:10 PM)XORadmin Wrote: This looks a bit like either cable / connection issues or a hardware issue (maybe power). It's surely not related to the latest Firmware Release candidate.
In general, never hotplug any of the expanders (or change the channel).
Try to isolate the issue to a specific cable or expander. If it gets detected on multiple NSA then there is something wrong for sure. That could lead of course then to the individual ports not working properly.
I'll connnect the CV16 directly to NS, check cables/connections, try if that works normally on all NSA ports and do the same for the Trigger16.
I'm not hotplugging anything, but thanks for the heads up!
Problem occurs when CV16 jumper is set to NSA-2.
Same behaviour when connecting CV16 straight to NS NSA header, no other expanders installed. Any other NSA address works normal. I've tested different psu's & ribbon cables, ruling out any of these possibilities. Trigger16 works as normal on NSA-2.
Thanks for your help.