Dimensions are not transferred correctly

Snapmaker Luban
1

Hello together
I would like to mill a tip on a 12mm diameter wooden bar with my turning module on the A350.
When I import my data of 40mm length and 12mm diameter into Luban, a workpiece with 90mm diameter and 95mm length appears.
To get anywhere near my dimensions, I have to enter a diameter of 37mm and a length of 39.5mm. What is going wrong here?

2

I can’t say much about rotary milling but essential information is missing.

Whats your work flow, used modeling software, file extension, Luban version, operation system?

3

Hello xchrisd
Thank you for your reply.
My operating system is a Mac, the model was designed on Autodesk Fusion 360 and with Dashboard | Tinkercad, with the same result. My Luban version is the latest 4.15.0.

4

I think the best way to get a response would be to open a ticket, support@snapmaker.com or https://snapmaker.formcrafts.com/support-ticket
Share your model and the information with them, I hope this will bring a future update or bug fix.

5

From SM
Yes, currently, Luban has a known issue where STL files are scaled when processed in four-axis mode. Unfortunately, this is not something that can be fixed in the near future.

We have already reported this issue to the product team and hope it will be fixed in future versions.

You might want to try using other software to see if you can achieve the desired result.

Apologies for the inconvenience.

1 Like
6

Are there any alternatives?

7

Old luban Version maybe?

8

There was a lot of discussion about alternatives for 4 axis, take a look at this topic:

9

Hallo
no, latest version

10

Hello
Thank you very much, I will do some research.
By the way, no matter what the diameter of the object is, after the transfer in Luban it is 90mm.
Snapmaker knows, but has no solution for the time being.
Yours sincerely
Roland

11

yeah, i got that. I mean to reinstall an old version without that bug in meantime. As mentioned, it is not easy to find another software for 4axis cnc work.

12

I now have all versions back to 4.0, which is probably the first version with the 4.axis. The error already existed back then and was apparently never noticed.