Q Light Controller+

Has anybody got any good pointers as to why my PKnight ArtNet controller doesn't seem to show up in the InputOutput view.

https://www.pknightpro.com/collections/ ... 2665978011

It shows up on other applications like my Companion so I know it's there and functioning.

Here's Lachie's tried and tested artnet tutorial for QLC+ users:

There are 3 critical things that need to be known for your artnet device to work with QLC+. These are:

• The IP Address of the controller. (e.g. 2.0.0.100) This should be similar but not the same as your computer's IP address. (e.g 2.0.0.1)
• The subnet mask for the controller MUST be the same as the computers (e.g. 255.0.0.0)
• The Universe number for the controller (e.g 0 which means universe 1 in QLC+)

In my personal setup, I don't rely on DHCP (the automatic address given to the controller and your computer) Instead, I manually assign them to the values in the (e.g.) parts in the list above. See below to manually assign an IP address in Windows 10:
https://pureinfotech.com/set-static-ip- ... _windows10

If all is well, you may select the output checkbox for the Artnet Output corresponding to the IP address of the computer.

PhilVale wrote: ↑Wed Jan 17, 2024 7:08 pm my PKnight ArtNet controller doesn't seem to show up in the InputOutput view.

Note: the device will not "Show Up" in the input/output view directory, you will need to select the artnet row and click "configure plugin", where a list of devices will be shown if all is well.

For more information, please read the documentation:
https://docs.qlcplus.org/v4/plugins/art-net

and adding to that:
* do not use Wifi
* try to use the unicast method before using the broadcast method. In QLC+ configure plugin, you have to fill in the IP-Address of the Artnet interface
* a simple ping gives you confirmation that the device is reachable after all your network settings have been done.

I'm on QLC+ v5, not V4 - but also seem to be having issues getting my DMX controller to appear in QLC+ (despite it being on the network).

The device in question is a eDMX MAX 1 DIN - I can configure it is on the network, I am able to access it over the network using the eDMX MAX configuration tool:



In QLC+ V5, I see a list of ARTNet addresses - however, that device isn't listed.



If I drag one of them over, in the Configure Plugin screen, I *don't* see any way to change the IP address...



Does anybody know how to point QLC+ at that controller, or how to make it appear to the auto-scan?

Is there any documentation on how the ArtNet autoscan functionality works?

Try to select the ArtNet output in the right side of the Input/Output tab. The IP 127.255.255.255 I think is not correct.

* 127.255.255.255 is the localhost (mask 255.0.0.0) this is configured as an input.
* if you open the configuration of the Artnet 10.5.1.158 NIC, there you should find your device. (If the broadcast discovery procedure succeeded. After configuring I would close and reopen QLC+).
* your device should be present at 10.51.1.62 ( simple ping should answer that question).

And for network 101's sake: private Class 1 IP addresses 2.x.x. and 10.x.x.x should have a 255.0.0.0 mask.

I bought that same node and had the same problem. Then I found this elsewhere on the forum:
viewtopic.php?t=16313&sid=afadd1b1ca11d ... 2c2a77a0e8

There, someone said to set the subnet mask to 255.255.0.0, and the IP address to 169.254.17.159 on the node.

I did this and it worked. Also make sure you set the transmission mode to Artnet->DMX. It came out of the box the other way around.

When it's working, the blue LED will flash. Hope this helps!

Notice: do not use the 169.254.x.x range of IP addresses. These are (the ugly) addresses M$ windows gives you when there is no network (DHCP) connection, messing up with people's minds.
https://www.whatismyip.com/169-254-ip-a ... %20working.

GGGss wrote: ↑Mon Jun 24, 2024 11:08 am Notice: do not use the 169.254.x.x range of IP addresses. These are (the ugly) addresses M$ windows gives you when there is no network (DHCP) connection, messing up with people's minds.
https://www.whatismyip.com/169-254-ip-a ... %20working.

From what I read in that article, it seems you can use a 169.254.... as long as it's the only node and you're not connecting to the internet. And using that address does work with the aforementioned node when others didn't.

However, I am concerned after reading this. What address(s) do you suggest?

Update: Under the input/output tab it shows most of the artnet IP addresses as 169.254... And this is using my DMXking artnet dongle. It has always worked fine using one of those addresses. I'm getting confused.

As per Artnet standard (including the previous versions), Artnet devices defaults in the 2.x.x.x MASK 255.0.0.0 network region.
See p.12 here https://art-net.org.uk/downloads/art-net.pdf

In the wild you also will find devices running in the 10.x.x.x MASK 255.0.0.0 network region.

I can't make much sense of this. I've been using the 169.254... artnet addresses that show up in the input/output section for years (both wirelessly and wired), and never had a problem. According to the sources, you're supposed to use addresses in the 255... range, but I've never seen any addresses in that range show up in the input/output section.

ShagLight wrote: ↑Thu Jun 27, 2024 3:05 pm I can't make much sense of this. I've been using the 169.254... artnet addresses that show up in the input/output section for years (both wirelessly and wired), and never had a problem. According to the sources, you're supposed to use addresses in the 255... range, but I've never seen any addresses in that range show up in the input/output section.

Newer devices will work in the 169.254.x.x private IP range, which is why you were successful. As long as the host and the Artnet interface find themselves, you are clear. The easiest test is a ping instruction to the interface.
I merely stipulated the standards and norms. Older Artnet devices may struggle with an IP address outside the 2.x.x.x (or 10.x.x.x) networks.

GGGss wrote: ↑Fri Jun 28, 2024 6:50 am

ShagLight wrote: ↑Thu Jun 27, 2024 3:05 pm I can't make much sense of this. I've been using the 169.254... artnet addresses that show up in the input/output section for years (both wirelessly and wired), and never had a problem. According to the sources, you're supposed to use addresses in the 255... range, but I've never seen any addresses in that range show up in the input/output section.

Newer devices will work in the 169.254.x.x private IP range, which is why you were successful. As long as the host and the Artnet interface find themselves, you are clear. The easiest test is a ping instruction to the interface.
I merely stipulated the standards and norms. Older Artnet devices may struggle with an IP address outside the 2.x.x.x (or 10.x.x.x) networks.

That helps and I fell relieved. I was starting to think I've been doing something wrong all this time.

The thing is I only need to connect from the laptop to the Artnet node, whether through a Cat 5/6 or WIFI. I don't need a big complex network for what I'm doing. I just need to connect to the Artnet node and nothing more. And as I understand it, 169.254... will work fine for that.