You are not logged in.

#76 Re: Help and Support » Projector exposed too early » 2016-04-10 20:05:00

I have now installed the new version, unfortunately, nothing has improved.
Apart from the "Z_move_comp" answer of the firmware that me still
a little confused, the mechanical movements are actually correct.
In my opinion, the main problem is, that the projector does not wait until the block "Before Each Layer" has been processed

#77 Re: Help and Support » Projector exposed too early » 2016-04-09 10:54:32

I have downloaded the Marlin-Version two weeks ago.

#79 Re: Help and Support » Projector exposed too early » 2016-04-08 12:28:08

I have changed the GCode, but the exposure problem do exist futher.
With delays i could change the exposure timing of the Layers after the first Layer,
but for the first Layer it will be ignored.
If i have a look at the terminal and compare it with the movements from my printer,
I sometimes think that the returned Z_move_comp command
from the firmware is send at the begin of the movement and not at the end.
I made a gif of the terminal output:
Terminal.gif

Now my GCodes are:

GCode - Start of Print:
==========================
M203 X2 Y10 Z7
M201 X10 Z40
M204 X0.1 Z0.1
G21
G91
G1 Z-1 F90
G4 P100
[[WaitForDoneMessage]]
G1 Z300 F90
G4 P100
[[WaitForDoneMessage]]
[[Delay 5]]
G90
G92 X-9.5 Z123.4
[[PositionSet 123.4]]
G1 Z20 F400
G4 P100
[[Delay 20]]    <<<<<<<<<<<<<<<<<<<<<< Here I tried to prevent the premature exposure, but seems to be ignored
[[WaitForDoneMessage]]
G1 Z5 F90
G4 P100
[[WaitForDoneMessage]]
=========================

Before Each Layer:
=========================
G1 X0 F150
G4 P100
[[WaitForDoneMessage]]
G1 Z[[LayerPosition]] F40
G4 P100
[[Delay 10]]    <<<<<<<<<<<<<<<<<<<<<< with this delay I got to prevent the premature exposure, but not for the first Layer
[[WaitForDoneMessage]]
[[PositionSet [[LayerPosition]]]]
=========================

After Each Layer:
========================
G1 X-4 F50
G4 P100
[[WaitForDoneMessage]]
G1 Z{[[LayerPosition]]+[[ZLiftDistance]]} F20
G4 P100
[[WaitForDoneMessage]]
[[PositionChange [[ZLiftDistance]]]]
========================

#80 Help and Support » Projector exposed too early » 2016-04-04 20:12:27

Xmike
Replies: 20

Hi,
My printer uses an Arduino and Ramps.
Unfortunately, the projector begins too early to expose.
I could partially overcome the problem by increasing the "Wait BeforePrint"  to 10 sec
in "Normal Layers" as well as in "Burn-in layer".
But there is further the expose problem in the first layer .
I have attached the terminal output and there I marked the Position where it happens.
My GCodes are:

GCode - Start of Print:
==========================
M203 X2 Y10 Z7
M201 X10 Z40
M204 X0.1 Z0.1
M84 S0
G21
G91
G1 Z-1 F90
G1 Z100 F90
[[Delay 10]]
G90
G92 X-9.5 Z123.4
[[PositionSet 123.4]]
G1 Z20 F400
[[WaitForDoneMessage]]
G1 Z10 F90
[[WaitForDoneMessage]]
=========================


Before Each Layer:
=========================
G1 X0 F150
[[WaitForDoneMessage]]
G1 Z[[LayerPosition]] F40
[[WaitForDoneMessage]]
[[PositionSet [[LayerPosition]]]]
=========================


After Each Layer:
========================
G1 X-4 F50
[[WaitForDoneMessage]]
G1 Z{[[LayerPosition]]+[[ZLiftDistance]]} F20
[[WaitForDoneMessage]]
[[PositionChange [[ZLiftDistance]]]]
========================



Terminal output:
========================
M203 X2 Y10 Z7
M201 X10 Z40
M204 X0.1 Z0.1
M84 S0
G21
G91
G1 Z-1 F90
G1 Z100 F90
ok ok ok ok ok ok ok Z_move_comp ok Z_move_comp echo:endstops hit: Z:123.40

G90
G92 X-9.5 Z123.4

G1 Z20 F400
                          <<<<<<<< missing "Z_move_comp"
G1 Z10 F90
ok ok ok Z_move_comp
M280 P0 S1100
G1 X0 F150
ok Z_move_comp

G1 Z0.1 F40
ok ok Z_move_comp ok Z_move_comp   <<<<<<<< why there are two "Z_move_comp" ?
M280 P0 S1900
ok   <<<<<<<<<<<<<<<<<<<<<<<<<<  Beginn to expose, shutter did not realy open-close, but it is too early, Z move not complete
M280 P0 S1100
ok
G1 X-4 F50
ok Z_move_comp

