BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

pi_printer · 2021-04-25 15:14:10

matt3o wrote:

I had it working on a 4K BOE RGB, 4K AUO RGB and 4K BOE mono. So far they all worked out of the box without timing but only on a rpi4. On the rpi3 as far as I can tell you need timing.

Diffuser3D has a post on facebook where he documents how he used this lcd in his Phrozen 2018

https://www.facebook.com/permalink.php? … &__tn__=-R

He used these settings.

hdmi_force_hotplug=1
start_x=1
gpu_mem=128
hdmi_pixel_freq_limit=400000000
disable_camera_led=1
dtparam=i2c1=on
dtparam=i2c_arm=on
disable_overscan= 1
#hdmi_timings=1440 0 60 10 35 2560 0 8 4 4 0 0 0 50 0 199000000 0
#hdmi_timings=2160 0 105 32 100 1280 0 12 2 10 0 0 0 24 0 222290000 0
hdmi_timings=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0 223290000 0
hdmi_drive=2
dtoverlay=pi3-disable-bt
#dtoverlay=pi3-disable-wifi
force_turbo=1
enable_uart=1
disable_overscan=1
max_framebuffer_width=2160
max_framebuffer_height=3840
hdmi_group=2
config_hdmi_boost=4
#display_rotate=0x10000
framebuffer_width=2160
framebuffer_height=3840
force_turbo=1
#arm_freq=1300
#over_voltage=4
gpu_freq=300
core_freq=400

Jonners59 · 2021-04-25 19:11:22

You lost me on this, sorry. You say that

matt3o wrote:

.......... without timing but only on a rpi4. On the rpi3 as far as I can tell you need timing.

But

matt3o wrote:

hdmi_timings=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0 223290000 0

this is the timing.....

Also, in a Pi4 because it has 2 x HDMI ports all these numbers MUST be even

hdmi_timings=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0

, but you have a 105, that should be 104 or 106.

matt3o · 2021-04-26 15:34:03

Jonners59 wrote:

You lost me on this, sorry. You say that

those timings (posted not by me anyway) are for the RPI3 not the 4.

as someone else reported, I do no recommend using 4K screens on the rpi3 because it's really too slow and you have to add a lot of delay after displaying the image.

Jonners59 · 2021-04-26 18:24:24

matt3o wrote:

Jonners59 wrote:
You lost me on this, sorry. You say that
those timings (posted not by me anyway) are for the RPI3 not the 4.
as someone else reported, I do no recommend using 4K screens on the rpi3 because it's really too slow and you have to add a lot of delay after displaying the image.

It's become a messy thread.

Shahin · 2021-04-27 06:15:39

When you are using high resolution display on RPi 4, make sure assign values only to active HDMI. I have seen cases which it does not work or working with large delays due to setting up both display.
To assign values to one output only add :0= or :1= instead of =
eg.
hdmi_timings:0=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0

Also delays should not be visible during printing as most of image load and decode being done during movement. If there is a visible delay I guess it is wrong configuration.

matt3o · 2021-04-27 06:31:05

it is slow on the rpi3, not on the 4 (at least for me). Adding the manufacturer's timings never worked for me on the rpi4 but they do work on the rpi3. I don't know why

Last edited by matt3o (2021-04-27 06:32:45)

Jonners59 · 2021-04-27 07:03:30

Shahin wrote:

When you are using high resolution display on RPi 4, make sure assign values only to active HDMI. I have seen cases which it does not work or working with large delays due to setting up both display.
To assign values to one output only add :0= or :1= instead of =
eg.
hdmi_timings:0=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0
Also delays should not be visible during printing as most of image load and decode being done during movement. If there is a visible delay I guess it is wrong configuration.

That isn't strictly true, Shahin.
The Timings you have there are strictly Pi3 or below. A Pi4 has two HDMI outputs and needs timings to be all equal numbers, but it is also not essential to assign the Timings to a given port, although it may be useful as only one port can run high resolution at a time so you may want to monitor activity on another at a lower resolution, but typically only one LCD is connected so not important.

I am using, very successfully:
[All]
hdmi_timings=2160 0 106 32 100 3840 0 12 2 10 0 0 0 60 0 277976160 3

Note without any assignment. Note the numbers are all even - ignore the last one, which is not important to be even as it refers only to <aspect_ratio>.

https://www.raspberrypi.org/documentati … i4-hdmi.md
https://www.raspberrypi.org/documentati … t/video.md
https://en.wikipedia.org/wiki/Extended_ … _Version_3
https://www.raspberrypi.org/forums/view … 29&t=24679
https://elinux.org/RPiconfig
https://www.raspberrypi.org/documentati … itional.md

I have created a spreadsheet for 4k and 2k LCDs to calc the frame rate and frequencies....

Jonners59 · 2021-04-27 07:04:57

matt3o wrote:

