You are not logged in.
Pages: 1
Ah!
If submitting an STL DIRECT to nanoDLP, it creates the sliced images with the mask applied.
If submitting a zip file from nonoslicer to nanoDLP, it DOES NOT apply the mask to the sliced images.
Shahin, is there anything in the pipeline to fix this? I find slicing on the RPi to be a gigantic pain. I really like using nanoslicer on the Mac, as I have written a perl script that will take all of the STLs in a directory and produce three output files each sliced in the three main Z resolutions I use (Very handy!)
Cool, thanks. Is there any way of projecting just the mask to ensure that it's close to what is required?
Hi
I'm using Nanoslicer on a Mac to slice as the Raspberry Pi just can't handle it.
Am I correct in believing that the mask will have no effect on the generated plates when I add them to nanoDLP on the RPi?
Also, my source files are STLs - If I upload these directly, am I correct in believing that the mask will have no effect when slicing?
ran the following:
nohup ./nanodlp &
./nanodlp &
./nanodlp
Nothing made any difference at all
root# ./nanodlp &
2017/07/11 20:04:33.759517 {"Layer":"0","module":"Hardware","level":"Notice","msg":"Initializing build # 0 - generic"}
2017/07/11 20:04:33.759803 {"Layer":"0","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
⇛ http server started on [::]:8080
As already stated, it's a clean install. It's impossible to upload an STL as a few seconds after starting the process, it stops responding
Yes, it's the Mac version and a clean install. ps -ef shows the process as running. Even curl fails:
curl -vvv http://127.0.0.1:8080
* Rebuilt URL to: http://127.0.0.1:8080/
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET / HTTP/1.1
> Host: 127.0.0.1:8080
> User-Agent: curl/7.51.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Curl_http_done: called premature == 1
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
Hi all
I start nanoDLP from the terminal (either logged in as a user and running run.sh or logged in as root and directly running the binary) and it works for 5 seconds then it stops responding and I start seeing the following in the logs:
default 18:15:22.017087 +1200 kernel process nanodlp[89199] caught waking the CPU 49103 times over ~18 seconds, averaging 2613 wakes / second and violating a limit of 45000 wakes over 300 seconds.
default 18:15:22.035944 +1200 symptomsd Received CPU wakes trigger:
nanodlp[89199] () woke the CPU 49103 times over 18.79 seconds (average 2613/sec), violating a CPU wakes limit of 45000 over 300 seconds.
default 18:15:22.037959 +1200 symptomsd Found DiagUsageStats for RESOURCE_NOTIFY of EXC_CPU_WAKE : NON-FATAL (nanodlp) - <DiagnosticCaseUsage: 0x7f8040224840> (entity: DiagnosticCaseUsage; id: 0x4900008b <x-coredata://5E2726C4-920E-4DD8-A522-784D90CD9691/DiagnosticCaseUsage/p292> ; data: {
casesAccepted = 5;
casesSeen = 5;
domain = "RESOURCE_NOTIFY";
"interarrival_mean" = "617.0155860036612";
"interarrival_var" = "61926.21579847985";
lastAccepted = "2017-07-11 05:52:23 +0000";
lastSeen = "2017-07-11 05:52:23 +0000";
process = nanodlp;
subtype = "NON-FATAL";
type = "EXC_CPU_WAKE";
})
default 18:15:22.038014 +1200 symptomsd Reached limit of 5 RESOURCE_NOTIFY reports for nanodlp. Disallow report.
Pages: 1