Can you run the following command and post back the output?
...and double-check you're connecting it to Galileo's host USB port, not the client one. Just in case
sorry for the delay and thank you in advance for your help:
it is plugged into the host port
Bus 001 Device 004: ID 0694:ff00
Bus 001 Device 002: ID 8087:07da
Bus 001 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0002
when I run dmseg:
: usb 1-1: new full-speed USB device number 3 using ohci_hcd
I think I have the same problem as: How to access USB host from Linux (Python)? but im confused about the process.
Yeah, looks like it's the same situation as in the thread you've linked - lack of the driver in Galileo's Linux out of the box.
As per the Device IDs you've posted it looks like you need the following one:
0694:ff00 - usbtmc (CONFIG_USB_TMC kernel option)
It's not built by default as far as I can see, so you'll need to build it yourself - or let me know and I'll build one for you :-)
Thanks for your reply. Are you talking about building from board support packages and including this individual option? I am sorry for the confusion but I am new to this and learning as I go.
Yep, that's exactly the thing I'm talking about. Basically it boils down to rebuilding a kernel with an additional option enabled.
You can find more information in Yocto's manual here: http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#configuring-the-kernel
And an example of how I'm doing that to enable support for a specific type of webcams here: meta-alext-galileo/recipes-addfeatures/enable_gspca_pac207_webcam at master · alext-mkrs/meta-alext-galileo · GitHub
Any further questions are more than welcome :-)
Thanks AlexT_Intel I will try this and let you know the results.
This works perfectly. I now have node js controlling Mindstorm NXT motors... although they behave erratically. Excellent help, cant thank you enough.
When using Node.js on the board compared to the laptop the code doesnt run correctly. Sometimes the commands run on the brick and sometimes they dont run at all.
Would you have any idea why this would happen? Could it be a connection issue? I installed the usb driver using:
CONFIG_USB_TMC=m in a .cfg file.
I cant seem to figure out why sometimes it will run but then other times not run at all.
It's hard to say, to be honest as I've never worked with the NXT neither do I have it to try it out... What specific code you're trying to run? Do you have any correlationbetween e.g. command you're executing and frequency of such dropouts? What happens if you just try single command over and over again, does it eventually start dropping them, or it's unpredictable?
It a piece of Node.js code which runs and then stops the motors using a module called node-nxt. The drop outs appear to be totally random. More often than not, the code doesnt work but works perfectly on the laptop.
Hi philly. Do you have any updates on that? I'm going to do a similar thing and I would be a really appreciate if you can provide some information.
Sorry for the delayed reply. I am afraid not, I couldnt get the motors to behave correctly. I assume the bits were being corrupted when being sent by the board... Its bizarre.