this post was submitted on 20 Mar 2024
226 points (97.9% liked)
Asklemmy
43863 readers
1591 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've done some gcode but moved onto other programming(mostly c# so completely different. One thing I HATED about gcode, I don't know if it was just my machines or gcode in general(most of mine were based on fanuc cnc controllers typically seen as top of the line) , we were not able to name variables.
I create a variable and assign it #315. What does #315 do? What does it mean? Who knows... Better have notes or comments to explain or your fucked. I can't say variable x_offset_tool_15 nope...just #315.
I worked with Fanuc control machines for 20 years up until 2023. Sounds like you were needlessly in macro hell. Just declaring an offset will use either an H (typically height) or D (typically a radius offset in Fanuc controls, but sometimes they are setup for diameter).
It would go something like this:
You don't need true macro variables for 9/10 applications, or general operation. I feel like you got placed on some overenginered solution.