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

 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.

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.

I’ve been having the same issue with our rig. Did this firmware update have a positive impact? Thanks!

Andrew is the only person reported to have a firmware update to trial, not heard anything further….

Disabling the per CH priority has been fairly bomb proof for me so far… no reported issues (yet!).

So two things happened at the same time. We originally disabled the "per channel priority" and that seemed to solve it.

I was also sent a beta version of the software that was updated to all two-port devices. Then we re-enabled the per channel priority. There have been no issues since.

Here's the explanation from Pathway:

BACKGROUND: Per Channel Priority is part of the E1.31 sACN standard that allows setting a priority between 1 and 200 for each of the 512 data slots. Pathway Connectivity Solution's Pathports have always supported this method of operation, but by default, the check box is not checked - meaning that the entire Universe is evaluated for a priority between 1 and 200; far and away the most common use of sACN priorities. Venues that employ an ETC Paradigm architectural controller often opt to use PCP as that is the native way of setting priorities on these networks.
 
The attached version of firmware is v6.3.4-rc.1. The RC stands for Release Candidate. If you are willing and able, please unzip the file into a directory and from Pathscape's Tools menu, launch the Firmware Updater and select 
 
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.

This was back in May/June so that software may be out in general release now. I am not on a computer where I can check.

ETC: I can send you a copy of that software version if you want.