 | | | | | |
In lugnet.robotics, David Hurley wrote:
> Bluetooth isn't functioning very well with mine.
What exactly seems to be the problem? Can you connect to the NXT from the
programming environment?
> I thought it had more memory than it does.
Note that if you don't want the "Try Me" and on-brick programming options,
these can all be deleted freeing up some room. From the memory pane, there's a
small check box in the upper right corner. Click it to see the "system files",
and you can delete those as well. You can even delete the system sounds - it
won't crash it, just not make the sounds anymore
> One other thing I did notice too was that the ultrasound
> sensor minimum range was about two inches.
Yep. If you're still yelling, it's hard to tell if you're hearing an echo, or
your original yelp :-).
--
Brian Davis
| | | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics, Brian Davis wrote:
> In lugnet.robotics, David Hurley wrote:
>
> > Bluetooth isn't functioning very well with mine.
>
> What exactly seems to be the problem? Can you connect to the NXT from the
> programming environment?
>
> > I thought it had more memory than it does.
>
> Note that if you don't want the "Try Me" and on-brick programming options,
> these can all be deleted freeing up some room. From the memory pane, there's a
> small check box in the upper right corner. Click it to see the "system files",
> and you can delete those as well. You can even delete the system sounds - it
> won't crash it, just not make the sounds anymore
>
> > One other thing I did notice too was that the ultrasound
> > sensor minimum range was about two inches.
>
> Yep. If you're still yelling, it's hard to tell if you're hearing an echo, or
> your original yelp :-).
I am still having Bluetooth connectivity problems. It may be endemic of my USB
dongle I am using; I don't know. I have had a couple successfull connections
with BT, but nothing I would consider reliable or consistent. I did mess around
with it early on but I think I have undone those boo-boos.
I even updated the firmware to v1.03,but still no change. I may have to do some
registry hack or uninstall everything. I have already reinstalled the NXT
software and drivers. I'm not sure where the problem is right now -- all I know
is that the logo blinks on and off like it is trying to connect. Maybe it's a
refresh thing with my dongle vendor software.
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics, David Hurley wrote:
> Bluetooth isn't functioning very well with mine.
A couple ideas.
It seemed to work exactly once for me on a couple laptops. I was able to
restore it by deleting all of the virtual serial ports it created (it seems
to create one for each scan, then it looses track of which one it's supposed
to be talking to). After it starts working, don't rescan, just use it.
The lego software didn't seem to play nice with the vendor-supplied USB
driver (in that it seemed to be fighting for which app would do the PIN
authentication). Since it only needs a virtual serial port, I just
"updated" the device to use the native microsoft driver (calls it something
like a 'cambridge digital radio') instead. Note you can flip back and forth
between these drivers without harm, although you will get the little
microsoft bluetooth icon as active instead of the vendor one (which will
show inactive).
Hope this help!
--
View this message in context: http://www.nabble.com/Have-you-got-your-NXT-yet--tf1861916.html#a5175465
Sent from the LEGO Robotics forum at Nabble.com.
| | | | | | |
