You are not logged in.
- Topics: Active | Unanswered
#26 Bug Reports » Lamp Hours » 2016-10-03 10:09:47
- Xmike
- Replies: 19
#27 Re: Bug Reports » Servo Signal Length » 2016-10-02 20:23:24
I have already tried. Unfortunately the behavior persists.
#28 Bug Reports » Servo Signal Length » 2016-10-02 17:30:51
- Xmike
- Replies: 3
I now changed controlling of the shutter from Ramps to GPIO of RPi.
With Ramps-Board I had lot vibrations.
But NanoDLP ignores the "Servo Signal Length".
The Projector begins to exposure at the same time when the shutter begins to open.
The shutter need about 500ms for complete opening.
In "Projector Calibration"->"Shutter Open" / "Shutter Close" I can recognize this "Servo Signal Length", but not during printing.
#29 Re: Help and Support » X-direction Stepper Motor » 2016-09-13 18:01:05
Although it is a different issue , but here you can see my G-Codes:
http://www.nanodlp.com/forum/viewtopic.php?id=57
#30 Re: Help and Support » X-direction Stepper Motor » 2016-09-12 19:24:38
I have installed this firmware
https://github.com/mUVe3D/Marlin-mUVe1DLP-Running
#31 Re: Help and Support » X-direction Stepper Motor » 2016-09-12 16:19:10
@color
I do it that way. I control my X-axis only with G-code and add each to a [[WaitForDoneMessage]
#32 Re: Feature Requests » manually input of "Lamp Hours" » 2016-08-24 16:45:14
Sorry for the late reply, I was not present.
In the log I can not see anything of the processing the lamp hours,
only the entries "Curing for xxx seconds" are available for the projector.
#33 Re: Feature Requests » manually input of "Lamp Hours" » 2016-08-22 16:09:28
I have made some test inputs.
It seems that the answer *000 is " OK " and *001 is " NOT OK " means .
The return value 0389 are then the lamp hours
#34 Re: Feature Requests » manually input of "Lamp Hours" » 2016-08-21 10:27:55
The projector must be turned on, not standby, then i get this response:
#35 Re: Feature Requests » manually input of "Lamp Hours" » 2016-08-20 16:39:52
Is it possible to show the Lamp Hours on dashboard, if successful queried ?
Here the terminal output:
#36 Feature Requests » manually input of "Lamp Hours" » 2016-08-20 14:16:19
- Xmike
- Replies: 8
Unfortunately "Query Lamp Hours" with my projector does not work ( acerH6510BD ).
But I would like avoid having constantly to adjust the exposure times of all my printer profiles.
It would be therefore useful if you can enter the Lamp time manually to get "Lamp Brightness Decrease",
and let the printer profiles unchanged.
#37 Re: Feature Requests » Auto Mask Generation » 2016-08-20 11:08:34
@lcluff2000
May I ask what sensor you are using . With my UV sensor unfortunately I have no good experiences.
Since the DLP chip emits the light at a certain frequency,
the measurement results of my sensor at the same measuring point are very different.
#38 Re: Everything else » Successful Prints » 2016-07-27 07:37:01
A view of this page might answer your question.
#39 Re: Bug Reports » NanoDLP v.1198 crashes » 2016-07-22 09:41:44
Hello Shahin,
To reproduce the problem, I do this:
Projector is already turned on, then
"Setup" -> "upgrade to the beta version",
then as shown in my movie, turn on the projector again.
Afterwards I have to restart RPi.
If I try the latest stable version with "Setup" -> "Upgrade to the latest stable version", it changes nothing, unfortunately.
The latest stable version for me was "Build 1194"
#40 Bug Reports » NanoDLP v.1198 crashes » 2016-07-21 18:53:44
- Xmike
- Replies: 3
Hello Shahin,
I have upgraded NanoDLP to the version 1198.
Now NanoDLP crashes immediately, if it try to control the projector with serial interface.
#41 Re: Bug Reports » Slicer makes hollows » 2016-06-18 10:11:13
I have now increased the value of "Post Sides" to 32 , but unfortunately that did not help , here are the results.
#42 Re: Tips, Tricks and Tutorials » Mask Generation » 2016-06-11 12:06:10
Here is described how to make a mask by means of uv sensor.
http://www.buildyourownsla.com/forum/vi … f=5&t=3684
I , however, was not successful with both a UV sensor or a light sensor.
With the printing of cylinders over the entire platform and its dimensional variation I could then create a working mask,
with the help of the software Rhino .
#43 Help and Support » Query Lamp Hours » 2016-06-11 10:17:00
- Xmike
- Replies: 1
Hello Shahin,
my projector is a Acer H6510BD and for the Serial Command i write into "Setup" - > "Query Lamp Hours" * 0 Lamp
and in "Lamp Brightness Decrease" 2.5
But I can see nowhere the Lamp Hours.
Even a change in the exposure times I could not notice. It seems as if nothing happens.
Should not be anywhere displayed the Lamp Hours?
#44 Re: Bug Reports » Slicer makes hollows » 2016-06-04 07:10:48
I would like the STL file upload, but the file size (zip) is a little more than 1MB and the attachment size has to be < 1MB
#45 Bug Reports » Slicer makes hollows » 2016-06-01 16:44:39
- Xmike
- Replies: 21
Hi Shahin,
the integrated slicer makes hollows in the supports.
In the picture you can see a layer where the supports are shown, generated with meshmixer.
Please compare the slice generated with Asiga Stomp and shown with Asiga Sleece, and the slice generated with nanoDLP.
It seems that overlaps are removed.
#46 Feature Requests » Choose the origin when adding a Plate » 2016-05-28 16:20:05
- Xmike
- Replies: 2
Hello Shahin,
It would be good if one could choose the origin for the centering of the layers, while adding a Plate.
I use Meshmixer for preparing the print job, where the default origin is in the middle of the platform.
It is possible to change the origin in Meshmixer, but that does not work somehow.
If I want to keep the arrangement in NanoDLP, I currently load the file in ASIGA Stomp and make there an offset of the origin to the corner,
before I load it in NanoDlp without "Auto Center".
It would be good if I could choose the origin between "Auto Center" , "Bottom Center" and "Bottom Corner" when adding a Plate,
then an origin offset is not anymore necessary.
#47 Re: Help and Support » Printer process has terminated » 2016-05-09 09:55:32
Hi Shahin,
nanodlp runs on raspian lite.
The only thing I additionally installed is webmin.
In "printer.log.1.gz" I can see, that the last Layer was printet at 2016/05/08 00:16:45,
it was also the last entry in this log-file, then a new Log-file "printer.log" was created.
>crontab -e -> "no crontab for pi - using an emty one"
>sudo crontab -e -> "no crontab for root - using an emty one"
Is Plymouth needed, or can I disable it ?
#48 Help and Support » Printer process has terminated » 2016-05-08 09:52:25
- Xmike
- Replies: 3
The printer process has unfortunately terminated at Layer 1285, but Raspberry ran normal.
After the reboot nanodlp stands at Layer 1286.
What I noticed in the logs, apparently exactly on this layer a Logrotate was made from printer.log to printer.log.1.gz
LOG:
nanodlp.debug.-1449308449.zip
I really do not know what happened there . In syslog , the line is
"May 8 00:17:28 raspberrypi systemd[1]: Starting Wait for Plymouth Boot Screen to Quit..."
suggesting that a reboot has been. But this was not the case.
#49 Re: Bug Reports » Some Issues » 2016-05-04 17:02:36
Hi Shahin,
2) Please have a look on the Layer numbers in the Messageboxes (Build 1151):
3) Build 1155
The only GCode that appears in the terminal is the Bootup - code otherwise no movement is possible .
#50 Bug Reports » Some Issues » 2016-05-03 20:22:16
- Xmike
- Replies: 3
Hi Shahin,
I have multiple problems in Build 1151 and Build 1155.
Build 1151:
1 ) In the menu "Printer Profile" -> "Mask File" , the options "Use if Available" and "Ignore" are selectable.
If I select "Ignore", then after saving still appears only "Use , if Available".
2 ) When I stop the print and afterwards continues with "Resume Print", then there appears a Messgebox
"Are you sure ... print from Layer X ?".
Depending on whether "Resume Print" from the main page or from "Plates" will be startet,
a different layer number appears.
3) After installing Build 1155 my printer doesn't work anymore.
I can not move the axis, neither with "Z Axis Calibration" nor with a manual GCode.
When I type a command in the GCode window, in the Terminal does nothing appear.
When I again restore the previous version (Build 1151) then the printer works again.