16
RaftAway / Re: Error when Removing Raft with Shell Infill
« on: February 17, 2017, 11:25:30 AM »
FYI: the update 1.1.2 is already online since yesterday or so.
User Forum
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
17
RaftAway / Re: Error when Removing Raft with Shell Infill
« on: February 15, 2017, 01:39:47 PM »
OK, thanks. Will be fixed in 1.1.2.
Actually it's not really a bug in RaftAway, but obviously Z-Suite sometimes doesn't start with a first layer model contour but with "model contour" instead.
Wasn't aware of that ... could be actually a bug in Z-Suite. Even if Julia says I'm trying to whitewash.
Actually it's not really a bug in RaftAway, but obviously Z-Suite sometimes doesn't start with a first layer model contour but with "model contour" instead.
Wasn't aware of that ... could be actually a bug in Z-Suite. Even if Julia says I'm trying to whitewash.
18
RaftAway / Re: Error when Removing Raft with Shell Infill
« on: February 14, 2017, 07:41:13 PM »
RaftAway searches for a certain pattern to maintain the skirt line (which is marked as raft as well).
I would guess that shell infill changes something in the command order that disturbs RaftAway.
I tried with a minimum example (test cube) and raft removal worked in this case, so I guess there must be other contributors...
Could you upload an example ZCode somewhere?
I would guess that shell infill changes something in the command order that disturbs RaftAway.
I tried with a minimum example (test cube) and raft removal worked in this case, so I guess there must be other contributors...
Could you upload an example ZCode somewhere?
19
RaftAway / Re: Raftaway 1.1.0 Released, Adds Speed Multiplier
« on: February 13, 2017, 01:38:46 PM »
Glad to hear that it's useful.
Since nobody reads the manual anyway, I'd also like to point out that the ZCode created after raft removal should be displayer correctly in Z-Suite 1.7.x now. When the raft was removed with <= v1.0.8, Z-Suite tended to suppress the display of the uppermost layers (slightly inconsistent behavior, so it happened usually only for the 1st ZCode loaded after starting Z-Suite). Still happens with Z-Suite 1.6.x but that version also has issues displaying ZCode created by 1.7.x.
Since nobody reads the manual anyway, I'd also like to point out that the ZCode created after raft removal should be displayer correctly in Z-Suite 1.7.x now. When the raft was removed with <= v1.0.8, Z-Suite tended to suppress the display of the uppermost layers (slightly inconsistent behavior, so it happened usually only for the 1st ZCode loaded after starting Z-Suite). Still happens with Z-Suite 1.6.x but that version also has issues displaying ZCode created by 1.7.x.
20
RaftAway / Re: Raftaway 1.0.8 Released, Adds Extrusion Multiplier
« on: February 10, 2017, 12:46:14 PM »
If they even were customers 
21
RaftAway / Re: Raftaway 1.0.8 Released, Adds Extrusion Multiplier
« on: February 10, 2017, 10:43:35 AM »
Are you talking about a speed down for the raft or an extrusion multiplier for the raft?
Both would be possible from a technical point but I'm not 100% sure if I understand the use case.
I.e. reducing the extrusion (through an extrusion multiplier) would most probably decrease raft adhesion.
Anyway, maybe let's get the general speed down option working 1st.
Also note that my concern is that something that started as standalone raft remover is beginning to get cluttered with new options.
Both would be possible from a technical point but I'm not 100% sure if I understand the use case.
I.e. reducing the extrusion (through an extrusion multiplier) would most probably decrease raft adhesion.
Anyway, maybe let's get the general speed down option working 1st.
Also note that my concern is that something that started as standalone raft remover is beginning to get cluttered with new options.
22
RaftAway / Re: Raftaway 1.0.8 Released, Adds Extrusion Multiplier
« on: February 06, 2017, 01:12:30 PM »
Well, as stated above, it would be relatively easy to implement a multiplier to change the feedrate.
Problem is that in Z-Code (unlike the in G-Code example given above) the feedrate is set with a separate command, so it's not easily possible to change e.g. only the speed of print movements.
I wouldn't say it's impossible but it would be much easier to change all speeds which however also includes retract/unretract moves and "jumping" (movement without extrusion).
I'd also suggest to only allow decreasing of the speed as increasing speeds may have undesired effects. So let's say I could add a "Speed factor" with a default of 100% which could be decreased down to 50%.
@Julia: do you have an opinion on this?
Problem is that in Z-Code (unlike the in G-Code example given above) the feedrate is set with a separate command, so it's not easily possible to change e.g. only the speed of print movements.
I wouldn't say it's impossible but it would be much easier to change all speeds which however also includes retract/unretract moves and "jumping" (movement without extrusion).
I'd also suggest to only allow decreasing of the speed as increasing speeds may have undesired effects. So let's say I could add a "Speed factor" with a default of 100% which could be decreased down to 50%.
@Julia: do you have an opinion on this?
23
RaftAway / Re: Raftaway 1.0.8 Released, Adds Extrusion Multiplier
« on: February 03, 2017, 11:44:43 AM »
Well, he said "extrusion speed" so I assumed that's want he meant 
Also the values "40 or 60 mm/s" given translate into 2400 to 3600mm/min which would be rather high feedrates (travel speeds).
As far as I can tell, Z-Suite usually uses something like 1200 mm/min as feedrate for the contour and 2400 mm/min for the infill.
Besides, using material dependent extrusion multipliers is a common feature of slicers. E.g. the Simplify3D troubleshooting guide says:
This being said, a fixed feedrate (travel speed) wouldn't make much sense as it changes quite a bit depending on the movement/action performed. E.g. movements without extrusion should be fast, movements while printing the contour should be slower than movements printing the infill. So the only way feasible to change the feedrate would be a multiplier but I just don't think it would make much sense. If at all, it could be used to slow the printing process down but I'm not sure if this is really desirable.
[EDIT]
About the relation between feedrate and extrusion: the feedrate is a speed (position change per time) value that defines the travel speed of the following movement commands. The extrusion value however is a position value that is used in movement/extrusion commands like the X/Y coordinate. In plain G-Code this looks like this:
"F" is the feedrate, so "F1200" means that the X/Y/Z position should be moved to with 1200mm/minute. X/Y/Z/E are the according position values in mm.
You can see how this extrusion value increases continuously during extrusion. It only decreases for retraction moves. As all the other coordinates, it can be set (redefined, not moved) to a new value though.
E.g. some slicers (including Z-Suite) set the extrude value to 0 at each layer change.
Anyway, even the though some details are different in ZCode, you can see in the GCode example that it would be very easy to change the feedrate values with a multiplier but this wouldn't have an influence on the material extruded, just on the movement/printing speed. Actually manipulating the extrusion values is a bit trickier because of the resetting of the value and the retract/unretract moves but this is what RaftAway does for the 1st model layer (and therefore also could do for the rest of the model).
Also the values "40 or 60 mm/s" given translate into 2400 to 3600mm/min which would be rather high feedrates (travel speeds).
As far as I can tell, Z-Suite usually uses something like 1200 mm/min as feedrate for the contour and 2400 mm/min for the infill.
Besides, using material dependent extrusion multipliers is a common feature of slicers. E.g. the Simplify3D troubleshooting guide says:
Quote
It is typical for PLA to print with an extrusion multiplier near 0.9, while ABS tends to have extrusion multipliers closer to 1.0.There is actually a G-Code command to set the extrusion multiplier (E.g. "M221 S70" sets the extrusion multiplier to 70%). IdeaMaker uses it for different material profiles.
This being said, a fixed feedrate (travel speed) wouldn't make much sense as it changes quite a bit depending on the movement/action performed. E.g. movements without extrusion should be fast, movements while printing the contour should be slower than movements printing the infill. So the only way feasible to change the feedrate would be a multiplier but I just don't think it would make much sense. If at all, it could be used to slow the printing process down but I'm not sure if this is really desirable.
[EDIT]
About the relation between feedrate and extrusion: the feedrate is a speed (position change per time) value that defines the travel speed of the following movement commands. The extrusion value however is a position value that is used in movement/extrusion commands like the X/Y coordinate. In plain G-Code this looks like this:
Code: [Select]
G1 F1200 X71.838 Y101.911 E1.928
G1 F1200 X71.847 Y101.834 E1.931
G1 F1200 X71.877 Y101.753 E1.934"F" is the feedrate, so "F1200" means that the X/Y/Z position should be moved to with 1200mm/minute. X/Y/Z/E are the according position values in mm.
You can see how this extrusion value increases continuously during extrusion. It only decreases for retraction moves. As all the other coordinates, it can be set (redefined, not moved) to a new value though.
E.g. some slicers (including Z-Suite) set the extrude value to 0 at each layer change.
Anyway, even the though some details are different in ZCode, you can see in the GCode example that it would be very easy to change the feedrate values with a multiplier but this wouldn't have an influence on the material extruded, just on the movement/printing speed. Actually manipulating the extrusion values is a bit trickier because of the resetting of the value and the retract/unretract moves but this is what RaftAway does for the 1st model layer (and therefore also could do for the rest of the model).
24
RaftAway / Re: Raftaway 1.0.8 Released, Adds Extrusion Multiplier
« on: February 03, 2017, 10:46:06 AM »
Well, letting the user define the extrusion speed would be a little tricky, but of course there could be an extrusion multiplier for the rest of the model just like it is implemented for the 1st layer.
Actually, internally, this is already the case.
However, Julia's approach was to keep the tool as plain and simple as possible, which is the main reason why the according input field is missing in RaftAway's GUI.
Then again, if you managed to convince her that this 2nd/global multiplier would be beneficial, it would be easy to add it.
Actually, internally, this is already the case.
However, Julia's approach was to keep the tool as plain and simple as possible, which is the main reason why the according input field is missing in RaftAway's GUI.
Then again, if you managed to convince her that this 2nd/global multiplier would be beneficial, it would be easy to add it.
Pages: 1 [2]