Did some testing with it tonight. The code generated works fine, however, I am making the travel distance from z probe to the x probe as well as the x prob to the y probe able to be customized.
I use 123 blocks with holes in them for a touch plate. Works great with the alligator clips. However, I didn’t have one in front of my while programing and found it was 5mm more than I thought to miss the hole and hit a solid point for the start of the program (z probe). I figure it would be good for this to be a user definable value.
So now every value for the gcode that is generated will be user defined. I am working on tool tips right now so that it will hopefully be clear as possible and easy to use.
I also needed to redo my stepper calibration since adjusting my Z pot, so I tested that tool. I will be adding a copy button in order to quickly copy $10X=VAL output to paste into the sender of your choice. The buttons are in place for hopefully a future feature to send this directly to the machine.
The idea is, when you need to calibrate, you can click “get values” and it will connect to the machine, read the current values and auto populate the boxes. You input the value you want to move to, click “send machine” and it will issue the G0X600 or whatever command for you. I will be adding a return to 0 key for each. Then, input where it “went to” the new value will be calculated and you can then click “update machine”. It will then send the $10X=NEWVAL command.
In other words, one window with everything you need in order to calibrate.
A question regarding adjusting and reading the meter for the pots. Does it need to be moving in order to get an accurate reading? If so, I might write a loop that will send the machine to travel back and forth to a desired distance… basically loop the command G0X600;G0X0 until the user press the stop key. Or, rather, user defines how many times it will loop and stop. This way it will be easier to get the motors moving without having to program it to “cut” a long rectangle.
I also added @PhilJohnson deflection calculator. If we can get this to communicate with the controller, then I would like to have it generate code based on the parameters to cut a “cutout” or “hole” for this test. In other words, no need to jump into whatever program to make a quick circle… just throw the numbers in, zero it, and send. Again, the idea is a one stop shop for the needs in question.
I hope this makes sense. If not now, then I hope it will later after things are hashed out some more.
as I’d be keen to give it a run around to see how it operates.