Advanced Search

You need to go through the config docs and make sure you're getting the signal and if you're getting the signal and everything is set properly in hal look in the post GUI hal file at the bottom and there's a spindle connection for actual readout, make sure that connection reflects what you have and your main hal file and in the settings tab in probe basic select actual RPM

Tool table problem first
I believe linuxcnc will just not write the axes that are zero.
The comment line is probably limited to a certain length in linuxcnc - though I can't find that limit at the moment. QtDragon is less limiting on comment length.

As for the Error message.
Am I understanding right, if you cancel the G54 offsets the process works once?

Chris

do you have a good config for this set up.
i have the same setup, but could not get right config. spindle wont start

i would seriously consider your options before you buy the rack thing, and also buy more than one if you really want it that bad.

how deep are you actually going?

since its for work, i would stray away from kickstarter tier stuff. not being able to actually adjust your settings is going to be a painful experience for you, depending on the spec of your hole.

if someone wanna chime in and correct me, but i dont think a short detect is really a control loop.

To get good results with the technology requires experimenting and constant process control. (from what I could find watching youtube, and from  conversations)

 

it does, and its called fast hole, not precise hole. depends on the spec, but overburn, combined with not being able to adjust the settings, runout from the setup, excessive electrode wear

THAT WORKED THANK YOU.

Thanks guys! Sorry for being annoying my coding skill is zero so I actually need to spelt out to me like a child but that's how I learn haha

Thanks again

I've looked through the updated config you linked and I can't see anything about a House section or HALLUI = halui

I tried the new debs and I have the same problem when booting.
I made an image after nvme that does not boot and I wrote it on an SDcard. From the SDcard the same image (6.1.75-rt23) starts.
Can you upload an image that worked for you on nvme. I would like to see if it works.

Hal, in the section you posted above..

[HAL]
HALUI = halui
HALFILE = CNCMACHINE.hal
# HALFILE = custom.hal
POSTGUI_HALFILE = probe_basic_postgui.hal
TWOPASS = on

If you download the file to the ~/Downloads directory then do the following:

Is [HOUSE] a section I'm supposed to have in my .ini? because I don't have that

See my post above you need to add that line in the house section

Haven't changed my .ini since posting it in the start of the thread besides adding one comment to my [HAL] here is that section

[HAL]
HALFILE = CNCMACHINE.hal
# HALFILE = custom.hal
POSTGUI_HALFILE = probe_basic_postgui.hal
TWOPASS = on

Aciera wrote:

Thanks Rod, I find it rather unfortunate that somebody like you does not seem be offered write access to the 'official' install documentation. The pull request process is so sluggish that by the time new install docs might actually make it through they're already outdated.

I have tried to keep my doc current but I have not installed on a problem PC for quite a while. It has been suggested the install ISO should install the R8168 driver as it should not get in the road. Not sure on that. (I built the ISO and the Pi images for Linuxcnc).

At one stage I was asked to edit the getting Linuxcnc docs and it included most of my documentation notes you refer to. This was accepted and was published in the 2.9 docs. However, when 2.9.1 was released, this was all blown away and replaced with content based on 2.8 docs.

I think there should be a new document added that might be called something like "System Optimisation for Linuxcnc", perhaps a seperate doc for the raspberry Pi it links to. If somebody was to have a go at that from my material, I would not have a problem. Asciidoc and I are not good friends.
I almost know enough about git to be trusted with write access... but time is an issue

For a gantry machine you must have homing sensors on both sides of the gantry.
for an XYYZ machine, start with a HOME_SEQUENCE of 0, -1, -1, 2  for each joint in order
Ref: linuxcnc.org/docs/stable/html/config/ini...l#sec:homing-section

Hey!

I am currently trying to get my machine running. My current issue is that I can not get the connection between my spindle (A BD600 via VFDmod over RS485) working in ProbeBasic. I can change the speed of the spindle using GCODE, so I can confirm that it works. However, I can not see the speed in BasicProbe nor can set the Speed. I think I am missing any HAL connection. My machine hal (iHSV57.hal) is currently a mess but I attached it as well.

My BD600.hal looks as following:
Does anyone know the correct connection? Is there any documentation available?