Announcement

Collapse

Technology Forum Has Moved!

The FIRST Tech Challenge Technology forum has moved to a new location! Please take a look at our forum blog for links and instructions on how to access the new forum.

The official blog of the FIRST Tech Challenge - a STEM robotics programs for students grades 7-12.


Note that volunteers (except for FTA/WTA/CSA will still access their role specific forum through this site. The blog also outlines how to access the volunteer forums.
See more
See less

Odd problem with Core Device Interface (seems to impact both Color Sensor and ODS)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    As somebody who's been lurking on this and the related threads I just wanted to say "thank you!" to all you folks with the skills and wills to investigate and post this stuff. While I may understand what you guys are posting, and could thus steer the kids from trouble, I really lack the time and java skills to have done this kind of investigation on my own. Your efforts kept my kids, and surely countless other teams, out of the weeds. Understanding the current system's limitations really helped me ensure my kids had a positive experience this season so far. Even while using an MR range finder, gyro & integrated heading, and color sensor all at once.

    Comment


    • #62
      Originally posted by gof View Post
      what about improvements in Analog (or Digital) when an I2C is present? If there were a short term fix to allow full speed (or at least a lot better) performance while the I2C continues to be tuned that would be wonderful as well.
      I have a feeling the I2C improvement will also improve Analog performance. Regarding short term fixes on the ODS, did you try "unregistering I2C devices" when using the ODS and re-registering them afterwards? We are using the ODS to detect line while the I2C bus has 2 sensors on it (color, range). It's working fine detecting the line even without the "short term fix".

      Comment


      • #63
        It looks like the solution is now being implemented. I'd suggest closing this thread and continuing over here:


        I know the ODS is mentioned as still unknown, but it's more than likely that this is going to be the solution thread. Thanks to everyone who added more data to this thread to prompt the investigation by the core team (and to the core team for taking it on mid-season).
        Technical Coach, Newton Busters FTC 10138, FLL 3077
        Chicago 'burbs, IL

        Comment


        • #64
          Originally posted by gof View Post
          It looks like the solution is now being implemented. I'd suggest closing this thread and continuing over here:
          http://ftcforum.usfirst.org/showthre...nt-team-update
          You are the original author of the thread. You can close the thread. At the top under the thread title on the right hand side, you see an "administrative" drop down which gives you the option of closing the thread.

          Comment


          • #65
            Ok, Done! (needed more characters)
            Technical Coach, Newton Busters FTC 10138, FLL 3077
            Chicago 'burbs, IL

            Comment

            Working...
            X
            😀
            🥰
            🤢
            😎
            😡
            👍
            👎