We are shipping rev 5.2 boards with the OLED display on the boards starting with our next production run in progress at this time. Rev 5.1 boards had the correct socket so can be used as discussed in earlier post or on our github (link in next paragraph)
The display node had to be renamed and is not part of the image yet but we hope to do that very soon. It is on our github now located here with a readme to help use it now.
A couple months back I added the I2C info and more from prior post on this thread. It is on learn pages so that may be handy for those wishing to use I2C. https://learn.ubiquityrobotics.com/diagnostics
Some people on this thread also asked about GPIO. A page that tries to explain all the GPIO we use and how to use some of the lines if your application needs them now exists. That is here https://learn.ubiquityrobotics.com/doing_more/GPIO_lines.html
Ok, hope that brings this up to date. Let us know other things that you want to see in terms of the learn pages that would help so our docs can improve.
We are actively working on two OLED related things. One is we will show battery voltage on the OLED soon!
Next there seems to be an all too common issue with some displays don’t properly initialize. This one is stumping me so if anybody figures this out we would greatly love to benefit from suggested code changes. I have it a bit better but it can still fail. Devil is in the details as always in tech.
We have pushed a more completed set of initialization parameters to the OLED display and also have a battery voltage now showing up if the ROS system has a /battery_state topic like our robot has.
While looking at this I also ran across one display that came up in an odd state even on my tried and true test rig for these displays. So I now will have to watch for quality control on these displays and get a test going in production so at least at the factory we have validated the display is good. We do not have an image that supports the display yet so we must have that then implement the production test.