Collaboration diagram for playerjoy:
$ 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, instead of sending commands only on change (useful with drivers with watchdog timers, like the segwayrmp)
- -n : dont send commands or enable motors (debugging)
- -k : use keyboard control
- -p : print out speeds on the console
- -a : send car like commands (velocity and steering angle)
- -udp : use UDP instead of TCP (deprecated, currently disabled)
- -speed : maximum linear speed (m/sec)
- -turnspeed : maximum angular speed (deg/sec)
- -dev <dev> : Joystick device file (default /dev/js0)
- <host:port> : connect to a Player on this host and port
playerjoy supports both joystick and keyboard control, although joysticks are only supported in Linux. If supported, joystick control is used by default. Keyboard control will be used if: the -k option is given, or playerjoy fails to open /dev/js0 (i.e., there is no joystick).
Joystick control is as follows: forward/backward sets translational (x) velocity, left/right sets rotational (yaw) velocity.
Details of keyboard control are printed out on the console.
- Calibrate out initial offset; should be possible by parsing the JS_EVENT_INIT message.