Advanced Search

Didn't get a chance to update and try the label yet as I'm working on the hal file at the moment. Couple of things I'm noticing now that I'm running some sims......

Since I added a qss, INPUT = TOUCH seems to not have an effect anymore. Pretty sure I had the touch style file browser before the qss but now it is back to the normal one.

The file browser is a little hard to navigate because it doesn't show the current directory, easy to get lost. Any chance you can add current directory at the top or something?

The flood and mist push buttons disable when a program is running. I'm used to Gmoccapy where you can still operate the mist and flood while running a program. Sometimes I forget to add coolant to the program and need to turn it on when it's running. Not quite sure why yet but as soon as the GUI disables coolant even if I stop the program I can't control it again with the hal buttons until I first turn it on with the GUI buttons.

I tried every possible combination with the X axis limits and homing. Still isn't working. I noticed something with the Z axis. The search velocity for home is a positive number. It should be negative? But I change it it goes the wrong way. My limits for Z are 250 positive away from the spindle. And 40 negative pass homing.Iv attached two other working ini files from other people. Iv noticed in one of them that for X axis the search velocity is positive. That would bring it up but the home switch is in the negative direction. Is there other settings somewhere else in a file for machine setup ?

Ok. As long as I am aware of it I can handle with it and I will choose smaller values.

Right now I am trying to get a 4 axis Machine running. Right now the scurve tp is making a lot dump things.

Grotius, do you have a 4 axis sim machine running to play with?

Boot into Ubuntu, mount the linuxcnc partition and bingo you have access to the files.

But if you can’t do that what’s more annoying, copying the files or not being happy with your machine ?

If you want to be helped you need to provide the info.

Without the info it’s hard to impossible for those helping and you don’t get the answers you require.

Yes, the problem with using a fixed blend radius on all segment intersections would be that the path deviation depended on the angle at which the two segments intersect, which would be rather unfortunate (If that is indeed what it is doing). For angles larger than 60° the blend radius and thus the feed rate could actually be larger for a 0.1mm deviation while angles below 60° would require a smaller blend radius to stay within a maximum deviation of 0.1mm.