Update of /cvsroot/playerstage/code/player/config
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27187/config
Modified Files:
Tag: release-2-0-patches
readlog.cfg wsn.cfg
Added Files:
Tag: release-2-0-patches
erratic.cfg wbr914.cfg
Log Message:
backported client lib stuff from HEAD
--- NEW FILE: wbr914.cfg ---
driver
(
name "wbr914"
provides ["position2d:0" "ir:0"]
port "/dev/ttyUSB0"
)
--- NEW FILE: erratic.cfg ---
# Example file instantiating the Videre robot driver
# All options you might want to use are instantiated here
# In general, the player standard units are
# translational velocity: m/s
# rotational velocity: deg/s
driver
(
# Standard player options for presenting this instance of the driver
name "erratic"
# Standard player option, tells the driver to expose all interfaces, and
# assigns them IDs
provides [ "position2d:0"
"power:0"
"aio:0" ]
# Serial port to use for connecting to robot
# USB/serial link would be /dev/ttyUSB0
port "/dev/ttyS0"
# Maximum translational and rotational speeds accepted during operation.
# This is also capped by robot's internal hard limits, potentially
lower than
# given here. For Erratic, it's about 2 m/s and 720 deg/s
max_trans_vel 3
max_rot_vel 720
# The robot uses these acceleration values to achieve desired velocity.
There
# is a hard minimum acceleration as well as a top one, set by the robot.
trans_acc 1
rot_acc 200
# If set, these specify the robot to use another acceleration when
target
# velocity is zero.
# trans_decel 3
# rot_decel 300
# Parameters for the PD control loop onboard the robot. When in
individual
# wheel control, translation parameters are used for each wheel control.
# Warning: Changes can have unexpected effects, including truly erratic
# behavior.
pid_trans_p 40
pid_trans_v 100
pid_rot_p 40
pid_rot_v 100
# These set how to drive the wheel motors. Frequency affects noise, and
# perhaps power efficiency.
motor_pwm_frequency 10000
motor_pwm_max_on 0.7
# Set to 1 to have the driver use individual wheel control. PD settings
for
# translation will be used. This might be useful depending on the kind
of
# control loop in your application, but probably you want to leave it
at 0
# (default).
direct_wheel_vel_control 0
# Setting this option to 1 saves the settings in the robot, making
permanent
# whatever settings state it is in after settings of this config file
are
# applied. The settings can then be left out of other configuration
files.
# Note that some of the settings here are driver settings and not robot
ones,
# and are therefore not affected by a save.
# NOTE: If a bad setting messes up the behavior of the robot, it can be
reset
# to factory defaults by holding down its button while powering it up.
save_settings_in_robot 0
)
Index: wsn.cfg
===================================================================
RCS file: /cvsroot/playerstage/code/player/config/wsn.cfg,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -C2 -d -r1.3 -r1.3.2.1
*** wsn.cfg 12 Apr 2006 12:47:35 -0000 1.3
--- wsn.cfg 9 Jun 2006 01:17:52 -0000 1.3.2.1
***************
*** 5,9 ****
(
name "mica2"
! provides ["wsn:0"]
port "/dev/ttyS0"
speed "57600"
--- 5,9 ----
(
name "mica2"
! provides ["wsn:0" "rfid:0"]
port "/dev/ttyS0"
speed "57600"
***************
*** 17,19 ****
--- 17,36 ----
# Calibrate node 3 from group 125 (default) with X={435,545} and Y={426,534}
node3 [3 125 435 545 426 534 0 0]
+
+ # Use RAW values
+ converted 0
+ # Filter the base node (in case TOSBase is not installed on it)
+ filterbasenode 1
+ )
+
+ driver
+ (
+ name "rcore_xbridge"
+ provides ["wsn:1"]
+ port 5555
+
+ # Use converted engineering units (G)
+ converted 2
+ # The packet contains 8 samples.
+ readppacket 8
)
Index: readlog.cfg
===================================================================
RCS file: /cvsroot/playerstage/code/player/config/readlog.cfg,v
retrieving revision 1.1
retrieving revision 1.1.8.1
diff -C2 -d -r1.1 -r1.1.8.1
*** readlog.cfg 12 Nov 2004 06:08:19 -0000 1.1
--- readlog.cfg 9 Jun 2006 01:17:52 -0000 1.1.8.1
***************
*** 1,5 ****
#
# Example of playing back laser data from a log file. Playback will start
! # when the first client connects to laser:0, and will autorewind when it
# reaches the end of the file.
#
--- 1,5 ----
#
# Example of playing back laser data from a log file. Playback will start
! # when the first client connects to laser:4, and will autorewind when it
# reaches the end of the file.
#
***************
*** 7,11 ****
(
name "readlog"
! provides ["log:0" "laser:0"]
autoplay 1
autorewind 1
--- 7,12 ----
(
name "readlog"
! provides ["log:0" "laser:4"]
! filename "laser.log"
autoplay 1
autorewind 1
_______________________________________________
Playerstage-commit mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-commit
