After mega-20180426-normal sending TEXT tro OLED don't work

Moderators: Voyager, BertB, rtenklooster, Stuntteam, grovkillen, TD-er

Post Reply
Message
Author
User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

After mega-20180426-normal sending TEXT tro OLED don't work

#1 Post by M*I*B » 14 Jun 2018, 22:31

Hello there again,

I use it also with the small OLED SSD1306. Controller is FHEM and I'm sending TXT and rtttl from FHEM to the OLED.

Today I have try the last ESP_Easy_mega-20180614_normal_ESP8266_4096 and see that rttti work well and also the 2nd two lines defined in EE, but sending TXT don't work; no errormessages or anything else.
I step down to ESP_Easy_mega-20180524_normal_ESP8266_4096 with the same result
I step down to ESP_Easy_mega-20180426_normal_ESP8266_4096 and all work fine
I step down to ESP_Easy_mega-20180316_normal_ESP8266_4096 and all work fine
I step up to ESP_Easy_mega-20180426_normal_ESP8266_4096 and all work fine
I step up to ESP_Easy_mega-20180524_normal_ESP8266_4096 and I can't sending TXT again

Sometime between the two versions from the 26th of April to the 24th of May I must have crept in a BUG.

Or has something changed meanwhile what I have not noticed yet?
DLzG
Micha

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#2 Post by M*I*B » 14 Jun 2018, 22:50

20180504 work well
20180511 work well
20180515 work well
20180522 work well
20180524 don't work
...
20180606 don't work

The error must have crept in from version 0522 to version 0524
DLzG
Micha

TD-er
Normal user
Posts: 1127
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#3 Post by TD-er » 14 Jun 2018, 23:57

Please post the exact command you try to send and to what plugin version (there are 2 OLED plugins)

You mention 20180522 - 0524.
Then I know what commit is was.
There were several bug reports related to it and I applied already a quick fix for it, but apparently there is some other that's still not working.

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#4 Post by M*I*B » 15 Jun 2018, 10:42

... the complete FHEM like commandstructure is this:

Code: Select all

define set_oled DOIF ([HWBR] eq "on" and [HWi1] ne "on" and [HWi2] ne "on" and [HWi3] ne "on") (set WM_08 oled 4 1 BR: . Vorwaermen)(set WM_08 rtttl 16:d=10 o=6 b=180 c) \
	DOELSEIF ([HWBR] eq "on" and [HWi1] eq "on" and [HWi2] ne "on" and [HWi3] ne "on") (set WM_08 oled 4 1 BR: Normal-Betrieb)(set WM_08 rtttl 16:d=10 o=6 b=180 e g) \
	DOELSEIF ([HWi2] eq "on") (set WM_08 oled 4 1 BR: ! STOERUNG !)(set WM_08 rtttl 16:d=10 o=6 b=180 c e g e c e g e c e g e c e g e c e g e c e g e c) \
	DOELSEIF ([HWi3] eq "on") (set WM_08 oled 4 1 BR: ! OVERTEMP !)(set WM_08 rtttl 16:d=10 o=6 b=180 c e g e c e g e c e g e c e g e c e g e c e g e c) \
	DOELSEIF ([HWBR] ne "on") (set WM_08 oled 4 1 BR: . STAND BY . )(set WM_08 rtttl 16:d=10 o=6 b=180 g c) \
	DOELSEIF ([HWHP] eq "on") (set WM_08 oled 5 1 UP: . RUN  67.0^C)(set WM_08 rtttl 16:d=10 o=6 b=180 c g) \
	DOELSEIF ([HWHP] ne "on") (set WM_08 oled 5 1 UP: . OFF  52.7^C)(set WM_08 rtttl 16:d=10 o=6 b=180 g c) \
	DOELSEIF ([HWWP] eq "on") (set WM_08 oled 6 1 LP: . RUN  63.2^C)(set WM_08 rtttl 16:d=10 o=6 b=180 c g) \
	DOELSEIF ([HWWP] ne "on") (set WM_08 oled 6 1 LP: . OFF  52.7^C)(set WM_08 rtttl 16:d=10 o=6 b=180 g c) \
	DOELSEIF ([HWZP] eq "on") (set WM_08 oled 7 1 ZP: . RUN  52.7^C)(set WM_08 rtttl 16:d=10 o=6 b=180 c g) \
	DOELSEIF ([HWZP] ne "on") (set WM_08 oled 7 1 ZP: . OFF  52.7^C)(set WM_08 rtttl 16:d=10 o=6 b=180 g c) \
	DOELSEIF ([HM4SW2_4] eq "on")(set WM_08 oled 8 1 GP: . RUN . )(set WM_08 rtttl 16:d=16 o=4 b=120 g c g) \
	DOELSEIF ([HM4SW2_4] eq "off")(set WM_08 oled 8 1 GP: . OFF	. )(set WM_08 rtttl 16:d=16 o=4 b=120 c g c)
