BUNKERpro User Manual

Version: V.1.0.0

Date: 2021.10

Team: AgileX Robotics Team

Important Safety Information

This chapter contains important safety information. Before the robot is powered on for the first time, any person or organization must read and understand this information before using the device. If you have any questions about use, please contact support@agilex.ai. Please follow and implement all assembly instructions and guidelines in the chapters of this manual, which is very important. Particular attention should be paid to the text related to the warning signs.

Effectiveness and Responsibility

Environment

Check

Operation

Maintenance

1 Introduction to BUNKERPRO

BUNKERPRO is a tracked chassis vehicle for all-round industry applications. It has the characteristics of simple and sensitive operation, large development space, suitable for development and application in a variety of fields, independent suspension system, heavy-duty shock absorption, strong climbing ability, and being able to climb stairs. It can be used for the development of special robots such as robots for inspection and exploration, rescue and EOD, special shooting, special transportation, etc., to solve robot movement solutions.

1.1 Product list

Name Quantity
BUNKER PRO Robot Body X1
Battery Charger(AC220V) X1
Aviation male plug (4-Pin) X1
FS remote control transmitter(Optional) X1
USB to CAN communication module X1

1.2 Tech specifications

Parameter Types Items Values
Dimensions Dimensions 1064mm*845mm*73mm
Chassis height 120mm
Track width 150mm
Length 740mm
Weight Weight About180kg
Load 120kg
Type Lithium battery
Capacity 60AH
Battery Voltage 48V
Maximum climbing capacity 30°
Maximum speed 1.5m/s
Motion Minimum turning radius Can rotate in place
Maximum obstacle 180mm
Motor parameters 2×1500W brushless servo motor
Code disk parameters 2500 lines
Control Operating temperature -20~60°C
Reduction ratio 1: 7.5
Control mode Remote control
RC transmitter 2.4G/extreme distance 200M
Communication interface CAN

1.3 Requirement for development

BUNKERPRO is equipped with FS remote control at the factory, and users can control the BUNKERPRO mobile robot chassis through remote control to complete the movement and rotation operations. BUNKERPRO is equipped with CAN interface, and users can carry out secondary development through it.

2 The Basics

This section will give a basic introduction to the BUNKERPRO mobile robot chassis, so that users and developers have a basic understanding of the BUNKERPRO chassis.

2.1 Instructions on electrical interfaces

The rear electrical interfaces are shown in Figure 2.1, where Q1 is the CAN and 48V power aviation interface, Q2 is the power switch, Q3 is the charging interface, Q4 is the antenna, Q5 and Q6 are respectively the driver debugging interface and the main control debugging interface (not open to the outside), and Q7 is the power display interaction.

Figure 2.1 Rear Electrical Interfaces showing ports labeled Q1 through Q7.

The definition of Q1's communication and power interface is shown in Figure 2.2.

Pin No. Pin Type Function and Definition Remarks
1 Power VCC Power positive, voltage range 23 - 29.2V, Max.current 10A
2 Power GND Power negative
3 CAN CAN_H CAN bus high
4 CAN CAN_L CAN bus low

Figure 2.2 Pin Definition of the Rear Aviation Extension Interface

2.2 Instructions on remote control

FS remote control is an optional accessory for BUNKERPRO. Customers can choose according to actual needs. The remote control can easily control the BUNKERPRO universal robot chassis. In this product, we use the left-hand throttle design. Refer to Figure 2.3 for its definition and function. The functions of the buttons are defined as: SWA, SWC and SWD are temporarily disabled; SWB is the control mode selection button, dialed to the top is the command control mode, dialed to the middle is the remote control mode; S1 is the throttle button, which controls the BUNKERPRO forward and backward; S2 controls rotation, while POWER is the power button, and you can turn on the remote control by pressing them at the same time. It should be noted that SWA, SWB, SWC, and SWD need to be at the top when the remote control is turned on.

Figure 2.3 Schematic diagram of the FS remote control buttons, showing buttons labeled SWA, SWB, SWC, SWD, S1, S2, and POWER.

2.3 Instructions on control demands and movements

We set up a coordinate reference system for ground mobile vehicle according to the ISO 8855 standard as shown in Figure 2.4.

Figure 2.4 Schematic Diagram of Reference Coordinate System for Vehicle Body, showing X, Y, and Z axes.

