Design overview
(→Version 4.1) |
(→Version 4.1) |
||
| Line 66: | Line 66: | ||
[[File:regbot_v4.1_board_300.png]] | [[File:regbot_v4.1_board_300.png]] | ||
| − | Figure 5. PCB layout version 4.1 | + | Figure 5. PCB layout version 4.1. NB! I2C and IMU is different, I2C has 5V on pin 5, this is NC in IMU socket. Other pins are 1: GND, 1:3.3V, 3: SDA, 4: CLK. |
Revision as of 10:33, 25 February 2018
Back to Regot main page.
Contents |
Design overview hardware
Regbot consist of a microprocessor board (teensy 3.1/3.2) that controls 2 motors (Pololu 25D) through a motor driver (MC33926). Motor rotation data is collected from motor encoders. Motor current is avaiable and there is further a gyro-accelerometer sensor (see figure 1 below).
The processor is supplied with 5V from either USB or from a 12V battery or power supply.
A reset button disables the power - and therefore initiates a reboot.
The robot is differential controlled, where a difference in velocity between left and right wheel generates a turn.
The processor is an ARM MK20DX256 processoren (a 32bit 96MHz microprocessor) and is programmed to implement a number of control loops that is able to control some basic movements of the robot (see figure 2).
Figure 1. Hardware blockdiagram. Most blocks are off-the-shelf hardware modules from PJRC (Teensy), Pololu (motor, driver and buck-boost converter) and Sparkfun (IMU). Some of the supported sensors are optional, but all will have gyro to enable balancing and most also wifi to enable monitoring and confuguration without a USB cable.
Other sensors like an line (edge) detector (edge of a tape line on the floor), IR distance sensors (Sharp 2Y0A21 type) and wifi access may be implemented on some of the robots.
Design overview software
The robot software is shown as a block diagram in figure 2 below.
Figure 2. Overview of software data flow. Yellow is control blocks. Green is hardware (motor and sensors), Light green is calculations. Light blue is obtained values. Gray is input values.
Sample time for all controllers and data values are 1ms. All software is written in c++, based on Arduino libraries.
Most controllers can be switched off. I.e. if the velocity controller is switched off, then the reference input is fed directly to the output (in this case the reference input is then in Volts rather than m/s) and the acceleration limiter is bypassed too.
PCB connections revision 2B
Component placement and values (in red) are shown here. Plug connections are shown in blue.
Figure 3. The Sharp IR sensor output is not connected to an AD converter input.
The IR sensor voltage divider output should be between 0 and 1.2V, and could be connected to A0 and A1 (used to be feedback from motor-controller). Unfortunately a plug can not be mounted (space conflict with USB plug).
The orange wires are patches (line sensor low power at pin 32 and from IR sensor to A0 and A1).
Version 3 of the robot uses the same pin-configuration in all plugs (and adds a few more).
Version 4 also uses the same pin-configuration for motor-encoder, IR-sensor, line sensor + LED drive and IMU (IPU) and adds 3-pin servo and io.
Version 4.1
Figure 4. Schematic of version 4.1 with Teensy 3.5 configuration (red board). Open image in full resolution to use.
Figure 5. PCB layout version 4.1. NB! I2C and IMU is different, I2C has 5V on pin 5, this is NC in IMU socket. Other pins are 1: GND, 1:3.3V, 3: SDA, 4: CLK.
