-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
19 changed files
with
468 additions
and
100 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,40 @@ | ||
faults | ||
# Faults, Causes, and Solutions | ||
|
||
稍后见~拼命扒字中。。。 | ||
| Fault Description | Possible Causes | Solutions | | ||
| --------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| Robot cannot start normally | Upper limbs not calibrated | 1. Turn off the embedded robot computer.<br />2. Perform calibration according to the procedures stated in the following section.<br />3. Start the robot. | | ||
| | Abnormal wiring connections | Check the wiring connections of all interfaces and start the robot. | | ||
| | Emergency Stop switch not released | Release the Emergency Stop switch and then start the robot. | | ||
| Robot cannot stand or walk stably | Low battery level | Charge the robot. | | ||
| | Actuators overheating resulting from long-time operation | Stop operation, allow for cooling before resuming use. | | ||
|
||
For any other operational irregularities, kindly reach out to Fourier Intelligence after-sales engineers for expert assistance. | ||
|
||
## Calibration Procedure | ||
|
||
If the upper limb posture appears abnormal or if the motors have been replaced, you should perform zero calibration. The calibration procedure is as follows: | ||
|
||
1. Turn off the robot actuators and the embedded robot computer. | ||
2. Insert the calibration tool into the robot's lower limbs and waist joint pinholes. There are `6*2` zero-position pinholes in the lower limbs and `3*1` zero-position pinholes in the waist. | ||
|
||
![1703213432655](image/operation_instruction/1703213432655.png)![1703213495926](image/operation_instruction/1703213495926.png) | ||
3. Connect the embedded robot computer to a monitor through the extension dock. Plug in a keyboard and a mouse into the extension dock as well. | ||
4. Release the Emergency Stop switch and power on the embedded robot computer. The login password is `fftai2015`. | ||
5. Open a terminal and input the following command: | ||
|
||
```powershell | ||
cd ~/Documents/server_app/bin/pythonscripts/ | ||
python3 abs_run.py | ||
``` | ||
If prompted with `get abs angle complete!`, it indicates successful completion. | ||
6.Run the following commands: | ||
|
||
```powershell | ||
python3 checkabsjson.py | ||
python3 setmotorzeropos.py | ||
``` | ||
If prompted with `Set Motor Zero Position Success`, it signifies successful zero-point setting. | ||
6. Shut down the embedded robot computer. | ||
7. Press down the Emergency Stop switch. | ||
8. Remove the calibration tools. Ensure that all calibration tools have been removed before proceeding with other operations. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,24 +1,27 @@ | ||
# About RoCS Server Introduction | ||
# RoCS Server Introduction | ||
|
||
The rocs_server covers the entire communication process and capabilities of robot control. For ease of use and installation, we provide 5 .deb packages based on the Ubuntu AMD64 operating system, which will allow you to quickly and efficiently complete the installation and use of the rocs_server, so that you can focus more on manipulating the robot. | ||
The `rocs_server` covers the entire communication process and capabilities related to robot control. To simplify the installation and utilization, we offer five .deb packages specifically designed for the Ubuntu AMD64 operating system. These packages expedite the installation of the RoCS Server, streamlining your experience with robot control. | ||
|
||
## rocs-lib | ||
|
||
`rocs-libs` are the library files that our entire robot operating system relies on. We have packaged them to avoid the tedious process of you needing to download, decompress, and compile them. | ||
`rocs-libs` are the libraries that the RoCS system relies on. It provides essential features to: | ||
|
||
* Conduct rigid body dynamics computations, facilitating precise modeling of the robot's physical movements. | ||
* Tackle quadratic programming (QP) problems efficiently, enabling the robot's control system to address complex optimization tasks. | ||
* Perform various linear algebra operations, serving as the mathematical foundation for critical robot functionalities. | ||
|
||
## rocs-svr | ||
|
||
The `rocs-svr` essentially serves as the bridge between the upper computer and the lower computer. It handles commands originating from the upper computer, which can be a Control APP user interface or SDK control programs. Its primary function is to process these commands and transmit control instructions to the lower computer using underlying communication protocols. This intricate communication mechanism enables the achievement of precise control over the robot's movements. | ||
|
||
## rocs-wifi | ||
|
||
`rocs-wifi` is a crucial component in the RoCS system, responsible for managing and configuring the robot's Wi-Fi connection, including configuring and activating Wi-Fi functions. Through this component, it ensures that you can seamlessly connect to the Wi-Fi network where the robot is located. | ||
`rocs-wifi` is a crucial component in the RoCS system, responsible for managing and configuring the robot's Wi-Fi connection, including configuring and activating Wi-Fi functionalities. Through this component, it ensures a seamless connection to the Wi-Fi network where the robot is located. | ||
|
||
## rocs-webots | ||
|
||
`rocs-webots` is a simulation environment provided by us based on Webots! Perhaps before you access the robot, in order to better familiarize yourself with the operation and use of the robot, we strongly recommend that you first experience it in the Webots simulation environment. The simulation environment accurately reproduces the motion characteristics and structure of the robot, which will be a very important step. | ||
`rocs-webots` is a simulation environment based on Webots, an open source robot simulation application from Cyberbotics. Prior to interacting directly with the robot, we strongly recommend that you gain familiarity with its operation and usage by first experiencing it within the Webots simulation environment. This simulation environment faithfully replicates the motion characteristics and structure of the robot, making it an essential preliminary step. | ||
|
||
## rocs-control | ||
|
||
`rocs-control` is the core part of our robot control program, and we provide a binary file that runs in the '~/RoCS' directory of the robot host. If you need to adjust and modify configuration items, including but not limited to the PID, mass, filtering and other parameters of the robot, you can achieve this by manually modifying the configuration file. This can help you control the robot more accurately. | ||
|
||
`rocs-control` is the core component of the RoCS system, and we provide a binary file that operates within the '~/RoCS' directory of the embedded robot computer. If you need to fine-tune and customize configuration settings, which may include PID, mass, filtering, and other parameters of the robot, you can achieve this by manually editing the configuration file. This approach allows for precise control of the robot's behavior. |
Oops, something went wrong.