attr set_oled do always
... including 0524 and up command like "set WM_08 rtttl 16:d=10 o=6 b=180 c e g e c e g e c e g e c e g e c e g e c e g e c" work well, command for writing text like "set WM_08 oled 4 1 BR: ! STOERUNG !" don't do anything

I belive you mean what I have declare as Device in ESPEasy? That's the whole time "Display - OLED SSD1306" for the cheap I²C China-Trash...


Hint: If you plan to use the china-display 24/7 it's better to order a hand full of them and make it plugable. After arround 4 months the luminace is down to 50% and I belive after lates a year the display is for the trash...

EDIT say by the way:
What I'm missing with that is an option to send a ETX (end of text, ASCII 0003) and/or FF (form feed, ASCII 0012) that clear the rest of the line (ETX) or clear the rest of the line and jump to the next one. The Problem is that you have to send a SPACE for every sign or fill the line with a sign like a dot tro delete the unwanted rest of the line. Also a problem is that (sending from FHEM) more as one SPACE are ignored; this way to clean to EOL don't work...
DLzG
Micha

TD-er
Normal user
Posts: 1127
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#5 Post by TD-er » 15 Jun 2018, 20:55

About the OLEDs... I added some dimmer function to the OLED Framed plugin just to save the lifetime of those OLED pixels.
Those organic LEDs already have a limited lifetime and setting them to full brightness is shorting that even more.
And I have lots of them laying around. Even among those cheap Chinese clones there is some variation in cheapness.
Some don't allow to be set below some dimming threshold while others can. (or they start making noise)

About the command.
So the command you're giving to ESPeasy is something like "oled 4 1 BR: ! STOERUNG !"

And about that other feature. Would it be helpful to add a clear display command, although it may lead to some flickering.

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#6 Post by M*I*B » 15 Jun 2018, 21:53

So the command you're giving to ESPeasy is something like "oled 4 1 BR: ! STOERUNG !"
Jepp, that's right. The stuff before is simple the Device in FHEM that you have to adress (name can be as you like)

I believe that a full clear is not a good idea. Bot about the bad idea later...

A command that clear the rest of a line will be much more helpfull. I.e. let us say that ASCII 0003 (ETX) will delete the rest of the line. And also let us say that the 1st textmessage sending is ...

Code: Select all

oled 4 1 Some Text here
That will generate in line 4 the Text "Some Text here"
If you now send a shorter text similar the 1st one like ...

Code: Select all

oled 4 1 Thats it
... you get "Thats itt here" as result. Not nice, right?
So if you can sent the ETX like ...

Code: Select all

oled 4 1 Thats it{ETX}
... so ETX (as example) delete or override the rest of the line with spaces...

Full clear Idea...
If you clear the full display you also have to write all (!) information again. That will be a monster construct in FHEM :cry: Problem is that you must catch every event that can create a new text (i.e. a temperature) and trigger all other events parallel and also you must write static information also... Simply you must write the whole display again from top to botton. This is also mucht traffic and recources if you have to do that every second...

