DMX Issue Resolved : (Lighting)

 I was able to narrow down the issue after manually reviewing the cabling and flow. Unfortunately, this still leads me to 2 issues, even known the main one is solved.

But first, what was the Main Issue?

    The Pathport UNO unit that connects our networking layer to the physical Dimmer Rack layer failed, even know the status of the unit was active and showing output of DMX Data. That was very odd since I relied on the tools we had to find the issue, and such appeared to always be functioning.


How did I find this issue?

    Using the experimental DMX flow chart I made, I was able to narrow it down to the physical UNO unit, as it was either that or the physical DMX going into the ETC. But still, that would be very unlikely since Q-Sys then wouldn't have a way of interacting with the dimmer Rack.

- I didn't believe I mentioned earlier, but the reason I didn't figure this out sooner was because we had a Pathport Quattro Gateway on the 2nd floor of the booth, which I figured acts as the gateway to the Dimmer rack, and since it accepts network sACN and outputs to DMX, which then leads down into the booth and plugs into another DMX wallport... It was outputting that it was receiving and sending DMX data on the physical unit, but following the cable, it was genuinely leading to absolutely nowhere; the DMX cable it was plugged into was not even fully connected to the wall, it was just in enough to the point where it doesn't make contact, but stays in to not fall out.

ANYWAYS

    I was able to find this issue by looking at the Error logs output from my Q-Sys core, and then connecting into the physical managed switch to inspect the connection of the gateway to the network. It stated that it was completely disconnected, and it thought that nothing was plugged in. That's very troublesome.

    After some inspection, I went through the basic fixes, unplugged it, and then replugged it. I replaced the Ethernet cable and disconnected it to give it some time to think about what it's done.
    Even know I now have a Spare Pathport Quarttro I can drop into the rack and make magic. This is still a very expensive $500 unit that possibly just stopped functioning, and I very much would like to make it work so that life can move on.

    After following all these steps and physically restarting the entire networking layer, it actually started functioning again. I saw that the switch recognized that its port was active, Q-Sys no longer showed any (Failed to reach) errors, and after restarting the ETC console, it was able to actually send DMX data to the dimmer rack. So the issue is solved! The Pathport UNO just needed a bit of attention. 

Is this a permanent fix?

It seems to be so, after playing around with it a bit and testing the cable, that all seems fine. I got rid of the older, sticky cable with a nice new patch cable. The Issue seemed to be the actual Networking layer, which seems to be fully corrected now.


What caused the Error?

I'd like to assume it has something to do with a power outage we had during the weekend, and due to this such our system UPS was fully drained, and something happened to the actual Layer 2 Switch that caused the connection to rip, and after powering back on, the issue persisted. I can say this confidently because I was able to recognize that some other ports received the same treatment and turned off, even know the devices they were connected to received POE, and (Supposed Data), but in reality, when checking the switch, they had the same issue as the UNO.

    The Switch is surge-protected, and it is on a battery backup, so I'm unsure of how this issue might be reproduced.


Now even know lighting works, there are a couple of other questions we need to ask.

First Conspiracy Theory.

  1. Where does the DMX connect to the inside of the rack? 

    Thankfully, I found out where the input cable is, but from there, it leads into piping that is completely unlabeled and undocumented.

Inspecting the physical hardware, there are no visible input ports, no Phoenix connectors, nor any stripped connections anywhere. After removing the C21 core processor and following the online guide for the board connections, I was unable to narrow it down, apart from a few sketchy old connections that work but will need some attention.

    Otherwise, if something were to happen to this connection, we would be out of service even longer until we physically disassemble it.


And unfortunately, this is the most valuable information that the official C21 user guide offers, which still does not expose where they're connected. If you'd like to you can check out the Operation guide yourself.



2nd Issue?

    The ETC console has 1 RJ45 port in and 2 DMX ins. The RJ45 connects our console to the network in order to communicate via sACN. The 2nd DMX port communicates to the fixtures I manually installed overhead the A/V booth for frontstage lighting.

    But the first DMX port simply leads into the wall. Our Strand Dimming Rack has always shown 1 actual connection, a Single DMX input from Port A. There was never a secondary Input or an Ethernet connection. So the question is, what does that cable do, and is it even necessary? I will be testing later on when I get a chance to do so.


This is it for now. I will be updating this later on. Next up, expect more Q-Sys updates in terms of the New versions. I will be releasing a patchnote for every version from the present to the future. I will not cover the old versions I've made unless required.

Thank you for reading.

Comments

Popular posts from this blog

Restoration Of Floor Plans & schematics

Why Lighting Sucks. (When done wrong)