You are not logged in.

#1 2019-01-26 07:02:44

mystamo
Member
Registered: 2019-01-23
Posts: 22

2k 1440 x 2560 screen issues on NanoDLP

Hi All,

So I opted to drop the Arduino GRBL and windows edition of NanoDLP. (After I made a barehanded shield)

I'm now using NanoDLP on a Pi 3 and I made a TOS sheild to fit onto the pi.

Everything works. And I mean everything now works.. Except! The screen!

I can see the calibration screens.. I can see the layers individually in the plate screen and keep them there and cycle through other layers.

But as soon as I come to print something... The layer image pops up for a moment during the time the printer is suppose to cure and the image quickly goes away.

This isn't my curing and lift and wait times as I've modified all times to greater than 5s and still see the image only for a moment.

Can someone please help me. It's 2am my wife is pissed as I've givin' up my last week to trouble shooting NanoDLP. I'm about to jump ship on this whole nanoDLP thing and go back to an ancient version of CW that I have

if you search aliexpress 5-5-inch-2560-1440-2K-LCD-Screen-LS055R1SX04-HDMI-to-MIPI-driver-controller-for-3d/32816576938 you will find my screen. With some config.txt settings which I have applied. As well as some NanoDLP resolution settings I have also applied.

Linked is my screen. I have applied the noted settings. That is where I am now.

Mo

Offline

#2 2019-01-26 08:52:16

mystamo
Member
Registered: 2019-01-23
Posts: 22

Re: 2k 1440 x 2560 screen issues on NanoDLP

I'm still up...

This sucks.

I really can't fathom this being a setup related issue. How can the screen display without any issues in the calibration screens.. Allow me to switch between the RED WHITE and Blank without any issues and any stoppage.. But then when it comes to printing. The momentary image.

I'm not getting the momentary image anymore. which has me thinking it may be somewhat setting related. As now I've iterated through 100 settings. But I just think it's a combo of a bug an a very sensitive 1440 2560 screen.

Help would be sooooo appreciated.

Sleep time. It's almost 4am.

Mo

Offline

#3 2019-01-26 10:38:03

mystamo
Member
Registered: 2019-01-23
Posts: 22

Re: 2k 1440 x 2560 screen issues on NanoDLP

This will keep me up all night.

I've attached my debug nanodlp.debug.282235049.zip

Also, i'm coming back to thinking more a Nanodlp issue?  Why if once I open the view stream I can switch between other drawings but the clear screen command during printing seem to be keeping the screen black?

I tried an assortment of new stl files and tried different scales. I was thinking maybe bigger images on the screen would yield different results. Wasn't the case.

My other research of people having this similar issue is they gave up or didn't post their solution.

Mo

Offline

#4 2019-01-26 11:21:38

mystamo
Member
Registered: 2019-01-23
Posts: 22

Re: 2k 1440 x 2560 screen issues on NanoDLP

OK OK... Now i'm coming off like i'm crazy.. Yeah.. It's 6AM .. I'm CRAZY

I fixed it.. Shahin.. Now I'm nearly certain this is somehow NanoDLP related.

The solution was going back to the original image that I started my NanoDLP build off from the main page Pi image download link.

This is Build 1819.. It works without any issues. Each frame coming onto the screen. Motors working. Endstops working. IRL44 (Logic Level Fet) Used to drive LED array.

God. I need Sleep..

Shahin.. Tomorrow.. or this week. I'll give you a hand doing some tests to figure out what is wrong with the newer builds when it comes to HDMI sync with prints.


