From: ahoward <ah...@us...> - 2004-09-23 15:41:47
|
On Thu, 23 Sep 2004, Cameron Stone wrote: > Not sure if I mentioned it, but the joysticking part of playerjoy is a > little silly. It only sends commands if the joystick state has changed > (which makes sense), but if the state hasn't changed it sends a stop > command (which doesn't). This means, of course, that if you want to > continue driving forward, or keep turning, you have have to wiggle the > joystick. $ playerjoy -h USAGE: playerjoy [options] <host:port> [<host:port>] ... -v : verbose mode; print Player device state on stdout -3d : connect to position3d interface (instead of position) -c : continuously send commands -n : dont send commands or enable motors (debugging) -k : use keyboard control -p : print out speeds on the console -udp : use UDP instead of TCP -speed : maximum linear speed (m/sec) -turnspeed : maximum angular speed (deg/sec) <host:port> : connect to a Player on this host and port Note the -c option; maybe this should be the default. A. Andrew Howard email: ah...@po... Department of Computer Science http: www-robotics.usc.edu/~ahoward University of Southern California phone: 1 (213) 740 6416 Los Angeles, CA, U.S.A. 90089-0781 fax: 1 (213) 821 5696 << Insert pithy saying here >>> |