Probe Basic Lathe Status

I don‘t generate Gcode.
I run the scripts from Andy and use the gui variables wit named parameters. and a sub_button to run the script. It‘s really that stupid.
I know the conevtional in the mill vcp are more capable and there is the native cam. But I am just scratching the surface of LinuxCNC.
And mostly just thinking for my needs and my capabilities and they are limited.
I avoid python when I can (don‘t really like it) so most of my Cosimo codes are written in G-Code and bash. My Popup windows are done with Zenity. Cause that’s where I now roughly what I am doing. But most of the time I copy everything together from parts once programmed in the past. So it‘s not really programming more a stick and glue. I call this in denglish „educated pfusch“ I think it would be something like educated botch.
But never the less I hope it helps others I think this weekend I will have everything in such a way I don‘t feel to embarrassed to share it. And wit a litte help I might also be able to upload it to git.

cheers Patrick

I wonder if the MDI widget Joco did might be able to help save conversational created gcode. it is pretty useful if you need a couple of the same small fairly simple parts and don't really need cam but is more convenient to use conversational then mdi entry.

which MDI widget?

{I have too many options on GUI's and struggling to focus on one that is clean, simple and does the simple routine tasks ...... I keep going back to NativeCAM and trying to Python3 it..... current pythonism is doing my head in and about to give up again... until next time}

so...
I finished all cycles
turniing, boring, facing, chamfer, radius, threading, "drill n bore" and tapping.
All its in English now and I found the right section in the ui(xml) file.
So it should be easy to copy it into a fresh checkout from the git repo.
So I will test everything on Saturday and then I can merge it into a fresh checkout and find a way to upload it. I will also try to document how to integrate it.

cheers Patrick

Thank you very much Patrick. Still waiting for my PC parts.

well I have two issues, the radius doesn't work. And on high rpm the tap doesn’t reverse, but I think that’s an issue of my long ramp time at high rpm. At low rpm it works without problem.

If someone wants to try it I've attached the files.And here a howto for someone who wants to try it.

Download:
 

1. unpack
2. copy images to:  probe_basic/probe_basic_lathe/images/
3. copy the subroutines into your subroutines folder
4. open your "probe_basic_lathe.qrc" file and copy the content of  "add to probe_basic_lathe.qrc" to the image section
5. open your "probe_basic_lathe.ui" replace the section between
<widget class="QWidget" name="tab_4">
and 
<widget class="QWidget" name="tab_3">
with the content go "substitute snipet probe_basic_lathe.ui"
6. go to the main folder of your probe basic folder and run qcompile . 

I also have merged it this way into a fresh checkout from probe basic master.
and if someone tells me what to do I can upload it.

cheers Patrick

Patrick - the cleanest way to request a merge is to generate a pull request on the PB master repo in github. But that is easiest if you have your work on a github repo.   This will generate a pull request in the PB repo’s queue. 

it is possible to do a request outside of github using git request-pull. But you will need send emails manually. ie no github direct integration.  

cheers.

Hello,

the way to open a pull request is very easy

1- fork the probe basic repository from github to your github account

2- clone your fork and apply the patches

3- commit and push to your remote repository (your github account)

4- then from your repo you will be able to start a pull request

thanks!

you can use gitkraken a non free very easy git client

Thanks!
I‘ve made a fork of master now.
This weekend I used the conventional and found two minor errors.
What I also have to mention is that the default settings match my lathe and standard inserts. Which is fine for me. And I share this state this week.
I wonder if it would be more useful, if I store and load the last settings. I could do it with two custom M-Codes.
The one for storing the date I can put in the scripts the other must go into the default Mcodes at startup.

I guess loading and storing more sets in a table would be even better, but a bit over my skill level at the moment. Not the loading and storing, this I can do in bash, but I would like to have the data in a table displayed in the tabs.
If I can display a csv and trigger a reload from mcode…

Or I need to dive into python for that. I still dislike it but since Iv‘e done similar stuff in Perl, so I sure find a way. But this sounds useful.
Besides the parameters I would give it a name and a comment.

Since I am a python noob there seems to be a bigger change in python at the moment. I guess I should use python3 for development. Can I do that without problem my older version of probe_basic?
Cause I would develop it on my running lathe, otherwise I can’t really test.

Sorry for bothering you guys with such basic questions.

Cheers Patrick