Gah, I need sleep.. First Test print tomorrow (Once I'm up!) I've already tested exposure times on the LCD screen using some extra FEP things look promising

Mo

Offline

#5 2019-01-27 05:26:15

Shahin
Administrator
Registered: 2016-02-17
Posts: 2,760

Re: 2k 1440 x 2560 screen issues on NanoDLP

Not much changed on nanodlp side which could cause kind of issue. I suspect gpu firmware bug. If you are switching between SD card images. Try upgrade raspberry pi firmware on newer SD image see if it fixed the issue or not.
Recently I have seen some strange issues caused by firmware on pi.

Offline

#6 2019-01-27 14:57:51

mystamo
Member
Registered: 2019-01-23
Posts: 22

Re: 2k 1440 x 2560 screen issues on NanoDLP

Thanks for the reply Shahin.

This is sort of new to me. I didn't realize.. I mean. I should have realized that the Pi has a built in Bootloader (Firmware)

I was under the incorrect assumption that the image loaded onto the SD card was the Bootloader/firmware and didn't realize there is a small part of code needed on the Pi sort of as a BIOS code for reading code and executing it.

But I'm unfamiliar to the process of updating that bit of code.

I'll do some research today to see if I can update the pi to the latest firmware image.

I'll report back my findings.

As far as I see it now. There is a bug somewhere that is software dependant and non dependant at this point on how I have my hardware setup.

1819 works 1939 doesn't

Mo

Offline

#7 2019-01-28 20:10:30

mystamo
Member
Registered: 2019-01-23
Posts: 22

Re: 2k 1440 x 2560 screen issues on NanoDLP

Shahin wrote:

Not much changed on nanodlp side which could cause kind of issue. I suspect gpu firmware bug. If you are switching between SD card images. Try upgrade raspberry pi firmware on newer SD image see if it fixed the issue or not.
Recently I have seen some strange issues caused by firmware on pi.



Thanks Shahin,

You were damn right correct.


All... If you face issues. Remember to update your Pi firmware. (This is essentially the bit of code that tells the Pi how to do anything including reading the SD card to run your nanodlp software)

Procedure to upgrade:


1. Go on the Pi main site and get a copy of Raspbian. (The edition with software and desktop)
2. Copy to a memory card using winimage32
3. Run Raspbian
4. Go to terminal(use desktop icon)
4. Run command "sudo apt-get update"
5. Run command "sudo apt-get upgrade"

6. Reboot Pi

7. Load NanoDLP back
8. Enjoy 2K video on your 5.5 Inch China HDMI to MIPI LCD.

Thanks for the support Shahin.

Mo


Edit.. There may be an easier way to do this.. But this is what I did and it worked.. Better this than an internet of hopeless dreams and lack of answers leading to all all nighter and an angry wife.

Last edited by mystamo (2019-01-28 20:12:25)

Offline

#8 2019-03-25 14:05:18

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

Hi Shahin,

i have the same problems as Mystamo,
The screen can show single image, show the grids, show the samples image of a slice,
but when i launch a print, nothing shows.
i have re install Raspbian+ Nanodlp, try the image of nanodlp..do all the update possible, but cannot solve this problem.
I am using raspi pi3 with shieldV2.2. all the rest working perfect. Any idea? stuck!

Before i have RAMP board and nevr have this problem, i use the same parameters for my display.

Thanks

Offline

#9 2019-03-25 19:04:46

Shahin
Administrator
Registered: 2016-02-17
Posts: 2,760

Re: 2k 1440 x 2560 screen issues on NanoDLP

laopa,

Please, share a debug file.

Offline

#10 2019-03-28 10:43:58

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

Hi Shahin,

i log into Facebook to upload the debug file, but only showing pending.
do you have other way to send debug?

Yesterday i tryed again, install raspian desktop, update all, install nanodlp, but after reboot, the raspi does not want boot on Nanodlp. do you know where to change that?

Thanks

Offline

#11 2019-03-28 19:31:31

Shahin
Administrator
Registered: 2016-02-17
Posts: 2,760

Re: 2k 1440 x 2560 screen issues on NanoDLP

Upload anywhere share it here.

Offline

#12 2019-03-29 04:58:20

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

Hi Shahin,

My config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
dtoverlay=pi3-disable-bt

# CAMERA SETTINGS ( 1 = ON, 0 = OFF)
#start_x=1
disable_camera_led=1

# DISPLAY SETTINGS
display_rotate=0x10000
hdmi_force_hotplug=1
#disable_overscan=1
framebuffer_depth=24
gpu_mem=192
framebuffer_ignore_alpha=1
#start_x=1
hdmi_cvt=1440 2560 48
hdmi_group=2
hdmi_mode=87
hdmi_pixel_freq_limit=400000000
hvs_priority=0x32ff
max_framebuffer_width=1440
max_framebuffer_height=2560
framebuffer_width=1440
framebuffer_height=2560
config_hdmi_boost=4

enable_uart=1

Offline

#13 2019-03-29 05:00:50

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

the printer.txt
2019/03/25 11:16:19.128035 {"Layer":"2","module":"Hardware","level":"Notice","msg":"Initializing build # 2065 - generic"}
2019/03/25 11:16:19.147533 {"Layer":"2","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
2019/03/25 11:16:19.295263 {"Layer":"2","module":"WIFI","level":"Warning","msg":"WIFI interface wlan0 detected"}
2019/03/25 11:16:19.545490 {"Layer":"2","module":"WIFI","level":"Warning","msg":"Connecting to Home2"}
2019/03/25 11:16:26.677125 {"Layer":"2","module":"GPIO","level":"Notice","msg":"Limit has been touched"}
2019/03/25 11:16:26.677315 {"Layer":"2","module":"Pulsing","level":"Warning","msg":"Limit touched, position set to zero"}
{"time":"2019-03-25T11:17:44.919652705Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
{"time":"2019-03-25T11:17:49.609789101Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
crypto/rand: blocked for 60 seconds waiting to read random data from the kernel
2019/03/25 11:18:01.530008 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:22:16.419756 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/0/1.png"}
{"time":"2019-03-25T11:22:25.490396607Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:22:25.508047 {"Layer":"1","module":"Calibration","level":"Warning","msg":"Printing layer 1 from 60"}
2019/03/25 11:23:57.099843 {"Layer":"1","module":"Image","level":"Warning","msg":"Display layer public/plates/0/1.png"}
2019/03/25 11:24:24.856395 {"Layer":"2","module":"Calibration","level":"Warning","msg":"Printing layer 2 from 60"}
2019/03/25 11:24:36.888566 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/0/1.png"}
{"time":"2019-03-25T11:24:59.453491016Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:25:04.219290 {"Layer":"2","module":"Calibration","level":"Warning","msg":"Stop Command Received"}
{"time":"2019-03-25T11:25:05.436659135Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:26:24.588986 {"Layer":"2","module":"Printing","level":"Notice","msg":"Printing Auto Calibration Plate Completed"}
2019/03/25 11:26:44.181120 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
{"time":"2019-03-25T11:26:52.343732125Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:27:07.831204 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:25:00.661037 {"Layer":"2","module":"Hardware","level":"Notice","msg":"Initializing build # 2065 - generic"}
2019/03/25 11:25:00.680524 {"Layer":"2","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
2019/03/25 11:25:00.830988 {"Layer":"2","module":"WIFI","level":"Warning","msg":"WIFI interface wlan0 detected"}
2019/03/25 11:25:01.084391 {"Layer":"2","module":"WIFI","level":"Warning","msg":"Connecting to Home2"}
2019/03/25 11:25:08.310894 {"Layer":"2","module":"GPIO","level":"Notice","msg":"Limit has been touched"}
2019/03/25 11:25:08.311097 {"Layer":"2","module":"Pulsing","level":"Warning","msg":"Limit touched, position set to zero"}
crypto/rand: blocked for 60 seconds waiting to read random data from the kernel
{"time":"2019-03-25T11:31:15.159191871Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:31:26.670727 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:31:32.452671 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:32:15.749876 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:32:26.798980 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
{"time":"2019-03-25T11:46:47.006533725Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
{"time":"2019-03-25T11:48:47.36110927Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
printer: imageLayer.c:255: destroyImageLayer: Assertion `result == 0' failed.
SIGABRT: abort
PC=0x76cf845c m=0 sigcode=4294967290

goroutine 66 [syscall, 2 minutes]:
runtime.notetsleepg(0x9a200c, 0xf79a5aca, 0x46, 0x0)
    /usr/local/go/src/runtime/lock_futex.go:227 +0x24 fp=0x1941790 sp=0x1941778 pc=0x1c1ac
runtime.timerproc(0x9a1ff8)
    /usr/local/go/src/runtime/time.go:311 +0x440 fp=0x19417e4 sp=0x1941790 pc=0x5db08
runtime.goexit()
    /usr/local/go/src/runtime/asm_arm.s:868 +0x4 fp=0x19417e4 sp=0x19417e4 pc=0x6ba84
created by runtime.(*timersBucket).addtimerLocked
    /usr/local/go/src/runtime/time.go:169 +0x174

goroutine 1 [IO wait, 2 minutes]:
internal/poll.runtime_pollWait(0x651a9eb4, 0x72, 0x0)
    /usr/local/go/src/runtime/netpoll.go:182 +0x48
internal/poll.(*pollDesc).wait(0x197a014, 0x72, 0x0, 0x0, 0x5619e3)
    /usr/local/go/src/internal/poll/fd_poll_runtime.go:87 +0x80
internal/poll.(*pollDesc).waitRead(...)
    /usr/local/go/src/internal/poll/fd_poll_runtime.go:92
internal/poll.(*FD).Accept(0x197a000, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
    /usr/local/go/src/internal/poll/fd_unix.go:384 +0x1b0
net.(*netFD).accept(0x197a000, 0x2dabe077, 0x0, 0x5c98c1e7)
    /usr/local/go/src/net/fd_unix.go:238 +0x20
net.(*TCPListener).accept(0x1810080, 0xed90d08d, 0x192, 0xedabe077)
    /usr/local/go/src/net/tcpsock_posix.go:139 +0x20
net.(*TCPListener).AcceptTCP(0x1810080, 0x1, 0x13a98, 0x2b74bc)
    /usr/local/go/src/net/tcpsock.go:247 +0x40
github.com/labstack/echo.tcpKeepAliveListener.Accept(0x1810080, 0x98c1e700, 0x49208, 0x2bbd38, 0x1d18e64)
    /home/pi/go/src/github.com/labstack/echo/echo.go:713 +0x1c
net/http.(*Server).Serve(0x1978000, 0x62d0e8, 0x1810088, 0x0, 0x0)
    /usr/local/go/src/net/http/server.go:2859 +0x1e4
github.com/labstack/echo.(*Echo).StartServer(0x188d6c0, 0x1978000, 0x1, 0x57e5cf)
    /home/pi/go/src/github.com/labstack/echo/echo.go:646 +0x2d4
main.webInit()
    /home/pi/printer/app/routes.go:26 +0x22c
main.main()
    /home/pi/printer/app/server.go:86 +0x414

goroutine 19 [chan receive, 26 minutes]:
projects/printer/app/move.(*speedStruct).calc(0x99f610, 0x18a60c0)
    /home/pi/go/src/projects/printer/app/move/speed.go:94 +0x3c
created by projects/printer/app/move.init.0
    /home/pi/go/src/projects/printer/app/move/speed.go:31 +0x60

goroutine 53 [IO wait]:
internal/poll.runtime_pollWait(0x651a9fbc, 0x72, 0x0)
    /usr/local/go/src/runtime/netpoll.go:182 +0x48
internal/poll.(*pollDesc).wait(0x189a7e4, 0x72, 0x400, 0x400, 0x0)
    /usr/local/go/src/internal/poll/fd_poll_runtime.go:87 +0x80
internal/poll.(*pollDesc).waitRead(...)
    /usr/local/go/src/internal/poll/fd_poll_runtime.go:92
internal/poll.(*FD).ReadFrom(0x189a7d0, 0x1953b44, 0x400, 0x400, 0x0, 0x0, 0x0, 0x0, 0x0)
    /usr/local/go/src/internal/poll/fd_unix.go:219 +0x16c
net.(*netFD).readFrom(0x189a7d0, 0x1953b44, 0x400, 0x400, 0x1a93bc, 0x1aab70, 0x1c6e300, 0xa, 0x10)
    /usr/local/go/src/net/fd_unix.go:208 +0x38
net.(*UDPConn).readFrom(0x195c140, 0x1953b44, 0x400, 0x400, 0x1c99024, 0x4, 0x4, 0x10)
    /usr/local/go/src/net/udpsock_posix.go:47 +0x38
net.(*UDPConn).ReadFromUDP(0x195c140, 0x1953b44, 0x400, 0x400, 0x1d93000, 0xdf, 0x0, 0x0)
    /usr/local/go/src/net/udpsock.go:109 +0x44
projects/printer/app/ssdp.Server(0x57e5cf, 0x2, 0x18b0d67, 0x8, 0x6207c8, 0x4)
    /home/pi/go/src/projects/printer/app/ssdp/ssdp.go:58 +0x1b8
created by main.afterIP
    /home/pi/printer/app/server.go:114 +0xac

goroutine 21 [chan receive]:
projects/printer/app/machine.(*StatusStruct).FindIP(0x99f7e8)
    /home/pi/go/src/projects/printer/app/machine/status.go:134 +0x5c
created by projects/printer/app/machine.(*StatusStruct).Load
    /home/pi/go/src/projects/printer/app/machine/status.go:114 +0x70

goroutine 5 [chan receive]:
main.wifiStatus()
    /home/pi/printer/app/wireless.go:78 +0xc4
created by main.wifiConnect
    /home/pi/printer/app/wireless.go:23 +0xc0

goroutine 28 [chan receive]:
projects/printer/app/hw/monitor.FreeMem()
    /home/pi/go/src/projects/printer/app/hw/monitor/memfree.go:11 +0x5c
created by main.main
    /home/pi/printer/app/server.go:63 +0x2c0

goroutine 29 [sleep]:
runtime.goparkunlock(...)
    /usr/local/go/src/runtime/proc.go:307
time.Sleep(0x5f5e100, 0x0)
    /usr/local/go/src/runtime/time.go:105 +0x15c
main.(*termStruct).readLine(0x99f288, 0x8, 0x0, 0x195c000)
    /home/pi/printer/app/term.go:50 +0x2a4
main.(*termStruct).Reader(0x99f288)
    /home/pi/printer/app/term.go:39 +0x78
created by main.main
    /home/pi/printer/app/server.go:64 +0x2dc

goroutine 30 [chan receive]:
projects/printer/app/slicer.(*MonitorStruct).Watch(0x99f328)
    /home/pi/go/src/projects/printer/app/slicer/slicer.go:93 +0x78
created by main.main
    /home/pi/printer/app/server.go:65 +0x2fc

goroutine 32 [chan receive]:
projects/printer/app/hw/monitor.Monitor()
    /home/pi/go/src/projects/printer/app/hw/monitor/monitor_linux.go:34 +0xb4
created by main.main
    /home/pi/printer/app/server.go:71 +0x42c

goroutine 55 [sleep, 2 minutes]:
runtime.goparkunlock(...)
    /usr/local/go/src/runtime/proc.go:307
time.Sleep(0xe11d6000, 0x37)
    /usr/local/go/src/runtime/time.go:105 +0x15c
main.updateControlPanel()
    /home/pi/printer/app/server.go:216 +0xac
created by main.afterIP
    /home/pi/printer/app/server.go:116 +0x10c

trap    0x0
error   0x0
oldmask 0x4000
r0      0x0
r1      0x1941148
r2      0x0
r3      0x8
r4      0x0
r5      0x1941148
r6      0x76fbb210
r7      0xaf
r8      0x194125c
r9      0xff
r10     0x19a21c0
fp      0x96b2b4
ip      0x20
sp      0x1941148
lr      0xffffffff
pc      0x76cf845c
cpsr    0x10
fault   0x0
2019/03/25 11:56:51.616343 {"Layer":"2","module":"Hardware","level":"Notice","msg":"Initializing build # 2065 - generic"}
2019/03/25 11:56:51.647813 {"Layer":"2","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
2019/03/25 11:56:51.792763 {"Layer":"2","module":"WIFI","level":"Warning","msg":"WIFI interface wlan0 detected"}
2019/03/25 11:56:52.075247 {"Layer":"2","module":"WIFI","level":"Warning","msg":"Connecting to Home2"}
2019/03/25 11:56:59.153417 {"Layer":"2","module":"GPIO","level":"Notice","msg":"Limit has been touched"}
2019/03/25 11:56:59.153599 {"Layer":"2","module":"Pulsing","level":"Warning","msg":"Limit touched, position set to zero"}
{"time":"2019-03-25T11:57:03.441582387Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
crypto/rand: blocked for 60 seconds waiting to read random data from the kernel
{"time":"2019-03-25T11:58:49.228164076Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 11:58:57.417518 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/dynamic.png"}
2019/03/25 11:59:52.439765 {"Layer":"2","module":"Upload","level":"Notice","msg":"Plate file being processed"}
2019/03/25 12:00:11.815183 {"Layer":"2","module":"Upload","level":"Notice","msg":"Plate file has been processed"}
2019/03/25 12:00:28.220390 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/1/1.png"}
{"time":"2019-03-25T12:00:41.32287751Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 12:02:13.692490 {"Layer":"1","module":"Image","level":"Warning","msg":"Display layer public/plates/1/1.png"}
2019/03/25 12:02:44.882348 {"Layer":"2","module":"Image","level":"Warning","msg":"Display layer public/plates/1/2.png"}
{"time":"2019-03-25T12:03:04.460923405Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}
2019/03/25 12:03:06.712491 {"Layer":"2","module":"Printing","level":"Warning","msg":"Stop Command Received"}
                                                                                                                   2019/03/25 12:03:34.366891 {"Layer":"2","module":"Hardware","level":"Notice","msg":"Initializing build # 2065 - generic"}
2019/03/25 12:03:34.396185 {"Layer":"2","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
2019/03/25 12:03:34.542928 {"Layer":"2","module":"WIFI","level":"Warning","msg":"WIFI interface wlan0 detected"}
2019/03/25 12:03:34.789095 {"Layer":"2","module":"WIFI","level":"Warning","msg":"Connecting to Home2"}
2019/03/25 12:03:42.006992 {"Layer":"2","module":"GPIO","level":"Notice","msg":"Limit has been touched"}
2019/03/25 12:03:42.007187 {"Layer":"2","module":"Pulsing","level":"Warning","msg":"Limit touched, position set to zero"}
{"time":"2019-03-25T12:03:52.997386636Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"580","message":"code=404, message=Not Found"}

Offline

#14 2019-03-29 05:02:46

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

all the rest are machine config. jason. tell me the file you need?

Thanks

Offline

#15 2019-03-29 07:33:43

Shahin
Administrator
Registered: 2016-02-17
Posts: 2,760

Re: 2k 1440 x 2560 screen issues on NanoDLP

Laopa it is most probably firmware issue I cannot tell without take a look at your complete debug file, My guess is you are not using patched firmware but applying waitfordonemessage, search forum there are load of thread about this issue.

Offline

#16 2019-03-29 12:42:32

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

Hi Shahin,

I have redo everything again. Install fresh Nanodlp SD from download, update pi via SSH, enter all GPIO for shield v2.2, everything work fine, mvt, display. import files....Only when launch printing, printer down, burn the layers, up, down....... but nothing display.

the link of the NEW FULL debug file
nanodlp.debug.222635215.zip

thanks

Offline

#17 2019-03-29 20:27:48

Shahin
Administrator
Registered: 2016-02-17
Posts: 2,760

Re: 2k 1440 x 2560 screen issues on NanoDLP

Is it continue works without displaying other layers? All I can see on log files is single layer.

Offline

#18 2019-03-30 03:40:45

laopa
Member
Registered: 2017-03-01
Posts: 17

Re: 2k 1440 x 2560 screen issues on NanoDLP

Hi Shahin,

I FOUND THE PROBLEM. on the machine settings, Display options, Display communication type must be DISABLE.

And everything working fine.

Thanks

Last edited by laopa (2019-03-30 11:56:02)

Offline

Board footer

Powered by FluxBB