G1 Z4.1000 F20
ok Z_move_comp
G1 X0 F150
ok Z_move_comp

G1 Z0.2 F40
ok Z_move_comp
M280 P0 S1900
ok
M280 P0 S1100
ok
G1 X-4 F50
ok Z_move_comp

G1 Z4.2000 F20
ok Z_move_comp
G1 X0 F150
ok

G1 Z0.3 F40
Z_move_comp ok Z_move_comp
M280 P0 S1900
ok
M280 P0 S1100
ok
G1 X-4 F50
ok

G1 Z4.3000 F20
Z_move_comp ok Z_move_comp
G1 X0 F150
ok Z_move_comp

G1 Z0.4 F40
ok Z_move_comp
M280 P0 S1900
ok
M280 P0 S1100
ok
G1 X-4 F50
ok Z_move_comp

G1 Z4.4000 F20
ok Z_move_comp
G1 X0 F150
ok Z_move_comp

G1 Z0.5 F40
ok Z_move_comp
M280 P0 S1900
ok
M280 P0 S1100
ok
G1 X-4 F50
ok Z_move_comp

G1 Z4.5000 F20
ok Z_move_comp
G1 X-9.5 F150
G1 Z250 F200
M84
M280 P0 S1100
ok Z_move_comp ok Z_move_comp echo:endstops hit: Z:123.40 ok

#81 Re: Bug Reports » nanoDLP crashed » 2016-04-01 19:30:22

Now nanoDLP is working again.
I  converted the Projektor Mask from grayscale into 24 bit color and it works smile
thank you

#82 Bug Reports » nanoDLP crashed » 2016-04-01 17:33:15

Xmike
Replies: 2

I tried to upload a svg. file and afterwards nanoDLP crashed.
Now I do not get working nanoDLP anymore,
even if I reboot Raspberry, the website is unreachable.
What can I do to get nanoDLP working ?

Here is a part of /var/log/printer.log:

goroutine 24 [running]:
panic(0x4d21b0, 0x10b4e7a0)
    /usr/local/go/src/runtime/panic.go:464 +0x330
_/home/pi/printer/app/svg.(*SVG).loadMask(0x10a4e180)
    /home/pi/printer/app/svg/svg.go:205 +0x2b0
_/home/pi/printer/app/svg.(*SVG).SliceRender(0x10a4e180, 0x4ea800)
    /home/pi/printer/app/svg/svg.go:107 +0x55c
main.(*monitorStruct).watch(0x7731a8)
    /home/pi/printer/app/slice-monitor.go:62 +0x338
created by main.main
    /home/pi/printer/app/server.go:52 +0xc8
2016/04/01 18:49:33.773330 {"Layer":"1","module":"JSON","level":"Warning","msg":"Skipping db/buttons.json file. stat db/buttons.json: no such file or directory "}
2016/04/01 18:49:33.775369 {"Layer":"1","module":"JSON","level":"Warning","msg":"Skipping db/custom-inputs.json file. stat db/custom-inputs.json: no such file or directory "}
2016/04/01 18:49:33.794167 {"Layer":"1","module":"Shutter","level":"Error","msg":"Pipe Access Problem open /dev/pigpio: no such file or directory "}
2016/04/01 18:49:33.828160 {"Layer":"1","module":"JSON","level":"Warning","msg":"Skipping public/plates/4/info.json file. stat public/plates/4/info.json: no such file or directory "}
panic: interface conversion: image.Image is *image.Paletted, not *image.RGBA

goroutine 24 [running]:
panic(0x4d21b0, 0x10b5a8a0)
    /usr/local/go/src/runtime/panic.go:464 +0x330
_/home/pi/printer/app/svg.(*SVG).loadMask(0x1090c400)
    /home/pi/printer/app/svg/svg.go:205 +0x2b0
_/home/pi/printer/app/svg.(*SVG).SliceRender(0x1090c400, 0x4ea800)
    /home/pi/printer/app/svg/svg.go:107 +0x55c
main.(*monitorStruct).watch(0x7731a8)
    /home/pi/printer/app/slice-monitor.go:62 +0x338
created by main.main
    /home/pi/printer/app/server.go:52 +0xc8

#83 Help and Support » positioning mode » 2016-03-27 09:48:41

Xmike
Replies: 1

Hallo Shahin,
is for "position recovery"  the absolute positioning mode (G90) required or can the relatieve positioning (G91) also be used,
are there any disadvantages with use of relatieve positioning.
In my self built printer I use a arduio with ramps board and Repetier-firmware, have I also to use the
[[WaitForDoneMessage]] to control movement ?

Board footer

Powered by FluxBB