search

satoshinm / oledterm

Mirror your Linux console terminal output to an OLED display module
35 stars 7 forks source link

Unable to access %s #4

Open peterbmckinley opened 3 years ago

peterbmckinley commented 3 years ago

Hi Im keen to use this with my Orange Pi Zero setup. Luma.oled is installed and working, and can display all the luma.examples. I'm using an SSD1306 controller OLED display connected via the i2c bus. When I run the following command from the oledterm directory:

sudo python3 oledterm.py --display ssd1306 --interface i2c --rotate 2

it blows up as follows:

File "oledterm.py", line 55 print "Unable to access %s, try running as root?" % (VIRTUAL_TERMINAL_DEVICE,)

Any clues what might be wrong?

Peter

peterbmckinley commented 3 years ago

Let me know when you get it working after login.

Good luck!

Krizzel87 commented 3 years ago

It Work

I dont have issues

peterbmckinley commented 3 years ago

Can you upload a photo of your oled screen AFTER you log in. As requested before. Mine is fine up to the login screen, but after I log in its unusable.

On Mon, 24 Aug 2020, 00:47 Krizzel87, notifications@github.com wrote:

It Work

I dont have issues

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-678841161, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDKXVXBIO54PTFD4K3TSCGTAJANCNFSM4PADFK5Q .

peterbmckinley commented 3 years ago

fix_oled Also, can I check you changed THIS oledterm.py file and NOT satoshinm's original oledterm.py file? Please confirm

peterbmckinley commented 3 years ago

SH1106

This is SH1106

peterbmckinley commented 3 years ago

It Work now for you? No sh1106 ist not the Same SSD1306 both are oled 1.3 inch. Try to play with arduino to see Differenz. Ssd1306 is better

No. see videos.

By the way 0.91" and 0.96" oled displays are always SSD1306 controller. 1.3" oled display is ALMOST always SH1106 controller. They CAN be SSD1306 controller, but this is very rare.

peterbmckinley commented 3 years ago

So if you upload a video of your display AFTER YOU LOG IN, and its ok, then I know the problem is with Orange Pi Zero and it can't be fixed. So can you please upload a new video, AFTER log in.

Krizzel87 commented 3 years ago

20200824_023314_3.gif

20200824_023314_2.gif

20200824_023314_1.gif

peterbmckinley commented 3 years ago

You are lucky! Good work Krizzel87 👍😁

Any idea why its unstable for me? I can't use it.

Would you consider getting an Orange Pi Zero and fixing it for me? As you know its not possible to make a commercial product from a Raspberry Pi, because the Compute module is too expensive.

Krizzel87 commented 3 years ago

May be the Resolution is wrong.

Oledterm.py try to play with COLS = 24 and ROWS = 7 . I would try 

VIRTUAL_TERMINAL_DEVICE = "/dev/vcsa"
ROWS = 9 
COLS = 31

Or try Other fonts in def main or size. 

    fontname = "tiny.ttf"
    size = 6
peterbmckinley commented 3 years ago

I know the resolution for both the 0.96" SSD1306 and the 1.3" SSH1106 is 128x64, but surely yours is the same?

I haven't changed the defaults.

But I'll try it later today. What settings did you use to make it stable?

On Mon, 24 Aug 2020, 11:39 Krizzel87, notifications@github.com wrote:

May be the Resolution is wrong.

Oledterm.py try to play with COLS = 24 and ROWS = 7 . I would try

VIRTUAL_TERMINAL_DEVICE = "/dev/vcsa" ROWS = 9 COLS = 31

Or try Other fonts in def main

fontname = "tiny.ttf"
size = 6

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-679051367, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDI6HFB2HGMKCC2FJNLSCI7PHANCNFSM4PADFK5Q .

Krizzel87 commented 3 years ago

I prefer tiny.ttf, but the are more cool fonts.i use size 6 to 12. But always have to fit COLS and ROWS .

On your screen it you truely have to much ROWS try 7

peterbmckinley commented 3 years ago

Given that yours works and you are using the same resolution display (128x64), please post your CURRENT values for SIZE, ROWS & COLUMNS

I will match your values and re-test. Hopefully that will fix my problem.

On Mon, 24 Aug 2020, 11:52 Krizzel87, notifications@github.com wrote:

