QLC+ 4.13.1 Not opening if Enttec Open DMX USB is plugged

[matafoc]

good afternoon,

A few weeks ago I bought an ENTTEC OPEN DMX USB.

I have installed the latest version of QLC+, 4.13.1, and if I have the converter connected to the PC, the software does not start. If I disconnect it, open the software without problems, then connect the USB cable, it does nothing.

From what I see in my fixture, in this case and in test mode, a Eurolite LED BAR-12, it seems that it does not receive commands from any controller, it keeps indicating the DMX address intermittently.

I've tried using the Freestyler as a controller, and just turning it on the fixture detects that there is a controller, a fixed led remains, which is the same as when I connect the classic DMX table.

It makes me think that the driver is correct (because with Freestyler, yes it seems to work) but that there is some problem with the QLC+.

I have tried other versions, both lower ones, like the Beta, and the result has been the same.

I've tried it on different computers with QLC+ 4.13.1, and the problem persists.

I don't know how much I can help you to give you clues to fix this problem, but I'm here for whatever it takes.

Let's see if together we can fix it, apparently I'm not the only one with this problem.

Thank you very much!

[alessxandro]

I have the same issue with my Enttec Open DMX Interface. There are two solutions to fix this problem at the moment from what I saw on this forum:
- Install any older version from the 4.12 release cycle (4.12.7 is good)
- When connecting the USB device, go to device managment, than click on "USB Controllers". You should see a "USB Converter" option. Right click -> Disable device and click ok on the flyout.
After disabling it, re-enable the device with the same procedure and QUICKLY open QLC from a desktop shortcut. 4.13.1 now should work but you need to to this every time you start the app, while when using 4.12.7 you don't. I really hope 4.14 will finally fix this issue.

[Yestalgia]

Can you guys give us some more details so we can try to replicate it?

Windows version?

USB Hub used?

Anything helps. Cheers

[kenact]

Have you downloaded and installed the Windows drivers from Enttec?

[u2b22]

Hello, I have the same problem as matafoc describes but with EUROLITE USB-DMX512 (https://www.steinigke.de/en/mpn51860118 ... aptor.html). I installed the drivers from the manufacturer. I tired to open the exe file from the command line to check for errors, but nothing is displayed and the program won't open. The USB DMX interface is plugged directly to the desktop and I can see it in my Windows device list as FT232R USB UART

Here are the details of my system:
QLC 4.14.1

OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Manufacturer: HP
System Model: HP Z2 SFF G4 Workstation
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 158 Stepping 13 GenuineIntel ~3000 Mhz
BIOS Version: HP Q50 Ver. 01.08.08, 10/12/2023

In case you need more information, let me know.

Thanks, Matous

[alessxandro]

https://github.com/mcallegari/qlcplus/issues/1666

[lifeowner66]

I had a similar issue. I'm using my homemade controllers with the FT232 chip. The first one worked normally, but the second one had the exact issue described in this thread. I burned the same serial number from the first controller into the second one using FTDI's tool. Now both of them work normally. Maybe the issue is related to the serial number, the hardware ID, or something similar.

br,

[alessxandro]

I burned the same serial number from the first controller into the second one using FTDI's tool. Now both of them work normally.

br,

could you please explain in a more detailed way what you did to make it work properly? Please, this issue is getting really frustrating for me

[lifeowner66]

I burned the same serial number from the first controller into the second one using FTDI's tool. Now both of them work normally.

br,

could you please explain in a more detailed way what you did to make it work properly? Please, this issue is getting really frustrating for me

I don't think this is a good approach for a consumer controller!

But in case it helps to debug the problem

I'm using a Waveshare FT232 USB-UART board, which contains a genuine FTDI FT232 chip. FTDI provides a utility called MProg, which I used to write a new serial number to the chip. After doing this, everything is now working normally.