Advanced Search

I found this app to do the design so can cut this with laser

I have recreated the problem with the function generator. Now I am sure the problem lies in the configuration, or so I believe. For now, I would like to know which parameters I need to set to have the same parameters for frequency and pulse times in the hal and ini files (like pulse 1,000,000ns frequency 988Hz). Thank you again for your patience!

 

Ok, thank you, as you can tell, I’m not very versed on Linux. I will be at my shop soon to upload any pictures. I am putting 32 cross cut grooves into the handle of a wood baseball bat. I’ve already tested it and it takes the shock out of your hands. I have the patent and I have MLB guys waiting to try the bats so there is a lot weighing on me to get this done so I appreciate you. Cooper Groove is my company, my shop is in Joliet , IL, just outside of Chicago

I'm pretty sure you must issue a G43 command to reload and make the tool offset after changing the offset in the tool table.

I believe the "Apply" merely saves changes you've made so that Linuxcnc is aware of the change, but the new offset isn't actually put into effect until either a new G43 command is issued to actually apply the new offset, or the tool is changed while G43 is in effect. (At which point the new offset is loaded automatically).

Personally I feel that G43 should not be automatically applied with a tool change. I don't think most other cnc controls do this, and it leads to poor g-coding practices. (My opinion is that always explicitly issuing G43 Hn to set your tool offset after tool changes or an offset change is best G-coding practice.)

I tested the driver with the function generator and managed to reliably reproduce the problem. From the video, we can see the frequency and the ns coming from nvem. Therefore, I would like to understand how I can change these ns in the ini file and hal. Thank you for your help.

video

I have installed and works except lathe.
Why this project stalled ?

Hello,
so after some digging around i found the Doosan G Code explanation sheet. I uploaded it into my GitHub so everybody can access it. It was a pain in the **** to get it.

github.com/jochenr91/Integrex

It explains every G-code the machine accepts. Including G400 starting on Page 155 (Page 157 with example pictures).

Also interessting: The Doosan Machine exepts G68:

Three-dimensional coordinate conversion without B-axis rotating (G68.1/G69.1)
Three-dimensional coordinate conversion with B-axis rotating (G368/G369)

The question is how to implement it into the PP or replace G400 in the PP. I get the benefits of using G400. But i don't need this functionality, at least to get things running. On the long run of course it would be quite nice, cause this is one of the huge benefits of a mill turn. Since this G code works with the tool offsets automatically it should be used by the motion planner?!

But yes the touch off should be at  B0.