As shown in Figure 2.4, the vehicle body of BUNKERPRO is parallel to the X axis of the established reference coordinate system.

In the remote control mode, push the remote control joystick S1 forward to move in the positive direction of the X axis, and push S1 backward to move in the negative direction of the X axis. When S1 is pushed to the maximum value, the movement velocity in the positive direction of the X axis is the maximum, and when it's pushed to the minimum value, the movement velocity in the negative direction of the X axis is the maximum; the remote control joystick S2 controls the rotation of the vehicle body left and right. When S2 is pushed to the left, the vehicle body rotates from the positive direction of the X axis to the positive direction of the Y axis, and when S2 is pushed to the right, the vehicle body rotates from the positive direction of the X axis to the negative direction of the Y axis. When S2 is pushed to the left to the maximum value, the linear velocity of counterclockwise rotation is the maximum, and when S2 is pushed to the right to the maximum value, the linear velocity of clockwise rotation is the maximum.

In the control command mode, the positive value of the linear velocity means moving in the positive direction of the X axis, and the negative value of the linear velocity means moving in the negative direction of the X axis; the positive value of the angular velocity means that the vehicle body moves from the positive direction of the X axis to the positive direction of the Y axis, and the negative value of the angular velocity means that the vehicle body moves from the positive direction of the X axis to the negative direction of the Y axis.

3 Use and Development

This section mainly introduces the basic operation and use of the BUNKERPRO platform, and how to carry out the secondary development of the vehicle body through the external CAN interface and the CAN bus protocol.

3.1 Use and operation

Check

Shutdown

Startup

Basic operating procedures of remote control:

3.2 Charging

BUNKERPRO is equipped with a standard charger by default, which can meet the charging needs of customers. The specific operating procedures of charging are as follows:

3.3 Development

BUNKERPRO provides a CAN interface for the user's development, and the user can control the vehicle body through this interface. The CAN communication standard in BUNKERPRO adopts the CAN2.0B standard; the communication baud rate is 500K, and the message format adopts the MOTOROLA format. The linear velocity of the movement and the angular velocity of the rotation of the chassis can be controlled through the external CAN bus interface; BUNKERPRO will feedback the current movement status information and the status information of the BUNKERPRO chassis in real time. The protocol includes system status feedback frame, movement control feedback frame, and control frame. The content of the protocol is as follows:

The system status feedback command includes the current vehicle body status feedback, control mode status feedback, battery voltage feedback, and fault feedback. The content of the protocol is shown in Table 3.1.

Table 3.1 Feedback Frame of BUNKERPRO Chassis System Status
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
System Status Feedback Command Steer-by-wire chassis Decision-making control unit
0x221 200ms None
Data length 0x08
Position Function Data type
byte [0] Current status of vehicle body unsigned int8 0x00 System in normal condition
0x01 Emergency stop mode
0x02 System exception
byte [1] Mode control unsigned int8 0x00 Standby mode
0x01 CAN command control mode
0x03 Remote control mode
byte [2]
byte [3]
The battery voltage is 8 bits higher
The battery voltage is eight bits lower
unsigned int16 Actual voltage × 10 (with an accuracy of 0.1V)
byte [4]
byte [5]
byte [6]
byte [7]
Reserved
Failure information
Reserved
Count check (count)
unsigned int8 0x0
Refer to [Description of Fault Information]
0x00
0~255 cycle count; every time an instruction is sent, the count will increase once
Table 3.2 Description of Fault Information
Byte Bit Meaning
byte [5] bit [0] Battery undervoltage fault
bit [1] Battery undervoltage warning
bit [2] Remote control disconnection protection (0: normal, 1: remote control disconnection)
bit [3] No.1 motor communication failure (0: No failure 1: Failure)
bit [4] No.2 motor communication failure (0: No failure 1: Failure)
bit [5] Reserved, default 0
bit [6] Reserved, default 0
bit [7] Reserved, default 0

The command of movement control feedback frame includes the feedback of current linear velocity and angular velocity of moving vehicle body. The specific protocol content is shown in Table 3.3.

