You are not logged in.

#2 Re: Tips, Tricks and Tutorials » Touch screen for NanoDLP » 2017-11-14 15:08:30

juliendelnatte wrote:

It's what I said, I looked at your HMI and your code. It's not the name of the component is sent to the program but the ID. and the event is "click_b"+id. So I sent you the fix

Oh my goodness.  Is that it?  It uses the id instead of objname?   /me smacks his head

#3 Re: Tips, Tricks and Tutorials » Touch screen for NanoDLP » 2017-11-14 14:29:15

juliendelnatte: 

Take a look at "2.4_LittleRP.HMI", which is the one I modified for my LittleRP resin printer.  If you look at home.js, you will see four new buttons with objnames c0, c1, c2, and c3. 

I then reference them as I did in the following two files:

https://github.com/sgraber/TouchScreen- … es/home.js

https://github.com/sgraber/TouchScreen- … es/home.js

The /button/press/0 event calls an M8 gcode which disables my stepper.  The /button/press/1 event calls M9 gcode which enables the stepper.  Pressing either of those buttons do nothing to my stepper motor at all.  If I log into http://localhost/ I can click the button on the webpage that calls these two urls and they work.

I'm at a loss why it's not working.

#4 Re: Tips, Tricks and Tutorials » Touch screen for NanoDLP » 2017-11-14 13:55:38

Would someone more knowledgeable care to look at my mods to the nextion 2.4" touchscreen? 

https://github.com/sgraber/TouchScreen-For-NanoDLP

Based on what I can tell, I have modified it appropriately, but none of the 4 buttons I placed in the home.js file work.  They show up on the Nextion screen and I can press them, but they don't call the proper URLs, which are /button/press/0 and /button/press/1.  Thank you!!!

#5 Re: Tips, Tricks and Tutorials » I added a button on nextion to send the Gcode "M806" to the RAMPS » 2017-11-02 21:03:31

Ok, I've used the Nextion Editor to add buttons to the home screen (id's are b0 and b2) and I've adjusted the home.js file to include the following:

                this.addListener("click_b0", function (e) {
                  _this2.changePage("/button/press/0");
                });

                this.addListener("click_b2", function (e) {
                  _this2.changePage("/button/press/1");
                });

From what I see, this should allow me to press on these two buttons and get a changePage call to my buttons I made in NanoDLP.

I assume I hit compile and compiling adds all of the .js files from the repository into the .tft?

#7 Re: Tips, Tricks and Tutorials » I added a button on nextion to send the Gcode "M806" to the RAMPS » 2017-10-26 21:04:37

Shahin wrote:

You need to send post request from nextion side to nanodlp /gcode path.

Is there an example of a proper post request that we could use?

#8 Re: Tips, Tricks and Tutorials » I added a button on nextion to send the Gcode "M806" to the RAMPS » 2017-10-26 13:07:42

I'm looking at the source available at https://github.com/Tibus/TouchScreen-For-NanoDLP

I do not see a /gcode directory.   I, too, would like to add a custom button or two to the Nextion touchscreen.

#9 Re: Tips, Tricks and Tutorials » Touch screen for NanoDLP » 2017-09-07 14:15:38

leaphr wrote:

