FTDI DMX Plugin Available

[Simon Newton]

I've merged in the FTDI patch from rbarreiros and pushed them to the
main repo. If you have an Open DMX or similar device please test it
out. Even if you don't have a device please update and attempt a build
to make sure there are no warnings I've missed.

The new plugin is marked as Conflicting with the USB Pro and existing
Open DMX (kernel module) plugins. To enable it you need to do the
following:

After the build, start & stop olad to create the new config file.
Edit ola-usbserial.conf & ola-opendmx.conf and set enabled = false.
Edit ola-ftdidmx.conf and set enabled = true


Simon

[RenZO]

Some precisions to get it work:

You need to install libftdi-dev on your system.
On ubuntu:
sudo apt-get install libftdi-dev

Then you will have, in the configure output:
checking for libusb... yes
checking for libftdi... yes

The ftdi dmx plugin will be built, enable it with conf files in your home (~/.ola/).

Now you could need to add a udev rule (to have permissions on the device):
sudo gedit /etc/udev/rules.d/30-ftdidmx.rules

ACTION=="add", BUS=="usb", SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001",
GROUP:="dialout", MODE:="0660"

As said here:
http://code.google.com/p/open-lighting/issues/detail?id=164#c45

Plug the usb device first, then start olad -l3, enjoy :)

RenZO

[Simon Newton]

On Thu, Aug 16, 2012 at 4:35 PM, RenZO <renzo...@gmail.com> wrote:
> Some precisions to get it work:
>
> You need to install libftdi-dev on your system.
> On ubuntu:
> sudo apt-get install libftdi-dev
>
> Then you will have, in the configure output:
> checking for libusb... yes
> checking for libftdi... yes
>
> The ftdi dmx plugin will be built, enable it with conf files in your home
> (~/.ola/).
>
> Now you could need to add a udev rule (to have permissions on the device):
> sudo gedit /etc/udev/rules.d/30-ftdidmx.rules
>
> ACTION=="add", BUS=="usb", SYSFS{idVendor}=="0403",
> SYSFS{idProduct}=="6001",
> GROUP:="dialout", MODE:="0660"
>
> As said here:
> http://code.google.com/p/open-lighting/issues/detail?id=164#c45
>
> Plug the usb device first, then start olad -l3, enjoy :)

Thanks for pointing out the bits I missed. I've updated the wiki.

Simon

>
> RenZO
>
> Le jeudi 16 août 2012 17:09:07 UTC+2, Simon Newton a écrit :
>>
>> I've merged in the FTDI patch from rbarreiros and pushed them to the
>> main repo. If you have an Open DMX or similar device please test it
>> out. Even if you don't have a device please update and attempt a build
>> to make sure there are no warnings I've missed.
>>
>> The new plugin is marked as Conflicting with the USB Pro and existing
>> Open DMX (kernel module) plugins. To enable it you need to do the
>> following:
>>
>> After the build, start & stop olad to create the new config file.
>> Edit ola-usbserial.conf & ola-opendmx.conf and set enabled = false.
>> Edit ola-ftdidmx.conf and set enabled = true
>>
>>
>> Simon
>

> --
> open-l...@googlegroups.com /
> http://groups.google.com/group/open-lighting
> To unsubscribe email open-lightin...@googlegroups.com

[RenZO]

It works with my adapter USB-RS485-WE-1800-BT:
http://www.ftdichip.com/Products/Cables/USBRS485.htm

PluginManager.cpp:105: Trying to start USB
PluginManager.cpp:109: Started USB
PluginManager.cpp:105: Trying to start FTDI USB DMX
FtdiWidget-libftdi.cpp:291: Found FTDI device. Vendor: 'FTDI', Name:
'USB-RS485 Cable', Serial: 'FTUN869F'
DeviceManager.cpp:111: Installed device: USB-RS485 Cable with serial
number : FTUN869F :13-FTUN869F
PortManager.cpp:151: Patched 13-FTUN869F-O-0 to universe 1
PluginManager.cpp:109: Started FTDI USB DMX
FtdiDmxThread.cpp:143: Granularity for ftdi thread is GOOD


If I reduce the speed to 10 fps in the conf file, I see the red led
blinking, and fades are jerky.
At 40 fps it works almost smoothly but I can see some breaks randomly.

RenZO

On 17 août, 16:53, Simon Newton <nomi...@gmail.com> wrote:

[RenZO]

When I start olad with ftdi device, it sends dmx values even if not
patched.
Not all the channels are affected, and values can changed on every
start.
I've monitored the values with another machine receiving the signal:
http://imaginux.com/lighting/debug/download/ftdi_monitor1.png
http://imaginux.com/lighting/debug/download/ftdi_monitor2.png

The only way to have a blackout is to patch the device and send values
on the universe.
So I guess it's not normal...

RenZO

[Simon Newton]

On Wed, Aug 22, 2012 at 8:40 AM, RenZO <laurent...@gmail.com> wrote:
> When I start olad with ftdi device, it sends dmx values even if not
> patched.
> Not all the channels are affected, and values can changed on every
> start.
> I've monitored the values with another machine receiving the signal:
> http://imaginux.com/lighting/debug/download/ftdi_monitor1.png
> http://imaginux.com/lighting/debug/download/ftdi_monitor2.png
>
> The only way to have a blackout is to patch the device and send values
> on the universe.
> So I guess it's not normal...

