RE: [open-lighting] Velleman K8062 stops working after serveral seconds

319 views
Skip to first unread message

Jason Kyle

unread,
Apr 9, 2013, 4:48:35 PM4/9/13
to open-l...@googlegroups.com

Try a powered USB hub and see if that fixes it. Maximum current available from the RPi USB port is limited and it dies with many common USB DMX interfaces.

 

Best Regards,

 

Jason Kyle

DMXking.com / JPK Systems Limited

j...@dmxking.com

 

From: open-l...@googlegroups.com [mailto:open-l...@googlegroups.com] On Behalf Of Stephan Nachtsheim
Sent: Wednesday, 10 April 2013 08:14
To: open-l...@googlegroups.com
Subject: [open-lighting] Velleman K8062 stops working after serveral seconds

 

I installed OLA Version 0.8.26 on my raspberry pi and connected a Velleman K8062 (bought 03/2013, unmodified) to it. In the beginning all works fine, but after a few seconds no DMX-commands are transmitted anymore.
This is in the logfile:

Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:105: Trying to start USB
Apr  9 12:58:29 raspberrypi olad: UsbDmxPlugin.cpp:184: Found a Velleman USB device
Apr  9 12:58:29 raspberrypi olad: DeviceManager.cpp:111: Installed device: Velleman USB Device:12-velleman
Apr  9 12:58:29 raspberrypi olad: PortManager.cpp:151: Patched 12-velleman-O-0 to universe 0
Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:109: Started USB
Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:105: Trying to start Pathport
Apr  9 12:58:29 raspberrypi olad: DeviceManager.cpp:111: Installed device: Pathport [10.21.2.13]:9-1
Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:109: Started Pathport
Apr  9 12:58:29 raspberrypi olad: Universe.cpp:584: Added source client, 0xdc4fc8 to universe 0
Apr  9 12:58:37 raspberrypi olad: VellemanOutputPort.cpp:293: USB return code was -7, transferred 8
Apr  9 12:58:37 raspberrypi olad: VellemanOutputPort.cpp:156: Send failed, stopping thread...


after restarting the olad service, it works again for a few seconds.

is anyone out there, who yould help me?

regards,
Stephan

--
The Open Lighting Group: open-l...@googlegroups.com, #openlighting (irc.freenode.org)
To unsubscribe from this group, send email to open-lightin...@googlegroups.com
For more options, visit https://groups.google.com/groups/opt_out?hl=en
 
 

Simon Newton

unread,
Apr 9, 2013, 10:52:37 PM4/9/13
to open-l...@googlegroups.com
-7 is LIBUSB_ERROR_TIMEOUT . Is there anything in dmsg?

Simon

Stephan Nachtsheim

unread,
Apr 27, 2013, 11:30:13 AM4/27/13
to open-l...@googlegroups.com
no, after the connection of the usb device, there is no further entry in dmesg:


[  636.146313] usb 1-1.3.3: new full-speed USB device number 8 using dwc_otg
[  636.250055] usb 1-1.3.3: New USB device found, idVendor=10cf, idProduct=8062
[  636.250084] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  636.250100] usb 1-1.3.3: Product: K8062 DMX Controller Rev 3.0
[  636.250114] usb 1-1.3.3: Manufacturer: Velleman Instruments
[  636.262807] generic-usb 0003:10CF:8062.0003: hiddev0: USB HID v1.01 Device [Velleman Instruments K8062 DMX Controller Rev 3.0] on usb-bcm2708_usb-1.3.3/input0

kind regards

Stephan Nachtsheim

unread,
Apr 27, 2013, 11:33:00 AM4/27/13
to open-l...@googlegroups.com
Unfortunately, it makes no difference if i use a powered usb hub or not

kind regards

Simon Newton

unread,
Apr 29, 2013, 10:27:02 PM4/29/13
to open-l...@googlegroups.com
Try editing ~/.ola/ola-usbdmx.conf and setting libusb_debug_level to
3. That should print some more logs.

Simon

Beatboxx

unread,
Jun 26, 2013, 2:57:13 PM6/26/13
to open-l...@googlegroups.com
Hello together
 
Unfortunately, i have exact the same problem. I have a new Velleman K8062, which is working without any problem on a windows machine.
when i try to use it with OLA the interface is stop working after 3-10 seconds.
 
I tried it with a powered USB-Hub and with different versions of Raspbery ola.
 
I changed the log-Level to 3. 
 
Here is my log output:
---------------------------------------------------

Jun 25 13:12:51 raspberrypi olad: PluginManager.cpp:108: Trying to start USB

Jun 25 13:12:51 raspberrypi olad: UsbDmxPlugin.cpp:184: Found a Velleman USB device

Jun 25 13:12:51 raspberrypi olad: DeviceManager.cpp:112: Installed device: Velleman USB Device:12-velleman

Jun 25 13:12:51 raspberrypi olad: PortManager.cpp:151: Patched 12-velleman-O-0 to universe 0

Jun 25 13:12:51 raspberrypi olad: PluginManager.cpp:112: Started USB

Jun 25 13:13:53 raspberrypi olad: Universe.cpp:585: Added source client, 0x1f0eaa8 to universe 0

Jun 25 13:13:55 raspberrypi olad: VellemanOutputPort.cpp:293: USB return code was -7, transferred 8

Jun 25 13:13:55 raspberrypi olad: VellemanOutputPort.cpp:156: Send failed, stopping thread...

Jun 25 13:14:25 raspberrypi dbus[1996]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)

Jun 25 13:14:25 raspberrypi dbus[1996]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)

Jun 25 13:14:25 raspberrypi polkitd[2235]: started daemon version 0.105 using authority implementation `local' version `0.105'

Jun 25 13:14:25 raspberrypi dbus[1996]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