Hi,
It is so excited to finally see a computer-less solution for Nanodlp, so I just got my new nextion screen and tried as everything you list on Github, but I couldn't get anything displayed except "Connecting to printer..." message. It was so frustrating after trying for all afternoon.
I checked the output log in nextion by using WinSCP, and there is a looping of "error opening port  /dev/ttyAMA0 retry in 2 sec". Then I just found this article(http://www.briandorey.com/post/Raspberry-Pi-3-UART-Boot-Overlay-Part-Two) which including the method to enable /dev/ttyAMA0 of almost all version of Raspberry Pi, anyone who has the same problem as me could follow the instruction of your version on Raspi in it.
I'm using the latest verion of Raspberry Pi 3B, so for me, it can be done in just 5 steps:
1:run this in the terminal:sudo systemctl disable hciuart 
2:sudo nano /lib/systemd/system/hciuart.service  and change every "ttyAMA0" to "ttyS0", there will be 2 of them in total, then save and exit.
3:sudo nano /boot/config.txt   and add "dtoverlay=pi3-miniuart-bt" to the end, save and exit.
if you don't have "pi3-miniuart-bt" in your /boot/overlays, just download it here:http://ukonline2000.com/wp-content/uploads/2016/03/pi3-miniuart-bt-overlay.zip, and put "pi3-miniuart-bt-overlay.dtb" into /boot/overlays
4:sudo nano /boot/cmdline.txt delete "console=serial0,115200" or "console=ttyAMA0,115200"
5:run sudo apt-get update 
      sudo apt-get upgrade 
      sudo reboot 
Then finally I got it right! and thanks juliendelnatte for sharing your great work!!

Ok, I'm trying to get my 2.4" Nextion screen working with my LittleRP / DLP printer on a Pi 3.  I followed the above and now have successfully gotten the nextion display to function.  It shows the GUI and I can successfully us it to start a print.  However, my DLP will no longer display the layer images during printing.  The display just stays completely black.  Any idea what might have caused this in the above instructions?

#10 Re: Help and Support » Display does not blank upon booting » 2017-09-01 13:41:17

Thanks!  I'll give that a shot!

Also, this may be a silly question:  if I wanted to move my nanodlp install from one Pi to another, is it as simple as zipping up my /printer folder and moving it to the new Pi?  Use-case:  let's say I want to use a larger SD card.  I download the pre-configured NanoDLP Pi image, burn it to a SD card, expand the filesystem, then move the /printer folder over and that's it?

#11 Re: Help and Support » Display does not blank upon booting » 2017-09-01 05:54:09

Thanks but that did not work.:(  I started see the same problem...

#12 Help and Support » Display does not blank upon booting » 2017-09-01 04:52:24

sgraber
Replies: 5

Ok, I was messing around with the cmdline.txt and config.txt files and now when my Pi boots, the display no longer blanks.  sad  What in the program files controls this and how do I fix my problem?  Here's a picture of what I'm seeing:  https://goo.gl/photos/onZkmbbUCnYek54c7  It's really washed out, but usually the display blanks at about that point in the boot process.  NanoDLP boots up just fine, but the screen just won't blank for me any longer.  Any ideas?  I should mention that when the screen should be blank between layers, it goes back to that image that I linked instead of a black screen.

#13 Re: Bug Reports » NanoDLP crashes when model too large » 2017-05-05 12:50:44

FWIW I pretty much exclusively use Asiga Stomp to make .slc files now which I then upload to NanoDLP.

#14 Re: Everything else » NanoDLP complexity » 2017-03-27 17:17:28

Shahin wrote:

It is on /boot
Point is that as /boot is fat32. If you put it on windows you can freely edit nanodlp-network.txt by any text editor.

Awesome!

Quick question on functionality:  is it setup so that if the Pi does not see a network it knows, will it then create an Access Point so that someone could log in wirelessly?  I've seen certain 3D printer controllers (Astroprint?) have this functionality.

#15 Re: Everything else » NanoDLP complexity » 2016-11-29 14:34:54

Shahin wrote:

Hi Olivier,

Sure it is possible but I am not sure if it is a good Idea to make it AP. They need to manually edit this file to use nanodlp WIFI to connect somewhere.

Take a look at how OctoPrint does it for FDM printers:  http://octoprint.org/download/

They have you manually edit and configure your WiFi connection by editing octopi-network.txt on the root of the flashed card when using it like a thumb drive.

I will say the one thing that drives me nuts is that I have to hardwire my Pi into my router for the first time use to get WiFi setup.

#16 Re: Everything else » NanoDLP complexity » 2016-11-29 14:30:43

This is part of the reason that I requested a way to import Printer Setup configs like we can for Print Profiles.  I share my .json resin profiles with users regularly for MakerJuice resins.  The other option is to start adding additional Printer Setup options like you have for the mUVe printer.

#17 Feature Requests » Export / Import Printer Setup » 2016-11-17 20:04:36

sgraber
Replies: 1

Hi!  Is there any chance you could implement the ability to import/export Printer Setups similar to how you have Printer Profiles?  Essentially upload/download a .json file.

#18 Bug Reports » Add Feed Rate to Z Calibration buttons » 2016-11-17 16:22:03

sgraber
Replies: 2

Hi!  Would it be possible to add feed rate gcode to the Z-calibration buttons on the Calibration tab?  A couple of us running GRBL have problems with the Z- up/down buttons not functioning.  Adding something like F200 to the gcode would fix this for us.  smile

#19 Re: Bug Reports » Raspi showing "nothing" ie NO display patterns on latest official/beta » 2016-11-10 16:36:24

Shahin wrote:

Official distribution on the raspbian website contains latest firmwares as it very up to date. 
Upgrading nanodlp to latest version will be really helpful as we could be sure it is a firmware issue.

Ok, I'll do that this weekend.  I need to get a bunch of prints done first.  smile

#20 Re: Bug Reports » Raspi showing "nothing" ie NO display patterns on latest official/beta » 2016-11-10 14:31:26

Shahin wrote:

Another solution could be downgrading firmware.

Choose an old firmware and downgrade https://github.com/Hexxeh/rpi-firmware/commits/

sudo rpi-update 17ff0bb5bb46210bad235d32589d35f951f269cf

Please, fill a bug report on github, if you could find where firmware update goes wrong.

Firmware downgrade crashed my Pi.  sad

This time, I installed the NanoDLP Pi image from the Download page (instead of using a stock Raspbian image and manually installing NanoDLP).  As of this install, the NanoDLP version is #1209.  I can confirm that this version of NanoDLP does work with the projector.  So the take-away is that there is something fundamentally different between the Download NanoDLP image and doing the manual Raspbian/wget NanoDLP install. 

I'd like to upgrade to the latest version of NanoDLP (as it looks like some threading issues were resolved), but I'm a bit nervous that if I do it'll cause that problem to reappear...

#21 Re: Bug Reports » Raspi showing "nothing" ie NO display patterns on latest official/beta » 2016-11-09 16:12:44

FWIW, I would uninstall the latest version and go back to Build #1220 and try it as I know it worked with that version on my Pi 2, but I don't see a place where previous versions of NanoDLP are available for download.

Edit:  Is there any way you could add a page to the current website for previous releases?

#22 Re: Bug Reports » Raspi showing "nothing" ie NO display patterns on latest official/beta » 2016-11-09 15:32:17

@bolsoncerrado:  No, I did not, but I will give it a shot.  I don't see how this will make a difference but I'm open to trying it.

#23 Re: Bug Reports » Raspi showing "nothing" ie NO display patterns on latest official/beta » 2016-11-09 14:42:00

Shahin:

I have the exact same problem with the latest build available for download.  If I plug the Pi 3 into a HDMI TV, I can see the bootup text scroll past when I first power the Pi.  However, if I plug it into my projector and reboot, I do not see any bootup text nor will the projector display Calibration images nor sliced images during a print. 

I'll give you the whole background:

Prior to last night, I had an old Raspberry Pi 2 running NanoDLP and I had frequent kernel panics with it - happened every 2-4 weeks.  Thinking it was the SD card, I replaced it with a new Sandisk 32GB card.  I obtained a kernel panic a week later, so I upgraded the pi to a Pi 3 with a 2A/5V power supply, Sandisk 16GB microSD card last night.  My projector is an Acer X1240, which only has a VGA port.  However, on my old Pi 2, I was successfully using a HDMI --> VGA adapter for months with NanoDLP and my LittleRP so I know the cable adapter is good.  I used the latest stock Raspbian Jessie Light September 2016 image from https://www.raspberrypi.org/downloads/raspbian/ followed by using the command line to manually install NanoDLP.  I plugged in the HDMI/VGA adapter and VGA cable, turned on the projector, and then powered on the Pi 3.  I did not observe text scrolling from the projector - nor any images at all.  NanoDLP ran fine and I accessed the Calibration tab in my browser and clicked on the Display button for each of the calibration images.  Nothing appeared from the projector.  I performed a sudo apt-get update / sudo apt-get upgrade and rebooted.  Still no change.  At this point, I'm a bit confused what is going on as it should be displaying something - even during bootup.

Any help would be appreciated!

#24 Re: Feature Requests » Temporary Lift Control on print screen » 2016-11-09 14:03:34

I was actually going to mention this exact route: 

I have this in my Stop GCODE section:

G1 Z25 F200

And I now have this in my Resume GCODE section:

G1 Z-25 F200
[Delay {25/200*60}]

Hit the STOP button on the home screen, NanoDLP stops the print and indexes up 25mm.  I hit the Resume key and the print indexes back down and starts printing again.

#25 Re: Feature Requests » Temporary Lift Control on print screen » 2016-11-08 19:02:41

Ok, I wondered if it needed a delay in there, so here's what I'd try next:

G1 Z25 F200
[Delay 10]
G1 Z-25 F200
[Delay 10]

The delays give enough time for the platform to fully extend and decend before the next command.  Try it?  This needs to go all in 1 button.

Board footer

Powered by FluxBB