Machine: FSLaser Muse
Firmware: Smoothie Cluster
It’s likely this question is more suited to the Smoothieware forums/etc., but since the Cluster firmware modifications look to be touching multi-axis acceleration management, I thought I’d start by asking here.
I replaced a Full Spectrum Laser Muse’s stock controller with a LaserBoard. This swap was a bit of a project in itself, but aside from some PWM quirks, I didn’t encounter any hardware, wiring or basic setup problems I couldn’t address. My problem, in a nutshell, is this: the Muse’s X and Y axis have drastically different acceleration capabilities, and Smoothieware consolidates them in a way that’s proving unintuitive and problematic. For some background, the Y axis can accelerate nearly an order of magnitude faster than the X axis. Let’s say (ballpark) 8,000 mm/s^2 vs. 1000 mm/s^2. Y’s maximum velocity is roughly three times that of X’s also.
When configured as default_acceleration = 8000, alpha_acceleration = 1000, beta_acceleration = 8000, Y is fast and can apparently (I haven’t tested this extensively) support a few hundred mm/s for engraving. However, the X axis acceleration limit doesn’t appear to be respected fully, and I can hear X missing steps occasionally when following complex paths when vector-cutting a test pattern (e.g. a Hello World text outline). This is with junction_deviation dialed down all the way.
When configured as default_acceleration = 1000, alpha_acceleration = 1000, beta_acceleration = 8000, X behaves as expected, and never misses any steps. However, Y is then limited to 1000 mm/s^2, which severely limits its engraving speed. Even straight, X-axis-only G0 moves are apparently limited to 1000 mm/s^2. I know Smoothieware does coordinated moves, but it’s unclear why it limits single-axis moves the way it does.
default_acceleration defaults to 100 mm/s^2, so if unset, that’s what both X and why are limited to. Basically, changes to default_acceleration govern machine motion, even though the acceleration is specified explicitly for X and Y. This has my stumped at the moment. I see the same behavior with stock Smoothieware firmware, so it doesn’t appear to be related to the Cluster firmware changes.
Does this ring any bells, and/or does anyone have suggestions for experiments to try?