You are not logged in.
Pages: 1
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.
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.
No it not depend on framebuffer, directly calling dispmanx
I think that explains why the projector output goes to the default display.
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?
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.
I had the same issue. Problem was with the "Waitfordonemessage" commands in gcode. The grbl 0.8c that I am using does not seem to be compatible with the RAMPs sync module in nanodlp. Remove those commands and see if it works. You may want to put a delay instead.
I changed the printer profile to one of predefined and also removed Waitfordonemessage from gcode. That has done the trick. I had noticed that the ramps sync module was not able to recognize the ok messages from grbl. I am now able to simulate the entire print job.
This is what I see once the print is initiated:
Notice 1 2016-11-26 00:42:13.967548 Projector Projector on
Debug 1 2016-11-26 00:42:13.967409 Shutter Shutter Close
Debug 1 2016-11-26 00:42:13.96729 Image Clear screen
Notice 0 2016-11-26 00:42:13.94763 Projector Projector on
And after a while, there is a fault (there is lot more in the output, this is just the tail end of it):
goroutine 69621 [runnable]:
syscall.Syscall(0x6, 0x11, 0x0, 0x0, 0x0, 0x0, 0x0)
/usr/local/go/src/syscall/asm_linux_arm.s:17 +0x8
syscall.Close(0x11, 0x0, 0x0)
/usr/local/go/src/syscall/zsyscall_linux_arm.go:296 +0x44
os.(*file).close(0x10c498b0, 0x0, 0x0)
/usr/local/go/src/os/file_unix.go:140 +0x54
os.(*File).Close(0x10b6e3f8, 0x0, 0x0)
/usr/local/go/src/os/file_unix.go:132 +0x54
io/ioutil.WriteFile(0x4d8d60, 0x12, 0x10c8d7a0, 0xd1, 0x103, 0x1b6, 0x0, 0x0)
/usr/local/go/src/io/ioutil/ioutil.go:85 +0xdc
main.jsonSave(0x4d8d60, 0x12, 0x4bed70, 0x6929b0)
/home/pi/printer/app/db.go:543 +0x20c
main.(*StatusStruct).Save(0x6929b0)
/home/pi/printer/app/db.go:471 +0x64
created by main.setLayer
/home/pi/printer/app/printing.go:243 +0x9c
trap 0x6
error 0x0
oldmask 0x0
r0 0x0
r1 0x58e
r2 0x6
r3 0x0
r4 0x76d54094
r5 0x76a49460
r6 0x0
r7 0x10c
r8 0x1
r9 0x76baa6d0
r10 0x109005a0
fp 0x674948
ip 0x76a49920
sp 0x76a48a88
lr 0x76c43f44
pc 0x76c43f70
cpsr 0x20000010
fault 0x0
Would there be any reason why nanodlp does not go past Layer 1 when print is initiated. The RAMPs communication is OK. The gcode for start of print goes through, but there is no movement in the stepper motor. And the print does not progress. I do not have a projector attached yet, just an hdmi lcd. z axis calibration works just fine and I can move the stepper in either direction.
When trying to submit changes on the Setup page, it shows an error message that says "please enter value no less than 500.". The page does not complete the submit action. The message is displayed at top left corner of the screen.
I just tried this latest (1280). Now the HDMI is blank and the projector calibration images go to VGA.
It displays the calibration image on hdmi and vga remains blank. I want to use vga as the information panel.
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?
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.
RogerP, it would be nice if you could tell us how you did it. So far, I have my VGA666 board installed into the RPI. I can see the output and also startx, but without nanodlp. The moment nanodlp is started, it takes control of the GPIO port and the display goes blank.
I got it to work, but it wasn't that easy. My WiFi doesn't work unless nanodlp is started. So, I had to connect it through a wired connection first and then enable WiFi.
I clicked on the "Terminate Wifi" connections and now my wifi is permanently disabled. How can I enable it?
I am trying to avoid the use of a networked connection to the pi. I will see how it performs with the x server. BTW, is there a command line interface to nanodlp? This could be useful to fire up print jobs.
I am trying the same thing. I plan on connecting the display using VGA GPIO adapter. I am still waiting on the VGA adapter to arrive. So far, I have tested the display in HDMI mode and with projector calibration images. It shows the image but it is zoomed in. I am logging into the raspi through my PC. However, once the VGA gets connected, it should be a localhost via the graphic interface through the touchscreen and a remote keyboard. I just hope that the processor is fast enough to handle everything, the projector / arduino and the X11 interface.
Pages: 1