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

wondering if anyone has come across any strange issues with pathway products. 
I’ve got a fairly large static rig, occupying around 16 Universes with circa 8 pathways splitting the universes up there (ergo, one pathway dealing with U6 & U7, next one U8 & U9).

99% of the time, rig is fine, behaves as it should. But randomly, that 1%, random gateways lose one their universe outputs… (display shows dmx output, no universe). 

fix requires reboot of POE supply to Gateway when disconnected from DMX chain. 

Am I looking at some weird RDM Blinding on Fixture boot? Or some other DMX Control Knocking the Universe out such as Standalone from the fixtures?

Rig Comprises largely of CHAUVET maverick heads…

Parents Reply Children
  • 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.

Related