Just some words to my construct line by line and translated:
Line 1: Date and Time with seconds (display refresh = 1sec)
Line 2: IP Adress and RSSI
Line 3: empty
Line 4: Status of oilburner (BR, Centralheating). Can be "Stand by", "Preheat nozzle", "Burning", "Fault" and "Overtemp boiler" (what also creat an alarm, emergency shutdown, email and WhatsApp message)
Line 5: Status of circulating pump (WP). Can be "OFF" or "RUN", followed by the temp of the forerun, that can be change every second
Line 6: Status of loading pump (LP) for warm water. Can be "OFF" or "RUN", followed by the temp of the warmers, that can be change every second
Line 7: Status of circulating pump (ZP) for warm water. Can be "OFF" or "RUN", followed by the temp of the temp on pin spot, that can be change every second
Line 8: Status of gardening groundwater pump (GP). Can be "OFF" or "RUN", followed by the pressure of the sytem, that can be change every second
DLzG
Micha

TD-er
Normal user
Posts: 1127
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#7 Post by TD-er » 15 Jun 2018, 23:12

OK Point taken :)
I will add an issue for it on Github.

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#8 Post by danmero » 16 Jun 2018, 12:04

If you don't want to clear the display and reconstruct from FHEM, why not use event to clean the line.

Code: Select all

on CL do
  oled,%eventvalue%,1, 
endon
and from here you call event using the line value

Code: Select all

event,CL=4
That will clean the line 4

Regards,

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#9 Post by M*I*B » 16 Jun 2018, 12:48

.... äääääähhhh ...
Sorry, I have no Idea how it works.

The on...endon comes into RULES as a new Rules set??? And "event,CL=4" comes where? As a command sending from FHEM? :cry:
DLzG
Micha

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#10 Post by danmero » 16 Jun 2018, 14:50

This will be a new event on rules(first rules set or next)

Code: Select all

on CL do
  oled,%eventvalue%,1, 
endon
now from your previous post

Code: Select all

DOELSEIF ([HWBR] ne "on") (set WM_08 oled 4 1 BR: . STAND BY . )(set WM_08 rtttl 16:d=10 o=6 b=180 g c) \
you call on device WM_08 the function OLED to write on ROW 4 & COL 1 the text "BR: . STAND BY ." (correct me if I'm wrong).

Code: Select all

(set WM_08 oled 4 1 BR: . STAND BY .)
base on this assumption you can try

Code: Select all

(set WM_08 event CL=4)
if works as expected should clear the ROW 4

Please let me know if the solution works for you.

Regards,

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#11 Post by M*I*B » 16 Jun 2018, 15:26

.... ahhh! Got it :D

I will check that out in the evening and will report asap.

Thx a lot!
DLzG
Micha

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#12 Post by M*I*B » 16 Jun 2018, 22:37

... half and half ...

I have enter part one as new rule and send "set WM_08 event CL=4" from FHEM...
It clears the first 2/3 of the line and leave the rest of it untouched

I.E.: From ...

BR: . STAND BY .

stay after command ...

BY .

So I can say that the base are right but only clear 12 signs from start
DLzG
Micha

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#13 Post by danmero » 16 Jun 2018, 23:03

What is the "Display Size" on OLED SSD1306 configuration?

Regards,

Edit: we are talking on two different versions , upgrade to the latest nightly built

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#14 Post by M*I*B » 16 Jun 2018, 23:24

... nope, not possible! After 20180522 there is a BUG so that I can't send nothing. See also the Topic and the first messages here ...
DLzG
Micha

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#15 Post by danmero » 16 Jun 2018, 23:32

I test on 20180606

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#16 Post by M*I*B » 16 Jun 2018, 23:38

... don't work with FHEM. The BUG slime in at 0524 and is present in all versions from 0524 till today ...
DLzG
Micha

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#17 Post by danmero » 17 Jun 2018, 00:29

What you see as a bug, other see as improvement.
Maybe you can adapt/adjust from here.

Regards,

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#18 Post by M*I*B » 17 Jun 2018, 00:35

hu? If I can't send Text is a improvement? Sorry, can't follow that ...
DLzG
Micha

danmero
Normal user
Posts: 64
Joined: 11 May 2017, 01:19

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#19 Post by danmero » 17 Jun 2018, 01:26

You did send the text(fact) however not in the new format as per changes.
I will take a look at plugin code and try to spot the changes.

Regards,

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#20 Post by M*I*B » 17 Jun 2018, 11:07

... ahhh! I haven't read anything about a new format :shock:
I also have ask for that in my 1st post of this topic with no hint- response:
Or has something changed meanwhile what I have not noticed yet?
Folks like me are not able to understand the code of a modul and certainly not able to read out any changes ...

EDIT say:
What I do not understand is why such changes are nowhere documented? The developer/s of the module/s must know what the new format should look like ?!
DLzG
Micha

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#21 Post by M*I*B » 20 Jun 2018, 20:00

... any news maybe about the changed parameter?
DLzG
Micha

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#22 Post by M*I*B » 09 Jul 2018, 08:29

:? PUSH :?
DLzG
Micha

User avatar
budman1758
Normal user
Posts: 192
Joined: 15 Apr 2017, 05:13
Location: Riverside CA USA

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#23 Post by budman1758 » 10 Jul 2018, 19:17

I too would li8ke to know what the commands to write to the display have changed to. If it has changed it would be nice to know the differences are. :?: :?: :?:
"The glass is twice as big as it needs to be".

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#24 Post by M*I*B » 30 Sep 2018, 20:32

... looks as if no more sow cares, just like to the matter with the BME280 (viewtopic.php?p=28956#p28956) ...
That's a pity. I think the system is pretty good, but of course with this way of "support" you get the best OpenSouce software broken down quite quickly.

There is nothing left to do but switch to another system where support isn't a unknown word ...
DLzG
Micha

User avatar
grovkillen
Normal user
Posts: 2077
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#25 Post by grovkillen » 30 Sep 2018, 20:49

M*I*B wrote:
30 Sep 2018, 20:32
... looks as if no more sow cares, just like to the matter with the BME280 (viewtopic.php?p=28956#p28956) ...
That's a pity. I think the system is pretty good, but of course with this way of "support" you get the best OpenSouce software broken down quite quickly.

There is nothing left to do but switch to another system where support isn't a unknown word ...
We're doing our best to get it stable and thus some issues are taking more time than anticipated. I'm sorry you're thinking our support is not good. I will improve.

Did you open an issue on GitHub?
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Sponsor ESP Easy, we need you :idea: :idea: :idea:

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#26 Post by M*I*B » 30 Sep 2018, 20:55

... I have not say it's not good. I have say that the support not exist ...

It's month ago not only I ask for the new implemented parameter. Normaly if someone implement new parameter or attributes there is a changelist where the (what the name say) changes are documented... But here is nothing... Just changed and leave all alone with that. That's the same i.e. I cut a single cable in your home but don't tell you whith one and who ...
DLzG
Micha

User avatar
grovkillen
Normal user
Posts: 2077
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#27 Post by grovkillen » 30 Sep 2018, 21:56

M*I*B wrote:
30 Sep 2018, 20:55
... I have not say it's not good. I have say that the support not exist ...

It's month ago not only I ask for the new implemented parameter. Normaly if someone implement new parameter or attributes there is a changelist where the (what the name say) changes are documented... But here is nothing... Just changed and leave all alone with that. That's the same i.e. I cut a single cable in your home but don't tell you whith one and who ...
I totally understand you. We will get better in the change log, at least for stable releases, maybe not much better for nightly. But have you opened one or more issues on GitHub? We have very little time to parse through the forum on search of issues.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Sponsor ESP Easy, we need you :idea: :idea: :idea:

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#28 Post by M*I*B » 30 Sep 2018, 22:04

... no ... Some time ago I have tell you that I don't know what GitHub is and how to handle ... I'm not a programmer/coder... I'm just a simple user with much scills in hardware and do my best to report faults and/or achievements and also ever be there to test some new things. But if I have'nt any things to test or have'nt any docs/changelist to read I can't check and test anything. And I believe that most of the users here also just users and don't know to handle GitHub but are able to describe problems and wishes in a forum like this ...
DLzG
Micha

User avatar
grovkillen
Normal user
Posts: 2077
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#29 Post by grovkillen » 30 Sep 2018, 22:13

M*I*B wrote:
30 Sep 2018, 22:04
... no ... Some time ago I have tell you that I don't know what GitHub is and how to handle ... I'm not a programmer/coder... I'm just a simple user with much scills in hardware and do my best to report faults and/or achievements and also ever be there to test some new things. But if I have'nt any things to test or have'nt any docs/changelist to read I can't check and test anything. And I believe that most of the users here also just users and don't know to handle GitHub but are able to describe problems and wishes in a forum like this ...
Ok, then it's a bit hard for us to take care of those issues. We prefer you to use the GitHub issue tracker since it'll keep you updated with current status. We're not (yet) a big company so it's essentially me and TD-er taking care of everything around here. Once we get a chance to release a first stable we'll get more up to date with the documentation. I hope you understand our side of the story, we're doing our best and will get better doing it. Please bear with us.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Sponsor ESP Easy, we need you :idea: :idea: :idea:

User avatar
M*I*B
Normal user
Posts: 45
Joined: 22 Jan 2018, 15:47
Location: Germany
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#30 Post by M*I*B » 30 Sep 2018, 22:32

... I understand you and your point of view ... That's not the problem. But I think you also have to take care of this user that can't handle GitHub; I believe that are the most.
If I have to wait 6 month or more without result for a thing I'm watching out for an other way to do it. In my matter it is the BME280 (it goes cold again and I have no way to mount this on the roof before next springtime) and the O-LED that meanwhile is the 4rd one due nobody knows about the dimmimg-attributes that are important for the livetime of this type of display... And meanwhile my stock of this displays are near empty due I have to replace it all 2-3 month... Gradually to destroy hardware and not to move forward is not really useful and not my goal ...

Maybe it's time to think about an other way where you not spend more time while pharsing the forum for issues but give the user without GitHub experience a way to incorporate the problems into the development. I'm sure that there is a viable solution that meets all sides, which does not leave the pure user in the rain and thus makes the project itself more manageable and thus more popular in the medium term...
DLzG
Micha

TD-er
Normal user
Posts: 1127
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#31 Post by TD-er » 30 Sep 2018, 23:38

The Framed Oled plugin has support for dimming (not the normal OLED plugin)
I did add an issue about it: https://github.com/letscontrolit/ESPEasy/issues/1506

But I've simply been too busy fixing other stuff, that it kinda slipped my mind.

TD-er
Normal user
Posts: 1127
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: After mega-20180426-normal sending TEXT tro OLED don't work

#32 Post by TD-er » 01 Oct 2018, 00:29

I have re-read the topic and am now looking at the source code of the plugin.

It looks like it is looking for "," (a comma) as parameter separator.

For example:

Code: Select all

oled 4 1 Some Text here
Becomes:

Code: Select all

oled,4,1,"Some Text here"
And about the 'support'.
We're spending a hell of a lot of time in making it a better product, and maybe the time isn't spent as optimal as possible.
I do most of the coding (like 90+%) and thus visit the Github page the most.
I try to visit the forum also on a regular basis, but when I do, it takes about half of my evening reading through all the new replies and helping out where I can.
Also on the reported issues at Github, a lot of time is lost in trying to gather enough info to get an idea on what is really happening.

It is all done in our free time.
This is not meant as an excuse on why your question was missed a number of times, just some view on what is going on here.
We're simply short on time and manpower and there is too much which has to be done.
For me, the last few months have been mainly about getting stuff stable and making sure a lot of code duplication was taken out.
A lot of code was <cut><paste><paste><paste><paste> and then altered in just a few lines to match its use.
The problem with that kind of development is that when you fix something in the first few "paste" occurrences, it is still broken in the others.
That's probably also what happened to this OLED command, that it got broken by changing something else.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest