| | Re: NXT Robot Swarm at BrickFest -- featuring Bluetooth
|
|
(...) My problems with this solution are two-fold. First, NXT-G currently can't send anything back to the PC, as it's not running anything to get the NXT-G message structure (yes, folks could write this... almost certainly will. But likely not me). (...) (18 years ago, 13-Aug-06, to lugnet.robotics.nxt)
|
|
| | Re: NXT Robot Swarm at BrickFest -- featuring Bluetooth
|
|
Here's an idea of how to get more than 3 NXTs connected via Bluetooth (BT). It involves using a PC as a "relay point". I think standards allow up to seven simultaneous connections per BT device. The limitation to three connections on the NXT may be (...) (18 years ago, 13-Aug-06, to lugnet.robotics.nxt)
|
|
| | Re: NXT Motor Encoder Accuracy and Dead Reckoning
|
|
(...) I've played with it a good bit. It seems to be extremely accurate, in that one motor will slavishly follow the other - you can do demos like set a Move block to drive forward 10 rotations, and while it's trying to do that pick up the robot and (...) (18 years ago, 13-Aug-06, to lugnet.robotics.nxt)
|
|
| | Re: NXT Motor Encoder Accuracy and Dead Reckoning
|
|
Dick, the article you referenced with the PID controller is excellent. I spent a lot of time trying to do a straight line with an RCX model a few years ago, but with a different approach: It was track-driven and the drive shaft extension on each (...) (18 years ago, 13-Aug-06, to lugnet.robotics.nxt)
|
|
| | NXT Motor Encoder Accuracy and Dead Reckoning
|
|
Has anyone done any experiments on the accuracy of the NXT motor "move to" block? If so, can they post their results or impressions? I know NXT supports PID calculations to synchronize two motors and run in a straight line. Can you use this to drive (...) (18 years ago, 13-Aug-06, to lugnet.robotics.nxt)
|