Table 3.3 Movement Control Feedback Frame
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Movement Control Feedback Command Steer-by-wire chassis Decision-making control unit
0x221 20ms None
Data length 0x08
Position Function Data type
byte [0]
byte [1]
The movement speed is 8 bits higher
The movement speed is 8 bits lower
signed int16 Actual speed × 1000 (with an accuracy of 0.001m/s)
byte [2]
byte [3]
The rotation speed is 8 bits higher
The rotation speed is 8 bits lower
signed int16 Actual speed × 1000 (with an accuracy of 0.001rad/s)
byte [4]
byte [5]
byte [6]
byte [7]
Reserved
Reserved
Reserved
Reserved
0x00
0x00
0x00
0x00

The control frame includes linear velocity control opening, angular velocity control opening and check sum. The specific content of the protocol is shown in Table 3.4.

Table 3.4 Movement Control Frame
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Movement Control Frame Decisionmaking control unit Chassis node
0x111 20ms None
Data length 0x08
Position Function Data type
byte [0]
byte [1]
The linear velocity is eight bits higher
The linear velocity is eight bits lower
signed int16 Moving speed of vehicle body, unit: mm/s, range [-1700,1700]
byte [2]
byte [3]
The angular velocity is eight bits higher
The angular velocity is eight bits lower
signed int16 Angular velocity of vehicle body rotation, unit: 0.001rad/s, range [-3140,3140]
byte [4]
byte [5]
byte [6]
byte [7]
Reserved
Reserved
Reserved
Reserved
0x00
0x00
0x00
0x00

The mode setting frame is used to set the control interface of the terminal. The specific protocol content is shown in Table 3.5.

Table 3.5 Control Mode Setting Frame
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Control Mode Setting Command Decision-making control unit Chassis node
0x421 20ms 500ms
Data length 0x01
Position Function Data type
byte [0] CAN control enable unsigned int8 0x00 Standby mode
0x01 CAN command mode enable

Note [1] Description of control mode: When the remote control of BUNKERPRO is not powered on, the control mode is standby mode by default, and you need to switch it to command mode to send movement control command. If the remote control is turned on, the remote control has the highest authority and can shield the control of commands. When the remote control is switched to the command mode, it still needs to send the control mode setting command before responding to the speed command.

The status setting frame is used to clear system errors. The specific protocol content is shown in Table 3.6.

Table 3.6 Status Setting Frame
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Status Setting Command Decision-making control unit Chassis node
0x441 None None
Data length 0x01
Position Function Data type
byte [0] Error clearing command unsigned int8 0x00 clear all errors
0x01 Clear motor 1's error
0x02 Clear motor 2's error

Note 3: Sample data; the following data is for testing purposes only.

1. The vehicle advances at a speed of 0.15/S

byte [0]0x00byte [1]0x00byte [2]0x00byte [3]0x00byte [4]0x00byte [5]0x00byte [6]0x00byte [7]0x00

2. The vehicle rotates at 0.2RAD/S

byte [0]0x00byte [1]0x00byte [2]0x00byte [3]0x00byte [4]0x00byte [5]0x00byte [6]0x00byte [7]0x00

In addition to the chassis status information will be fed back, the chassis feedback information also includes motor data and sensor data.

Table 3.7 Motor Speed Current Position Information Feedback
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Motor Drive High Speed Information Feedback Frame Steer-by-wire chassis Decision-making control unit
0x251~0x254 20ms None
Data length 0x08
Position Function Data type
byte [0]
byte [1]
The motor speed is 8 bits higher
The motor speed is 8 bits lower
signed int16 Current motor speed Unit RPM
byte [2] Reserved - 0x00
byte [3] The drive temperature is 8 bits lower - Unit 1 °C
byte [4]
byte [5]
byte [6]
byte [7]
Reserved
Drive status
Reserved
Reserved
unsigned int8 0x00
See Table 3.9 for details
0x00
0x00
Table 3.8 Motor Temperature, Voltage and Status Information Feedback
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Motor Drive Low Speed Information Feedback Frame Steer-by-wire chassis Decision-making control unit
0x261~0x264 None None
Data length 0x08
Position Function Data type
byte [0]
byte [1]
Reserved
Reserved
- 0x00
0x00
byte [2]
byte [3]
The drive temperature is 8 bits higher
The drive temperature is 8 bits lower
signed int16 Unit 1 °C
byte [4] Reserved - 0x00
byte [5]
byte [6]
byte [7]
Drive status
Reserved
Reserved
unsigned int8 See Table 3.9 for details
0x00
0x00
Table 3.9 Drive Status
Byte Bit Description
byte [5] bit [0] Whether the power supply voltage is too low (0:Normal 1:Too low)
bit [1] Whether the motor is overheated (0: Normal 1: Overheated)
bit [2] Reserved
bit [3] Reserved
bit [4] Reserved
bit [5] Reserved
bit [6] Reserved
bit [7] Reserved
Table 3.10 Odometer Feedback Frame
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Odometer Information Feedback Frame Steer-by-wire chassis Decision-making control unit
0x311 20ms None
Data length 0x08
Position Function Data type
byte [0]
byte [1]
Highest bit of left wheel odometer
Second-highest bit of left wheel odometer
signed int32 Chassis left wheel odometer feedback Unit: mm
byte [2]
byte [3]
Second-lowest bit of left wheel odometer
Lowest bit of left wheel odometer
byte [4]
byte [5]
Highest bit of right wheel odometer
Second-highest bit of right wheel odometer
signed int32 Chassis right wheel odometer feedback Unit: mm
byte [6]
byte [7]
Second-lowest bit of right wheel odometer
Lowest bit of right wheel odometer
Table 3.11 Remote Control Information Feedback
Command Name Sending node Receiving node ID Cycle (ms) Receive time-out (ms) Description
Remote Control Information Feedback Frame Steer-by-wire chassis Decision-making control unit
0x241 20ms None
Data length 0x08
Position Function Data type
byte [0] Remote control SW feedback unsigned int8 bit[0-1]: SWA: 2-Up 3-Down
bit[2-3]: SWB: 2-Up 1-Middle 3-Down
bit[4-5]: SWC: 2-Up 1-Middle 3-Down
bit[6-7]: SWD: 2-Up 3-Down
byte [1] Right lever left and right signed int8 Range: [-100,100]
byte [2] Right lever up and down signed int8 Range: [-100,100]
byte [3] Left lever up and down signed int8 Range: [-100,100]
byte [4] Left lever left and right signed int8 Range: [-100,100]
byte [5] Left knob VRA signed int8 Range: [-100,100]
byte [6] Reserved - 0x00
byte [7] Count check unsigned int8 0-255 cycle count

3.3.2 CAN cable connection

BUNKERPRO is shipped with an aviation plug male connector as shown in Figure 3.2. The definition of the cable: yellow is CANH, blue is CANL, red is power positive, and black is power negative.

Figure 3.2 Schematic Diagram of Aviation Plug Male Connector showing a connector with pins labeled 1, 2, 3, 4 and corresponding wire colors: Red (VCC), Black (GND), Yellow (CAN_H), Blue (CAN_L).

Note: In the current BUNKERPRO version, the external extension interface is only open to the rear interface. In this version, the power supply can provide a maximum current of 10A.

3.3.3 Realization of CAN command control

Start the BUNKERPRO mobile robot chassis normally, turn on the FS remote control, and then switch the control mode to command control, that is, turn the SWB mode selection of the FS remote control to the top. At this time, the BUNKERPRO chassis will accept the command from the CAN interface, and the host can also analyze the current status of the chassis through the real-time data fed back by the CAN bus at the same time. Refer to CAN communication protocol for specific protocol content.

3.4 Firmware upgrade (not open yet)

In order to facilitate users to upgrade the firmware version used by BUNKERPRO and bring customers a more complete experience, BUNKERPRO is provided with a hardware interface for firmware upgrade and corresponding client software. The client interface is shown in Figure 3.3.

Upgrade preparation

Firmware upgrade software

Figure 3.3 Client Interface of Firmware Upgrade showing the Firmware Upgrade Tool V1.32 interface with fields for Port number, Baud rate, buttons for Start Connection, Load File, Start Upgrade, and a welcome message detailing the upgrade process.

Upgrade preparation steps:

3.5 BUNKERPRO ROS Package Use Example

ROS provides some standard operating system services, such as hardware abstraction, low-level equipment control, implementation of common functions, inter-process message and data packet management. ROS is based on a graph architecture, so that processes of different nodes can receive, release, and aggregate various information (such as sensing, control, status, planning, etc.). Currently ROS mainly supports UBUNTU.

