- Toolchain/IDE : MDK-ARM V5
- package version: STM32Cube FW_F4 V1.21.0
- FreeRTOS version: 9.0.0
- CMSIS-RTOS version: 1.02
- Naming of variables and functions should follow Unix/Linux style
- chassis_task and gimbal_task is hard real-time task, have the highest priority cannot be preempted or blocked by other tasks
- The tasks that do not need accurate timing are realized by self-actualized software timer, and the timing accuracy is affected by task scheduling
1.As the shooting system trigger have a low resistance, small rotation of load motor could make the bullet move across the trigger and touch the friction wheel, causes the friction wheel motor unable to launch. friction wheel will be wore and motor launch fail. As a result, before you turn on the power, please be sure that no bullet have across the trigger. How to take the bullet out：hold friction wheel on one side with your hand, rotate the other friction wheel.
2.As the snail motor fail to initialize, the frequency of the sound generate by the motor is in the response range of angular velocity. it will disturb the control of the gimbal, result in loss of control. Solution：could use bandstop filter on gyroscope data. （not include in this version）
3.In gimbal control logic, consider that testing virsual recognize armor may need shoot bullet, we allowed single shoot mode under full-auto mode, but if you forget to return the rod to the middle. it will cause the robot change from full-auto mode to manual mode and start continuous shoot mode. As a result, after you shoot a bullet under full-auto mode, please return the left rod to the middle
4.International development board type A have a jumper cap. it used to short on board 4-pin serial port R and G (only the board on chassis need short R and G). the firmware check if the signal of R is low to decide it on the chassis or gimbal. if you cannot control the robot and no-sound-and-light alert, please check if the jumper cap is loose.
Underlying code integrated with gimbal automatic calibration function. it first uses IMU to calibrate pitch, making gimbal stays at water level. This process spends 20 to 30 seconds. Then Yaw calculate the mid-value after turns left until reach the left limit and turns right until reach the right limit.
Triggering Condition:
- Development board first time flashed program or parameter area is emptied
- press the on-board white button to trigger
- Host send a protocol signal to trigger
Notice：when you calibrate, you must put the chassis on a horizontal ground. Pitch may not able to reach the position in the range of error during calibration. That's because the load on gimbal is too heavy. you can manually move upward the gimbal in this case, to accelerate the calibration.
When a certain module of the vehicle is offline, it can determine which module has a problem according to the different state of the buzzer of the development board. And perform error positioning.
The number of buzzer beeps is indicated according to the priority of the offline module. For example, the priority of the gimbal motor is higher than that of the load motor. If offline occurs at the same time, the current offline device is indicated as the gimbal motor.
The status of the module offline is as follows. The number corresponds to the number of times the buzzer sounds each time, sorted according to priority:
- right-front chassis motor offline
- left-front chassis motor offline
- left-back chassis motor offline
- right-back chassis motor offline
- gimbal yaw motor offline
- gimbal pitch motor offline
- load motor offline
- single axis gyroscope offline
The red light is always on when The remote control is offline or the referee system or the serial port of the PC is not connected.
- Protocol protocol
Using RM Development Board Type A as main control board, the location of each functional port is as follows：
Chassis Hardware Port
Attention: uwb, single axis gyroscope and CAN2 communication port use the same CAN bus, no need to care about the specific order
Gimbal Hardware Port
support basic control with remote controller
In this mode, Host PC have the full control of chassis, gimbal and shooting system. Full control includes control of these actuators in specific physical units.
remote control (chassis follows gimbal) : right toggle rod goes up remote control (gimbal follows chassis) : right toggle rod goes middle
- turn on/off friction wheel (left toggle rod goes up)
- single/continuous shoot (left toggle rod goes down)
Auto mode when competition (right toggle rod goes down)
left toggle rod position and its corresponding function:
- up: turn on friction wheel,
- mid: turn off friction wheel,
- down: single projectile shooting mode only
- Using free and open-source freertos operating system, consistent with other open-source protocol license
- Using standard CMSIS-RTOS interface, convenient to transfer to other operating system or platform
- Provide a set of abstract infantry robot bsp, simplifying upper logic
Driver：Directly operate the device driver of the underlying hardware. On the basis of library functions and registers, add lock and asynchronous mechanisms to provide an easier to use api.
Device：An external module with one or more bus inputs, one or more data outputs, or a general-purpose software module (drop-off protection). Currently, the driver is abstracted into devices for RM materials.
Controller：Single-input single-output models. Providing some common call interfaces, and changing different control algorithms depends on different registration functions.
Algorithm：Providing module algorithms, no interdependencies between basic files.
Module：A module consisting of a driver, device, controller, and algorithm, which can realize a specific function. For example, a two-axis pan gimbal composed of RM motors and a McNamm wheel chassis.
Utilities：General system components, such as the log system.
Protocol：A set of upper and lower layer communication protocols for oriented-interfaces.
Application：Upper application logic, including various mode switches.
system startup and distinguish the start task through jumper cap of the international Development Board Type A.
- Main control MCU：STM32F427IIHx, Operating frequency: 180MHz
- Module communication method：CAN；CAN devices：motor speed controller, gyroscope module
- upper layer and lower layer communication method: USB Virtual serial port
- McNamm wheel install method：X-type
Protocol data can be divided into two categories according to the direction of communication：
lower layer send to upper layer:
- Feedback information: including feedback information of each sensors, and some feedback information calculated by the bottom layer;
- The underlying state information: including the running state of the underlying device, some response of the underlying layer to the upper layer data, etc.
- Forward data: contains all the information of the referee system, customized information on the server side；
lower layer receive from upper layer:
- Control information: upper layer control information on the bottom three actuators