![]() ![]() This might be a big problem for laptop users without a secondary big screen, or who are portable and don’t have a dedicated work space. either way it’s a annoying… or i need to buy another real big monitor, but i already have a 15" macbook pro, which is great and enough when i hide the panels. To come around this, i currently scroll around and zoom in and out, or hide and show the panels, most probably its a mix of both. If the robot is docked extra information about the dock ID, and charge status is provided.I need as much real state as possible to view the designs and screens am working in a readable viewable way, if the makes sense. It will indicate if the robot is already docked, currently docking, or not docked. Issuing a GetDockingState command will return the docked status of the robot independent of any DockingCommand. This can help determine what the robot will detect as a dock, and which type of dock. ![]() Issuing a GetDockingConfig command will return a list of dock IDs and their dock type. Under normal circumstances it’s recommended to use the automatic undocking behavior. If the area in front of the robot isn’t clear it’s possible to manually undock the robot by simply powering it on, standing, and driving, just like you would if the robot wasn’t docked. The robot will remain standing waiting for its next command. It should report STATUS_IN_PROGRESS while executing then STATUS_AT_PREP_POSE once undocking has finished. Poll the robot with DockingCommandFeedback with the provided docking command ID to check on the status on the execution. The robot will stand up, and walk in front of the dock. ![]() A docking_station_id is not required to undock. Issue a DockingCommand with an end time, but this time set the prep_pose_behavior=PREP_POSE_UNDOCK. Power on the robot however you like, this is not the responsibility of the docking service for safety reasons. To undock the robot it should be sitting on the dock with the area in front of the dock unobstructed. You do not need to issue multiple DockingComand RPCs unless you explicitly want to issue a new docking command. ![]() It should report STATUS_IN_PROGRESS while executing then STATUS_DOCKED when finished.ĭocking the robot automatically powers it off at the end. You will be provided a docking command ID in return. Issue a DockingCommand, with an end time long enough to complete the docking sequence (30 seconds is a recommended value). To dock the robot it should be powered on and standing near the dock so that the robot can detect it. Get the current docking status of the robot There are four RPCs to the docking service. The docking service provides an interface to control Spot and use a Spot Dock. The rear tower is secured by an interlock preventing the electrical connector being exposed without a robot. When Spot docks, they lower, revealing the connector. There are two indexing cones on the dock which help locate the robot connector. It should be kept clean and unobstructed. The tag on top of the robot is used by the robots vision system to locate the dock. The Spot Dock (pictured below) is a docking station for the Spot Robot that has power and high speed ethernet connections to recharge and download data from the robot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |