Bad z starting position
Bad z starting position
Just built mine this week. I am trying out some different slicers because Slicer keeps crashing on large objects.
I have tried Kiss and Cura but both are creating prints that are starting at almost the highest Z position. Never had this problem with Repetier and Slicer. I downloaded all the Kiss settings from mhackney and tried adjusting zoffset but nothing is working.
I have tried Kiss and Cura but both are creating prints that are starting at almost the highest Z position. Never had this problem with Repetier and Slicer. I downloaded all the Kiss settings from mhackney and tried adjusting zoffset but nothing is working.
Re: Bad z starting position
so, I've only been printing about 2 weeks now, but since nobody has replied yet I thought I'd say something.
I have only used slicer and have a solid gaming computer. My rig slices stuff pretty quick, but I have noticed that at about 80% the completion bar slows way down. this probably isn't your problem since you say it crashes but thought I'd mention it.
so far all my problems have been solved by running my .obj files from sketchup through netfabb and using the repair feature. maybe this will help you. just google netfabb basic and the download page is on the top. If not that specific software, I would at least try exporting your files from a couple different CADs if possible to see if those work better with repieter
I have only used slicer and have a solid gaming computer. My rig slices stuff pretty quick, but I have noticed that at about 80% the completion bar slows way down. this probably isn't your problem since you say it crashes but thought I'd mention it.
so far all my problems have been solved by running my .obj files from sketchup through netfabb and using the repair feature. maybe this will help you. just google netfabb basic and the download page is on the top. If not that specific software, I would at least try exporting your files from a couple different CADs if possible to see if those work better with repieter
Re: Bad z starting position
What do you mean by 'creating prints at almost the highest Z position'? Like it's printing in mid-air?mcgragger wrote:Just built mine this week. I am trying out some different slicers because Slicer keeps crashing on large objects.
I have tried Kiss and Cura but both are creating prints that are starting at almost the highest Z position. Never had this problem with Repetier and Slicer. I downloaded all the Kiss settings from mhackney and tried adjusting zoffset but nothing is working.
Re: Bad z starting position
I actually got slicer to stop crashing when I updated it. No more memory issues. The packaged version with Repeteir is now out of date. Thanks for the suggestion I will play around with more.carter wrote:I have only used slicer and have a solid gaming computer. My rig slices stuff pretty quick, but I have noticed that at about 80% the completion bar slows way down. this probably isn't your problem since you say it crashes but thought I'd mention it.
Re: Bad z starting position
Correct. The gcode generated by Kisslicer/Cura/Skeinforge all look like they are placed correctly when I load it into Repeteir but all start printing in mid air. Slicer also looks correct but starts printing on the bed though.Tinyhead wrote:What do you mean by 'creating prints at almost the highest Z position'? Like it's printing in mid-air?
Re: Bad z starting position
This is my Kisslicer prefix code ....
T<EXT+0>
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>
This is my postfix code ....
G1 X70 Y0 F5000
G28
What are others using?
T<EXT+0>
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>
This is my postfix code ....
G1 X70 Y0 F5000
G28
What are others using?
- geolupulus
- Printmaster!
- Posts: 67
- Joined: Mon Apr 14, 2014 3:03 pm
- Location: Albany NY
Re: Bad z starting position
I am in the same boat, this happens to me I'd say 30% of the time. I reboot the printer, and Repetier and load the same EXACT G-code and it prints fine. Drives me mad. (Using Rostock Max V2, Windows XP & newest Repetier.)mcgragger wrote:
Correct. The gcode generated by Kisslicer/Cura/Skeinforge all look like they are placed correctly when I load it into Repeteir but all start printing in mid air. Slicer also looks correct but starts printing on the bed though.
Last edited by geolupulus on Fri May 09, 2014 10:48 am, edited 1 time in total.
Re: Bad z starting position
I have the same issue with Cura (but not slic3r or kiss). Half the time the print starts about 10cm above the bed.
I have a Max V2 and using Repetier Host to initiate the print from a Mac running Mountain Lion.
I have a Max V2 and using Repetier Host to initiate the print from a Mac running Mountain Lion.
Re: Bad z starting position
Its finaly working with these prefix and post in kisslicer
Pre:
G28
T<EXT+0>
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>
M117 KEEP HANDS AWAY
Post:
G1 X70 Y0 F5000
G28
M104 S0 ; turn off temperature
M140 S0 ; turn off bed temperature
M84 ; disable motors
M117 PRINT FINISHED
Pre:
G28
T<EXT+0>
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>
M117 KEEP HANDS AWAY
Post:
G1 X70 Y0 F5000
G28
M104 S0 ; turn off temperature
M140 S0 ; turn off bed temperature
M84 ; disable motors
M117 PRINT FINISHED
- Eaglezsoar
- ULTIMATE 3D JEDI
- Posts: 7159
- Joined: Sun Apr 01, 2012 5:26 pm
Re: Bad z starting position
It's good to see that you got it working.
Happy Printing!
Happy Printing!
“ Do Not Regret Growing Older. It is a Privilege Denied to Many. ”
- foshon
- Printmaster!
- Posts: 600
- Joined: Fri Mar 08, 2013 3:05 pm
- Location: Just to the right of SeeMeCNC
Re: Bad z starting position
G1 X70 Y0 F5000
Take that out, it's for cartesions and places the print to the front for grabbing it more readily. On a Rostock its just moving your effector to one side before going straight up with the G28.
Take that out, it's for cartesions and places the print to the front for grabbing it more readily. On a Rostock its just moving your effector to one side before going straight up with the G28.
Purple = sarcasm
Please do a board search before posting your question, many have been answered with very time consuming detail already.
Please do a board search before posting your question, many have been answered with very time consuming detail already.