-------------------------------------------

 

Has somebody some ideas, where the problems come from???

 

Thanks for any answers

beatboxx

Mac Hosehead

unread,
Jun 27, 2013, 3:05:50 PM6/27/13
to open-l...@googlegroups.com
--
The Open Lighting Group: open-l...@googlegroups.com, #openlighting (irc.freenode.org)
To unsubscribe from this group, send email to open-lightin...@googlegroups.com
For more options, visit https://groups.google.com/groups/opt_out?hl=en
 
 
IMO, I would blame the Raspbian/Pi combination. It seems to work well with a FTDI based USB interface. Use any other USB interface and your mileage may vary. Something I haven't tried yet is running OLA on another Pi distro.

-MH

DeadRinger

unread,
Nov 7, 2013, 10:17:39 AM11/7/13
to open-l...@googlegroups.com
Does anyone have an update on this issue?  I am getting the same problem here, with latest builds of Raspbian and the OpenDMX release.  Tried various powered hubs, but they make no difference.  Error logs very similar to the above.  The K8062 seems to work fine on other linux machines.

Best regards

DeadRinger


Andrew Raby

unread,
Nov 19, 2013, 10:56:18 AM11/19/13
to open-l...@googlegroups.com
I'm having the same problem system will function fine on a PC but not on the PI interestingly enough the same problem presents on 2 pieces of PI software DMXWheel and OLA
 
Does anybody have any update on this work around I need to get this running ASAP
 
Cheers
 

On Tuesday, April 9, 2013 9:13:56 PM UTC+1, Stephan Nachtsheim wrote:
I installed OLA Version 0.8.26 on my raspberry pi and connected a Velleman K8062 (bought 03/2013, unmodified) to it. In the beginning all works fine, but after a few seconds no DMX-commands are transmitted anymore.
This is in the logfile:

Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:105: Trying to start USB
Apr  9 12:58:29 raspberrypi olad: UsbDmxPlugin.cpp:184: Found a Velleman USB device
Apr  9 12:58:29 raspberrypi olad: DeviceManager.cpp:111: Installed device: Velleman USB Device:12-velleman
Apr  9 12:58:29 raspberrypi olad: PortManager.cpp:151: Patched 12-velleman-O-0 to universe 0

Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:109: Started USB
Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:105: Trying to start Pathport
Apr  9 12:58:29 raspberrypi olad: DeviceManager.cpp:111: Installed device: Pathport [10.21.2.13]:9-1
Apr  9 12:58:29 raspberrypi olad: PluginManager.cpp:109: Started Pathport
Apr  9 12:58:29 raspberrypi olad: Universe.cpp:584: Added source client, 0xdc4fc8 to universe 0
Apr  9 12:58:37 raspberrypi olad: VellemanOutputPort.cpp:293: USB return code was -7, transferred 8
Apr  9 12:58:37 raspberrypi olad: VellemanOutputPort.cpp:156: Send failed, stopping thread...

after restarting the olad service, it works again for a few seconds.

is anyone out there, who yould help me?

regards,
Stephan

Andrew Raby

unread,
Nov 19, 2013, 10:58:48 AM11/19/13
to open-l...@googlegroups.com
Should also say that it wont pick it up through a Powered USB hub admittedly its a cheap hub but its still not seeing it in the OLA system

Simon Newton

unread,
Nov 19, 2013, 11:28:15 AM11/19/13
to open-lighting
On Tue, Nov 19, 2013 at 7:56 AM, Andrew Raby <andre...@gmail.com> wrote:
> I'm having the same problem system will function fine on a PC but not on the
> PI interestingly enough the same problem presents on 2 pieces of PI software
> DMXWheel and OLA
>
> Does anybody have any update on this work around I need to get this running
> ASAP

I'd ditch the K8062. It's possibly the worst interface out there.

Simon

Simon H.

unread,
Dec 10, 2015, 4:40:27 AM12/10/15
to open-lighting

One of our Lightkey users has the same problem on OS X (10.10.5 on MacBook Pro). After a few seconds, DMX output stops with this message:


2015-12-10 00:11:36.396 plugins/usbdmx/VellemanOutputPort.cpp:293: USB return code was -7, transferred 8

2015-12-10 00:11:36.396 plugins/usbdmx/VellemanOutputPort.cpp:156: Send failed, stopping thread...


Output continues (for a few seconds) when restarting OLA. On the same machine, output via FreeStyler in VMWare does work. The problem does not occur on other Macs.


Is there any progress on this?

Peter Newman

unread,
Dec 10, 2015, 8:35:49 AM12/10/15
to open-lighting
Not really unfortunately Simon. Similar to the user above, can we have some more logging, with libusb debug turned up to 3 or 4. Can they update to the latest OLA please, it may be fixed, or at least different in 0.9.8.

Simon H.

unread,
Dec 10, 2015, 9:58:01 AM12/10/15
to open-lighting
Thanks for the reply Peter. I will try to get the log output, but I can't ask the user for that and unfortunately I have been unable to reproduce the problem myself so far. We also hope to ship the latest OLA version with Lightkey soon, but it's not a top priority and will require a lot of testing. Anyway, I did not find anything in the release notes related to this issue.

Simon Newton

unread,
Dec 10, 2015, 10:57:40 AM12/10/15
to open-lighting
The K8062 are notoriously flaky on top of just being poorly designed
overall. See https://wiki.openlighting.org/index.php/Velleman_K8062

I think I recommended early on that you (LightKey) don't claim support
for the K8062 on your website, this is why.

We could add retry logic to the code but I think I tried that in the
past and it didn't help.


Simon
> --
> The Open Lighting Project: open-l...@googlegroups.com, #openlighting
Reply all
Reply to author
Forward
0 new messages