DJ Jules
25-02-2014, 07:27 AM
Following on from this post (http://www.forum.mobilediscodirectory.co.uk/showthread.php?41528-Wireless-DMX-retro-fit-of-my-fixtures!) yesterday about retro fitting fixtures with Wireless DMX, I got thinking about an issue I've been having for a while with a couple of my fixtures. I've got a pair of Eurolite Scanners and when I put them on the same DMX chain as my Acme Cougar's, they go nuts. Basically they switch from DMX control to master/slave and try and either slave the Cougar's or switch the Cougar's to master!
I normally get round this by putting them on their own DMX chain as I'm lucky enough to be using a DMX controller with four electrically isolated outputs. I'm assuming though that the problems are being caused by whatever custom protocol the Scanners and Cougar's are using to try and identify if there are any other fixtures on the DMX chain that they can talk to and I've been trying to work out how to block this from happening for a while. Yesterdays conversations about Wireless DMX and issues with the DMX Transceiver switching to "Transmit" mode because of the auto configuration stuff going on made this issue more relevant again as I've ordered 6 Wireless DMX PCB's :D I'm fairly sure that quite a few of my fixtures are going to cause issues with the Transceiver mode which will rule out hard wiring the PCB's to the DMX input - which means doing things like wiring the transceivers on separate power and enforcing a strict start up order (great fun if the power fails for any reason!!)
Does anyone know anything about the configuration protocol used by Acme and others? Has anyone else come across this problem? Has anyone found a solution? I've had a Google and have come up with nothing about this (or RDMX, which probably operates on similar principles).
Julian
I normally get round this by putting them on their own DMX chain as I'm lucky enough to be using a DMX controller with four electrically isolated outputs. I'm assuming though that the problems are being caused by whatever custom protocol the Scanners and Cougar's are using to try and identify if there are any other fixtures on the DMX chain that they can talk to and I've been trying to work out how to block this from happening for a while. Yesterdays conversations about Wireless DMX and issues with the DMX Transceiver switching to "Transmit" mode because of the auto configuration stuff going on made this issue more relevant again as I've ordered 6 Wireless DMX PCB's :D I'm fairly sure that quite a few of my fixtures are going to cause issues with the Transceiver mode which will rule out hard wiring the PCB's to the DMX input - which means doing things like wiring the transceivers on separate power and enforcing a strict start up order (great fun if the power fails for any reason!!)
Does anyone know anything about the configuration protocol used by Acme and others? Has anyone else come across this problem? Has anyone found a solution? I've had a Google and have come up with nothing about this (or RDMX, which probably operates on similar principles).
Julian