it is slow on the rpi3, not on the 4 (at least for me). Adding the manufacturer's timings never worked for me on the rpi4 but they do work on the rpi3. I don't know why

I too have absolutely no issues with the Pi4 on high def. The supplier configs are all Pi3 or below that is why as they do not understand the config. Mine works flawlessly with my 4k RGB LCD.

matt3o · 2021-04-27 07:07:56

Jonners59 wrote:

[All]
hdmi_timings=2160 0 106 32 100 3840 0 12 2 10 0 0 0 60 0 277976160 3

why bothering setting the hdmi_timing when the rpi4 seems to be able to find them by itself? not trolling actually wondering if there's a gain.

Jonners59 wrote:

I have created a spreadsheet for 4k and 2k LCDs to calc the frame rate and frequencies....

well now you have to share it

Last edited by matt3o (2021-04-27 07:08:23)

Shahin · 2021-04-27 07:09:01

Jon,

If you have spreadsheet, it will be great to share it on NanoDLP help. Lots of people having issue with these values.

Cao Luc · 2021-05-31 11:02:18

I also got the same error, the config file of the manufacturer failed, can someone share the configuration here?

GPM · 2021-06-30 19:21:17

Hi to all,

I need some help for printer model Shuffle 2018 upgrade configuration.

I have replace 2k display with 4K mono (duobond model - VS055QUB-NH1-DQP0). I have replace pi3b with pi4b.

Successfully set up the nanodlp firmware with advance installation process.

RAMP is connected (z is moving up and down) and LCD is working through test page (using matt3o's Config file).

Touch screen is going to be replaced because is not a Nextion model so I can't upload the TFT file.

My problem is that when I start a print z axis is going to (0 zero position), led array is working but screen doesn't showing the slices and no further movement on z axis.

Can someone please provide the setup for pages Display Engine, Axis/Movement, Hardware, Code/Gcode and Shutter?

Ce1ticWarri0r · 2021-09-05 22:13:04

Bumping this as I am also having issues and it would be great to see if anyone has had similar. I have tried so many different configuration files but I have got closest with the ones here. Problem is the image only appears for about 1 second, then the lcd controller led goes from green to flashing blue like it loses connection. Anyone have any ideas?

Ce1ticWarri0r · 2021-09-09 07:43:03

In case it helps anyone else I ended up having success with the below. Note that if this is for a 3D printer then set the display up first using the full rasberian OS, not the lite version. Then use the desktop display settings to rotate the screen to where it needs to be. Only then install Nano DLP.

##########HDMI Settings##########

hdmi_enable_4kp60=1
hdmi_ignore_edid:0=1
#hdmi_force_hotplug=1
hdmi_drive:0=2
#disable_fw_kms_setup=1

hdmi_group:0=2
hdmi_mode:0=87
hdmi_cvt:0=2160 3840 24 3 0 0 0

hdmi_pixel_freq_limit:0=300000000
#hdmi_timings:0=2160 0 105 20 100 3840 0 30 2 29 0 0 0 24 0 223290000 0
#hdmi_timings=3840 0 216 400 616 2160 0 3 5 24 0 0 0 24 0 266750000 3

hdmi_pixel_encoding:0=2
#config_hdmi_boost=7

##########Display Settings##########

disable_overscan=1
#overscan_left=0
#overscan_right=0
#overscan_top=0
#overscan_bottom=0

max_framebuffer_width:0=2160
max_framebuffer_height:0=3840
#framebuffer_width:0=2160
#framebuffer_height:0=3840
framebuffer_depth:0=32
framebuffer_ignore_alpha:0=1

#test_mode=0

#########Orientation Settings##########

display_hdmi_rotate=0
#0 No rotation (use default for screen)
#1 Rotate 90 degrees clockwise
#2 Rotate 180 degrees
#3 Rotate 90 degrees counterclockwise
#0x10000 Horizontal flip
#0x20000 Vertical flip

##########Overclock##########

#over_voltage=4
#arm_freq=1850
#v3d_freq=650
#gpu_freq=650

##########Hardware Acceleration##########

dtoverlay=vc4-fkms-v3d
#max_framebuffers=2

##########GPU Memory##########

#gpu_mem=512

nanoDLP

#26 2021-04-25 15:14:10

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#27 2021-04-25 19:11:22

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#28 2021-04-26 15:34:03

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#29 2021-04-26 18:24:24

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#30 2021-04-27 06:15:39

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#31 2021-04-27 06:31:05

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#32 2021-04-27 07:03:30

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#33 2021-04-27 07:04:57

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#34 2021-04-27 07:07:56

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#35 2021-04-27 07:09:01

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#36 2021-05-31 11:02:18

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#37 2021-06-30 19:21:17

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#38 2021-09-05 22:13:04

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

#39 2021-09-09 07:43:03

Re: BOE 5.5" 4k Monochrome VS055QUB-NH1-DQP0 LCD

Board footer