Please, another small question.
I see in the Oled expansion schematic (https://github.com/OnionIoT/Onion-Hardware/blob/master/Schematics/Omega-OLED-Expansion.pdf)
that the SCL and SDA lines are not directly connected between Omega2 module and display, but there are two mosfets.
What is the need of two additional components?
There are another type of display that I can connect to Omega2 and that are already supported with software?
Or, If connect to Omega a LCD I2C display with UC1601S controller, is easy for my "informatic colleague" to write code to control it?
What type of controller is inside the Onion Oled expansion module?
Thanks to all.
This project is continuation of Onion music server project of mine. Main motivation is improve sound quality and get rid of some Onion wierd issues that i have no skills nor time to solve. Project unique is i2s connection application for OrangePi Zero board that have no I2S soldered out by vendor.
Was really in a crunch on this one and needed to get it working, so I ditched OnionOS all together in favor of vanilla OpenWRT 18.06.5
I followed the first two steps here https://yoursunny.com/t/2019/omega2pro-openwrt/
I removed the -F from the command as it is not needed in my situation. I then had to locate and specify the correct file path.
Within minutes, OpenWRT was running flawlessly on the Omega2+
I connected to my home network Wifi AP and disabled the Omega2+'s access point by selecting "replace current wireless etc etc"
I then followed instructions here https://www.circuidipity.com/openwrt-bridged-repeater/ for bridging the wifi through ethernet which worked flawlessly upon the reboot.
I now have the BeagleBone Black (powered via 5v adapter) connected to a USB hub, which powers the Omega2+ as well as connects the Beaglebone to the webcam and 3D printer.
Test print is running now to see if the timelapse renders, which was the issue with running Octoprint on the Omega2+ directly; the timelapse would be captured and visible in unrendered timelapses but would crash the Octoprint server at any attempt to render.
The other motivation for switching was to get away from the baud rate limit on the Omega2+ which required me to run custom firmware on my TAZ6 as default firmware all runs 250k baudrate due to performance issues with 115.2k.
Hopefully this helps someone else in a similar scenario.
tl;dr for Onion developers: Your documentation is inaccurate and/or out of date. Had I been able to use the Onion Omega2+ as a Wifi to Ethernet bridge as described by your documentation I would not have had to ditch OnionOS/firmware entirely.
Please update your documentation so that a person could, if desired, use the Onion Omega2+ as described, out of box.
After working around the shortcomings of the device & documentation, I am pleased with the performance of the hardware using plain OpenWRT 18.06.5
Thanks @luz you give me a lot to think about. I am using Omega2S+ and my custom board doesn't have an ethernet port. Due to my form factor I don't want to add an ethernet connection but I was considering adding a non-standard plug and make some custom tails so i can plug a temporary RJ45. Thanks for the tip on the ipv6.
@Modest-Polykarpovich not my own, but I'm still trying to improve existin driver, here my post, I add some of my fixes, It works better with them, but not perfect with rates higher than 96kHz, I really wanna play bit-perfect 192/24 on i2s Omega2
Another scenario is if I boot the Omega2 up with the battery attached and using USB power and then disconnect the USB power, the Omega2 continues to operate. But... if I re-attach USB power again, the Omega2 dies (and the orange LED goes off and the AP stops to work). Power LED is still on and if I have anything presented on the attached OLED expansion, it still shows even if the Omega2 is not working so the hardware stack has power coming into it.
Fairly common problem I've seen. What I do to overcome it is use a really good power supply (>=2A) and a short USB cable with thick gauge cable.
Typically I see it when powering the device via USB with battery attached and then there's a power failure. The device continues to run on battery, but as soon as the power returns, it dies. Solution = short, thick gauge USB power cable.
tried 115200 8n1 to serial console on usbc port . it is detected as a cp2104 usb to uart bridge with serial app i use to program network switches .
video of unit with flashing lte and faintly flashing power led . no other lights . tried several cables and plugging into macbook . also tried usb power adapter . it is drawing some power , but no wifi or console output . video of board