Q Light Controller+

Good morning all ,

I allow myself to come to you because I have a problem with my Artnet configuration that I cannot resolve.
No matter how much I try and try, nothing helps : my lights don't turn on .

So if a charitable soul could help me by confirming me or not if my configuration is correct, it would be super nice .

In the preamble, I specify the following : my Artnet controler and my light sets work well. Indeed, in other software that I tested (but it is Qlc + that I want to use in the end ), the whole responds well. So I think I can eliminate a hardware failure from the start.

My goal is to run 2 scanners on the universe 2 of my controller. Simply ? Well...not really apparently .

Here is my IP configuration of my local network which welcomes my controler :



Here my Qlc+ Artnet configuration :



Here my Qlc+ Artnet nodes configuration (where we can find my controler) :



And finally, my global Qlc+ Artnet configuration



Here.
All is said.
Thank you very much in advance to those who will help me in this thorny problem

Kind regards,
François

Francois,

First off ... try to keep things easy in the beginning. Using universe 2 is already an 'advanced' feature.
Under testing conditions try to make an as dry as possible environment.

You are sending Artnet to .255 in your network ... this is wrong since your Artnet adapter resides on the .3 address.

And then you have to know that the Artnet universes are not zero-based. They start at 1 and not zero.
Since you are focusing on universe 2, it might be that you have to send to universe 1 for your adapter to do the right things. Do you see how quickly things can get confusing?

I advise you to start from scratch and KISS it - Keep It Stupid Simple (or Simple stupid)
Change the address QLC+ is sending to, to .3 and report (configure unicast instead of broadcast in the settings)

Hi GGGss,

Thank you for your response and your advice.
It would seem finally that it is my controller which sends a bad signal Artnet :/.
I'm going to get closer to the manufacturer.

Thank you in all for helping me, it's really very nice .

Thanks for reporting back.

Rereading and re-studying your setup, I see you want to connect your scanners to universe 2 of your Artnet controller. (!!)

Then you will have to instruct QLC+ to send Artnet to universe 2 at 192.168.60.3!
(in above pictures you are sending Artnet universe 1 to 192.168.60.255 <- this will not work because IP-address is wrong and base Arnet-universe is wrong also.)

Change those 2 settings and report back. (and 3th setting -> set in Artnet option to UNICAST to 192.168.60.3.

So:
- ArtNet sends traffic via UDP port 6454. UDP is stateless .. eg .. fire and forget the packet VS tcp which establishes and tracks the connection.
- Most ArtNET senders ( QLC for example ) defaults to sending ArtNET to 'broadcast' (That goes back to version 1 (https://art-net.org.uk/) .. eg on his /24 network the target addy would be 192.168.60.255 .. so that's correct.
- Most ( but not all ) ArtNet endpoints default to listening for 'broadcast' and 'unicast' , tho they can be set for unicast only, however regardless: You can certainly use it in 'unicast' .. to the 192.168.60.3 address .. and that will lower traffic overall on your network (broadcast packets are processed by everything on the network even if not used)
- ArtNet universe numbers do NOT have to correlate to QLC Universe - 1. So if you have say a USB DMX adaptor at universe 1 on QLC, you can setup Universe 2 to send ArtNet Universe 0 ( vs 1 ) to make things easier if you don't have the ability to reconfigure the endpoint.

What you will need to reconcile:

- What QLC Universe are you sending ( they start at 1 )
- What ArtNet Universe are you sending ( they start at 0 )
- What Artnet Universe are you *listening for* on the endpoint.

I've run ~54 Universes over Artnet using Unicast over 100M and 802.11B .. works quite well if you optimize things.