You are not logged in.
Pages: 1
It will be nice to have support for the VGA666 board which uses the GPIO pins on RPi3. At present, the GPIO pins are initialized by nanoDLP. If this can be disabled, it will be nice.
Offline
If you do not use any gpio, it will only open /dev/mem and allocate pointer to it. Are you sure it is preventing VGA666 to work with nanodlp?
Offline
Hi Shah in, I am quite sure it does prevent vga666 adaper from using the gpio. The screen works perfectly if I don't start nanodlp. But as soon as nanodlp is launched, the screen goes blank. I may be using the muve distribution. Could that be the issue?
Offline
Are you going to use this display as information panel or primary display to cure layers? What happening when you run nanodlp and display calibration image? Both HDMI output and VGA displays layer or only HDMI display layer and VGA one remains black?
Offline
It displays the calibration image on hdmi and vga remains blank. I want to use vga as the information panel.
Last edited by manojd (2016-11-24 04:52:54)
Offline
Try running this version. I have disabled GPIO initialization. http://www.nanodlp.com/nanodlp.debug.tar.gz
Offline
I just tried this latest (1280). Now the HDMI is blank and the projector calibration images go to VGA.
Offline
Disable your shutter and any other gpio related features. Any GPIO related will panic the program as GPIO is not initialized.
Offline
Hi Shahin, any further thoughts on this? My vga now shows the output that is intended for the hdmi port. AFAIK I am not using the GPIO for anything in nanodlp.
Offline
I will try to make gpio initialization on demand. Is there any other issue related to this kind of display?
Offline
I will try to make gpio initialization on demand. Is there any other issue related to this kind of display?
The display works perfectly. I was doing some more research on this and found out that the issue is due to raspberry pi having only one frame buffer by default. This can be changed by recompiling the kernel, which I did, but it requires a USB based display via a displaylink adapter. So, when you output am image, are you using /dev/fb0 or is the hdmi being referenced directly?
Offline
No it not depend on framebuffer, directly calling dispmanx
Offline
No it not depend on framebuffer, directly calling dispmanx
I think that explains why the projector output goes to the default display.
Offline
Hi Shahin,
Would it be possible to have nanodlp take a parameter such as --display=5 and redirect the output to hdmi. Omxplayer successfully does this and you can use dual displays with it. This will be a very useful feature.
Thank you.
Offline
Try the beta version. You can change display number.
Offline
You are too good .
The beta works perfectly. I can now have X running onto the VGA666 and the HDMI output shows projector calibration images. Thank you so much.
Offline
Hi Manojd,
I tried without success.
Could you give me your config, i'll test it.
regards,
Offline
Pages: 1