Q Light Controller+

Official forums of the QLC+ project
https://forum.qlcplus.org/

JMS usb2dmx

https://forum.qlcplus.org/viewtopic.php?t=8919

Page 1 of 1

JMS usb2dmx

Posted: Mon Sep 14, 2015 9:21 pm
by pengumaniac
yesterday I got contact w new member Corlight (@M. as admin: feel free to read my PN)
we're talking about
jms-usb2dmx.jpg
he is underdeveloped
jms-qlc.jpg
jms-qlc.jpg (8.48 KiB) Viewed 11596 times
on 60 € priceclass quite ok, but:
a) couldn't contact (only tried telephone...)
b) Only Win-version of QLC+ is always fine (AFAIK...)
c) I suggest different charges:
- ones, who can be flashed
- others who can't

my question is right now: how does QLC+ interpret the empty (or simply NULL) S/N on FTDI's
what if toLatin1() returns "\0" as I read somewhere in qt docus...
btw: udev SUBSYSTEM does not need RegEx "*" as wildcard. Sure

review:
viewtopic.php?f=5&t=7340&hilit=jms+usb2dmx

Re: JMS usb2dmx

Posted: Thu Oct 15, 2015 2:44 pm
by pengumaniac
if we could continue in peace now again, Dear Massimo, I think you're on a good way...
Would you please show me the right place in code, where the SerialNo. should be get from FTDI-Chip into new and reworked v4.10?

Re: JMS usb2dmx

Posted: Thu Oct 15, 2015 3:10 pm
by mcallegari
Since you haven't specified...

Linux:
https://github.com/mcallegari/qlcplus/b ... e.cpp#L182

Windows:
https://github.com/mcallegari/qlcplus/b ... e.cpp#L182

OSX:
https://github.com/mcallegari/qlcplus/b ... e.cpp#L114

Re: JMS usb2dmx

Posted: Sat Oct 17, 2015 1:40 pm
by pengumaniac
* OSX - sure not me ...
* QLC+_4.10.0-TEST-20150925.exe on WinXP has correct DMX output

* Linux (Gentoo, Kernel v4.2.3 / gcc v4.9.3)
+ the good: qt4 x86 build fine, no more "garbage" in S/N displayed
- but no Output - again only with NULL instead of serial().toLatin1() in
https://github.com/mcallegari/qlcplus/b ... e.cpp#L233

dmesg

Code: Select all

Event USB plug in:

[   93.830024] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[   94.016073] usb 2-1: New USB device found, idVendor=0403, idProduct=6001
[   94.016079] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   94.016082] usb 2-1: Product: USB <-> Serial
[   94.016084] usb 2-1: Manufacturer: FTDI
[   94.103972] usbcore: registered new interface driver usbserial
[   94.103996] usbcore: registered new interface driver usbserial_generic
[   94.104015] usbserial: USB Serial support registered for generic
[   94.124884] usbcore: registered new interface driver ftdi_sio
[   94.124911] usbserial: USB Serial support registered for FTDI USB Serial Device
[   94.125007] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
[   94.125059] usb 2-1: Detected FT232BM
[   94.128128] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0


Event Power plug in "DMX512 Decoder" on DMX-line:

[  254.790059] usb usb2-port1: disabled by hub (EMI?), re-enabling...
[  254.790069] usb 2-1: USB disconnect, device number 2
[  254.790260] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[  254.790275] ftdi_sio 2-1:1.0: device disconnected
[  255.070024] usb 2-1: new full-speed USB device number 3 using uhci_hcd
[  255.256148] usb 2-1: New USB device found, idVendor=0403, idProduct=6001
[  255.256153] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  255.256156] usb 2-1: Product: USB <-> Serial
[  255.256159] usb 2-1: Manufacturer: FTDI
[  255.262202] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
[  255.262248] usb 2-1: Detected FT232BM
[  255.264215] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
lsusb

Code: Select all

Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
qlcplus debug,
a) by serial().toLatin1():

Code: Select all

