ArtNet DMX In - Radig Quad Net Node

FrankB · Sun Jan 16, 2022 11:32 pm

Hello, I have problems DMX In pee ArtNet. I have this Quad Net Node, have port 1 set as DMX In and port 2-4 set as DMX Out.
https://www.ulrichradig.de/home/index.p ... ad-art-net

If I set only the input (Port 1 Universe 0) in QLC+, QLC+ will also capture any movement of the sliders of the connected DMX controller.
If I then add an output on the same ArtNet Node, the Quad Net Node will no longer send DMX In packets.

Does anyone have an idea what I still have to adjust?

According to https://www.qlcplus.org/docs/html_en_EN ... lugin.html it should be possible to send and receive multiple universes on one IP address.

Does anyone know the Quad Net Node from Radig?

Many thanks and greetings

GGGss · Mon Jan 17, 2022 9:52 am

Welcome to the forum.

FrankB wrote: ↑Sun Jan 16, 2022 11:32 pm will also capture any movement of the sliders of the connected DMX controller

Who or what does make these sliders move? Another DMX desk?
Without studying the interface further, I would think that it is a configuration thing.

What would you need the DMX input for? It would help if you give a full overview of your situation...

FrankB · Tue Jan 18, 2022 6:32 pm

Hi GGGss, thanks for the reply and inquiry.
I have outlined what we have today and what I would like to set up.
Since our DMX controller can't control every RGB light we are very limited in the light show.
To keep the usual DMX controller for all volunteers I want to put QLC+ on a Raspberry Pi and Quad Net Node in between. On special occasions, a private tablet should then be used to start a rainbow running light, for example.

Unfortunately the DMX-In function on the Quad Net Node breaks down as soon as I activate the input in QLC+.

janosvitok · Tue Jan 18, 2022 10:10 pm

Frank,

do you use different universe for input and output (both in qlc+ and in artnet)?

Jano

FrankB · Wed Jan 19, 2022 12:08 am

Hi Jano, I used universe 0 for DMX-In and universe 1 for DMX-Out

QLC+ is still running on a Windows 10 PC, if it works as desired I would like to use the Raspberry Pi.

greetings, Frank

GGGss · Wed Jan 19, 2022 10:02 am

Frank,

Thank you for your well-drawn sketches

Nice.
In the case, where QLC+ sits in between, I would opt to use the thru function of a QLC+ interface.
So 1 Universe as in & output with the thru option clicked.
The Artnet universes have to be different.
Now ... Artnet Universes are sometimes 1-based (0=1, 1=2, ... 9=10). Maybe that is the problem you see.
1st I would set Artnet input Universe to 1 and Artnet output universe to 3, so there is a distinct difference and much easier to troubleshoot.
2nd: verify your setting with an Artnet sniffer like DMX workshop.

In the end you should be able to switch from one situation to the other simply by connecting the DMX out with the DMX in at your Artnet interface. That would be ideal.
(Oh and By The Way -> Use IP-addresses in the 10.x.x.x mask 255.0.0.0 range for Artnet. That will clearly make a difference while sniffing)
(And BTW2: Use Unicast in stead of Multicast, because wifi does not like multicast packets.)

FrankB · Wed Jan 19, 2022 11:35 pm

hi, I have changed the output in QLC+ to Universe 4 (ArtNet 3), unfortunately without success

The screenshot in the sketch are from DMX-Workshop

