Advanced Search

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.




 

Last I checked this still worked, let me know if you encounter any issues:

linuxcnc.org/docs/devel/html/plasma/qtpl...#_material_converter

Can you post the original gcode file you’re having issues with please?

I'm almost certain that the problem with the stepper's jerky movement that I'm having is the ENABLE pin not connected. I tried connecting it to +com with no success. I would like to try connecting it to a GND but I'm afraid of causing damage. Does anyone know where I can connect it to ground without causing damage?

I think this is where my confusion comes in.

Because i only have one pin to use.
The home input.

I hooked up an external power supply.
And a switch from the positive lead.

Would this be the correct ting to do. Attachement 1.
Or do I need to add an extra resistor prior to the pin in or prior to npn signal.


Feeling like swimming with no land in site.

So im must be going about this the wrong way.
My brain hurts trying to think about this.
Im honestly trying.

Maybe best to get some other switches.

tool is fine.

Attached photo of where it has decided to put this job.

youtube.com/shorts/1EClHJCqams?si=MQ32zTsIXvcrC1F3

aDm1N wrote:

My project is slowly progressing. I've put together a few things using examples and AI.

Warning: Spoiler!

The interface starts, but I'm stuck in the ESTOP. The statuses in HALSHOW aren't changing either. So there seems to be no connection to the board, even though pinging 10.10.10.10 is successful. Is there a way I can test the communication? 

File Attachment:

File Name: custom_2025-05-05.hal
File Size:2 KB

 

File Attachment:

File Name: custom_postgui.hal
File Size:1 KB

 

File Attachment:

File Name: drehbank.ini
File Size:2 KB

 

File Attachment:

File Name: handrad_zxc.hal
File Size:2 KB

 

File Attachment:

File Name: nvem-rt1052.txt
File Size:7 KB

AI does not exist, it is just a big script with access to a huge database of data. Most of the time it responds randomly. It only helps you if you know, for example, C++ very well and then you have to correct all the errors it makes ... basically you have to re-do everything yourself.

I advise you to never use it again, it is a scam!

Hallo
Habe nicht gesehen Das noch wer einen Fehler gefunden hat (PCW) Danke das war der Fehler, somit dreht sich die Spindel. Habe das mindestens 5 mal angeschaut bis ich gesehen habe das das L fehlt.
Danke nochmal allen die geholfen haben.
PS: Habe die Software so mit den fehlern bekommen.

Looks like G368/G369 can be handled by the TWP functionality.
G400 is different as it transforms the tool offset rather than the tool position.
I'm not very familiar with cnc turning so I have little idea how linuxcnc handles the tool orientation as set in 'R' and 'K' words. There is this document which also refers to tool orientation but I have really no idea if this is actually used in motion planning or only in the GUI.
linuxcnc.org/docs/html/lathe/lathe-user.html
I'd say it's certainly possible to recreate this using a python remap.
Note though that even Doosan suggest that it is more accurate to touch off the tool at the b-axis angle used in the operation.