I'm trying to use a Nomad dongle to run 2 universes of DMX though a Gadget II. I'm running over an older Macbook pro 13" and headed into my dimming system via a net2 input node. It seems to connect initially and bring up the loaded Cue and relays, but within 2 seconds it dumps all DMX. If i fire another cue, it will bring those lights up again for a moment and then dump them again. Any thoughts?
Do you have a chance to test the Gadget's outputs with a DMX tester to determine if the issue is on the Gadget-sider oder the receiving device-side ?
Is there any chance that something else is connected to the net2 and is sending data with a higher priority that is cancelling your data. eg another console or architectural lighting control?
if i run the gadget into a moving head directly, i don't seem to have any issues so i don't think the gadget is at fault.
I've matched it to the other consoles on the system, and turned off the other consoles.
i attempted to change the DMX speed thinking that slowing down the data would effect some kind of change. It has allowed the lights to turn on for 5 sec, then off for 5 sec, then on. it seems as though there is a data stream issue that is not continuous.
It feels like you do have something else sending commands as well, and slowing the speed has just shifted the timing around a bit as to when the other thing gets to interrupt or something. I think I would be trying to test things with nothing else connected that could be sending the conflicting stuff - you've turned off other consoles but does the hall have any wall plates that also control the house lights as they could be sending commands on the network as well and produce the kind of thing you are seeing.
Solved it. Had a buggy net2 node in the mix. I hard wired the nomad straight into the dmx back up line on the wall and it was stable. Replaced my input node, and now has been stable. Thanks for the ideas and suggestions!