On another PC I watch the ArtNet with ArtNetView (https://artnetview.com/).

It's as if a "collision" or a "bad IP packet" kills the DMX-In ArtNet communication of the Quad Net Node....

my IP network is 192.168.1.0 netmask 255.255.255.0
Quad Net Node = 192.168.1.8
QLC+ PC = 192.168.1.13

The Quad Net Node can, according to the manufacturer, not be changed to e.g. 192.168.1.13 for DMX-In, it always sends to the broadcast address 192.168.1.255.

If at all the Quad Net Node sends the data at DMX-In from the DMX controller only very short via ArtNet.
Also the

symbol in QLC+ does not appear then any more...

scarffac3 · Thu Jan 20, 2022 8:54 am

Hello,
Did you try sending data from dmx-workshop, only for testing. So you can exclude the error in QLC+, i dont believe that there on is, but only for testing?
And maybe tried another software?

GGGss · Thu Jan 20, 2022 2:54 pm

FrankB wrote: ↑Wed Jan 19, 2022 11:35 pm It's as if a "collision" or a "bad IP packet" kills the DMX-In ArtNet communication of the Quad Net Node....

Artnet is UDP = shoot and forget. There is NO confirmation that the message got to the recipient, whatsoever, network-wise... Strange that your software is giving these errors? It should not give errors because it's UDP...

Something else is going Wrong for sure!!

I would really suggest you go to the 2.x.x.x or 10.x.x.x MASK 255.0.0.0 ip-address network range - just to be sure... I've had troubles in the past also & this did resolve the issue...
As per Artnet v4 https://art-net.org.uk/ you can use 192.168.x.y, but no one guarantees that your interface is committed to that version of the protocol.
I'd go back, way back, to the basics of Artnet and base my network to above (2. or 10.) network segments.

FrankB wrote: ↑Wed Jan 19, 2022 11:35 pm The Quad Net Node can, according to the manufacturer, not be changed to e.g. 192.168.1.13 for DMX-In, it always sends to the broadcast address 192.168.1.255.

... and you are connected through WiFi? Yes?

Wifi does not like broadcast storms, which you are producing now.
GO solid wired !! Computers + switches = cable for connecting. POINT FINAL

FrankB · Mon Jan 24, 2022 9:33 pm

scarffac3 wrote: ↑Thu Jan 20, 2022 8:54 am Hello,
Did you try sending data from dmx-workshop, only for testing. So you can exclude the error in QLC+, i dont believe that there on is, but only for testing?
And maybe tried another software?

Hi scarffac3,
yes, with DMX Workshop everything works.
But if I start QLC+ or PC-Dimmer no DMX-In ArtNet packets are displayed in Wireshark and ArtNetView anymore

FrankB · Mon Jan 24, 2022 9:47 pm

GGGss wrote: ↑Thu Jan 20, 2022 2:54 pm Something else is going Wrong for sure!!

I would really suggest you go to the 2.x.x.x or 10.x.x.x MASK 255.0.0.0 ip-address network range - just to be sure... I've had troubles in the past also & this did resolve the issue...
...
GO solid wired !! Computers + switches = cable for connecting. POINT FINAL

Hi GGGss,
i have now only one PC and the Quad Net Node connected via LAN through a switch.
PC = 10.0.0.10
Quad Net Node = 10.0.0.99

Unfortunately the error remains

GGGss · Tue Jan 25, 2022 9:18 am

FrankB wrote: ↑Wed Jan 19, 2022 11:35 pm it always sends to the broadcast address 192.168.1.255.

I am not sure that QLC+ is listening to broadcast packets at all for inputs...
Maybe a silly question, but you are listening to the right Artnet Universe yes? Double-check again please and verify through DMX workshop / Wireshark.

FrankB · Sat Jan 29, 2022 3:43 pm

Hi, yes QLC+ receives DMX-In via broadcast (with me in the default 192.168.1.255) and unicast (192.168.1.8).
But with me always only for a very short time. As written I recognize this in QLC+ by the appropriate symbol.
If I also activate DMX-Out, DMX-In aborts...

I have ordered today a node already mentioned here in the forum and am curious whether it works with the...

As to read here ArtNet packets are not always sent as broadcast. Controllers are even supposed to learn the subscribers and then send unicast.
https://art-net.org.uk/how-it-works/str ... scription/

Maybe I don't understand all this correctly