Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 19 of 19
Support changing direction, floating support and speed issue are the only problems I think I'm having.
And for the 'weird first layer problem' thing, it was corrupt STL file, I re made the model and all seems to be fine.
Sorry about the confusion.
Thanks
-Sun
by
zsunsun
-
Experimental
That didn't change anything other than RPM number in the comment of gcode file.
DId you try slicing the file I posted and see if first layer came out to be weird?
Thanks
-Sun
by
zsunsun
-
Experimental
Here's my ini files.
Only reason I set my RPM that high is to see if it is the limiting factor in feedrate and I just left it at that.
Thanks
-Sun
by
zsunsun
-
Experimental
STL file attached
Thanks for assist.
-Sun
by
zsunsun
-
Experimental
I printed 80 mm/s feedrate with SFACT till yesterday, so firmware is ruled out.
If you take a look at gcode I posted, RPM is nowhere near 280, which is max RPM I set.
I'm guessing here that maybe KISSlicer is limiting speed due to the size of the object, so I will try with something else later today.
And I would like to repeat that first layer, not only support layer but the entire one, is out
by
zsunsun
-
Experimental
I'm attaching truncated gcode file generated using KISSlicer
I was looking through gcode and found a few weird floating spot.
First, first layer of the print has different supporting pattern compared to the rest of the print making next layer of support material impossible to have strong adhesion, making them detach in the middle of the print. Also, this makes bottom look ugly
Another proble
by
zsunsun
-
Experimental
Do you really run at 2.5 meters per second squared? my TOM will vibrate to the point of self destruction if I set acceleration that high!
Mainly I am looking to have a smooth acceleration somewhere from ~10mm/s to 90mm/s, which is my TOM's max feed speed it can handle until extruder stepper motor starts to skip.
I'm still tweaking to reduce running noise and vibrations of my TOM, as many alrea
by
zsunsun
-
Experimental
Oh, I meant I would like to be able to customize different acceleration / feed speed per different portion of the layer.
For example, I would like to have 20 mm/s feedspeed at 40mm/s^2 acceleration for perimeter while 80mm/s feedspeed at 300mm/s^2 acceleration for infills.
Since infill is less likely affected by feedspeed / acceleration it would be a great time saving measure.
Thanks
Sun
by
zsunsun
-
Experimental
Ah, that could be it, on my Skeinforge setting I have it to remove all the comments (it recognizes both parenthesis and semicolon as comments).
I should update my files accordingly and try again tonight.
I'm really looking forward to see how well this prints on my printer as I'm more and more frustrated with fiddling with Skeinforge settings.
Also, could you add acceleration parameters for th
by
zsunsun
-
Experimental
Estimated duration (pessimistic): 75 layers, 00:16:52
T:42 B:35
Print Started at: 18:14:15
CRC mismatch:3
rs 3
Invalid line:4
T:41 B:34
I'm attaching entire gcode here
it's odd that printerface does not show preview of gcode generated by KISSlier.
Maybe it's fault from printerface?
by
zsunsun
-
Experimental
I've been printing using SFACT with Pronterface just fine, but when using gcode generated by KISSlicer nothing moves.
This is what is shown on command line
CRC mismatch:3
rs 3
Invalid line:4
rs 3
Invalid line:5
This is first 10 lines from actual gcode file
; KISSlicer
; version 1.0.5.32
; Built: Feb 8 2012, 11:23:26
;
; Saved: Tue Feb 14 20:44:39 2012
; 'Measurin.gcode'
;
; *** Printer Se
by
zsunsun
-
Experimental
Few things.
There are no ways to sort STL files in open window, I prefer to sort them by date which ensures newest file stays on top.
Also when I feed gcode file generated using Prontoface my printer does nothing, it just sits there.
Will report back if anything else is found
Thanks
Sun
by
zsunsun
-
Experimental
T0 is still present at the end of the gcode file
G1 X-25.38 Y-19.89 Z22 E6.333
G1 F210
G1 X-25.38 Y-19.89 Z22.75 E6.333
; END_LAYER_OBJECT z=22.00
T0 <==========================================here
M109 S0
;
; Estimated Build Time: 110.72 minutes
; Estimated Build Volume: 8.822 cm^3
; Estimated Build Cost: $0.00
Other than that, no error has been spotted. Will test print tomorrow and
by
zsunsun
-
Experimental
(**** beginning of start.gcode ****)
(This is being used lol?)
(This file is for TOM with 1.75mm ABS in a MK7 Extruder)
G21 (set units to mm)
G90 (set positioning to absolute)
M104 S215 (set extruder temperature, Pre-heat)
M140 S110 (Set heated build platform temperature for Sjfw firmware)
;M109 S110 (set heated-build-platform temperature for Makerbot firmware)
;M108 R5.0 (set extruder speed, not
by
zsunsun
-
Experimental
I'll gladly share my start&end gcode. I'll post them up after I test them.
Just yesterday I switched my firmware to Sjfw to try out acceleration as TOM was going through harsh shocks and vibrations while printing at 60mm/s although print looked excellent.
by
zsunsun
-
Experimental
Thanks for quick-fix and reply
Unfortunately I found a one more bug,
Under G-code Prefix and Postfix, I like to add a description of what each line of code do wrapped inside '()'
Whenever I hit 'save' button KISSlicer takes out last parenthesis in the box making entire reminder of code a comment.
Also 'T0' code problem is still there, not sure what that is for... heated bed temperature?
Tha
by
zsunsun
-
Experimental
I don't have a picture to post right now, but empty area is actually little more than one filament wide, I'm guessing its because I haven't done packing factor calibration?
Also, what does the 'Add Acceleration Rate' check box do? The only thing I can relate to is 'Main Acceleration Rate for Extruder (mm/s2)' but it doesn't say what values are effected by it. Am I correct in assuming it adds ac
by
zsunsun
-
Skeinforge
This is amazing. I just followed instruction except for the part where I need to measure thin wall feature (I misplaced my digital caliper) and just went with printing with minor adjustments (cool, inset etc).
And print came out to be excellent all around except for it does not fill 'fingers' in this design,
I just have perimeter with no infill for 'fingers' similar to the this picture,
Al
by
zsunsun
-
Skeinforge
Looking very promising, gonna give it a shot.
I've been looking for a little more user friendly solution as many of my family/friends are quite interested but scared that it takes me few hours to get one print right.
EDIT:
[19:58:59] Unrecognized MCode! M229
[19:58:59] Unsupported GCode!
M229 S0.80 P0.40 uses a code that ReplicatorG doesn't recognize.
[19:58:59] Unsupported GCode!
T0 uses a co
by
zsunsun
-
Experimental