Advanced Search

Search Results (Searched for: )

  • HansU
  • HansU's Avatar
02 Feb 2025 09:58 - 02 Feb 2025 09:58
Replied by HansU on topic Macros. File not open

Macros. File not open

Category: Gmoccapy

Try to give an absolute path for the macros or play around with that value:
[RS274NGC]
SUBROUTINE_PATH = macros

See linuxcnc.org/docs/devel/html/gui/gmoccapy.html#gmoccapy:macros[/color][/color][/color][/color][/code]
  • HansU
  • HansU's Avatar
02 Feb 2025 09:48
Replied by HansU on topic Gmoccapy 3.5.0 - opinions needed

Gmoccapy 3.5.0 - opinions needed

Category: Gmoccapy

Could be to only show elapsed time and predicted time (I did not get where this value comes from) instead of a progress number as you can already see how much the blue bar is filled.

I implemented a timer for the elapsed time myself to keep track of CAM-prediction vs. actual time as well as the spindle load which is super useful to get to know how hard you push your spindle. Not pretty but works^^

The G-Code Size I don't see much use for (if the program time is not there anymore), what I care about file size or lines of code? At least its hiding the currently used tool in the operating state. Imho more something for another layer like inside the file menu?

 


 
The predicted time is available in the G-code settings, see (2) forum.linuxcnc.org/gmoccapy/55010-gmocca...eded?start=20#319096

The reason why I put the progress and the elapsed time there is that it does not need further explanation there and is more  intuitive (IMHO).

The G-code size is usually not of big interest, I agree,  but I let it there to be consistent with the G-code properties e.g. in Axis.
And it is not hiding anything, as it is an optional tab.
  • Tim_cnc
  • Tim_cnc
02 Feb 2025 09:31

Fusion360 postprocessor for linuxcnc lathe with tailstock axis in Z Direction

Category: Fusion 360

Good morning everyone,

I've ran into some problems generating gcode for my linuxcnc lathe.

The lathe has following geometry:
XZ-lathe with turn-tooling on a revolver on the XZ-stack (Spindle rotates around Z)
Tailstock with drill-tooling on a revolver on a axis parallel to Z but named Y so i can use G33.1

This setup works perfectly fine for me if programmed by hand. My only problem is the CAM-programming with Fusion360. Everything works fine besides the drilling operations. The Fusion post spits out the Toolpath with the letter Z instead of the needed Y for drilling-cycles. I was unable to change this behaviour in the linuxcncturn-post.
Does anyone know a workflow or a fix to this problem? After a lot of research surprisingly few people even have a tailstock axis on their cnc lathe?

Thanks for your suggestions
Tim
Displaying 19666 - 19668 out of 19668 results.
Time to create page: 0.578 seconds
Powered by Kunena Forum