Announcement

Collapse
No announcement yet.

MR Sensors not working correctly on the rev hub

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • MR Sensors not working correctly on the rev hub

    We have had a number of teams contact us because they were having problems getting the Modern Robotics sensors working on the Rev hub. If you are a veteran team and own MR modules, verify that it is not a sensor hardware issue by testing the sensors attached to a Core Device Interface controlled from a Windows computer running Core Device Discovery app (http://modernroboticsinc.com/coredevicediscovery). If the sensors are working correctly then check the wiring to the Rev hub and the code to read the sensor.

    Another solution is to connect the Rev hub and the Core Device Interface to the Core Power Distribution Module. This gives direct access to the MR modules and sensors while still enabling you to control the Rev hub. In almost all cases, this approach solved the sensor issues.

  • #2
    We have been experiencing spikes where the MR Range sensor returns values of 255 then goes back down the the correct value. We are using the REV hub. Is there any way to fix this.

    Comment


    • #3
      Don't know if it's a software problem in this case, but our team has written code in the past where other sensors sometimes give crazy numbers. You can average multiple readings, or throw out impossible unreasonable numbers or both.

      sensor = readSensor
      while(sensor == 255 && count < timeToGiveUp) {
      sensor = readSensor
      count +=1
      if (count == timeToGiveUp) setAnErrorFlag
      }

      Comment


      • #4
        We have lost multiple color sensors when connected to the REV hubs. LED won't turn on, won't return values. I originally thought they had hooked them up backwards but even good sensors have gone bad after working correctly for some time.

        Comment


        • #5
          Originally posted by RollerCoaster45 View Post
          We have been experiencing spikes where the MR Range sensor returns values of 255 then goes back down the the correct value. We are using the REV hub. Is there any way to fix this.
          Yes, just throw away the 255 values.
          Keep a local copy of the last sensor value as a variable, and if you get a reading of 255 from the sensor, don't save it.

          Comment


          • #6
            Originally posted by FTC6180 View Post
            We have lost multiple color sensors when connected to the REV hubs. LED won't turn on, won't return values. I originally thought they had hooked them up backwards but even good sensors have gone bad after working correctly for some time.
            We would very much like to get back one or more of the sensors that has failed when connected to the rev hub so we can diagnose what may have gone wrong. Could you please contact support@modernroboticsinc.com or call support at (786) 393-6886.

            Comment


            • #7
              perhaps a different problem, but we found that the MR range sensors are broadcasting all the time. We have multiples on our robot. They interfere with each other. We turn one on at a time (manually) and have had no problems since then. We saw a lot of 255, and zero, that then would creep up to reality. Once we only ran one at a time, no problems.

              Comment


              • #8
                How do you turn off a sensor FTC9112 ? If we needed multiple during auto we wouldn't be able to unplug and replug them in.

                Comment


                • #9
                  correct. We only needed one or the other, depending on which alliance we were on. We could find no way to do so with code.

                  Comment

                  Working...
                  X