I've submitted a change, please pull & try again.

Simon

[RenZO]

On Aug 22, 5:48 pm, Simon Newton <nomi...@gmail.com> wrote:

> On Wed, Aug 22, 2012 at 8:40 AM, RenZO <laurent.nova...@gmail.com> wrote:
> > When I start olad with ftdi device, it sends dmx values even if not
> > patched.
> > Not all the channels are affected, and values can changed on every
> > start.
> > I've monitored the values with another machine receiving the signal:
> >http://imaginux.com/lighting/debug/download/ftdi_monitor1.png
> >http://imaginux.com/lighting/debug/download/ftdi_monitor2.png
>
> > The only way to have a blackout is to patch the device and send values
> > on the universe.
> > So I guess it's not normal...
>
> I've submitted a change, please pull & try again.
>

Yes, it works now. No data is sent until I send values. Thanks!

RenZO

[g.schlmm]

nice!
hope i can test it tommorow. i dont know if there is still a device
(enttec open dmx) findable :)

[Massimo Callegari]

Hi Simon, just tried on Ubuntu 12.04 (GCC 4.6.3, kernel 3.2.0)

I cloned the GIT repo and compiled but it failed on Olad.cpp.

I had to add 

#include <signal.h>

and then it compiled fine.

I followed the instructions to resolve the plugin conflicts and the FTDI module works like a charm. You and rbarreiros did a great job !

It would be great though if:

- the udev rules can be installed automatically (like QLC does), so a user doesn't have to dig the OLA website to find out why the dongle is not recognized

- the conflicts can be autodetected. If /dev/dmx0 is not present, it means no "old" Open DMX driver is loaded. As per "usbserial", I think the USB product/vendor can help you as well.

Just suggestions to make the whole thing more user friendly :)

Thank you very much !

[Simon Newton]

On Mon, Aug 27, 2012 at 10:43 AM, Massimo Callegari
<massimocal...@gmail.com> wrote:
> Hi Simon, just tried on Ubuntu 12.04 (GCC 4.6.3, kernel 3.2.0)
> I cloned the GIT repo and compiled but it failed on Olad.cpp.
> I had to add
> #include <signal.h>
> and then it compiled fine.

Which file? Can you publish your change somewhere so I can include it.

>
> I followed the instructions to resolve the plugin conflicts and the FTDI
> module works like a charm. You and rbarreiros did a great job !

It was a joint effort really. Heikki did the original code, Rui did
the plugin and I just integrated it across.

> It would be great though if:
> - the udev rules can be installed automatically (like QLC does), so a user
> doesn't have to dig the OLA website to find out why the dongle is not
> recognized
> - the conflicts can be autodetected. If /dev/dmx0 is not present, it means
> no "old" Open DMX driver is loaded. As per "usbserial", I think the USB
> product/vendor can help you as well.

The problem is that the open dmx plugins conflict with pretty much
every other USB device. Since there are more 'intelligent' USB devices
that the Open one I choose to support the former out the box.

Simon

>
> Just suggestions to make the whole thing more user friendly :)
>
> Thank you very much !
>
>
> Il giorno giovedì 16 agosto 2012 17:09:07 UTC+2, Simon Newton ha scritto:
>>
>> I've merged in the FTDI patch from rbarreiros and pushed them to the
>> main repo. If you have an Open DMX or similar device please test it
>> out. Even if you don't have a device please update and attempt a build
>> to make sure there are no warnings I've missed.
>>
>> The new plugin is marked as Conflicting with the USB Pro and existing
>> Open DMX (kernel module) plugins. To enable it you need to do the
>> following:
>>
>> After the build, start & stop olad to create the new config file.
>> Edit ola-usbserial.conf & ola-opendmx.conf and set enabled = false.
>> Edit ola-ftdidmx.conf and set enabled = true
>>
>>
>> Simon
>

[Massimo Callegari]

Il giorno martedì 28 agosto 2012 06:42:24 UTC+2, Simon Newton ha scritto:

On Mon, Aug 27, 2012 at 10:43 AM, Massimo Callegari
<massimocal...@gmail.com> wrote:
> Hi Simon, just tried on Ubuntu 12.04 (GCC 4.6.3, kernel 3.2.0)
> I cloned the GIT repo and compiled but it failed on Olad.cpp.
> I had to add
> #include <signal.h>
> and then it compiled fine.

Which file? Can you publish your change somewhere so I can include it.

Olad.cpp. It's written.

[Simon Newton]

On Wed, Aug 29, 2012 at 2:19 PM, Lorenzo Fattori <zit...@hotmail.com> wrote:
> hi,
> i've installed OLA on my raspberry
>
> i'm trying to get it working with my open dmx.. when i connect the open dmx
> and open olad it freezes completely! no response i have to re-power the r-pi
>
> i'm trying to do what you said...i downloaded libftdi-dev
> but now i cant find the configure output, and if i try to edit sudo gedit
> /etc/udev/rules.d/30-ftdidmx.rules
>
> 1) gedit unknow command > i use nano
> 2) it opens a new blank file
>
> could someone please explain exactly what i have to do... unfortunatly is
> the 1st time i work with ola

