michael-betz / espirgbani_pio

the platformio version of espirgbani
1 stars 1 forks source link

Artifacts on panel #2

Closed bipsendk closed 1 year ago

bipsendk commented 1 year ago

The artifacts as seen on the attached picture - are they to be expected, or should I try to increase the blanks value in the json file?

20231031_132141

michael-betz commented 1 year ago

Hi bipsendk, glad to see you got the code running :)

I've noticed the same kind of ghosting on my panels when driven at maximum brightness. My solution was to mount the panels behind some tinted acrylic, which makes the ghosting much less visible.

Maybe it can be fixed in the signal generation by putting some dead-time in the right place. Unfortunately I don't have the hardware setup right now to try that out.

You can also try playing with the parameters in the settings.json:

Good luck and let me know how it goes, Michael

bipsendk commented 1 year ago

I will try to adjust brightness - but not quite sure if that will resolve the issue (just make it less visible). Anyway - as I am not the only one seeing it, it is not something related directly to my hardware - so far, so good,

On the other hand, when trying to connect to the web interface, I get http error 500 .. I am using the IP address in the URL, not the hostname - but I guess that shouldn't be a problem. Can it be an issue with the json config file ? I have not yet tried to remove it, to see if that changes anything. Is it possible to add more logging a compile time - so I can get a hint on what is going on - and perhaps where in the code ? On the console, I see:

[W][AsyncTCP.cpp:950] _poll(): rx timeout 4 [W][AsyncTCP.cpp:950] _poll(): rx timeout 4

When trying to access the web interface

Is something missing on the sdcard ? Maybe a data folder with the index.htm file etc ?

michael-betz commented 1 year ago

Hmm that's a strange one. Just to be sure, did you flash the filesystem?

$ pio run -t uploadfs
bipsendk commented 1 year ago

That was the missing thing... As I am using pio via VSCode on Windows, I expected that to happen during the upload of the firmware - but apparently that needs to be handled as a separate task. Thanks