NanoDLP Display Engines

One of the basic requirements of the LCD 3D printers are to display object as sliced frames.

NanoDLP supports many way to display images, this post try to explain how each one works, what is the best and also give workaround for cases which one engine does not work well enough.

BCM (DispmanX)

It is a way to communicate directly with Raspberry Pi (Broadcom chipsets) to display images. Performance great but only works on Raspberry Pi.

No option needed to enable it, it automatically being used if other display engine does not enabled manually.

Only reason not use it on Raspberry Pi is when NanoDLP DisplaymanX is not compatible with your display in forms of reliability issue.


This is very basic form of updating display. Just need to put correct path on Linux to enable it instead of BCM.


It is desktop only solution, due to possible timing and reliability issue on desktop computers other way to control your NanoDLP suggested.

BCM (DispmanX) vs. Framebuffer vs. OpenGL

Comparison of the different engines:

Raspberry Pi w. Server OSYesNoNo
Raspberry Pi w. Full OSNoYes (Should be Enabled)Yes
Linux – Server (ARM, AMD64)NoYesNo
Linux – Desktop (ARM, AMD64)NoYes (Should be Enabled)Yes
MacNoNo (There are some workaround)Yes
Performance (FPS)GreatGoodGood

Latest Posts

Browser Based Slicer

Web Browser Based SLA 3D Printer Slicer

SLA 3D printer web browser based slicer rely on your browser resources to slice 3D files instead of Raspberry Pi (or other host SBCs)

Read More
NanoDLP Documentation

NanoDLP Documentation Launched

NanoDLP documentation contains both get started guides for novice users and also more advanced guides for expert users.

Hope you become one of the contributors to the new

Read More
NanoSupport Interface

Next Generation NanoSupport

New NanoSupport with completely new user interface and many new features including advanced auto support algorithm has been released.

Read More


0 0 votes
Article Rating
Inline Feedbacks
View all comments