You are not logged in.
We need some high level help on this one. This LCD seems to have some serious issues with NanoDLP for some reason, and I have not yet been able to crack this nut. There are others on this forum that have made requests for help too, and we don't seem to be able to get anywhere.
I've gone through and checked all the EDID settings using tvservice and edidparser on the Pi, and even used Monitor Asset Manager on Windows to make sure the settings were being reported correctly. Nothing I seem to do makes any difference when it comes to NanoDLP.
If I put Raspian Buster on an SD card and boot it to the desktop, everything works fine. The screen image is clear, and there is no distortion or artifacts. Using the same settings in NanoDLP, the image displayed while printing gets torn and corrupted every few seconds. With the dynamic calibration screen, I can get the image stable if I lower the printable resolution in the Machine Settings page, but I still get corrupt images when I go to print (I'm doing dry runs right now while trying to sort this out).
I've played with alternate resolution settings (based on the tvservice EDID reports), changing the pixel frequency, changing the refresh rate, swapping out adapter boards, changing HDMI cables (now running an 18" 4K rated cable to minimize any potential issues), boosting the HDMI output, etc...
I've purchased 2 screens, and two different adapter boards so far, and a third screen and adapter (new design by the looks of it) on the way.
So, how does NanoDLP differ from the X1/Pixel desktop in the way that video data is sent to the HDMI port? Considering that drastically different results between the two, there has to be some fundamental difference that we aren't seeing.
Please, some experienced help would be appreciated on this one
Recent debug data can be found here: https://drive.google.com/open?id=1C9jJk … ROW6qz1MEf
Last edited by evilc66 (2019-10-26 01:35:36)
Offline
I managed to get NanoDLP running on a Pi4 using the latest download of Raspbian Buster (not lite). After running tvservice and using edidparser to parse the output, I don't get any listings for a mode that has a resolution of 2560x1600. Why would that be? Using the NanoDLP image, I would get 2560x1600, which is what I set my initial display config to, and Monitor Asset Manager also would show 2560x1600, but not Raspian Buster?
Offline
Switch to framebuffer see if it solve your issue temporary or not.
Offline
Can you give a little more detail on that? I'm not entirely sure what that means
Offline
Checkout framebuffer field on the machine settings page. You can use onscreen help to get more information about this option.
Offline
Interesting results
With the Pi4 (Buster with NanoDLP installed manually), it started displaying the desktop instead of the calibration images or print image. I'll give Buster Lite a try later to see if that helps the situation.
On the Pi3 (with the NanoDLP image), I could get the calibration image to display at 2560x1600 for the first time with no image tearing or artifacts. When it came to displaying the print images, things didn't go so well. I've been using a 20mm calibration cube model for the moment, and all that's displayed on the screen is a series of lines extending the entire width of the screen.
What can we try next?
Offline
If you are not using lite version need to disable desktop scripts from systemd as they race for display adapter with nanodlp.
Have you sliced plates with correct resolution? Also share photos from what projected.
Offline
If you are not using lite version need to disable desktop scripts from systemd as they race for display adapter with nanodlp.
Have you sliced plates with correct resolution? Also share photos from what projected.
could you explain how it is done?
Offline
I think we finally have this nut cracked. After a second reboot and a reslice of the model, the print image is displaying perfectly on the Pi3 setup. I'm so grateful that I can finally get this printer running.
Offline
first off i'm new to all this. But from all my searching and my own testing i don't think the problem is with nanodlp. it seems to be a problem with the most recent raspberry os. i'm assuming that the current version of nanodlp image is based on current raspberry os. and when installing nanodlp from the script runs the updates. I was having hella issues then noticed from other boards that people were having the same problem with this display that were not using nanodlp. I went back and flashed older versions (2019-07-10-raspbian-buster.img among others) and it worked fine with the config provided by the manufacturer but everytime i update it kills it.
Offline
Actually display configs are not same for pi3 and pi4, manufacturers need to update config files.
Offline