Download the raspbian git image from here: http://nomis52.net/data/raspi/
Install to SD card & reboot
login as ola
cd ola
sudo make install
sudo ldconfig
unplug all the usb devices
run olad, wait for it to start, then stop it (either control-C or
through the web UI)
now all the config files have been created in ~/.ola/
use renzo's script to disable everything: ola_conf_plugins.sh
disable all plugins
enable just the ftdi plugin: ola_conf_plugins.sh enable ftdidmx
edit /etc/udev/rules.d/30-ftdidmx.rules and uncomment the last line
reboot
attach Open DMX USB device
login & start olad
profit

Or you could throw away the Open DMX USB interface and get a proper
DMX device :).

Simon



>
> Regards
> Lorenzo

[dmx...@gmail.com]

>>Or you could throw away the Open DMX USB interface

>>and get a proper DMX device :)

Amen! 


Sent from Samsung Mobile

[Lorenzo Fattori]

ok... i downloaded the not-git version... now i putted the git in download and tomorrow i will try!

i know, open dmx is cheap and crappy device... for work i use wing with 2 dmx out... but i want to make some stuff with led pixels and the controllers need 512ch for about 5mt... so i need a lot of universes... and open dmx are cheap ;)

i will keep you informed if it works :D

Thank you

Lorenzo

[Jason Kyle]

But probably not cheaper than the ultraDMX Micro, which although cheap is definitely not crappy since it includes a microcontroller for precise DMX timing.

 

Jason Kyle

DMXking.com / JPK Systems Limited

[Jason Kyle]

I actually have a breadboard prototype of an FT232AM based USB DMX interface that was designed well before enttec did the “open” however I decided not to unleash such pain and suffering on the world LOL.

From: open-l...@googlegroups.com [mailto:open-l...@googlegroups.com] On Behalf Of dmx...@gmail.com
Sent: Thursday, 30 August 2012 09:39
To: open-l...@googlegroups.com
Subject: Re: [open-lighting] Re: FTDI DMX Plugin Available

 

>>Or you could throw away the Open DMX USB interface

[dmx...@gmail.com]

Oh the pain, the pain! it has caused a lot of headaches over the years!

Thank you JPK, i propose we eradicate this pest.... :-) 

Sent from Samsung Mobile

[RenZO]

On Wednesday, August 29, 2012 11:28:05 PM UTC+2, Simon Newton wrote:

Just a mistake, to disable everything, the proper syntax is:
ola_conf_plugins.sh disable all

RenZO

[Lorenzo Fattori]

i have some problems....

ola@raspberrypi ~/ola $ ola_conf_plugins.sh disable all

ls: cannot access ola-usbdmx.conf: No such file or directory

deactivate ola-artnet.conf

deactivate ola-dummy.conf

deactivate ola-e131.conf

deactivate ola-espnet.conf

deactivate ola-ftdidmx.conf

deactivate ola-opendmx.conf

deactivate ola-pathport.conf

deactivate ola-sandnet.conf

deactivate ola-shownet.conf

deactivate ola-stageprofi.conf

deactivate ola-usbserial.conf

ola@raspberrypi ~/ola $ ola_conf_plugins.sh enable ftdidmx 

ls: cannot access ola-usbdmx.conf: No such file or directory

activate ola-ftdidmx.conf

and the main problem:

ola@raspberrypi ~/ola $ edit  /etc/udev/rules.d/30-ftdidmx.rules

Warning: unknown mime-type for "/etc/udev/rules.d/30-ftdidmx.rules" -- using "application/octet-stream"

Error: no write permission for file "/etc/udev/rules.d/30-ftdidmx.rules"

also tested with sudo:

ola@raspberrypi ~/ola $ sudo edit  /etc/udev/rules.d/30-ftdidmx.rules

Warning: unknown mime-type for "/etc/udev/rules.d/30-ftdidmx.rules" -- using "application/octet-stream"

Error: no "edit" mailcap rules found for type "application/octet-stream"

what i'm wrong?

regards

On Wednesday, August 29, 2012 11:28:05 PM UTC+2, Simon Newton wrote:

[Lorenzo Fattori]

i made a check, the file doesn't exist:

ola@raspberrypi /etc/udev/rules.d $ ls

10-local.rules  40-scratch.rules  91-local.rules  99-input.rules

[Simon Newton]

On Thu, Aug 30, 2012 at 2:10 AM, Lorenzo Fattori <zit...@hotmail.com> wrote:
> i have some problems....
>
> ola@raspberrypi ~/ola $ ola_conf_plugins.sh disable all
> ls: cannot access ola-usbdmx.conf: No such file or directory
> deactivate ola-artnet.conf
> deactivate ola-dummy.conf
> deactivate ola-e131.conf
> deactivate ola-espnet.conf
> deactivate ola-ftdidmx.conf
> deactivate ola-opendmx.conf
> deactivate ola-pathport.conf
> deactivate ola-sandnet.conf
> deactivate ola-shownet.conf
> deactivate ola-stageprofi.conf
> deactivate ola-usbserial.conf
>
>
>
> ola@raspberrypi ~/ola $ ola_conf_plugins.sh enable ftdidmx
> ls: cannot access ola-usbdmx.conf: No such file or directory
> activate ola-ftdidmx.conf

You can ignore those warnings. Renzo I think you should remove them
since they'll just confuse people.

>
>
> and the main problem:
> ola@raspberrypi ~/ola $ edit /etc/udev/rules.d/30-ftdidmx.rules
> Warning: unknown mime-type for "/etc/udev/rules.d/30-ftdidmx.rules" -- using
> "application/octet-stream"
> Error: no write permission for file "/etc/udev/rules.d/30-ftdidmx.rules"
>
> also tested with sudo:
> ola@raspberrypi ~/ola $ sudo edit /etc/udev/rules.d/30-ftdidmx.rules
> Warning: unknown mime-type for "/etc/udev/rules.d/30-ftdidmx.rules" -- using
> "application/octet-stream"
> Error: no "edit" mailcap rules found for type "application/octet-stream"

Sorry, you want /etc/udev/rules.d/10-local.rules instead.

Simon

[Jannis Achstetter]

Am 30.08.2012 11:10, schrieb Lorenzo Fattori:
> [...]

> and the main problem:
> ola@raspberrypi ~/ola $ edit /etc/udev/rules.d/30-ftdidmx.rules
> Warning: unknown mime-type for "/etc/udev/rules.d/30-ftdidmx.rules" --
> using "application/octet-stream"
> Error: no write permission for file "/etc/udev/rules.d/30-ftdidmx.rules"

> [...]

You forgot to use "sudo" here, that's why you get the "no write
permissions"-error.
And: are you sure the command "edit" does what you think it does? I
don't have an "edit" command here on gentoo but I guess you might want
to use "nano" or "vi" instead of "edit".

Best regards

[Lorenzo Fattori]

yes edit doesn't work... but nano works perfect ;)
and now it works!!! i can see the device, i re-activated artnet so i can put my artnet stream to my usb dmx... tomorrow i will try with an artnet device connected :D

another question... is possible to put more than one usb dmx in ola? my idea is to stream 2 or 4 artnet universes to 2 or 4 open dmx...

thank you

regards

[dmx...@gmail.com]

Hi Lorenzo,

Open dmx usb has problems..... I think you should forget about using them for anything other than strobe lights. 

Open dmx - 1 device only for testing/mucking around. 

The dmx king devices, you can have many devices... 

Cheers,

Hippy 

Sent from Samsung Mobile

Lorenzo Fattori wrote:

[Lorenzo Fattori]

i have my open dmx from years and years... never had problems... used with freestyler and now with magicQ...

i'm sure that kings devices are better, but i want to test that (i have 3 open dmx here)... i'm waiting for time to find on web how to receive and send dmx with pic for build my own interface :D

Regards

Lorenzo

[Lorenzo Fattori]

that works!!! perfect!

thank you so much for your help!

unfortunatly only one universe output with open dmx.. but now i have to check what usb-dmx buy :D

[Simon Newton]

On Wed, Sep 19, 2012 at 3:35 PM, Ian Shaw <ian.t...@gmail.com> wrote:
> Hi,
> first of all thanks for adding the ftdi - I managed to compile up and use
> the driver previously but when moving to Raspberry Pi became a little stuck.
> I'm still relatively new to linux and have been enthused by ola and RPi,
> trying to get ola running with Python to use for our house lighting.
>
> as I did have ola 8.22 and the manual driver working on ubuntu (dev/dmx0) I
> know my hardware is sound and patched the universe etc that time round.
> Now running with raspbian-git-05092012.zip I find myself challenged.
>
> I used the following running on the Pi to compile up:
> autoreconf
> ./configure --enable-python-libs
> make

>
> sudo make install
> sudo ldconfig
>

> (all worked, no issues)
>
> ola_conf_plugins disable all
> ola_conf_plugins enable ftdi
>
> updated the rules file to remove the #
>
> reboot
>
> olad -l 3
>
> received the following:
> Olad.cpp:286: OLA Daemon version 0.8.22
> OlaDaemon.cpp:105: Using configs in /home/ola/.ola
> OlaServer.cpp:215: Server UID is 7a70:1f02a8c0
> HTTPServer.cpp:437: HTTP Server started on port 9090
> PluginManager.cpp:73: Skipping ArtNet because it was disabled
> PluginManager.cpp:73: Skipping Dummy because it was disabled
> PluginManager.cpp:73: Skipping E1.31 (sACN) because it was disabled
> PluginManager.cpp:73: Skipping ESP Net because it was disabled
> PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
> PluginManager.cpp:73: Skipping SandNet because it was disabled
> PluginManager.cpp:73: Skipping ShowNet because it was disabled
> PluginManager.cpp:73: Skipping StageProfi because it was disabled
> PluginManager.cpp:73: Skipping Serial USB because it was disabled
> PluginManager.cpp:73: Skipping USB because it was disabled
> PluginManager.cpp:73: Skipping Pathport because it was disabled

> PluginManager.cpp:105: Trying to start FTDI USB DMX

> FtdiWidget-libftdi.cpp:291: Found FTDI device. Vendor: 'www.soh.cz', Name:
> 'Interface USB-DMX512', Serial: 'A1JROBJC'

> PluginManager.cpp:109: Started FTDI USB DMX
>

I suspect you're the first person using a soh device. I certainly
haven't seen one before.

To help us out can you plug in the device while the Pi is running and
then send the last ~15 lines of the output from dmesg?

Also try enabling one of the other devices like ArtNet of E1.31 and
confirm that that shows up in the output from ola_dev_info.


I've pushed a change to the git repo adding some more logging. You'll
need to run 'git pull' and then rebuild & install. Finally run olad
--logging 4 to get the extra output.

Simon


> but when I run ola_dev_info
>
> it's all blank - no devices seen, as what I used to see on ubuntu.
> I've tried the gui and there are no devices present to create the universe.
> I do notice that the ftdi presents as ttyUSB0 rather than dmx0 - is this
> correct for this new plugin?
>
> I'm confused, is there something I've just missed - I'm so close, can't wait
> to get it all working :)
>
> Any guidance appreciated.
>
> Cheers,
> Ian

[Ian Shaw]

Sorry for the slow reponse - day job :)

To help us out can you plug in the device while the Pi is running and
then send the last ~15 lines of the output from dmesg?

dmesg inc a couple lines before the usb detection:
[   17.597478] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   18.284416] bcm2835-cpufreq: switching to governor ondemand
[   18.284442] bcm2835-cpufreq: switching to governor ondemand
[   20.582416] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SS
[44911.212728] usb 1-1.2: new full-speed USB device number 5 using dwc_otg
[44911.322101] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[44911.322131] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[44911.322148] usb 1-1.2: Product: Interface USB-DMX512
[44911.322162] usb 1-1.2: Manufacturer: www.soh.cz
[44911.322174] usb 1-1.2: SerialNumber: A1JROBJC
[44911.457295] usbcore: registered new interface driver usbserial
[44911.458962] USB Serial support registered for generic
[44911.460734] usbcore: registered new interface driver usbserial_generic
[44911.460762] usbserial: USB Serial Driver core
[44911.474915] USB Serial support registered for FTDI USB Serial Device
[44911.475357] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[44911.475901] usb 1-1.2: Detected FT232RL
[44911.475929] usb 1-1.2: Number of endpoints 2
[44911.475944] usb 1-1.2: Endpoint 1 MaxPacketSize 64
[44911.475957] usb 1-1.2: Endpoint 2 MaxPacketSize 64
[44911.475970] usb 1-1.2: Setting MaxPacketSize 64
[44911.477313] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[44911.479123] usbcore: registered new interface driver ftdi_sio
[44911.479153] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
 

Also try enabling one of the other devices like ArtNet of E1.31 and
confirm that that shows up in the output from ola_dev_info.

added artnet:
ola@raspberrypi ~ $ ola_dev_info
TCPSocket.cpp:109: connect to 127.0.0.1:9010 failed, Connection refused
Device 1: ArtNet [192.168.2.39]
 port 0, IN , priority 100, RDM supported
 port 1, IN , priority 100, RDM supported
 port 2, IN , priority 100, RDM supported
 port 3, IN , priority 100, RDM supported
 port 0, OUT , RDM supported
 port 1, OUT , RDM supported
 port 2, OUT , RDM supported
 

I've pushed a change to the git repo adding some more logging. You'll
need to run 'git pull' and then rebuild & install. Finally run olad
--logging 4 to get the extra output.

pulled and re-built: 
ola@raspberrypi ~ $ olad -l 4
Olad.cpp:286: OLA Daemon version 0.8.23

OlaDaemon.cpp:105: Using configs in /home/ola/.ola

PosixInterfacePicker.cpp:139: skipping lo because it's a loopback
PosixInterfacePicker.cpp:190: Found: eth0, 192.168.2.39, b8:27:eb:54:27:90
InterfacePicker.cpp:85: Using interface eth0 (192.168.2.39)
OlaServer.cpp:215: Server UID is 7a70:2702a8c0

HTTPServer.cpp:437: HTTP Server started on port 9090

HTTPServer.cpp:541: Adding 15 as a new socket

PluginManager.cpp:73: Skipping E1.31 (sACN) because it was disabled
PluginManager.cpp:73: Skipping ESP Net because it was disabled
PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
PluginManager.cpp:73: Skipping SandNet because it was disabled
PluginManager.cpp:73: Skipping ShowNet because it was disabled
PluginManager.cpp:73: Skipping StageProfi because it was disabled
PluginManager.cpp:73: Skipping Serial USB because it was disabled
PluginManager.cpp:73: Skipping USB because it was disabled
PluginManager.cpp:73: Skipping Pathport because it was disabled

PluginManager.cpp:105: Trying to start ArtNet
PosixInterfacePicker.cpp:139: skipping lo because it's a loopback
PosixInterfacePicker.cpp:190: Found: eth0, 192.168.2.39, b8:27:eb:54:27:90
InterfacePicker.cpp:85: Using interface eth0 (192.168.2.39)
Socket.cpp:114: Binding to 0.0.0.0:6454
DeviceManager.cpp:111: Installed device: ArtNet [192.168.2.39]:2-1
PluginManager.cpp:109: Started ArtNet
PluginManager.cpp:105: Trying to start Dummy
DeviceManager.cpp:111: Installed device: Dummy Device:1-1
PluginManager.cpp:109: Started Dummy

PluginManager.cpp:105: Trying to start FTDI USB DMX

FtdiWidget-libftdi.cpp:292: Found FTDI device. Vendor: 'www.soh.cz', Name: 'Interface USB-DMX512', Serial: 'A1JROBJC'

PluginManager.cpp:109: Started FTDI USB DMX

SelectServer.cpp:454: ss process time was 0.000191
OlaServer.cpp:327: Garbage collecting

thanks,
Ian.
 

[Simon Newton]

Oh, I totally missed the obvious here. Shows what a lack of sleep can do.

if (std::string::npos != vendor.find("FTDI")) {
widgets->push_back(FtdiWidgetInfo(sname, sserial, i));
}

Patch submitted. Let me know if that works.


Simon

[Frosty]

Hi Simon,

no changed in logged output on olad and still missing from ola_dev_info.

just to sanity check did a complete new clean build also.

just to check - should the device still be picked up and registered as ttyUSB0 in dmesg? - As it is being so.

Cheers,

Ian

[Simon Newton]

On Tue, Sep 25, 2012 at 1:42 PM, Frosty <ian.t...@gmail.com> wrote:
> Hi Simon,
>
> no changed in logged output on olad and still missing from ola_dev_info.
>
> just to sanity check did a complete new clean build also.

I've done another patch, please try again.

>
> just to check - should the device still be picked up and registered as
> ttyUSB0 in dmesg? - As it is being so.

Yes, that's fine.

Simon

> --
>
>

[Ian Shaw]

Simon,

Fantastic - all working. Thanks very much, now off to figure out how to use with python and lua

Ian.

>> > [   18.284416] b--

[Simon Newton]

On Wed, Nov 7, 2012 at 6:37 AM, Thomas Eichstädt-Engelen
<teic...@gmail.com> wrote:
>
>> Fantastic - all working. Thanks very much, now off to figure out how to
>> use with python and lua
>

> Unfortunately not for me. The FTDI DMX Device doesn't show up as Port in OLA
> Admin. My environment looks like this:
>
> Debian Squeeze with olad installed from bin-packages
> Server-Info: 0.8.25
>
> root@squeeze:/dev# lsusb
> Bus 001 Device 003: ID 0403:e088 Future Technology Devices International,
> Ltd
>
> dmesg says:
> [ 2.784230] usb 1-2: new full speed USB device using ohci_hcd and address
> 3
> [ 2.996987] usb 1-2: New USB device found, idVendor=0403, idProduct=e088
> [ 2.996990] usb 1-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 2.996991] usb 1-2: Product: USB DMX512
> [ 2.996993] usb 1-2: Manufacturer: OksiD

This is the cause. The product ID doesn't match the FTDI one (0x6001).
Also I haven't come across this manufacturer before.

Do you have a link to the device online so I can check it out?

Simon



> [ 2.996994] usb 1-2: SerialNumber: ########
> [ 2.997052] usb 1-2: configuration #1 chosen from 1 choice
> [ 3.626781] udev[284]: starting version 164
>
> ftdi plugin seems to be available:
>
> root@squeeze:/dev# ola_plugin_info
> Id Plugin Name
> --------------------------------------
> 1 Dummy
> 2 ArtNet
> 3 ShowNet
> 4 ESP Net
> 5 Serial USB
> 6 Enttec Open DMX
> 7 SandNet
> 8 StageProfi
> 9 Pathport
> 11 E1.31 (sACN)
> 12 USB
> 13 FTDI USB DMX
> --------------------------------------
>
> and:
>
> root@squeeze:/dev# ola_plugin_info -p 13
> FTDI USB Chipset DMX Plugin
> ---------------------------
> This plugin is compatible with Enttec OpenDmx and other
> FTDI chipset based USB to DMX converters where the host
> needs to create the DMX stream itself and not the interface
> (the interface has no microprocessor to do so)
>
> --- Config file : ola-ftdidmx.conf ---
>
> frequency = 30
> The DMX stream frequency (30hz to 44hz max are the usual)
>
>
> but olad doesn't seem to find the device:
>
> Nov 7 15:17:59 squeeze olad: HTTPServer.cpp:437: HTTP Server started on
> port 9090
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:73: Skipping Enttec Open DMX
> because it was disabled
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:73: Skipping Serial USB
> because it was disabled
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:105: Trying to start ArtNet
> Nov 7 15:17:59 squeeze olad: NetworkUtils.cpp:69: Could not convert address
> eth1
> Nov 7 15:17:59 squeeze olad: DeviceManager.cpp:111: Installed device:
> ArtNet [192.168.56.2]:2-1
> Nov 7 15:17:59 squeeze olad: Universe.cpp:428: Full RDM discovery triggered
> for universe 1
> Nov 7 15:17:59 squeeze olad: PortManager.cpp:151: Patched 2-1-I-0 to
> universe 1
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:109: Started ArtNet
> ...
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:105: Trying to start FTDI
> USB DMX
> Nov 7 15:17:59 squeeze olad: PluginManager.cpp:109: Started FTDI USB DMX
> Nov 7 15:18:06 squeeze kernel: [ 16.681331] eth1: no IPv6 routers present
>
> probably this is due the fact that
>
> ls -l /dev doesn't show up a device "ttyUSB0"
>
>
> What do i miss here?
>
> Regards,
>
> Thomas E.-E.
>
> --
>
>

[Thomas Eichstädt-Engelen]

Hi Simon,