Loaded I/O plugin "DMX USB" from "libdmxusb.so" 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB VID: "403" PID: "6001" 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB serial:  "" name: "USB <-> Serial" vendor: "FTDI" 
[setOutputsNumber] base line: 0 outputMap: QHash((0, 0)) 
... 
[Universe] setOutputPatch - ID: 0 , plugin: "DMX USB" , output: 0 
[QLCIOPlugin] setting lines: 0 4294967295 0 
virtual bool DMXUSBWidget::open(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 1 
virtual bool LibFTDIInterface::open() "USB <-> Serial" unable to fetch serial number 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
virtual bool LibFTDIInterface::clearRts() "USB <-> Serial" USB device unavailable 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
...
virtual void DMXUSB::configure() 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB VID: "403" PID: "6001" 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB serial:  "" name: "USB <-> Serial" vendor: "FTDI" 
[setOutputsNumber] base line: 0 outputMap: QHash((0, 0)) 
...
void IOPluginCache::slotConfigurationChanged() 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
[QLCIOPlugin] setting lines: 0 4294967295 0 
virtual bool DMXUSBWidget::open(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 1 
virtual bool LibFTDIInterface::open() "USB <-> Serial" unable to fetch serial number 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
virtual bool LibFTDIInterface::clearRts() "USB <-> Serial" USB device unavailable 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
[Universe] setOutputPatch - ID: 0 , plugin: "None" , output: 4294967295 
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
[Universe] setOutputPatch - ID: 0 , plugin: "DMX USB" , output: 0 
...
virtual bool DMXUSBWidget::close(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 0 
virtual bool DMXUSBWidget::close(quint32, bool) All inputs/outputs have been closed. Close FTDI too. 
virtual IOPluginCache::~IOPluginCache() 
...
b) by NULL:

Code: Select all

Loaded I/O plugin "DMX USB" from "libdmxusb.so" 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB VID: "403" PID: "6001" 
static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>) DMX USB serial:  "" name: "USB <-> Serial" vendor: "FTDI" 
[setOutputsNumber] base line: 0 outputMap: QHash((0, 0)) 
... 
[Universe] setOutputPatch - ID: 0 , plugin: "DMX USB" , output: 0 
[QLCIOPlugin] setting lines: 0 4294967295 0 
virtual bool DMXUSBWidget::open(quint32, bool) Line: 0 , Input mask: 0 , Output Mask: 1 
virtual bool DMXUSBWidget::open(quint32, bool) Interface correctly opened and configured 
...
[QLCIOPlugin] setting lines: 3 4294967295 0 
...
Again good old Patch, to get at least one restive FTDI working...

Re: JMS usb2dmx

Posted: Sat Oct 17, 2015 10:51 pm
by mcallegari
Here's your fix
https://github.com/mcallegari/qlcplus/c ... 6b68ce7ea2

Re: JMS usb2dmx

Posted: Mon Oct 19, 2015 3:16 pm
by pengumaniac
should that really mean, wait --- home:mcallegari79 / qlcplus-qt5 on oSL13.2 by "One Click Install"

* install works fine
* output DMX, too - Out of the Box

Congratulations, you got the beast! 8-)

Re: JMS usb2dmx

Posted: Thu Jul 22, 2021 9:44 am
by Smove
Dear all,

I have a problem with the JMS USB2DMX Pro converter on Win10. Converter works fine on OSX but on Win10 it seems that no DMX data is send to the controller.
Latest driver for Windows is installed. No errors in Windows Devie Manager. QLC+ Version 4.12.4. Device is recognised and selected as output in the In/Out-Manager.

In other posts I read that the missing serialnumber of the JMS USB2DMX Pro is causing the problem. I tried to reprogramm (enter a serialnumber) the converter with FT_Prog as mentioned in another post but the converter doesn't keep the changes after I klick 'programm'. When I rescan the devices the serial is empty again.

As I can read here there is a patch to get at least one USB2DMX Pro converter working. But unfortunately I don't know how to patch QLC+ with the sourcecode posted here:

https://github.com/mcallegari/qlcplus/c ... 6b68ce7ea2

Any help would be highly appreciated. :)

Thanks in advance,
Smove
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited