Pathway 2 port gateway - Loss of DMX universe on one output

YES! I have a large system that includes Pathway 2-port portable gateways. I had the same issue with Port B losing its connection. After many back-and-forths with Pathway here is the first solution that seems to have fixed the problem.

Through Pathscape, under "Network DMX Properties" disable Per Channel Priority on the port. I believe it ships from ETC with this selected.

As far as I know, this has fixed the problem for the last 5 months. I am going back to this site next week for a 6-month follow-up and will see if this is still the case.

-Wolf

I've seen stuff like this as well. We didn't have to reboot the gateways, for us it was enough to open the config software, change the assigned universe and then change it back to what it had been before.

I had done that first, but the issue came back. We think it was something to do with the console being turned off and on. We tried duplicating and the console cycling seemed to trigger the issue, sometimes. Other times it was random and during times when the console was just on. Turning off the priority seems to have fixed it.
This space has 4 performance spaces and three rehearsal/studios and over 100 portable gateways. resetting the universe was not a long-term solution for us.

Nice, any paradigm also sitting on the back of the rig? 

I have some arbitration moving priority in show mode, but shouldn’t make any difference to these universes… just curious. 

Seven Paradigm processors in the overall system. ETC did the actual system config, not sure what arbitration is going on in the background.

Oof, I only had 2 processors sitting in the background…. 
I need to try this. Like you, resetting the universes every time isn’t an option… it’s just bizzare how it sits absolutely fine for ages, then randomly drops out. 

let us know if your checkup is positive… but I’m guessing you’ve not had any call outs in 5 months! 

 MWiggins , ueliriegg, and Andrew34375 Pathway is aware of this issue and has been working with us on a resolution.  As Andrew notes, disabling the Per-Channel Priority will alleviate the issue. However, as he notes as well, if you make use of Paradigm Arbitration it will prevent that from operating as expected.

Thanks Seth, I’ve implemented this on all 2 port gateways… fingers crossed. Can you please add me to a mailing list (if there is one) for me to be updated on fixes/updates. 

does this issue extend to 4 port versions too? 

We have about 9 4-port gateways on the same project and none of them have shown this issue. I recently received this from Pathway: "This bug only affected the 1-Port and 2-Port devices and almost always just the B-Port (hence, not often seen on the 1-Ports). It only affected systems that had PCP sACN active sources 24/7. The bug may have presented itself on legacy 10M Pathports or the newer 100M versions. The 4-Ports and 8-Port Pathports were never affected by this issue."

Just last week they sent me some new firmware but I have not been to the site to upload.