1. 10 May, 2005 4 commits
  2. 09 May, 2005 2 commits
  3. 28 Apr, 2005 1 commit
  4. 22 Apr, 2005 2 commits
  5. 08 Apr, 2005 1 commit
  6. 07 Apr, 2005 1 commit
  7. 06 Apr, 2005 4 commits
  8. 01 Apr, 2005 1 commit
  9. 31 Mar, 2005 2 commits
    • Timothy Stack's avatar
      Tweaks for garcia-pilot: · bcfa8a85
      Timothy Stack authored
      	* robots/primotion/garcia-pilot.cc: Turn off the fall sensors,
      	since they have a tendency to go off for no good reason.
      
      	* robots/primotion/pilotButtonCallback.cc: A short-click on the
      	user-button now shuts the garcia down.
      
      	* robots/primotion/pilotClient.cc,
      	robots/primotion/wheelManager.hh,
      	robots/primotion/wheelManager.cc: Set the wheel speed.
      bcfa8a85
    • Timothy Stack's avatar
      · 6cce1762
      Timothy Stack authored
      Pass camera local to world offsets through vmcd.
      
      	* event/sched/rpc.cc: Add the camera fixed_x,fixed_y values to the
      	emcd.config file.
      
      	* robots/emc/emcd.c: Pickup the cameras fixed_x,fixed_y values
      	from the config file.  Add supports for setting the speed of the
      	robot.
      
      	* robots/mtp/mtp.h, robots/mtp/mtp.c: Add support for setting
      	speed in GOTO packets and constructing vmc-client config packets.
      
      	* robots/mtp/mtp.x: Add a vmc-client config packet that contains
      	the cameras origin in world coordinates.
      
      	* robots/mtp/mtp_dump.c: Dump the min/max values for x and y,
      	handy for figuring out the bounds of the camera.
      
      	* robots/vmcd/visionTrack.c, robots/vmcd/visionTrack.h: Handle
      	cameras that are overlapping on two axes.
      
      	* robots/vmcd/vmc-client.c: Accept a vmc-client config packet that
      	tells us where the camera is in world coordinates.  Add an
      	orientation flag that specifies how the camera is oriented wrt to
      	the world coordinate system.
      
      	* robots/vmcd/vmcd.c: Send vmc-client config packets out.  Fix a
      	bug that left unknown tracks in the previous frame, which could
      	confuse the matching algorithm causing it to match unknown tracks
      	instead of valid known tracks.
      6cce1762
  10. 18 Mar, 2005 3 commits
  11. 16 Mar, 2005 1 commit
  12. 07 Mar, 2005 3 commits
  13. 04 Mar, 2005 3 commits
    • Leigh B. Stoller's avatar
      This started out as a cleanup pass ... · 4e1cc382
      Leigh B. Stoller authored
      * Add nodeinfo backend page for the tracker applet to query for info about
        the nodes, including what type, what size, fixed/mobile, allocated etc.
        This is so we can draw the dots in the right scale, and make sure that
        fixed motes cannot be dragged around in the applet.
      
      * Clean up a bunch of hardwired constants, mostly related to the size
        of the dots, and the font size (which determines where labels get
        drawn.
      
      * And then I noticed the oddity resulting from having a robot that is 10.5
        inches long, but sweeps a diameter of 14 inches. The dot we draw is in
        scale (10.5in), but when I changed it to draw a 14in scale dot, that
        looked all wrong. So, there are actually two sizes now; the size of
        the robot, and the radius of the circle it sweeps (which is critical
        for determining obstacle avoidance). Still, this is confusing cause the
        user will place a robot near an obstacle (not overlapping) but will be
        told there is overlap cause the bubble around the robot is bigger then
        the dot. Not sure what to do about that. I could draw a large bubble
        around the robots but that is going to increase the clutter quite a bit.
      4e1cc382
    • Leigh B. Stoller's avatar
      Add checks to make sure that a robot destination does not overlap a · 84c4f96b
      Leigh B. Stoller authored
      current robot location (or its destination if the other robot is
      moving or being dragged to a new location).
      
      Oh, I should mention that to make the calculation easier, I am
      treating robots as rectangles not circles. This is not ideal, but I
      was not sure how to calculate overlap of two circles in a reasonably
      efficient manner. I'm sure a high school student can tell me though.
      84c4f96b
    • Leigh B. Stoller's avatar
      As per Tim's comments, just the center point of a robot needs to be · be6ded17
      Leigh B. Stoller authored
      fully contained within at least one camera (not the entire robot).
      be6ded17
  14. 03 Mar, 2005 4 commits
  15. 02 Mar, 2005 2 commits
  16. 01 Mar, 2005 1 commit
  17. 22 Feb, 2005 2 commits
    • Leigh B. Stoller's avatar
      Add loc_z to the location info table, and display that on both the · 67ff3af6
      Leigh B. Stoller authored
      static robot map and in the robot tracker applet.
      67ff3af6
    • Timothy Stack's avatar
      · 48d5c24a
      Timothy Stack authored
      Report battery stats using the watchdog:
      
      	* robots/emc/emcd.c: Don't send events with battery levels
      	anymore.
      
      	* tmcd/tmcd.c: Add 'battery' command that updates the
      	battery_percentage, battery_voltage, and battery_timestamp values
      	in the nodes table.  It's currently only called by the watchdog
      	running on the garcias.
      
      	* tmcd/common/libtmcc.pm: Add TMCCCMD_BATTERY function.
      
      	* tmcd/common/watchdog: Updated to send back battery information
      	obtained from garcia-pilot.
      48d5c24a
  18. 18 Feb, 2005 3 commits