richrd / nxt-python

Automatically exported from code.google.com/p/nxt-python
GNU General Public License v3.0
1 stars 0 forks source link

throws BrickNotFoundError #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install nxt-python
2. Install pyUSB
3. Attempt to run file from examples folder

What is the expected output? What do you see instead?
The expected output would be to successfully run the file (Ex: mary.py).  
However, with all files, I receive the following output:

Host: 54:32:59:92:F9:39 Name: MyNXT Strict: True
USB: True BT: False Fantom: False FUSB: False FBT: False
Traceback (most recent call last):
  File "C:\Users\Student\Downloads\nxt-python-2.2.1 (1)\nxt-python-2.2.1\examples\mary.py", line 15, in <module>
    b = nxt.locator.find_one_brick(debug=True)
  File "C:\Python26\lib\site-packages\nxt\locator.py", line 137, in find_one_brick
    raise BrickNotFoundError
BrickNotFoundError

(This is with passing debug=True)

What version of nxt-python are you using? On what operating system?
2.2.1, Windows 7

I realize it was stated using USB is buggy, but I would like to continue trying 
to use it.

Original issue reported on code.google.com by mherr...@bryant.edu on 26 Jan 2012 at 3:32

GoogleCodeExporter commented 9 years ago
Have you set up the configuration file?

I would try importing usb to see if that completes correctly. You could also 
try not specifying the MAC and name of the brick and see if that fixes it (you 
might have one of them wrong).

Original comment by marcus@wanners.net on 26 Jan 2012 at 6:34

GoogleCodeExporter commented 9 years ago
I have the same problem, the force solution (Ubuntu):

from nxt.bluesock import BlueSock
blue = BlueSock('xx:xx:xx:xx:xx:x')
b =  blue.connect()

Conclusion: the BlueSock not receive the parameter of the MAC of the brick...

Original comment by alan...@gmail.com on 24 Feb 2012 at 10:01

GoogleCodeExporter commented 9 years ago
This is not the same as this issue. It does look like an interesting bug/fix, 
so I'd appreciate it if you would open a new ticket with more details. Thanks!

Original comment by marcus@wanners.net on 25 Feb 2012 at 11:52

GoogleCodeExporter commented 9 years ago
Appears to be abandoned by reporter; Will reopen if more information is given.

Original comment by marcus@wanners.net on 22 Mar 2012 at 11:46