Thanks, that would be too easy. I‘ll check when back from shoppingthetechnobear wrote: ↑Mon Sep 07, 2020 9:58 amttuitest i think requires the orac image (orac.pbm) to be in the current directory.

Moderators: Kent, luketeaford, Joe.
Thanks, that would be too easy. I‘ll check when back from shoppingthetechnobear wrote: ↑Mon Sep 07, 2020 9:58 amttuitest i think requires the orac image (orac.pbm) to be in the current directory.
just checked.... there is no support for display rotation in ArduiPi_OLED lib
i'll alter the ttuitest to send the last text to the second display. like that i may get proof that the 2nd display is workingthetechnobear wrote: ↑Tue Sep 08, 2020 6:12 amhowever, Im a bit surprised, you didn't get output on both screen, since its the same code...
and Id assume the I2C address is correct, otherwise the ttuitest app would complain it cannot open the 2nd display.
the 1306 and 1106 are not too different, sh1106 has an internal RAM"area" of 132x64. so most of the time changing from one controller to another requires a offset of 2 pixels to draw things at the same position.thetechnobear wrote: ↑Tue Sep 08, 2020 6:37 amits looks like the SSH1306 hardware supports this so should not be that difficult... or it could likely be done in the GFX lib quite easily.
but that would all need testing.
There's also some bytes in the controller init sequence that determine the RAM to screen mapping. One changes the scan direction, the other the mapping so you can flip the screen without changing the drawing code. Similarly you can bake in the 2px offset.
a cool - that would be one(or two) more byte in the init sequence and then problem solved. thx pld
If you've not found it yet, bit 0 of the the segment remap parameter (0xA0) can be used to vertically flip the screen on the ssd1306. 0xA0 maps segment 0 to column 0, 0xA1 maps column 127 to segment 0. I think you currently have the latter configured.
thats not true
I tried bothjmsiener wrote: ↑Sun Sep 13, 2020 11:43 amDid you build it from the fates image? Is this still on your zero based board? I feel like ORAC has to be installed on a modified Norns image to get all the stuff preconfigured so ORAC can run on top.
Meanwhile I got my TT plus OLEDs working with ORAC but when I powered in the other day I got no response... more to debug.
as you say, there is not really a way to do this within orac since there basically the UI doesn't have space to show 6 parameters.haK wrote: ↑Sat Sep 19, 2020 12:49 pm
I have one question though: Is it possible to use the cv inputs 3 and 6 and somehow pipe them straight into a patch?
I have successfully converted some of my patches into ORAC modules however pretty much all of my patches use the 6 cv inputs/knobs and it would be great to have them all at once available/cv-able without having to change pages.
I tried to incorporate the terminal_tedium_adc external into a patch but that didn't work.
I am aware that some of the ORAC routing and oled display wouldn't work as it should anymore, nevertheless I could take advantage of the filesystem and load my old patches without having to reboot and changing SDs.
cheers