1. Scope of Application
This technical specification applies to companies using Tongyi drives for automatic transformation of R&D, production, and technician debugging.
Second, Debugging Resources
Tongyi Wheel and Driver Selection Problem ****
(Answers are available for absolute value encoder schemes. The following configuration documents are for incremental encoder schemes.)
3. Transformation Process
3.1 Transformation (chassis driver part)
Based on the mechanical design drawing and electrical drawing, the driver must be securely attached to the vehicle body. Verify that the driver is properly connected to the three-phase wire and encoder line of the corresponding motor.
Figure 3-1: Driver Terminals
When installing a robot with multiple drives (number ≥2), all of the slave stations'
CAN_L
andCAN_H
pins can be directly connected in a series connection. The final driver, Driver4, should have itsCAN_H
pin pressed into a Decci cartridge connector and itsCAN_L
pin pressed into a Dci cartridge connector, which should then be connected to a DCI DT06-4S male head. Finally, connect the T3532
and33
number line (can1).
Note: Please refer to the Appendix for pin definitions of each driver type.
Figure 3-2: Connecting Drivers in Series
To ensure high-quality communication on the
CAN bus
, it is necessary to activate the 120Ω terminal resistor on the drive farthest from the core controller. This can be done by opening the terminal resistance onDriver1
through the dial, while forDriver2
,Driver3
, andDriver4
, the terminal resistance switch is shown in Figure 3-3.
Figure 3-3
Testing method for proper opening of terminal resistance:
Shutdown: Power off, disconnect the driver and controller. Connect the cables as shown in Figure 3-2 (Driver4 and the controller), and use a multimeter resistance gear to measure the driver side CAN bus (CAN_L, CAN_H). The resistance value should be 120 Ω, as displayed in Figure 3-4. If the resistance value is less than 120 Ω (e.g. 60Ω), it indicates that there are at least two open driver terminal resistors.
Disconnect Driver1 and Driver2 as shown in Figure 3-2. Use a multimeter to measure the resistance of the Driver1 lateral CAN bus (CAN_L, CAN_H). The resistance value should be 120 Ω, as displayed in Figure 3-4. If the resistance value is significantly greater than 120 Ω (e.g. a few KΩ), it indicates that the terminal resistance is not opened at the end of the CAN bus and needs to be adjusted.
Figure 3-4
Our company's domestic driver can enable or disable emergency stop function by controlling the motor. The corresponding IO port level on the driver determines whether the motor can be enabled or not.
Figure 3-5 shows the Tongyi drive. Connect the driver control signal terminal No. 22 pin (+15V_DIG) to No. 1 pin (IO_COM+), connect all the driver control signal terminals No. 2 pin (USRC_DI1) in parallel, and then connect the SRC2000 emergency stop output 1+(line TE354). Connect the 20th-digit pin (GND_DIG) of all drivers in parallel to another emergency-stop output 1- (line TE355) connection.
If the steering motor driver needs to be connected to a limit sensor, the driver can provide power supply to the limit sensor. Connect the positive pole to the driver's control signal terminal pin No. 22 (+15V_DIG), and the negative pole to the driver's control signal terminal pin No. 20 (GND_DIG). The positive direction limit sensor signal output should be connected to the driver's control signal terminal No. 14 pin (USRC_DI2), and the negative direction limit sensor signal output should be connected to the driver's control signal terminal No. 15 pin (USRC_DI4).
Figure 3-5
Treatment of motor lock line
Tongyi's walking motor supports a locking brake, and the wiring mode is illustrated in Figure 3-6:
Figure 3-6
Four, Drive Configuration
4.1 Communication Connection
Description of the sequence
Software version description for driving
Previous firmware version:
9.1: represents September 1st;
9.829: September 29th, 8: with 485 firmware update function (BootLoader);
Latest firmware version:
2203.801: represents March 1st, 2022. 8 represents the firmware update function (BootLoader) for 485.
22103.801: represents March 1st, 2022. 8 represents the firmware update function (BootLoader) for 485. 22 after the 1 represents the MCU's ability to switch between different pin numbers and select functions, namely P_144 and P_196. This feature is not yet in production.
22203.801: represents March 1st, 2022. 8 represents firmware update with 485 (BootLoader), and 2 after 22 represents the firmware version of IXL150 drive P_144.
12206.815: represents June 15th, 2022. The first 1 represents the general version, and 8 represents the firmware update function (BootLoader) for 485.
!! The problem-free version
The currently available version without any issues should be the version after 12206.815. It is unclear whether this is the old or new version, so please take a screenshot and ask the supplier for clarification.
The currently available version without any issues should be the version after 12206.815. It is unclear whether this is the old or new version, so please take a screenshot and ask the supplier for clarification.
The currently available version without any issues should be the version after 12206.815. It is unclear whether this is the old or new version, so please take a screenshot and ask the supplier for clarification.
Launch the software on the host computer (Refer to the driver supplier for the XML configuration file and software)
Import XML file:
Launch the easyDRIVER software and bring up the image shown above
Choose the XML file you wish to import
Establish serial port connection
Select the serial port number for the RS485 communication card and click on Connect. Once the connection is successful, the lower right section will display as follows:
4.2 Modifying Common Parameters
4.2.1 Modifying CANopen Parameters
Choose selection parameters
Select the Canopen parameter configuration
Set the baud rate to
250kps
Assign a specific node ID (the configuration in the model file must correspond, not the same for all drives)
Set the number of Pdos to
0
Activate the Canopen enable switch and select
Enable
Click on Save driver parameters
4.3 Modifying parameters of the Walking Motor (Refer to this part for walking driver)
4.3.1 Modifying the Enablement Mode
Input Drive Control Parameters
To deactivate internal I/O, choose
off
Adjust Control Mode Selection, choose
Standard Speed Loop
Save Changes
4.3.2 Modifying Speed Mode Parameters
Choose the speed control parameters
Set KP to
20000
in the stop segmentSet KI to
100
in the stop segmentSet KP to
30000
in the low speed segmentSet KI to
100
in the stop segmentSave changes
4.3.3 Modifying Electric Flow Control Parameters
Select the current control parameters
Change the Iq current proportional gain to 100
Change the Id current proportional gain to 100
Save
4.4 Modifying Steering Motor Parameters (Refer to this section for steering driver)
4.4.1 Modifying the Enable Mode
Select drive system control parameters
For example, change the internal I/O control to "off"
For example, change the control mode to "Standard Space Loop"
Save
4.4.2 Modifying Electric Flow Control Parameters
Select the current control parameters
Change the Iq current proportional gain to 30
For example, change the Id current proportional gain to 30
Save
4.4.3 Modifying Parameters for Location Control Mode
Choose the position control mode
Set the limit mode to
2
Note:
The previous version had a bug. To use this function, the software version of Tongyi Drive needs to be updated to 20220815
. Please refer to the "Driver software version Description" section. If you encounter any issues with the xml file
or have software versions earlier than this date, please contact Tongyi to upgrade.
Save
4.4.4 Setting Reset Parameters
Select motor reset control
Switch back to zero mode 1 (the steering motor must be equipped with a negative limit switch, connected to the driver's IO negative limit)
For example, change the zero offset to 00000
Save
5. Instructions for Configuring Robot Model Files
When installing the steering wheel, please ensure that it is installed in the direction indicated in the diagram. If it is a double steering wheel, please install both steering wheels in the same leading direction to avoid symmetrical installation around the origin. Although this method is feasible, it involves a coordinate system conversion, which can be rather confusing to understand. The following models are described in accordance with the aforementioned installation methods:
5.1 Walking Motor
Keyword | Description | Value | Unit |
---|---|---|---|
x | The X-coordinate of the driver installation | Set this parameter according to the actual installation position | m |
y | The Y-coordinate of the drive installation | Set this parameter according to the actual installation position | m |
Yaw | Driver installation orientation | Set this parameter according to the actual installation position | Angle of rotation |
CAN ID | The identifier for the drive's Controller Area Network | The specific value depends on the configuration of the drive's host computer | |
Max RPM | Maximum Driver Speed | 3000 | RPM |
Inverse | Logical Negation | ||
Encoder Line | Number of Encoder Wires |
| |
canPort | The port utilized by the drive | Input the value according to the actual situation | |
uplimitDI | Upper Limit of DI | -1 | |
downLimitDI | Lower Limit of DI | -1 | |
ZeroDI | Zero DI | Negative One | |
Function | Functionality | Walking | N/A |
Wheel Radius | The wheel radius, combined with the mechanical drawing parameters provided by the driver manufacturer | 0.08 | meters |
Reduction Ratio | Deceleration Ratio | 20 | |
Minimum Speed | Minimum Execution Speed | 0.05 | m/s |
Brand | Driver Brand |
|
5.2 Steering motor
Keyword | Description | Value | Unit |
---|---|---|---|
x | Driver Installation X Coordinate | Enter the value based on the actual installation position, which must be consistent with the walking motor | m |
y | The Y-coordinate of the drive installation | Enter the value based on the actual installation position, which must be consistent with the walking motor | m |
Yaw | Driver Installation Orientation | Enter the value based on the actual installation position, which must be consistent with the walking motor | Angle of Rotation |
CAN ID | The identifier for the drive's Controller Area Network | The specific value depends on the configuration of the drive's host computer | |
Max RPM | Maximum Driver Speed | 3000 | RPM |
Inverse | Logical Negation | ||
Encoder Line | Number of Encoder Wires |
| |
canPort | The port utilized by the drive | Input the value according to the actual situation | |
uplimitDI | Upper Limit of DI | -1 | |
downLimitDI | Lower Limit of DI | -1 | |
ZeroDI | Zero DI | Negative One | |
Function | Functionality | Steering | |
Max speed | Maximum velocity | Default | |
MaxAcc | Maximum Acceleration | Default | |
MaxDec | Maximum Reducer | Default | |
MaxJerk | Maximum Acceleration | Default | |
Reduction Ratio | Deceleration Ratio | 236 | |
maxAngle | Refers to the maximum angle that can be obtained according to the mechanical drawing. The maximum steering range of the steering wheel is 240°. Since the zero mode is fixed as the negative limit mark zero, maxAngle should be filled in as -240°. | -240° | Angle measurement |
minAngle | Minimum Angle | 0 | The measurement of the smallest angle |
steerOffset | SteerOffset is the angle of the zero position of the motor itself after zeroing in the car body coordinate system. When the negative limit is zero, the zero position of the motor itself is 120° in the right-handed coordinate system. Therefore, the steerOffset should be set to 120°. | 120 | Degrees |
Steering Resolution | |||
Steer Offset File | |||
Position Speed | |||
Brand | Driver Brand |
|
VI. Driver Function Detection Method
Before installing the shell, double-check the wiring to ensure it is correct.
Lift the body so that the wheels are off the ground. Turn on the robot and connect it to a network cable. Use the Roboshop software to control the robot and get the wheels moving. Use the CanScope clip to detect CAN messages on the CAN bus for at least 1 hour, ensuring that there are no errors in the CAN messages.
Place the body on the ground and use the Roboshop software to control the robot's movements: forward, backward, left, right, and left again.
Before pressing the emergency stop button, try pushing the robot to ensure that the motor is not enabled. Check the state of the Roboshop robot in the "No emergency stop" and "drive no emergency stop" states, as shown in the left image of Figure 6-1. After pressing the emergency stop button, the robot should be able to be pushed (motor enabled) again. Check the state of the robot in Roboshop in the "emergency stop" and "drive has emergency stop" states, as shown in the right image of Figure 6-1.
Perform a 24-hour task chain motion aging test and verify the Robokit Log for any error alarms.
Seven Frequently Asked Questions
7.1 Common Error Codes
The following are solutions to common errors:
Drive error and solution.pdf
改为: 改为:
Fault Code | Fault Name | Error Flag | Description |
---|---|---|---|
1 | DCBUS Overvoltages | ulSystemErrorBits (0) | Servo ON Detection |
2 | DCBUS undervoltage | ulSystemErrorBits (1) | Servo ON detection |
3 | Motor Overcurrent | ulSystemErrorBits (2) | |
4 | Encoder malfunction | ulSystemErrorBits (3) | |
5 | Control power undervoltage | ulSystemErrorBits (4) | |
5 | Control Power Undervoltage | ulSystemErrorBits (4) | |
6 | Drive Overheating | ulSystemErrorBits (5) | |
7 | Motor Overheating | ulSystemErrorBits (6) | |
8 | Motor Overload Alarm | ulSystemErrorBits (7) | |
9 | Hall signal anomaly | ulSystemErrorBits (8) | Servo ON detection |
9 | Hall signal anomaly | ulSystemErrorBits (8) | Servo ON detection |
10 | Encoder Disconnection Fault | ulSystemErrorBits (9) | Servo ON Detection |
11 | Motor Overspeed | ulSystemErrorBits (10) | |
12 | Motor Position Error/Speed Error | ulSystemErrorBits (11) | Position/Speed Control in Effect |
13 | Error verifying storage parameters | ulSystemErrorBits (12) | |
14 | Power module overcurrent (hardware) | ulSystemErrorBits (13) | non-erasable |
15 | Motor Braking Error | ulSystemErrorBits (14) | |
16 | Encoder Bias Angle Search Error | ulSystemErrorBits (15) | |
17 | Error in current detection reference | ulSystemErrorBits (16) | |
18 | Phase alarm missing | ulSystemErrorBits (17) | |
19 | Lingering | ulSystemErrorBits (18) | |
20 | Software dog reset error | ulSystemErrorBits (19) | Power off restart clear |
For instance:
0x800
can be split into two hexadecimal numbers: 100000000000
. The error sign u1SystemErrorBits (11) is 1, indicating an out-of-tolerance motor position/speed.0x80
when converted to binary is 10000000. The error sign u1SystemErrorBits (7) is 1, indicating a motor overload alarm.0x2000
when converted to binary is 10000000000000. The u1SystemErrorBits (13) is 1, indicating a power module overcurrent.