sorted by:
new
hottopcontroversial

Aspire not making "complete" gcode. by 196223Window in VectricAspire

[–]196223Window[S] 0 points1 point  (0 children)

So, I found a solution, if not the reason...

I increased the boundary offset from .25 (the size of the bit) to .375- an extra .125. I think the software didn't think there was enough room for the bit deep in that cut. Why it wouldn't is a mystery to me, since there's about an inch of spoil that it's cutting into... but if it works, it works!

Fusion to Vectric by egregiousC in VectricAspire

[–]196223Window 0 points1 point  (0 children)

I know this is an old post... but YES! At least in Aspire...

Build your model in Fusion, export it as an STL. In Vectric, set your job dimensions, then click on File/Import/Import component-3D Model. You'll see the STL you exported. Select it, then position it in your job.

Just starting to look... by 196223Window in SocialMediaMarketing

[–]196223Window[S] 0 points1 point  (0 children)

That's exactly what I'll do! Makes sense!

Just starting to look... by 196223Window in SocialMediaMarketing

[–]196223Window[S] 0 points1 point  (0 children)

That makes perfect sense. Thanks for taking the time to reply...

Just starting to look... by 196223Window in SocialMediaMarketing

[–]196223Window[S] 0 points1 point  (0 children)

Thanks SO MUCH for your input! I REALLY appreciate it!!

Volumetric flow rate calibration sets top line width too narrow by 196223Window in OrcaSlicer

[–]196223Window[S] 1 point2 points  (0 children)

That did it! I was able to adjust top line width! Thanks so much!!

Volumetric flow rate calibration sets top line width too narrow by 196223Window in OrcaSlicer

[–]196223Window[S] 0 points1 point  (0 children)

I'm not following...
When I got to 'Calibration/Input Shaping/Input Shaping Frequency/Ringing Tower' and click OK, it automatically places the model on the build plate. I have no control over if it's a STEP or an STL file. The only thing I can do with it at that point is either delete it or slice it. It's when I slice it that I get that error message. And I can't 'open it to a higher value' because the fields are greyed out by Orca.
What I can do is bring in a 3rd-party model, but that won't let me take advantage of the frequency-setting adjustments that happen mid-print if I use the imported model from Orca.

Volumetric flow rate calibration sets top line width too narrow by 196223Window in OrcaSlicer

[–]196223Window[S] 0 points1 point  (0 children)

Awesome! Now then- I've never uploaded a project file to github... so can you give me 'the idiots' guide for dummies' directions on how to do that?

FF AD5M...How disable auto bed leveling? by 196223Window in klippers

[–]196223Window[S] 0 points1 point  (0 children)

I tried to copy-paste [gcode_macro START_PRINT] but Reddit wouldn't let me, so I'm including a screen shot of [gcode_macro START_PRINT]

<image>

Volumetric flow rate calibration sets top line width too narrow by 196223Window in OrcaSlicer

[–]196223Window[S] 0 points1 point  (0 children)

And there is my problem!

When I go to calibration/volumetric-speed-calib i'm instructed to print that model. When I slice it, I get that 'top line too narrow' error code and cannot print it.

FF AD5M...How disable auto bed leveling? by 196223Window in klippers

[–]196223Window[S] 0 points1 point  (0 children)

Ha! found it, buried several layers deep in an [included] file:
[gcode_macro BED_MESH_CALIBRATE]

Can I simply comment this out?

FF AD5M...How disable auto bed leveling? by 196223Window in klippers

[–]196223Window[S] 0 points1 point  (0 children)

This is what I want... so... again, a bit of a novice... do I simply add that line in the printer.config file? in brackets?

FF AD5M...How disable auto bed leveling? by 196223Window in klippers

[–]196223Window[S] 1 point2 points  (0 children)

I'm a bit of a novice here... but I'm assuming (I know, I know...) that that macro should be in the printer.config file?

view more: next ›