Group Actions
Engagement
  • Author Author: dubbie
  • Date Created: Date Created
  • Views 2201 views
  • Likes 10 likes
  • Comments 7 comments
Related
Recommended

ARBot #2 : Connecting the Angle Sensor to the Servo Motor

dubbie
image

Electronic Toys

Enter Your Electronics & Design Project for a chance to win a Grand Prize of a SNES Classic and $200 Shopping Cart of Product!

Back to The Project14 homepage image

Project14 Home
Monthly Themes
Monthly Theme Poll

 

The next step in my augmented reality for the Project14 electronic toy challenge, after checking that I do seem to be able to display the Pixy cam processed image onto a display, is to create a headset that will detect rotation and tilt and transfer that information to the servo motors controlling the pan and tilt of the Pixycam.

 

To confirm that all the parts seem to be working and to obtain some feel for the way the system will operate I have just used one output from the rotation sensor connected to one servo motor. The sensor I am using is a BN0055 IMU from Adafruit and to start with I am only using the X rotation angle which varies between 0 and 360 degrees. The particular servo motor I am using rotates in the opposite direction to the value provided by the sensor so I have just subtracted the sensor value from 360 to create an angle that matches the servo motor direction. Also, the servo motor will only rotation 0 to 180 degrees so for a quick fix I have just limited the value sent to the servo motor to 180 degrees if the sensor rotation angle is greater than 180 degrees. This does create a problem in that the sensor produces angles continuously where 0 is adjacent to 360 degrees and is a modulo 360 value. This means the servo suddenly changes from 180 degrees to 0 degrees when rotating past 360 degrees. I'll have to think how best to fix that problem.

 

I have used the example program provided by Adafruit for their sensor so there is nothing much special about it. I have listed the statements converting sensor angle to servo angle below.

 

while (1)
  {
    imu::Vector<3> euler = bno.getVector(Adafruit_BNO055::VECTOR_EULER);

  /* Display the floating point data */
    Serial.print("X: ");
    Serial.print(euler.x());
    servo_angle = 360 - euler.x();
    Serial.print(" Servo: ");
    Serial.print(servo_angle);
    Serial.print(" Y: ");
    Serial.print(euler.y());
    Serial.print(" Z: ");
    Serial.println(euler.z());
//    Serial.print("\t\t");

    if (servo_angle > 180) servo_angle = 180;
    scan_servo.write(servo_angle);

 

I will need to calibrate the servo motor as currently it only rotates between 20 and 122 degrees in order to avoid entangling with bits of the mobile robot chassis. As I will have to make a better two axis servo motor mechanism at some point I didn't bother messing about with it currently.

 

Below is a video showing this first stage of testing which I hope the system working mostly. There does seem to be some problem with the calibration of the BN0055 sensor as the angle does seem to change for some reason I have not yet identified. I will have to do some more tests on it.

 

 

 

Dubbie

  • Your demo was kind of moving for me.image Keep up the great blogging. I am enjoying this a lot.

    Clem

  • in reply to dubbie

    Hi Dubbie,

    You might want to try putting some paper cylinders around the ultrasonic sensor.

    That will narrow its field of view so you only get reflection back from what is specifically in front of it.

    Since you are scanning anyway, it should improve your detection performance.

     

    DAB

  • in reply to DAB

    I'm mostly going with the try and see approach. I have done some measurements and these indicate that the yellow Lego man is probably only detectable within a maximum distance of about 60 - 70 cm, so not a great range. This makes the angles on the camera much larger and therefore much simpler to implement. What I am not sure about is the lag between the camera and the headset, as well as jitter in the servo movements. I have thought of implementing a smoothed acceleration/deacceleration element into the control of the servo motors (it's something like arcsine or asine or splines or something, using a lookup table.) I have done this before and it does produce really smooth servo motor movements, but it will be if time permits. I would rather have a jittery, unreliable but complete sort-of-working system than superior sub-systems not fully integrated together.

     

    Dubbie

  • in reply to genebren

    Gene,

     

    I did think of trying to combine the two types of control (camera positioning and mobile robot control) into the AR headset, but it just seemed a step too far, so I'm sticking to just controlling the camera. Thinking some more about this this morning, I might even not have time to implement control of the mobile robot and I might have to make it follow a pre-planned path, probably a straight line through the environment, as there is much to do and little time to do it in. A bit like work, but different, as being retired, if I don't want to do, I just go outside and sit in the sun, because there's always tomorrow.

     

    Dubbie

  • This is a great demonstration of the movement Dubbie. Really looking forward to see how you get on with the rest of the build.

     

    Kind regards.