Status: Ok.
10 |Altitude: ?
36 |Target: N/A
37 |Send a std_msgs/Float32 value to this topic.
53 | 54 |Clicking the altimeter will mark the depth/alitude with a yellow flag and publish it. Or click the button below and input it manually.
55 | 56 | 57 | 58 | 59 | 60 |Status: Ok.
5 |Defines an axis-alligned area in the fixed frame by dragging, and publishes it as a geometry_msgs/PolygonStamped rectangle.
13 | 14 |Click the icon once to enable, drag on the view area and release to publish. Long press the icon to open this menu.
15 | 16 | 17 | 18 |Status: Ok.
6 | 7 |Percentage: ?
16 |Voltage: ?
17 |Cell Voltages: ?
18 | 19 |Current draw: ?
20 |Charge: ?
21 | 22 |Status: ?
23 |Health: ?
24 |Type: ?
25 |Read and display battery data from sensor_msgs/BatteryState messages.
28 | 29 | 30 | 31 |Status: Ok.
6 | 7 |Multifunctional button. Behavior depends on the selected topic/service type:
22 |Click the icon to trigger. Long press to reopen this menu.
32 | 33 |Status: Ok.
11 |Sending images through rosbridge may cause TCP congestion. Lower the socket throttle rate to get faster data updates, but note that other visualizers may stutter.
48 | 49 |Status: Ok.
5 |If autoscale is off, the fixed size grid will stop rendering when the line density gets too high (to prevent lag).
20 | 21 |Renders a grid relative to the fixed frame.
26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 |Each step can be divided further.
47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 |Status: Ok.
5 |Display a nav_msgs/GridCells message that typically represents sparse navigational obstacles.
13 | 14 | 15 | 16 | 17 | 1.0 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 |Rendering fixed objects at their published timestamp causes them to lag behind when focusing on frames other than the map frame. Rviz uses the latest timestamp instead, which this emulates. Enable for techincally correct rendering.
36 | 37 |Status: Ok.
5 |Initialize the localization system by sending a starting geometry_msgs/PoseStamped in the global fixed frame.
13 | 14 |Click the icon once to enable, drag on the view area and release to publish. Long press the icon to open this menu.
15 | 16 | 17 | 18 |Status: Ok.
5 | 6 |Information about publishers and subscribers.
21 | 22 |View raw messages as text for debugging.
29 | 30 |Status: Ok.
5 |Display a nav_msgs/OccupancyGrid message that typically represents a 2D map or navigational costmap.
13 | 14 | 15 | 16 | 22 | 23 | 24 | 25 | 26 | 0.7 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 |Rendering maps at their published timestamp causes them to lag behind when focusing on frames other than the map frame. Rviz uses the latest timestamp instead, which this emulates. Enable for techincally correct rendering.
40 | 41 | 42 | 43 |Relay services for calling map loading and saving nodes.
46 | 47 | 💾 map_saver 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 🖶 map_server 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 |Status: Ok.
5 |Render primitive shapes to the 2D view. Note that not all marker types are currently supported (yet!).
13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |Note: Package executable detection is experimental so not all or too many files might show up.
27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 |Waiting for rosnode info...
68 | 69 |Note that if a node is set to respawn, it'll automatically restart itself.
72 | 73 | 74 |Waiting for roswtf report...
86 | 87 |Status: Ok.
5 |Track a TF link or nav_msgs/Odometry data.
13 | 14 |Status: Ok.
5 |Display a nav_msgs/Path.
25 | 26 |Status: Ok.
5 |Point clouds are very high bandwidth topics, and as such can easily cause TCP congestion. Lower the socket throttle rate to get faster data updates, but note that other visualizers may stutter.
37 | 38 |Currently experimental and might not decode all cloud formats correctly. XYZ coordinate data is required, the rest is ignored for now.
39 | 40 | 41 |Status: Ok.
5 |Display an array of Poses as a cloud of arrows.
13 | 14 |Status: Ok.
5 |X: ?
14 |Y: ?
15 |Z: ?
16 |Distance: ?
17 |Roll: ?
18 |Pitch: ?
19 |Yaw: ?
20 |Render a single PoseStamped or PoseWithCovarianceStamped.
23 | 24 |Note: Covariance rendering assumes a 2D pose for simplicity. Side effects may include inaccuracy in high roll/pitch orientations, ask your PhD if 2D covariance rendering is right for you.
25 | 26 |Status: Ok.
5 |Range: ?
14 |Min: ?
15 |Max: ?
16 |Field of view: ?
17 |Type: ?
18 |Render a range measurement, typically from sonar or infrared sensors.
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 0.9 37 | 38 | 39 | 40 | 41 | 42 |Status: Ok.
5 |Add your custom sprite into
32 |The files should start with an underscore, must be in .png format and will rotate around the image center.
33 | 34 |A WS (not WSS) rosbridge instance is expected on port 5001 by default.
9 | 10 | 11 | 12 | 13 | 14 |Status: Ok.
5 |Latitude: ?
14 |Longitude: ?
15 |Altitude: ?
16 |Ground Covariance: ?
17 |The tile server can be changed to anything that uses 265x256 sized tiles, the Web Mercator projection, and follows the same {x},{y},{z} convention.
30 | 31 | 32 | 33 | 34 | 35 | 36 |Max tile zoom doesn't provide much detail up close, so you get to chose between pixelated or blurry.
37 | 38 | 39 | 40 | 41 | 42 | 43 |Displaying the map with 0 yaw rotation can make viewing raw NavSatFix data from receivers more stable, but don't expect the robot to be facing the right way.
44 | 45 | 46 | 47 | 48 | 0.7 49 | 50 | 51 | 52 | 53 |Import and export downloaded tiles to a file.
56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 |All fetched tiles are stored in IndexedDB for quick loading and offline use. However, browser-cached data is tied to the site's URL, so if your robot's IP changes (e.g. switching from a local network to offline AP mode), the tiles won't be accessible. To solve this, fetch and export the database while online, and reimport it in offline mode or on other machines.
64 | 65 |Status: Ok.
5 |TF Frame: ?
14 |Angle: ?
15 |Angle increment: ?
16 |Points: ?
17 |Scan time: ?
18 |Min: ?
19 |Max: ?
20 |Laser scans are typically high bandwidth topics, and as such can easily cause TCP congestion. Lower the socket throttle rate to get faster data updates, but note that other visualizers may stutter.
50 | 51 | 52 |Status: Ok.
5 |25 | Exporting the current configuration will save the widget layout, settings, camera pose, and other info, so it can be imported later, 26 | or so it can be set as a default config. 27 |
28 | 29 | 30 | 31 | 32 |Reset only the camera to its default pose (zero relative to the fixed frame link).
33 | 34 | 35 | 36 | 37 |Clear layout and import server defaults.
38 | 39 | 40 | 41 |Status: Ok.
5 |Send a goal to the navigation stack as a geometry_msgs/PoseStamped.
13 | 14 |Click the icon once to enable, drag on the view area and release to publish. Long press the icon to open this menu.
15 | 16 | 17 | 18 | 19 |0.000
5 |m/s
6 |Status: Ok.
5 |Speed: ?
31 |Max Speed: ?
32 |Min Speed: ?
33 |Status: Ok.
10 |Adds a joystick overlay to the main view that can be used to send geometry_msgs/Twist movement commands.
17 | 18 |Scroll up and drag the preview box to position the joystick on the screen.
19 | 20 | 21 | 22 | 0.5 23 | 24 | 25 | 26 | 27 | 28 | 0.5 29 | 30 | 31 | 32 | 33 | 34 | 0.05 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 |Status: Ok.
5 |Temperature (°C): ?
13 |Variance: ?
14 |TF Frame: ?
15 |Set indicator values:
18 | 19 |The indicator icon will change based on the above defined threshold values.
32 | 33 | 34 |Status: Ok.
5 |Status: Ok.
5 |Defines a sequence of poses and publishes them as a nav_msgs/Path or geometry_msgs/PoseArray.
27 | 28 |X/Y Axis: Edit horizontal positions.
29 |Z Axis: Edit vertical positions.
38 |When editing X/Y/Z positions, click the icon again to stop editing.
46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 |Tip: If you're using a nav stack that doesn't use Paths or PoseArrays, but will accept simple goals, see the demo node at rosrun vizanti waypoints_to_simple_goals.py
66 | 67 |