Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown measurement units #2

Open
Carnaxus opened this issue Feb 6, 2018 · 3 comments
Open

Unknown measurement units #2

Carnaxus opened this issue Feb 6, 2018 · 3 comments

Comments

@Carnaxus
Copy link

Carnaxus commented Feb 6, 2018

There is absolutely no documentation anywhere on which measurement unit this simulator uses. I pasted in code designed for inch measurements, but the toolpath looks completely wrong.

@Carnaxus
Copy link
Author

Carnaxus commented Feb 6, 2018

After poking around some more, it seems that your simulator is simulating the workpiece by diameter, but the turning movements by radius. This leads to the toolpaths being offset from the workpiece by half the workpiece's diameter. Most CNC lathes use diameter-based coordinates, so for example if my workpiece was half an inch in diameter and I told the machine to move to X 0.31, it would in fact move to 0.155, thus bringing the diameter of the workpiece to 0.31". Your simulator, on the other hand, goes to the absolute position of 0.31, meaning that there is no engagement with my half inch workpiece due to the actual workable radius of the part being only a quarter inch, or 0.25".

@arthurbeggs
Copy link

arthurbeggs commented Feb 8, 2018

@Carnaxus the lathe simulator is supposed to work on a didatic CNC FANUC 21i-T lathe. To define which unit you want to use, you need to set G20 (for mm, maybe already inferred) or G21 (for inches, maybe not implemented). G90 code is probably inferred too and defines the absolute coordinates programming, and that's why you get unexpected toolpath behaviour (it's not wrong, just different than what you expected).
Please refer to this table and choose the correct configuration codes to the simulator behave the way you want.

@Carnaxus
Copy link
Author

Now I'm having a whole new issue: The simulator straight up doesn't work anymore in Chrome, and doesn't render anything in Firefox.

Arg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants