Excess Traversal moves

[Guillaume]

Hello again community,

The traversal moves on my device seems to be more present than ever before. I do not recall changing the settings or upgrading to a latest software version recently. It creates more useless movement and hence more printing time.

Would you know how to minimize the excess traversal moves?

Picture below shows ridiculously wide traversal moves :

Picture below shows what I am for :

I understand there will always be a little excess traversal move for the nozzle to slow down before going the other way; what setting should I toggle around with to optimize it?

Here are the machine settings :

Thanks for the insight.

Guillaume

[thelmuth (Tim Helmuth)]

It’s possible that Lightburn doesn’t have the proper settings from your machine. From what I understand a Ruida controller sets the overscan internally and lightburn has nothing to do with the actual overscan. Lightburn just estimates the overscan based on the settings in the device settings window, additional settings tab. Open this and click the read from controller button and see if things change.

[jkwilborn (Jack Wilborn)]

@thelmuth

estimates the overscan based on the settings in the device settings window,

Yes, so I’d at least follow his suggestion and read from the controller.

@Guillaume

how to minimize the excess traversal moves

If you mean in the red, the only way is to lower your scan speed or increase your acceleration, if possible.

When operating a Ruida at 90 degree scan increments the Ruida will compute and apply the overscan internally.

@Guillaume

below shows what I am for

Where did you get this? They are different, look at how the two are different –

I’d say this is scanning much slower or you’d have move overscan present. I can zoom in and see some red…

---

A lot of this depends on what settings have for optimized code generated and speed settings.

It would be nice if you could at least post the power/speed settings. If you can post the lbrn file, that would be better.

[Guillaume]

Hello Tim,

Thanks for coming back to me so quickly!

I’ve read from the controller. Values were not changed after the reading. I toggled around with the “x acceleration”, it does change the traversal movement amplitude! I will play around with it to see what fits best my current project.

[Guillaume]

@jkwilborn

lower your scan speed

You are totally correct! It took me a while to realize… I’ve changed from an amateur machine to a semi-industrial version. This explains why the traversal movement was almost non existent on the picture : Even thought the amateur machine was close its fastest speed, it still wasn’t enough to ‘need’ wide excess traversal movement.

[Guillaume]

I will let you know soon after the future try-outs but now that you’ve pinpointed the function to play around with, I’ll give it some goes!

Thanks again for your insights Tim & Jack!