@Patrick-Rainsberry This is pretty well what I expected except for the usage of GPIO 11 which surprises me
I have access to the circuit diagrams for the Omega1 and Expansion Dock and OLED Expansion
On these, what is marked as GPIO 11 on the pin out diagrams referenced above is used for VDD25 (i.e. 2.5Volt supply) and is used on the OLED Expansion to supply power to level shifters between the I2C signals from the Omega and the OLED display chip.
I am unable to find schematics for the Omega2 (hint to Onion devs: can we have ALL schematics for the Omega2 and related boards please :-) ) so can't tell whether this has been repurposed for the Omega2 etc. or whether the pin out diagrams for the Omega2 etc in the Omega2 docs referenced above are wrong in this respect
@jorgegarciadev i will try a fresh install with a new Omega2 image using only python3 and pyOmegaExpansion with --nodeps option. In the meantime i solved the problem temporarily by calling the bash skript with the subprocess module. this works suprisingly well.
I've tried both command line and web based but Oled is not displaying anything.
I have an Omega2+ with Firmware 0.1.10 b160
I have tried the following but with no success ...
oled-exp power on
oled-exp write "hello"
Also, 'opkg list | grep oled' shows that Oled driver is installed.
@MultiDJRoni While the display you reference (http://ebay.eu/2brESNp or http://ebay.eu/2bYf3pA) communicates via I2C and is potentially controllable from the Omega, I don't know whether or not the chip/display it uses is the same as or compatible with that used in the OLED expansion. If it is not, you may be up for additional coding work to control it from the Omega (not a totally trivial task).
I still think you would be better of using a Prototype Expansion (http://www.robotshop.com/en/proto-expansion-for-onion-omega.html) between your Expansion Dock and OLED Expansion and wiring the Prototype Expansion to provide access to the I2C lines (GPIO 20, GPIO 21, 5v, Gnd) and other pins you need for access to your other devices.