> This is the cause. The product ID doesn't match the FTDI one (0x6001).
> Also I haven't come across this manufacturer before.

you mean 0x6001 is hardcoded to the ftdi plugin?

> Do you have a link to the device online so I can check it

The device is somewhat diy (although i bought it some tome ago). You'll find a description here http://jeanmarclienher.homepage.bluewin.ch/usb2dmx/index_en.html.

I still have the problem that no /dev/ttyUSBx file is shown. Kernel-Drivers are properly loaded ... strange ...

Thanks for your help!

Thomas E.-E.

[Simon Newton]

On Wed, Nov 7, 2012 at 7:59 AM, Thomas Eichstädt-Engelen
<teic...@gmail.com> wrote:
> Hi Simon,
>
>> This is the cause. The product ID doesn't match the FTDI one (0x6001).
>> Also I haven't come across this manufacturer before.
>
> you mean 0x6001 is hardcoded to the ftdi plugin?

Yes, because that's what the FTDI USB -> DMX devices usually have.
That avoids us trying to use all FTDI devices as a DMX widgets.

http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_100_USB_VID-PID_Guidelines.pdf

Do you know where the product ID of 0xe088 comes from? If it was
assigned by FTDI for this interface then it's fine to add it to olad
but I'd like to confirm first.

>
>> Do you have a link to the device online so I can check it
>
> The device is somewhat diy (although i bought it some tome ago). You'll find a description here http://jeanmarclienher.homepage.bluewin.ch/usb2dmx/index_en.html.
>
> I still have the problem that no /dev/ttyUSBx file is shown. Kernel-Drivers are properly loaded ... strange ...

That's probably the same thing. I suspect the kernel driver doesn't
know about a product id of 0xe088 so it ignores it.

Simon

>
> Thanks for your help!
>
> Thomas E.-E.
>
>

> --
>
>

[Thomas Eichstädt-Engelen]

Hi,

i read it from "lsusb":

root@squeeze:/dev/bus/usb/001# lsusb -v

Bus 001 Device 003: ID 0403:e088 Future Technology Devices International, Ltd

Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0xe088
bcdDevice 0.00
iManufacturer 1 OksiD
iProduct 2 USB DMX512
iSerial 3 ########
bNumConfigurations 1

Thomas E.-E.

> --
>
>

[Simon Newton]

On Wed, Nov 7, 2012 at 8:28 AM, Thomas Eichstädt-Engelen
<teic...@gmail.com> wrote:
> Hi,
>
> i read it from "lsusb":

Yes, I realize that. I want to know who assigned it though. Did you
build this device yourself? If so, did you compile the firmware? Were
there any comments in the source code?

Simon

> --
>
>

[Simon Newton]

On Wed, Nov 7, 2012 at 8:31 AM, Simon Newton <nom...@gmail.com> wrote:
> On Wed, Nov 7, 2012 at 8:28 AM, Thomas Eichstädt-Engelen
> <teic...@gmail.com> wrote:
>> Hi,
>>
>> i read it from "lsusb":
>
> Yes, I realize that. I want to know who assigned it though. Did you
> build this device yourself? If so, did you compile the firmware? Were
> there any comments in the source code?

I've emailed the contact on
http://jeanmarclienher.homepage.bluewin.ch/usb2dmx/index_en.html with
the same question.

[Thomas Eichstädt-Engelen]

ah ok, sorry!

no, i didn't built it myself!

i bought it at ebay ... thanks for your effort!

Thomas E.-E.

> --
>
>

[Thomas Eichstädt-Engelen]

i talked to the guy who sold the adapter to me yesterday. He confirms that it is equal to elektor-circuit. Hope that Jean Marc can provide more information ...

 

Regards,

 

Thomas E.-E.

 

2012/11/7 Thomas Eichstädt-Engelen <teic...@gmail.com>

[Simon Newton]

On Thu, Nov 8, 2012 at 2:14 AM, Thomas Eichstädt-Engelen
<teic...@gmail.com> wrote:
> i talked to the guy who sold the adapter to me yesterday. He confirms that
> it is equal to elektor-circuit. Hope that Jean Marc can provide more
> information ...

Hmm, this is quite strange. From the article you sent me this devices
doesn't even use an FTDI chip, yet it uses the FTDI manufacturer id.
Quoting the article:

"...the USB standard defines two data transfer modes for low speed,
Control transfer and Interrupt transfer. The control mode uses all of
the bus bandwidth and is, according to the standard, reserved for USB
receiver configurations. The Interrupt mode is intended for data
transfer but we should note that it is limited to 800 bytes per
second!"

As an aside, the Velleman device has the same problem and can only
update at 800bytes / second.

