topic Re: Additive Travel Speed in Fusion Support Forum

Additive Travel Speed

fsonnichsen — Mon, 26 Apr 2021 15:12:09 GMT

I posted ""Additive Travel Speed" on the Manufacture forum but it has had no attention for some time. I think that this is a bug--basically the Travel Speed, which should be about 200mm/sec as the 3D print head moves to new locations, is nowhere near that. It is in fact very slow--about 3mm/sec. (vs 200). Check the above post for some details.

I think this was brought up once before but it does not seem that it was every solved. I placed my STL file in CURA and I get the results one would expect--the travel is very fast. At present, using Fusion, this problem can add an hour to a 3 hour print. It seems that travel speed is not being properly entered into the GCODE files, perhaps something with UNITS?

Thanks

Fritz

Re: Additive Travel Speed

jodom4 — Mon, 26 Apr 2021 21:39:26 GMT

@Sualp.Ozel , can you take a look at this one?

Re: Additive Travel Speed

robert.bowerman — Tue, 27 Apr 2021 12:22:56 GMT

Hi @fsonnichsen , are you able to provide a little more detail:

Which machine and post processor are you using?

Does your machine use G0 moves during travel or does it require a feedrate to be defined?

Are you able to share the output Gcode you have from Fusion and Cura - this should enable us to quickly spot the difference.

Thanks,

Rob

Re: Additive Travel Speed

fsonnichsen — Tue, 27 Apr 2021 15:12:40 GMT

Robert-

I had intended to include the GCODE but your site does not allow these attachments. I now see that I can include txt so I attached them as that. The GCODE uses G0.

I can probably dig up a simpler example if that helps --earlier I made a test design with two standing "towers" and one could see that the travel between towers was very slow for Fusion. In the case here. the travel is between the 6 boreholes and the same slowness is seen

thanks

Fritz

Re: Additive Travel Speed

robert.bowerman — Tue, 27 Apr 2021 15:36:51 GMT

Thanks for providing these @fsonnichsen.

I believe the issue may be that you have a post option set too low. The option is called "(Built-in) high feedrate", which you can find when you post process your toolpath (see attached image). This essentially will limit/cap the travel speed that is output. If you increase this value above the required travel speed then the travel speed in your print setting should appear in the gcode output.

Let me know how you get on.

Thanks,

Rob

Re: Additive Travel Speed

fsonnichsen — Tue, 27 Apr 2021 22:42:31 GMT

Thanks Robert

I made the change and ran a quick test on my machine-all looks good now (and no more little "hairs" between parts!).

Just curious why this parameter (and a few others) are placed separate from the rest. Seems like it would belong with the machine setup parms with the rest.

also- I had looked there and when I saw my original 250 (>200) I assumed I was OK.

cheers

Fritz

Re: Additive Travel Speed

robert.bowerman — Wed, 28 Apr 2021 09:31:53 GMT

That's great!

Thank you for reporting this to us, you may indeed have found a bug with the default value, I shall report it to the development teams.

Out of interest which post are you using and do you have the "Automatically get latest posts and machines" feature flag turned on? (see attached image)

Thanks,

Rob

Re: Additive Travel Speed

fsonnichsen — Thu, 29 Apr 2021 12:23:10 GMT

Thanks Robert-

I am using the "Creality Family/Creality" post.

I looked at my Preferences, the Post Action command, and various Manage items and I don't see the "automatically get latest posts" anywhere

Fritz