You are not logged in.
Pages: 1
Hi,
Any chance that nano dlp can work with an asiga? Has anybody make it work?
Thanks
Hi,
I've tried to slice the same object with build version 1280 and today with the beta (1296) and I keep obtaining a similar slicing error, some edges appear cut
I tried to upload the stl file, but I'm not allowed, can I email it to you?
Best
Hi,
I've been away from the machine, kust installed a new RPi and the most recent version, so I have no idea what could have been the behavior in earlier versions
Just found out how to add attachments, hope it works, just pointing out the sort of issue I'm observing. The top slice was done with Printstudio, the bottom one with nanoDLP, same layer height
best
Hello,
I'm using build 1261, just submitted a part for slicing and some layers exhibited strange cuts in some edges. This happened in every profile I've created (different layer heights, with or without dimming) in a very consistent manner, across the same part regions. The same part sliced in printstudio didn't present the same defect.
I would like to attach the stl file and a slice example to better show what I mean, but don't find a way to attach documents here
any help is appreciated
thanks
now it is working, just plugged back the camera, it was weird because it was in fact taking pics and saving them in the respective folder, but not showing them in the browser
thanks
I've plugged in a camera, it works fine
is it possible to have the last picture taken shown in the dashboard while printing?
Hi,
my build file does say "muve3dls", so I suppose the change worked
but as I said earlier, usually this change would upload some specific "printer profiles" and the inclusion of some custom Gcode to work with the mUVe printer.
thanks
there was no event reported on the dashboard application log
something I didn't mentioned earlier, I also tried to use the update instructions on the muve documentation, through ssh, but ended up in the same 1149 version.
How do I know in which distribution am I? I can only tell by the uploaded printer profiles and some Gcode in the hardware setup
pi@raspberrypi:~ $ ls -l /home/pi/printer/db/
total 20
-rw-r--r-- 1 root root 1637 Apr 29 13:57 buttons.json
-rw-r--r-- 1 root root 284 Apr 29 13:14 calibration.json
-rw-r--r-- 1 root root 1739 May 3 13:44 machine.json
-rw-r--r-- 1 root root 1435 May 3 13:50 plates.json
-rw-r--r-- 1 root root 3519 May 3 14:02 profiles.json
pi@raspberrypi:~ $ ls -l /home/pi/printer/distro/muve3d/opt/db/
total 16
-rw-r--r-- 1 pi pi 1984 Apr 25 15:21 buttons.json
-rw-r--r-- 1 pi pi 307 Apr 25 15:21 calibration.json
-rw-r--r-- 1 pi pi 1901 Apr 25 15:21 machine.json
-rw-r--r-- 1 pi pi 2779 Apr 25 15:21 profiles.json
> Keep dashboard open on a tab, change distribution, checkout dashboard error reports, do you see anything important?
you mean, check the Application log on the nanoDLP dashboard, while changing distribution?
Good morning,
I've recently uploaded nanoDLP to my microSD card, build 1149, I would like to change the distribution to muve3D, but it apparently doesn't happen
I ended up inserting some of the necessary gcode and it is working fine, but just don't know if I'm missing something from that distribution
thanks
Hi,
I have one comment and question about these issues
- I think the feature proposed by mandreas is quite interesting, I've also been thinking about a work hypothesis which involves configurable exposure times per different layers. I was also thinking that you could take advantage of the already implemented feature of applying blackouts. Instead of a 100% full blackout cover, one could define a cover with a configurable % of either exposure time and/or dimming, and why not, define as well to which layers it should be applied. Just a thought, have no idea how easy/hard these things are to implement
- my question is about the dimming feature, if I got it right, what are defining a perimeter with a custom thickness and a dimming percentage in the center of the object slice, right? similar to the FDM perimeter/infill features?
congrats on the great software, Shahin
best
yes, I did upload the muve3d patched software
in the meantime, I've restarted the RPi through terminal
I was blocking the gcode line with the G1 Z0 command (I don't want Z to go up, it is intentional) and the test ran well
As you mentioned, I suppose that was the message nanoDLP was waiting for
As far as I remember, it usually happens when I'm tuning the printer profiles, usually it is related with some mistake I have in my gcode, that likely blocks the work
Yes, I think enabling the option to force the print to stop, could be useful, there wouldn't be much room for accidents, if it was inside the setup window
thanks
I've been testing some printer profiles and sometimes it fails to start the job or for some reason it gets stalled in the beginning, after homing the printer. The thing is that it doesn't accept the "stop print" command. I can navigate normally through the menus, but it also doesn't accept the restart or shut down pi commands. It just stays stuck. Apparently, waiting from some order from the controller
I'm using muve3d version 1039
Here's the log below;
Error - 2016/03/11 14:52:12.486369 Access Control Printing in Progress -
Error - 2016/03/11 14:51:58.767828 Access Control Printing in Progress -
Warning - 2016/03/11 14:45:29.074618 Hardware Settings saved but critical settings could not switched in the middle of print. If you need all settings to be take effect stop the printer and submit again.
UNKNOWN 2016/03/11 14:42:31.824997 {"Layer":"-","module":"Terminal","level":"Info","action":"Data Received","msg":"ok
UNKNOWN 2016/03/11 14:42:31.824473 {"Layer":"-","module":"Terminal","level":"Info","action":"Data Received","msg":"ok
Info - 2016/03/11 14:42:18.743721 GCODE Waiting Waiting for done message from controller
Info - 2016/03/11 14:42:18.743364 GCODE Transfering Data ;M280 P2 S90; used with shutter wired to the ramps↵;M650 D4.0000 S1.0000↵;M651↵;G1 Z0.1↵
Info 1 2016/03/11 14:42:18.739899 Z-Axis Moving to Layer 1 -
Info - 2016/03/11 14:42:18.739194 Projector Turn On The Projector -
UNKNOWN 2016/03/11 14:42:18.734209 {"Layer":"-","module":"Terminal","level":"Info","action":"Data Received","msg":"ok
Info - 2016/03/11 14:42:18.726073 Shutter Shutter Close -
Info - 2016/03/11 14:42:18.725844 Image Clear Screen -
Info - 2016/03/11 14:42:18.725386 Projector Turn On The Projector -
Info - 2016/03/11 14:42:18.725068 GCODE Transfering Data ;M280 P2 S0; ramps wired shutter↵M650 D5 S5 ↵G28↵G91↵
UNKNOWN 2016/03/11 14:41:55.888400 {"Layer":"-","module":"Terminal","level":"Info","action":"Data Received","msg":"ok
I'm sorry Shahin, I didn't take notes of the changes I've made
I followed your option 1 instructions, somehow, the shutter was closing during prints, which was weird. I made a few more modifications and trying to root the problem, but I didn't try that hard nor it was that systematic. I don't think it was related to nanoDLP, more related to how I was writing my instructions.
sorry for not being that helpful in this case
Thanks for the quick reply,
I tried option 1, involved less changes, but I struggled a little bit with getting it right
I moved to option 2, the wiring was much simpler than I expected and it is working great.
It also improved the pauses before/after printing, now closing the shutter, while in pause. Maybe it was possible to set it up like that while connected to the ramps, but I didn't look over that
thanks again
Hi,
I like this new feature.
But I would like that the shutter would only open after the warm up period, just before printing the first layer, I think it would be helpful
I currently have installed the build 1039 of the muve3d version, with the shutter connected to the arduino board
thanks
Thanks Shahin,
I've been learning my ways around SSH. I've seen the data and file system of nanoDLP, I've found the info I was looking for
If I have any suggestion on how to improve any aspect, I'll come back to you
thanks a lot
Hi there,
I'm not sure if some sort of report/record of each print is already available, I couldn't find it
There's the export plate option, but as far as I could understand is the same file we previously uploaded, right?
I would like to have all the parameters used during one given print; in each layer;
I was imagining a CSV file with all the printer profiles parameters, for example. where we could easily spot any changes made during the print or due to some conditional order that we may have inserted
the image slice I don't see that important that is included, but maybe the data you extract from it, like the pixel count, solid areas, etc
I think this would be useful to further understand how all these parameters impact the printing
but also to be able to replicate the exact same print if needed
thanks
best wishes
João
Thanks Shahin,
then, @muve3d, could you have this information available? I mean, each time a new version for the muve is out, could you acknowledge it somewhere, like on the Instructions document
thanks
Hi there,
- Does a new release of nanoDLP also means the muve3D version was updated? I currently have the 988 build installed
- When updating the version, what happens to the printer profiles and uploaded plates? are they overwritten or kept in the new version?
thanks
Pages: 1