You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Help and Support » Increase web interface timeout » 2017-12-09 10:54:43
I'm using build 1749 - is that the latest beta?
#2 Re: Help and Support » Increase web interface timeout » 2017-12-04 23:40:36
It errors out after about 3:30 of uploading.
#3 Help and Support » Increase web interface timeout » 2017-12-02 14:08:39
- achingbrain
- Replies: 6
Is there any way to increase the timeout on web requests when uploading large STL files?
I'm trying to upload a 70MB STL, it gets to about 60% uploaded before I see ERR_CONNECTION_RESET in Chrome. In the nanodlp logs I see:
Error POST file issue read tcp 192.168.1.82:80->192.168.1.147:57582: i/o timeout192.168.1.82 is the rpi and 192.168.1.147 is my laptop.
I can happily browse around the nanodlp web interface in another window while this happens so my WiFi connectivity seems fine.
Thanks in advance.
#4 Re: Feature Requests » Read build plate position from Grbl » 2017-08-28 11:39:20
I was thinking to add something like:
[[WaitUntilZPosition 10.000]]
and/or
[[WaitUntilZPosition [[LayerPosition]]]]
#5 Re: Feature Requests » Read build plate position from Grbl » 2017-08-28 09:42:40
I've forked the Grbl repo and added support for the M114 command - is the NanoDLP source available anywhere so I can extend it to parse the response? I'd like to make sure it works properly before submitting a PR to grbl.
I found this account but there's not much there.
#6 Re: Feature Requests » Read build plate position from Grbl » 2017-08-28 08:45:46
I think you might want to do some variable substitution in there like:
[[Until 0.100 ? <Idle|MPos:0.000,0.000,[[LayerPosition]]|FS:0,0>]]
Just as long as the comparison takes into account that [[LayerPosition]] might be 10 but the string displayed is 10.000.
As for a standard response, there is the M114 GCode command which reports the current position. This would be preferable as it's part of the protocol and the output format seems to be well specified although Grbl doesn't support it.
#7 Feature Requests » Read build plate position from Grbl » 2017-08-27 21:23:17
- achingbrain
- Replies: 5
Grbl v1.1 reports the current machine position when the `?` command is sent over the serial port.
E.g. say the build plate is at Z0 and I move it to Z10, then enter ? a few times. The serial traffic looks like this (minus all the 'ok' messages):
G1 Z10 F100
?
<Run|MPos:0.000,0.000,1.180|FS:100,0|WCO:0.000,0.000,0.000>
?
<Run|MPos:0.000,0.000,2.673|FS:100,0>
?
<Run|MPos:0.000,0.000,4.098|FS:100,0>
?
<Run|MPos:0.000,0.000,6.383|FS:100,0>
?
<Run|MPos:0.000,0.000,8.265|FS:100,0>
?
<Idle|MPos:0.000,0.000,10.000|FS:0,0>The machine position is reported above in the format Mpos:x,y,z
This could be a better option than delays or [[WaitForDoneMessage]] etc for synchronising movements.
#8 Re: Help and Support » Calibration plate preview wrong? » 2017-06-16 21:07:06
Ah, right, makes more sense now thanks! It seems the blank layers in the plate mentioned above were caused by the pillars being outside of the printable area - clearly my settings were wrong.
I've tweaked the pillar width & sheer values and now the plate looks like it might actually print something useful:
In case anyone else has a similar problem in the future, these are the settings that produced the above plate:
#9 Re: Help and Support » Calibration plate preview wrong? » 2017-06-12 19:07:01
Hi Shahin, thanks for the speedy reply.
Do my settings look reasonable?
Just seems odd that there are only 12 layers in the calibration plate and the last 6 are completely black. Or is the preview not showing me the whole layer?
#10 Help and Support » Calibration plate preview wrong? » 2017-06-12 18:11:01
- achingbrain
- Replies: 5
I've used the following settings for the calibration plate:
But the layer preview shows this sort of thing:
I'd kind of expected to see little dots like in the changelog - any ideas what am I doing wrong? Am I doing anything wrong?
My projector settings are:
I am running build 1447.
Thanks in advance.
Pages: 1