Development preparation

Hardware preparation
Use example environment description

Hardware connection and preparation

Figure 3.4 Schematic Diagram of CAN CABLE Connection showing connections between external power supply (Red: VCC, Black: GND), CAN cable (Yellow: CAN_H, Blue: CAN_L), and a USB interface.

ROS installation and environment setting

Download ros dependent package
Test CANABLE hardware and CAN communication
Set CAN-TO-USB adaptor
AGILEX BUNKERPRO ROS PACKAGE download and compile

Reference source: https://github.com/agilexrobotics/bunker_ros

If no error occurred in the previous steps, you should be able to use the command to view the can equipment immediately
Install and use can-utils to test hardware
If the can-to-usb has been connected to the BUNKERPRO robot this time, and the vehicle has been turned on, use the following commands to monitor the data from the BUNKERPRO chassis

Reference sources:

Start the ROS nodes

4 Precautions

This section contains some precautions for using and developing BUNKERPRO.

4.1 Battery precautions

4.2 Precautions for operational environment

4.3 Precautions for electrical external extension

4.4 Safety precautions

4.5 Other precautions

5 Q&A

Q: BUNKERPRO is started normally, but why does it not move when using the remote control to control the vehicle body?

A: First, confirm whether the power switch is pressed; and then, confirm whether the control mode selected through the mode selection switch on the upper left side of the remote control is correct.

Q: The BUNKERPRO remote control is normal; the chassis status and movement information feedback is normal; but why can't the vehicle body's control mode be switched, and why does the chassis not respond to the control frame protocol when the control frame protocol is issued?

A: Under normal circumstances, if BUNKERPRO can be controlled by the remote control, it means that the chassis movement control is normal; if it can receive the feedback frame of the chassis, it means that the CAN extension link is normal. Please check whether the command is switched to can control mode.

Q: When communicating through the CAN bus, the chassis feedback command is normal; but why does the vehicle not respond when issuing control?

A: BUNKERPRO has a communication protection mechanism inside. The chassis has a timeout protection mechanism when processing CAN control commands from the outside. Suppose that after the vehicle receives a frame of communication protocol, but it does not receive the next frame of control command for more than 500MS, it will enter the communication protection, and its speed is 0. Therefore, the commands from the host computer must be issued periodically.

6 Product Dimensions

6.1 Illustration diagram of product dimensions

Diagram showing the top, side, and front views of the BUNKERPRO robot chassis with dimensions indicated: 845mm (width), 820mm (length), 230mm (height from ground to chassis), 270mm (track width), 473mm (height of chassis side).

6.2 Illustration diagram of top extended support dimensions

Diagram showing two extended support structures with dimensions: 820mm (length), 852mm (length), 230mm (width), 40mm (thickness).

Models: Bunker Pro Tracked Mobile Robot, Bunker Pro, Tracked Mobile Robot, Mobile Robot

File Info : application/pdf, 20 Pages, 535.42KB

PDF preview unavailable. Download the PDF instead.

bunker-pro-user-manual-en

References

WPS 文字

Related Documents

Preview AgileX HUNTER SE User Manual
Comprehensive user manual for the AgileX HUNTER SE programmable UGV, covering introduction, technical specifications, safety information, operation, maintenance, development, and ROS package usage.
Preview AgileX LIMO Quick Start Guide
A concise guide to setting up and operating the AgileX LIMO mobile robot, covering power, app connection, drive modes, and tire installation.
Preview AgileX LIMO Quick Start Guide | Génération ROBOTS
Get started with the AgileX LIMO mobile robot. This guide provides instructions on operation, app control, drive modes, and settings for your ROS-compatible robot.
Preview AgileX SCOUT MINI User Manual: Robotics Development & ROS Integration Guide
AgileX SCOUT MINI User Manual: A comprehensive guide to the SCOUT MINI R&D Kit and Pro, detailing setup, ROS integration, navigation, and development for autonomous robotics research and education.
Preview PiPER Robotic Arm Quick Start User Manual v1.0
This manual provides a quick start guide for the PiPER Robotic Arm, covering important safety information, basic usage, electrical interface, teach/demonstration mode, installation, and secondary development. It details the arm's specifications, including its 6 DOFs and 1.5kg payload capacity, and guides users through setup and operation.