Problem with A axis rotation

I am using a lasertree k30 with a longmill 4830.
I am also using a openbuilds X32 controller with a Chinese chuck rotator.

I have the A axis steps set up properly in lightburn and can rotate it accurately with commands through the console.

I then move the A axis to the zero position

However if I setup a small job approximately 2x3 inches and run the frame command the A axis will spin in full rotations for quite a while.

I then verified it again by running the program.
It repeats the motion.

Im not sure what is going on. It almost seems like a inch metric conversion issue.

Anyone seen this or have a idea. Merry Christmas and thanks for your input!

I recall a user earlier in the year that run into a units issue with their A-axis in the firmware.

Have you tried running with LightBurn set to mm?

No I haven’t, but I’ll give it a try

I forgot to mention that the X Axis appears to move the proper distance

Were you able to test with millimeter units?

I have not. It seems to move correctly in the X axis direction and it would seem odd that it would use different units of measure for each axis. I prefer to work in inches if possible. I also read in a article that it converts all the movements into a unified output and the issue is it sees as steps per mm for linear and rotation as steps per degree so it’s not a clean conversion and that could be the issue. I’m hoping tech support can straighten it out when they get back from the holiday. I really appreciate your help with this though. I’m not sure what all I have to change to put everything into hard mm…

On the bright side I’ve been playing with lightburn and it works great. My spoil board is 32 x48 and I burned a a grid on it for part placement and size reference. Turned out great but I need to do more research on work coordinates lol. I’m gonna defocus it some and run again so I can get a thicker line on the grid.

It’s not that it uses different units. It’s that how the units are interpreted per axis may be affected by a bug, specifically the A axis. At least that’s what I recall of the other incident with similar symptoms.

You can continue to work in inches without issue. I’m suggesting pushing the Units button in the Toolbar to switch to mm before starting the job.

I don’t think this is likely to be root cause. Others use this without issue. It’s either likely to be a units bug or a more basic configuration issue not yet explored.

I checked out the gcode it was producing. I know a little gcode but not enough to tell what’s going on.

I could probably make it work by setting it up with the y axis but I’m running my y steppers in parallel and have the power kicked up to compensate. Kind of defeats the whole purpose of how I want it set up

I also looked into the vectric laser module but from what I’m reading there’s not a post processor for rotary laser. If It had one I could use openbuilds control and be back in business. I don’t know enough about making post processor to make it work. Openbuilds control works great with router and 4th axis

Does tech support monitor this forum? I got my laser and rotator working with a different product but like using lightburn.

What program is it working with?

And did you try toggling units to mm?

I’m currently running it in the vectric laser module with a PP I edited to add the rotation.

According to lightburn documentation it runs in mm by default but can display in either inch or mm.

According to that I would just be toggling the display of measurements. Also the X movement appears to be correct.

This is true. However, as I stated earlier, I recall a user that ran into a firmware issue where if LightBurn sent commands to the firmware in inches for the A-axis that it did not work correctly.

Try clicking on the yellow highlighted units value to show “mm”. Then run the job. Do you get different results? It would be good to confirm whether or not this is the root issue.

What did you use for the content of the PP?

I based the laser rotary PP off of Openbuilds GRBL (mm) (!.GCODE).
I added the Rotary Requirements from G-Code WrapY2A (mm) (*.tap) from Vectric PP list.
I had run both both of these previously with good results.
I’m by no means a PP expert but setting them up side by side and editing I have a PP that works. Took awhile but happy so far with the results. I’m running other jobs today and out Monday but I’ll get to switching with mm first chance I get and report back. I agree it needs to happen to see if it works or not. Thanks again for the help!

I read every new post on this forum in the hopes of learning something. What does PP mean?

I inferred this to mean “post-processor”.

Nue Rotary OpenBuilds V3 GRBL (mm) (!.GCODE).txt (5.6 KB)

Switching to mm seems to have solved the issue.
Good catch, thanks for all your help!