Messages

1

RaftAway / Re: error?

« on: June 24, 2017, 05:04:25 AM »

Sorry, I misunderstand at first that 1.1.5 would fix it. I had a closer look and indeed the problem is of different nature.
Actually, recent versions of Z-Suite have a bug that creates "empty" ZCode commands (data is missing even though the command can't be executed without data).
I was aware of this for certain jump commands (which didn't affect RaftAway), but in your example, there are also empty retraction commands.
Never saw this before, so I didn't create a workaround for it.
Anyway, I created a version 1.1.6 to work around this bug in Z-Suite and sent it to Julia.

2

RaftAway / Re: error?

« on: June 23, 2017, 11:02:40 AM »

Yeah, this ZCode uses external material ABS which was an unknown material in older ZCode versions.
Actually I did some robustness improvement in 1.1.3 by introducing dummy materials in the profile enumeration but then Zortrax surprised me by using numbers >= 128 for the external materials.

3

RaftAway / Re: error?

« on: June 23, 2017, 09:46:57 AM »

Which version of RaftAway are you using? Something older than v1.1.5?
In case this happens with 1.1.5, please upload the ZCode in question so I can take a look.

4

RaftAway / Re: v1.1.4 released

« on: March 23, 2017, 04:31:54 PM »

I guess Julia would recommend to either switch the fan off (or to a fixed low value) or to insulate the hotend.
It was discussed before to add a feature to either limit or scale down the fan speed. In the end, there was no strong demand up to now.

5

RaftAway / Re: v1.1.4 released

« on: March 23, 2017, 01:59:15 PM »

It seems somewhat plausible that extruding material more quickly (due to faster print moves) could lead to a temperature drop.
I guess the combination of Z-Suite 1.8.x with its 100% fan speed mania would make this more likely to happen.
Plus some people here have dual fan setups which are said to create this problem even with older Z-Suite versions in auto fan mode.

6

RaftAway / v1.1.4 released

« on: March 19, 2017, 06:36:48 PM »

v1.1.4 increases maximum speedup to 150% but automatically suppresses speedup for the 1st two raft layers.

7

RaftAway / Re: v1.1.3a Released

« on: March 08, 2017, 01:33:21 PM »

As a compromise: I should be relatively easy to automatically exclude the Raft from speedup. Maybe only the first raft layer. Have to think about that.
Of course that will eat up another bit of the potential speedup.

8

RaftAway / Re: v1.1.3a Released

« on: March 07, 2017, 04:07:13 PM »

We scrapped the idea of simplicity a while ago, didn't we ?
I guess I shouldn't propose the fan speed graph then or should I?
Anyway, I guess the current speed down/up is good enough for most purposes.

9

RaftAway / Re: v1.1.3a Released

« on: March 07, 2017, 12:53:42 PM »

Increasing the maximum to 150% is a piece of cake. I'm just a bit concerned that some fast infills will suffer.
Having separate speed factors for infill, contour, raft is possible in theory but a bit more complicated and risky (letting aside that the GUI is starting to get messy).
Problem is that ZCode has a separate command for feedrate so it's not part of the actual movement/printing command (which is the case for G-Code).
So to check which area a feedrate command will affect, I'd need to parse at least one further command (sometimes maybe even two or so) which my current design doesn't allow.
It's not like I couldn't change the design, but it's work (*meh*) and there's always the chance of collateral damage.

10

RaftAway / Re: v1.1.3a Released

« on: March 06, 2017, 12:46:45 PM »

I must admit that I'm surprised to hear that the increase in speed also increased the weight. Honestly, I'd have expected the opposite.
Like I found it plausible to assume that the higher speed would lead to a certain amount of under-extrusion in infill.
Then again, what do I know about 3D printing ?

11

RaftAway / Re: v1.1.3a Released

« on: March 05, 2017, 05:54:53 AM »

The height sensing is done in firmware, so it's not influenced by ZCode patches.
Note that in "normal" quality mode, most jumps already use the maximum speed, so they are not accelerated.
All other (printing) movement should have been 25% faster, so some additional ringing etc. is expected.
Then again, if the print is still clean, this speedup feature doesn't seem so pointless after all.
Have you checked if the printing time was decreased compared to the original Z-Suite estimation?

12

RaftAway / Re: v1.1.3a Released

« on: March 03, 2017, 11:44:17 AM »

This was originally planned as test version to check if the speedup is beneficial. So potential users should keep in mind that this feature is more or less untested.

One thing that I forgot to mention in the RTF (and the included changelog) is that v1.1.3 will now modify the printing time by dividing by the speed multiplier.
Like a 2h job printed with 50% should now be displayed as 4h job. Note that while this might be somewhat correct for slowing down, it might be inaccurate when speeding up.
As the speedup functions limits the movement speed to 8000mm/min and the "normal" quality mode on the m200 uses speeds that high, these limitations are not considered.
So 125% speed with a 2h job will result in 1h 36min (120/125*100 = 96), no matter if some movement speeds are limited or not.

13

RaftAway / Re: Raftaway 1.1.0 Released, Adds Speed Multiplier

« on: March 02, 2017, 01:29:52 PM »

I'm somewhat sure that 8000mm/min is the maximum that Z-Suite uses for jumps, so I don't think it makes sense to try to push that limit.
Anyway, this is not the maximum printing speed but the maximum movement speed.
I'm not 100% sure but without deeper investigations I would assume the maximum printing speed is 3000mm/min.
It might be possible to increase that a bit, but I'm not sure how much sense it makes given that the extruder won't be able to push enough filament through the nozzle at very high speeds.

14

RaftAway / Re: Raftaway 1.1.0 Released, Adds Speed Multiplier

« on: March 01, 2017, 01:45:59 PM »

I was also not aware of this until recently, but in m200's "Normal" quality mode, Z-Suite already uses the highest possible (8000mm/min) movement speed for X/Y/Z jumps (movements without extrusion). This seems to be on par with the m300's "Draft speed".
I haven't analyzed this in detail, but a quick comparison between High and Normal quality for the m200 looks a bit like like a comparison between "Normal" and "Draft" Quality on the m300.
E.g. Jumps (no extrusion) are increased from 5400mm/min to 8000mm/min in both cases.
Actually the m200's "Normal" profile seems to be a bit faster than the m300's "Draft" profile.
E.g. it increases the speed for visible infill is increased from 2400mm/min ("High" quality) to 2880mm/min ("Normal quality"), while the m300's "Draft" profile just increases the speed for invisible infill from 2200mm/min to 2400mm/min.
A full comparison of profiles would be a lot of work, but I guess that goes to show that the m200's "Normal" profile might be even a bit faster than the m300 "Draft" profile. To my surprise, to say the least.

So if I should add a 125% maximum speed setting, I'd still need to limit the maximum speed to 8000mm/min...

15

RaftAway / RaftAway 1.1.2 released, bugfixes

« on: February 17, 2017, 01:58:21 PM »

Since the lady of the house seems to be occupied with more important matters, I'll jump in to promulgate the new version.
BTW: checked with Z-Suite 1.8.0, couldn't find any preview issues. Well, 1.8.0 is buggy as hell though, but that's a different matter.

1.1.0 -> 1.1.1
Fixed bug that prevented processing when only the speed option was selected

1.1.1 -> 1.1.2
Fixed issue where no raft was detected if Z-Suite didn't create a first layer model contour but started with model contour (related to shell infill)