Problems with RS485 with USB2-H-5001-M

[urieldiazg]

Hello, good day to everyone.

It is the first time that I make a query, so far I have successfully worked with Q Light Controller, on different devices, especially Linux, Debian, Ubuntu, RasberryPi and I have used Arnet and Enttec mainly as DMX controllers. However, now I have the challenge of working with a USB RS485 device called USB2-H-5001-M, below I will attach the datasheet page of this device.
I couldn't get Q light to recognize the device. I have successfully installed, for the moment in Ubuntu, the libftdi D2XX FTDI driver and have successfully run tests and examples by the ubuntu terminal, but Q Light does not recognize the device.

I would like to know if you can advise me, it does not matter if I make the device work with a PC or RaspberryPi, or with Windows or Linux, in fact I prefer to use Linux, the goal is to be able to use this USB2-H-5001-M device with Q light Controller ...

Thank you...

PD: This is the device that I want Q Light to recognize, it doesn't matter if it's on Debian, Ubuntu or Raspbian.

https://www.mouser.com/datasheet/2/119/ ... Y-3148.pdf

[sbenejam]

Hi,
Some things you can try on Ubuntu.
- What is the output of lusb command?
- With lsmod | grep ftdi you can check if ftdi modules are loaded
- Take a look at this search in forum posts: search.php?keywords=modemmanager

[urieldiazg]

First, thanks for answering and helping me.

Add my user to the group "dialout" with the following command:

sudo adduser your_user_name dialout

in my case:
sudo adduser uriel dialout

I wrote the commands in the terminal
lsmod | grep ftdi
dmesg | grep FTDI

The result was, I also add screenshots:

uriel @ uriel-ubuntu: ~ $ lsmod | grep ftdi
ftdi_sio 61440 0
usbserial 53248 1 ftdi_sio

uriel @ uriel-ubuntu: ~ $ dmesg | grep FTDI
[524.287173] usb 3-10: Manufacturer: FTDI
[524.309997] usbserial: USB Serial support registered for FTDI USB Serial Device
[524.310091] ftdi_sio 3-10: 1.0: FTDI USB Serial Device converter detected
[524.310426] usb 3-10: FTDI USB Serial Device converter now attached to ttyUSB0

Lastly I wrote echo "foo"> / dev / ttyUSB0 to see if it did something, apparently the device receives the data, because the TXD and RXD LEDs light for a brief moment. But QLC does not recognize the device.

I am doing something wrong... ...

[sbenejam]

Can you post the output of lusb command with your device connected?.
sbenejam@migjorn:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 012: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The device ID is used by QLC+ to detect the devices.
Can you see your device in Input/Output tab in QLC+?. Try to change through universe clicking on the different universes and check if you can see it.

[sbenejam]

Another point to revise, do you have the package modemmanager installed?. Try to stop the service modemmanager or un install the package.

[urieldiazg]

Thanks for the help, yes of course, I send the result of the lusb:

Bus 002 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 002 Device 003: ID 0000:0538
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
Bus 003 Device 004: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Bus 003 Device 002: ID 3938:1032 MOSART Semi. 2.4G RF Keyboard & Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Already disable the ModemManager package with the commands:

sudo systemctl stop ModemManager
sudo systemctl disable ModemManager

But unfortunately QLC still does not recognize the device, in any universe.

[sbenejam]

I have an Enttect DMX USB Pro and a couple RS-485 devices like this. All of them appears with the ID: 0403:6001. I think that support for your device needs to be added to the QLC+ code.
What happens if you click on the "refresh" button?.

[mcallegari]

I confirm that 0403:6014 is not recognized in the code.
Just as a test, you can change the code here:
https://github.com/mcallegari/qlcplus/b ... face.h#L91

[urieldiazg]

Hello, I still appreciate your appreciable help.

I modified the dmxinterface.h file located at /home/uriel/qlcplus/plugins/dmxusb/src, I replaced 0x6001 with 0x6014.

Unfoqrtunately it still does not recognize the device. I have pressed the refresh button and even change the universe, but it does not recognize the device.

Another thing that you suggest me to do?

[sbenejam]

Hi,
After modifying the code, the program must be build again following this instructions.
https://github.com/mcallegari/qlcplus/w ... -build-Qt5
You have done it?

[urieldiazg]

Excellent, yes I have ever compiled and built the program.

But I have not done it after the modification in the code that was suggested to me, I will do it today ... I will notify you of the results, thanks ...