You are not logged in.
Pages: 1
I used the default, 8080. You will need to have nanoDLP running in the remote machine as well, so you will have a total of 2 instances of it running: assuming you are using a rPi and a Windows machine, once they are you will be able to access each of them in your browser, and watching them interacting when the remote slicing process kicks in.
You can do that from the SETUP page on nanoDLP. The parameter is almost at the bottom of the page, if I remember correctly. If you do not see that option, you might need to update it to a more recent version to be able to use remote slicing.
It's also worth mentioning that I have been using this feature for the last week and it works like a charm!
Hey, Wisar! Let me know if the remote slicing works for you. It is not working for me (I updated the rPi3 version to the latest one, but not the Windows one... could be that?).
Thanks for the support, Shahin! And I'm with Will: I would me more than happy to contribute in a monetary way to the nanoDLP development.
--- EDIT ---
Nevermind! The IP of the Windows machine was incorrect! The remote slicing is working perfectly.
Hey, Shahin! Thanks for the quick answer. I have been running more tests and the results are not consistent: the first run it did reslice the STL after bringing the sliced images from the Windows machine. However, in subsequent ones the system worked perfectly. I tried with several resin profiles, just in case, but everything looks good. I could not savage the log from the first run, but next time it happens, I'll attach it here.
Thanks!
Hi!
I am using nanoDLP on a Raspberry Pi 3, and I have installed the Windows version as well. When doing remote slicing (sending the order from the RPi to Windows), the two instances of nanoDLP communicate successfully, and the slicing is done and sent back to the Pi. However, it looks like instead of just decompressing the PNGs from the ZIP it is redoing the slicing, since the temperature on the Pi goes from 40ºC to 80ºC, and I get messages in the log about the geometry on the .STL file (contained in the ZIP as well). Should the Pi instance skip this, since the slicing has been done remotely?
I confirmed this issue with another user that saw the same behaviour. Just wanted to leave this here in case this is something that can be addressed in the future.
Thanks a lot, and keep up the good work!
Pages: 1