I prefer tiny.ttf, but the are more cool fonts.i use size 6 to 12. But always have to fit COLS and ROWS

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-679056291, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDOWYSBQIB5AAEJVQETSCJA5NANCNFSM4PADFK5Q .

Krizzel87 commented 3 years ago

Maybe your Problem is that the fontscrip doesnt fit to terminal size and thats why it is shifted? Try to typ clear after logged in

And see if it will Happen again. I valve rows 9 cols 31 Font tiny.ttf size 6

peterbmckinley commented 3 years ago

I haven't changed it from the default "Tiny ttf".

If you could post your own settings for size, rows and columns for a working system using the same screen it would be very helpful.

I haven't changed my settings from the default. (size 6, 9 rows and 31 columns I think from memory)

Thanks in advance. Peter

On Mon, 24 Aug 2020, 12:55 Krizzel87, notifications@github.com wrote:

Maybe your Problem is that the fontscrip doesnt fit to terminal size and thats why it is shifted? Try to typ clear after logged in

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-679081819, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDLROQQL7SUWBXYEYLTSCJIKBANCNFSM4PADFK5Q .

Krizzel87 commented 3 years ago

I Gott it to Work like yours. It shiftig away all the time

peterbmckinley commented 3 years ago

You can fix it, I have much confidence in you 😁

Did you use the code from the later commit, that claims to fix this problem? I sent a screenshot

On Mon, 24 Aug 2020, 13:08 Krizzel87, notifications@github.com wrote:

I Gott it to Work like yours. It shiftig away all the time

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-679087708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDJHDQR5XHVZEKPV2DTSCJJ5RANCNFSM4PADFK5Q .

Krizzel87 commented 3 years ago

20200824_142432_1.gif Shifting oled. Connected hdmi to see terminal 20200824_142456.jpg

Fixed oled

20200824_142522_1.gif

Hdmi output 20200824_142616.jpg

Krizzel87 commented 3 years ago

It happend during change virtual Terminal2 with cntl Alt F2 . When i go black to virtual terminal 1 it will work.

Dont know how to change Resolution of Terminals. But how ever the issue is there.

Krizzel87 commented 3 years ago

Log in and typ in Bash stty rows 7 and stty col 24

It will change the size off terminal play around to find best valvues

peterbmckinley commented 3 years ago

Good work. I'll try it later today when I get home.

Peter

On Mon, 24 Aug 2020, 14:02 Krizzel87, notifications@github.com wrote:

Log in and typ in Bash stty rows 7 and stty col 24

It will change the size off terminal play around to find best valvues

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/satoshinm/oledterm/issues/4#issuecomment-679112518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFONLDI73H2YU4MHOBRP5DTSCJQG7ANCNFSM4PADFK5Q .

peterbmckinley commented 3 years ago

Ok I opened T2 with ctrl-alt-F2, but when I went back to T1 (ctrl-alt-F1) the problem is the exactly the same as shown in my videos. 🙄

I know Richard Hull is looking at doing a complete clean-room rebuild of oledterm, with a view to adding to his luma.examples repo. If you can't fix it maybe he can, or maybe you can fix it together.

Check issue #120 on oled.examples Github page.

https://github.com/rm-hull/luma.examples/issues/120#issuecomment-671255581

Hope this helps

peterbmckinley commented 3 years ago

Its good that you're seeing the same issue, so we know it isn't platform specific

peterbmckinley commented 3 years ago

fix_oled Also, can I check you changed THIS oledterm.py file and NOT satoshinm's original oledterm.py file? Please confirm

sorry to be a bore, but can you confirm you modified THIS version of satoshinm's code, and NOT the original?

Satoshinm claims to have fixed our exact problem in this commit. Please advise

Krizzel87 commented 3 years ago

Cool never read it before! i used original oledterm. And than run it my self thrue 2to3 and begann to debug it. Test the code with PI 2 B+ . But the load is too much. So my project is dead. Try to edit refresh time from 0.01 to 0.05 but is cpu load over 70%.

The code works with no Problems.

peterbmckinley commented 3 years ago

Might be worth enabling some virtual RAM by creating additional swap file? In my example 384MB.

dd if=/dev/zero of=/root/myswapfile bs=1M count=384 chmod 600 /root/myswapfile mkswap /root/myswapfile swapon /root/myswapfile nano /etc/fstab and add the line: /root/myswapfile swap swap defaults 0 swapon -s

I had to do that just to install luma.oled, or the process gets killed from lack of memory.