No announcement yet.

Inverted Camera!

  • Filter
  • Time
  • Show
Clear All
new posts

  • Inverted Camera!

    We use the phone camera to view the elements in autonomous. We have the phone mounted near the top of the robot at a 45 degree angle. Our autonomous program adjusts the position of the robot in order to view the two elements on the right (in the rare instance some slippage occurs and it is slightly out of position). This has worked very consistently.

    However, at the end of the day on Saturday, we were running the autonomous program and it stopped at the point of reading the elements. This particular challenge had not happened in our dozens and dozens of runs. Looking closer, the app is oriented correctly. However, the camera picture is upside down. To prevent reading elements in the crater, we have it programmed to read the lowest elements on the screen. Since the proper elements are now at the top of the screen, it is unable to read them so the program stops right there.

    Our programmer has some ideas for work-arounds that he will be trying this evening. However, time is limited with our league championship coming up Saturday. So, I thought I would pick your brains to see if this error has occurred for any of you. I have a few questions.

    1. What would cause the picture to invert? We are concerned that if it happened seemingly randomly one time, will it happen again in a competition? Without knowing the cause, it is difficult to analyze a solution to prevent it from happening in the future. We had just made one successful run. The programmer put in a couple of tweaks for a slight angle adjustment and one small distance adjustment. Then, this happened. So, what could have possibly caused it?

    2. Is there an easy fix to correct the orientation of the camera? It looks to me from searching over the weekend, that it is related to the mirroring function. I'm not familiar with that and the phones were at the school over the weekend, so we couldn't work on a fix.

    3. Has this occurred for any of you? If so, what did you do to prevent it from occurring again?

    Thanks for any input!

  • #2
    Our programmer was able to tweak the program and run with it. We still don't know what caused it, but we have a fix for it in case it happens again.