Embedded Motion Control 2017 Group 3 / Initial Design
This page is a part of the Embedded Motion Control Group 3 of 2017.
There are 2 main goals for PICO (robot).
- Corridor competition: To navigate through a corridor and take the first exit (that can be either right or left side of PICO) without colliding with the walls.
- Maze competition: To solve an unknown maze within given time limit, which has doors to be opened and exit the maze without touching any walls.
The overall Initial design of the project is mentioned in the following section:
The following requirements are listed for the robot (PICO) to complete maze successfully:
- PICO should not touch the walls or any other obstacles in the maze at any time instant.
- PICO must operate fully autonomous (i.e. without input from the team).
- PICO should not be idle for more than 3 seconds from the start of program unless it has passed the exit.
- PICO must be able to detect available space using the Laser Range Finder (LRF) and move to the detected space according to the path finding algorithm (this plans the motion).
- PICO must be able to find the exit within the provided time (≤ 7 sec for maze and ≤ 5 sec for corridor).
- PICO must be able to detect the objects (dead ends) that have a high probability of being a door.
- PICO must be able to open the door in the maze and pass through it.
In Initial design, there are 6 functions which has a 'Main Loop' and other separate modules which are called as 'supervisors'. Each supervisor is unaware of what is there inside the other supervisor and there are communicated only through interfaces. This approach is to make software architecture simpler, editing easier and error counts lesser. The reason for concept of independent supervisors came when we thought how PICO will be working if its a human. Each part is independent, has its own features and they have to communicate in order to run whole system peroperly. We used nominal number of supervisors (5), considering number of special skills PICO has to do. Also, the number of members in our team to code in each supervisor. All the functions are listed below:
- Main Loop
- Path-finding Supervisor
- Door Handling Supervisor
- Wall Detection
- Motion Supervisor
- Actuator Supervisor
Main loop is where
- IO layer is initialized.
- Rate of loop is set.
- every functions is initiated, arranged and called.
- Communication structs are initialized and interacted to different supervisors.
- Relevant initial movements are provided.
Path-finding supervisor is the brain of PICO. It make relevant decision for motion throughout PICO's travel. We chose Pledge Algorithm over all other existing maze solving algorithm like Random mouse, shortest path etc. because the maze is unknown before challenge. Hence, the algorithms that calculates optimal path before challenge wont work easier here. Also, there is a time limit of 7 min to solving maze. If we used some algorithm like Random mouse, it will solve the maze optimally after one full trip through maze which is not possible due time limit. Pledge algorithm works well in the context of an unknown maze with any shape of obstacles in it. The cornering concept came when we decided to code for the corridor challenge in simplest way and then the higher level of junction decision codes can be built over it.
This algorithm is mainly used in Maze challenge to solve the loop structures inside the maze. When an obstacle like loops are present, PICO continue the wall of obstacle until the sum of turns it took become zero. When the rurn counter sum is equal to zero, Pledge algorithm directs PICO to another path which make it to detach from the loop. The input to this function is the wall information which includes front, left and right side space information. Using the inputs, the algorithm sets a motion goals and then PICO moves to achieve those.
Cornering concept is introduced mainly for Corridor challenge. If space in right or left side is detected, this function instruct for a turn by changing bool turn_corner to true and wait until the motion supervisor is finished turning to set back the turn_corner to false.
As it was mentioned in the maze challenge that the door is situated at a dead end and the door will be fully opened within 5 sec from PICO request, we used Door supervisor specifically react to this part of challenge.
If detected dead-ends, actuate the bell by <io.sendOpendoorRequest()> and activates rest of relevant algorithms of door-handling.
Wait for 5 sec at every dead-ends. The times is counted using loop counter which resets to zero when left from dead-ends. If there is no change in front distance after 5 sec, the motion algorithm is continued.
The opening of door is detected by the change in the front distance. Once the door is opened fully, PICO uses motion algorithm to move through open door path.
Wall / Path Detection
1-Read LRF data:
Obtain raw data from the LRF sensor
2-Filter LRF data:
Reduces noise from raw LRF data and splits it into 3 directions (left, right and front).
Calculate one distance approximation for the 3 directions by finding mean of distance in particular direction.
Calculate for all directions if space is there to move in that direction by checking if the distance is more than the threshold given.
The relevant data like distances, angles etc are set for communication.
Whether it is corridor challenge or maze challenge, the attempt is failed if PICO hits the wall. In order to manage PICO without hitting walls, a good motion control over it is required and this made us to put code for avoid collision in motion supervisor. Apart from that, to solve both challenges, the motion skill of 'turning up to required angle' is also required. Hence, motion supervisor takes care all motion related tasks that PICO may require. It activates the actuator supervisor according to different situations.
In order to avoid bumping into walls, PICO keeps a safety margin from the wall and align to the center of the corridor by calculating center point using the distance to the left and right. Alignment is done along with forward speed.
When algorithm for turning at corner is activated, there will be only angular velocity send to <io.sendBaseReference>. ie, velocity in X and Y direction will be Zero until the turning at corner is finished. PICO will be taking a 90 degree turn either on left or on right.
This supervisor is like a servant of 'motion supervisor'. All it will receive is numerical data (velocities) to move the motion components on PICO. The idea of making an actuator supervisor came when we want to call the actuator supervisor only once in a loop and to avoid writing <io.SendbaseReference> at every situation of motion.
1-Steady PICO: Keep the front of the PICO aligned to the direction of movement.
2-Omni-wheels handling: Set speed and angle of Omni-wheels according to received data.
The interfaces are defined as the movement/flow of data between the functions that are defined in above section. The different interfaces Data types are described below.
- The information about the space in front, right and left are used in the form of 'Struct of Boolean'.
- The left, right and front distances are 'Struct of floats'.
- To turn left 'integer' value 1 is used while to turn right 'integer' value 2 is used.
- To indicate finishing turn, 'Boolean' is used.
- If a dead-end is detect, the door handling algorithm is activated using 'Boolean'.
- Confirmation of finishing door handling is by using 'Boolean'.
- Setting different velocity values for actuator using 'struct of floats'.
1- Sensors: Laser Range Finder (LRF), Odometry (Wheel Encoder).
2- Holonomic base (omni-wheels): Maximum translational speed of 0.5 m/s , Max angular speed of 1.2 rad/s.
3- Embedded platform Computer with Ubuntu 14.04 on an Intel i7 (other specifications are unknown)
4- Bell: To produce sound from PICO so as to open the door.
The initial design document File:Emc-design-specification.pdf briefly indicates the approach taken towards the problem of solving the maze by the PICO robot, the algorithm used and the system design.
The slides for the initial design presentation can be found here: File:Group3 2017 Initial design presentation.pdf