-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to run blinky under Ubuntu 12.04 #7
Comments
Hi there, Sorry for the delay responding - did you manage to get it working at all? cheers |
Not really, we switched to host it in Windows, and it works fine. |
Hi, I'm also experiencing this same issue. Sounds like you threw in the towel, fff, but were you able to make any progress before then? Cheers, John |
Hi Aurekin I'd like to get to the bottom of this - Would you be able to make code changes and try them out on your system? Perryn |
I'd be happy to. Also not sure if this helps or if I'm going in totally the wrong direction but I noticed in my lsusb output for my build light:
Looks like wMaxPacketSize is 8 bytes but libusb is sending:
which seems to be 16 bytes? Again, just messing around and clutching at straws but thought maybe it's useful. |
heh - no idea :) In the meantime try adding
after line 5 in light.rb? Also, what version of Ubuntu are you running? |
I'm running 14.04. I added your code and I'm now getting
Sounds like it might relate to light.rb:11 (@handle.set_configuration(device.configurations.first)) Also as an aside, I'm a Melb based TWer, just started at the beginning of the year. I'm working with Ranjeet and he mentioned that he knew you when we came across this project. Small world! |
doh In that case, instead of calling device.open in LightFactory and constructing Light with the result, you'll need to construct Light with the device and call open to obtain the handle. |
Working like a charm, now. Posting my light_factory.rb and light.rb for reference: light_factory.rb
light.rb
|
awesome, now we just need to make sure it still works on other platforms |
Sounds like a plan. I can check it on a Mac and possibly a Windows machine if that would help? |
it would, but I bet it wont work ;) |
had the same issue with my linux x64 machine, with the patch you guys figured out, its now working like a charm. thanks |
Just tested the fix on a windows machine and it seems to work just fine. Haven't had a chance to test on OSX yet but hopefully will sometime today. |
hey @Aurenkin did you get anywhere? |
I didn't get around to testing on OSX yet but thanks for reminding me, I should be able to borrow a Macbook today to test it out. |
Sorry for taking so long to get to this! Finally put OSX back on my mac and tested today. Unfortunately it looks like with the code changes we made, it doesn't work for mac :( . Let me know if you want me to test anything else out. |
hey @Aurenkin are you interested in helping out further on this? |
Yeah for sure, I don't know if I have access to a build light anymore On 7 October 2014 14:50, Perryn Fowler [email protected] wrote:
|
FWIW I'm having the same issue on a Raspberry Pi running Raspbian. |
hi @holmesjr - did you try the patch described above? |
First thing tomorrow, I'll give it a go and report the results. I can then test on a Mac to see if it still works there. |
OK, the patch makes things work once. After that the same error pops up. These were run immediately one after the other.
|
Hmm, saying it worked was slightly optimistic. While it returned without an error, the light flashed instead of actually showing the chosen status. I've run the latest from git against the same light on a Mac (without the changes above) and the correct behaviour is observed. |
I had the same problem when trying to control a 904008 light on a Raspberry Pi running Raspbian. After @Aurenkin's patch setting the lights worked. However something goes wrong later on when running .watch_test_server - not sure is it related with this patch or not. During the "WARNING" state the light blinks yellow and
|
The blinking / reconnecting problem was due to the Delcom pulling too much current from the Raspi port. Putting an active USB hub in between solved that problem. But the patch was necessary for it to work. |
I have also just run into this on current Raspbian on RPi 2. |
Not sure what's the cause
The text was updated successfully, but these errors were encountered: