To Probe Basic from Gmoccapy

Sure you put everything from post gui hal back in? Look for conflicts. Somewhere you are using program.idle maybe in a pendant, you need to connect both instances so it can be used.

Firstly, let me say, thanks for the help so far. You are a star. On Xmas and Boxing Day. Thank you. I know I'm a bit obsessive, but don't expect it from others, so know that ti was appreciated.

So I decided to do a new build based on what I have learnt to date, and I realised during that process that I had made an error in where I got the core files from. I am not a muppet often, but this was good example. I incorrectly used the files from the Probe_Basic directory. So I did a rebuild using the correct files from the Machine_setup_files.

And guess what??? It worked. So forgetting the chair-keyboard interface issue, the instructions are solid with some caveats.

So here is some feedback from me on the setup instructions to help with the documentation for the muppets out there who may not have experience in Linux etc...

a) You need to instruct to delete the comments from the replaced lines. This is for non-linux people.
b) I would recommend commenting out the existing items from the hal and ini files and made comments about the replacement items. My understanding this is good Coding 101. And should help anyone reverse engineer the problems.
c) I have MESA cards, and found that the setup of these was best achieved using the MESACT configurator and not the pncconf. NOTE: pncconf taught me a lot about the different aspects of the configuration items, however, MESACT was better for me for a holistic setup for MESA cards IMHO. It allows you to select all of the cards manually and then verify them.

Separately I noted that when I did the configuration this way, I did NOT need to add the GEOMETRY statement. It was not there initially, and not in your files for transfer, and it started ok, no errors. I still need to do some more testing, however, looks better from atm.

So where are we at:

I could start, no errors. Was able to Jog per my setup and return to home easily. The Switch gear seems to work, and I need to sort out how the Axis limits work when I get this onto a machine. I am bench testing atm.

So we are off to a good start.

Because I am completely new to this sort of thing... CNC setups etc.. and CNC machining... What would be a good reference for learning about how to set up a machine, XYZ coordinates, tool offsets, etc.. that would apply to the Probe Basic layouts. This would include how to start off a simple Conversation job.

Thanks again.

Great, glad you got it sorted!

The linuxcnc docs are a good place to start, they cover setting up the machine home and soft limits and cover G and M codes etc... All of the questions for the most part should be able to be answered there in the docs regarding configuration for basic machines.

What type spindle do you have on the machine? Does it have an ATC?

Well not completely, I'm still just a baby on this stuff trying to get it functional. Will be on the learning curve for a long time I feel. I have not been able to get the Hole or Facing Conversationals going, which to me would be the next step. Once these are working I feel that it will be working well enough for me to understand some of the basics. I did complete some manual GCode instruction processing. So I know that aspect works. Just wanted to get the conversationals working as I can see these being invaluable when starting out.

On the ATC, I don't have one as yet, but am working towards creating one. The Mill being converted is a PM728VT. So Spindle control is available. I need to get to this once the machine is together. I am only bench testing atm. Still need to fit the ball screws etc.. yet.. The plan is to have the ATC will be managed via a pneumatic drawbar. Still trying to figure out best way on the tool change. Thought a set on the side of the table for pickup and drop off wud work best. A rotating one, although good is a little way off for me.

conversational is useful for small quick jobs, but most parts will use cad/cam software to develop tool paths and part programs to be loaded in the PB control to be run.

conversational requires you to setup the tools to be used in the tool table and save and reload the table. then in the conversational, determine which parameters to enter in the required fields to accomplish your desired motion and enter them in the appropriate boxes. then set the work coordinate offset so that the motion is adequately inside the cmachines configured work envelope. it seems you have a long road ahead of you, but your install is now functioning correctly, so once you develop the correct cnc machine knowledge you should be able to accomplish your goals!

Good luck with your Journey!

I believed I did all of that, got the Tools from the Probe Basic Library. Created a Conversational for facing like the video, set a tools offset, and then generated the Gcode. The tool path was within the Machine Box, and from all accounts should have worked. Just would not run the gcode as generated. And I missed your "learning question" 

Thanks. I started learning the Gcode, and understanding what it is trying to do. I noticed that the Tool changing is included in the initialisation of the GCode.

So I adjusted the Gcode to exclude the Tool change, and off it went. Thanks for the poke...  

Is there a way to exclude this from the gcode generation? I'm sure there is a simple way until I get n ATC.

It doesn't require a tool changer to use as is. It does require the tool be in the table. It uses tool data to call for the tool.

Understand. However, I needed to adjust the Gcode to delete the Tool changing code. Is there a way of switching off the Tool changer from the Conversationals so it does not add the Gcode?

post up your error message

we made some changes that should resolve an issue found in the way tool edits/calls from the conversational works, they are up in the develop version and will be released soon in the new stable update in the next day or two. if you would like to change to the develop version you could give it a try!