"With the above in mind we’re more or less forced to use the 16C745 in
a configuration that’s not found in the USB 908485 Personal Download
for Eichstädt-Engelen, Thomas | copyright Elektorstandard. To do so,
we have selected the Control transfer mode in order to exchange data
between the computer and the microcontroller. Obviously, considering
that the USB bus was not designed for that use, we had to write a
special driver for this Microsoft Windows® application. The firmware
source code for the microcontroller is available from our website at
www.elektor-electronics.co.uk (file # 060129-11.zip). Unfortunately,
the copyrights for the driver source code rest with the author, hence
this file cannot be made freely available."

I have a copy of the zipfile if anyone wants it. It'll save you from
registering on the elektor site.

"The driver (see the screenshot in Figure 7), of which the source code
is regrettably not available, is in charge of shaping Control-type
requests travelling on the USB bus. The OGENINT.INF file makes the
driver installation possible. It creates the association between the
driver with our USB module, thanks to the Vendor ID and Product ID
identifiers that are specific to our application"

From the .INF file:

[SourceDisksNames]
1="www.oksidizer.com USB driver","",1

[SourceDisksFiles]
ogenint.sys=1

[Manufacturer]
%MfgName%=OksiD

[OksiD]
%USB\VID_04D8&PID_0000.DeviceDesc%=OGENINT.Dev, USB\VID_04D8&PID_0000
%USB\VID_0403&PID_E088.DeviceDesc%=OGENINT.Dev, USB\VID_0403&PID_E088


Interestingly enough it uses the dashard.dll , which seems to be based
on a similar driver from nicolaudie.


Maybe on of the USB experts on the list can help out.

Simon

>
> Regards,
>
> Thomas E.-E.
>
>
>
> 2012/11/7 Thomas Eichstädt-Engelen <teic...@gmail.com>
>>
>> ah ok, sorry!
>>
>> no, i didn't built it myself!
>>
>> i bought it at ebay ... thanks for your effort!
>>
>> Thomas E.-E.
>>
>

> --
>
>

[Simon Newton]

Jean responded:

"""
Yes this ID was assigned to me.

But my DMX512 interface doesn't use a FTDI chip, so I think that I was
not allowed to use it for it.

Today I don't know if FTDI has re-assigned the ID to an other person
or if it is still assigned to me.

[Thomas Eichstädt-Engelen]

Thanks Simon,

i gave up and bought an "Eurolite USB-DMX512-PRO" Interface ...

Hopefully it will work better :-)

Regards,

Thomas E.-E.

> --
>
>

[Andrew Frazer]

Hopefully in the next few weeks, we'll have an open source but purchasable really high quality DMX interface!

> --
>
>

[Thomas Eichstädt-Engelen]

ok ... that's within the official return timeframe :-)

I am curious about it!

> --
>
>

[Simon Newton]

On Mon, Nov 12, 2012 at 12:29 AM, Thomas Eichstädt-Engelen
<teic...@gmail.com> wrote:
> Thanks Simon,
>
> i gave up and bought an "Eurolite USB-DMX512-PRO" Interface ...

Just to close the loop on this, Jean sent me the source for his
windows driver. However it looks like the devices aren't made anymore,
if I ever come across one I'll look at adding support for it.

Simon

> --
>
>

[Thomas Eichstädt-Engelen]

Hi Simon,

the devices are still sold on ebay.

I could send you mine to test/implement the driver.

Regards,

Thomas E.-E.



2012/11/25 Simon Newton <nom...@gmail.com>:

> --
>
>

[kultex]

here is a cheap seller, if still somebody whants it

http://www.ebay.at/itm/USB-to-TTL-Serial-Cable-FTDI-chipset-/290828989695?pt=UK_Computing_Parallel_Serial_PS_2&hash=item43b6c234ff

[RenZO]

Le dimanche 9 décembre 2012 23:05:54 UTC+1, waldo a écrit :

Awesome, great work, folks! Just got it running.

A couple of documentation notes, that might make it easier for anyone starting from scratch, as I was:

(my notes in red)

Download the raspbian git image from here: http://nomis52.net/data/raspi/ Not the raspbian-ola image!

Install to SD card & reboot 

login as ola No, threre's no user with that name in latest image. Try user: pi passwd: openlighting  
cd ola No, the directory is open-lighting

sudo make install 
sudo ldconfig 

unplug all the usb devices 
run olad, wait for it to start, then stop it (either control-C or 
through the web UI) 
now all the config files have been created in ~/.ola/ 
use renzo's script to disable everything:

  Renzo's script is not included in the image, grab it from Renzo's site: http://www.imaginux.com/ccount/click.php?id=153

  HOWEVER! For me (safari 4) the php counter was failing, I had to manually increment it, to actually get to the file to download

  (php?id=154, php?id=155, etc)

Thanks waldo. Some precisions :

The current working link is :
http://www.imaginux.com/ccount/click.php?id=155

Also, you can get the git version :
https://github.com/RenZ0/ola-conf-plugins

Or the debian package (when starting olad with the init script) :
http://apt.openlighting.org/raspbian/pool/main/o/ola-conf-plugins/

RenZO
 

disable all plugins ./ola_conf_plugins.sh disable all
enable just the ftdi plugin:  ./ola_conf_plugins.sh enable ftdidmx 

edit  /etc/udev/rules.d/30-ftdidmx.rules and uncomment the last line 

  as noted above, the file is 10-local.rules

  but also: uncomment the line related to ftdi (it was the first line, not the last)

reboot
attach Open DMX USB device 

login & start olad just "olad", right, no flags needed? That is working for me.
profit 

Again, thanks and great stuff. Now I'm going to hack up a little javascript and get my holiday lights going.

cheers,

waldo

[RenZO]

Arg, I didn't see the url tag. here is the good one.
http://www.imaginux.com/ccount/click.php?id=155

Please note the last version is the git one anyway.

RenZO