Surfacemap Z compensation with Probe Basic

Just discovered that the .var file was created with group and other permissions set to read only. Changing these to read and write seems to have made a difference. The probe feed speeds now seem to be updating based on values entered in the ui.

The ui entry boxes for probe feed settings in the surfacemap user tab still don't work properly. 

I'm not super familiar with surface map, but I would guess it's because the bar doesn't have those parameters or the subroutines that updates the bar have those and needs to be updated.

Did you follow the surface map read me instructions and copy over the subroutines? Those are what set the var file parameters for surface map page

Yes, I did.

The surface_scan_param_update.ngc file only seems to handle parameters 3050-3054. These are associated with the ui buttons that seem to work.

github.com/zmrdko/01_surfacemap/blob/mai...can_param_update.ngc

The surface_scan.ngc file mentions several other parameters:
3055, 3057, 3058, 3059, 3060, 3061, 3062, 5061, 5062, 5063, 5403

github.com/zmrdko/01_surfacemap/blob/mai...nes/surface_scan.ngc

I did try adding these to the .var file but that didn't work. Perhaps they also need to be added in a similar way to surface_scan_param_update.ngc?

Another problem is that the instant you try to type a character into the ui boxes for feedrate on the surfacemap user tab it attempts to do something. I.e. It doesn't wait until you enter the value, it tries to send individual characters.

i found some really odd namings in the ui for the widgets, it is very confusing and appears to be unfinished or a the very least very poorly internally connected. i'm not sure where some of the parameters are coming from or if they were intended to be hard coded only in the var file or not. I don't think this is actually a finished project from the looks of it, at least not from the link you posted above. you may want to try contacting zmrdko.

from my scan through the ui, subroutines etc, things do not match up and widget names are duplicated as if copied and pasted but not correctly named so it's hard to follow the parsing flow correctly.

there is also no custom_config.yml setup instructions for the ui widgets to be stored in and saved and loaded on startup which means everytime you startup probe basic, those variables in the ui will be dumped and set to placeholder text (0.0000) which will be unsynchronized with the persistent var file data.

these are things that can be resolved in the upcoming release as i created a new var line edit widget that will not rely on subs to store and load variable from the var file.

some of the numbered parameters you listed above are linuxcnc params:

linuxcnc.org/docs/stable/html/gcode/over...:numbered-parameters

any params used in probe basic or any other add on would be between 3-5000 as these are user configurable parameters. anytime you see one 5001 or higher it will be a dedicated parameter used in linuxcnc.

I would say that this project is still a work in progress from my look into it.here is my mapping of everything, you could probably fix it and ask the developer for a pull request if you wanted, that would be the course i took,but as it stands i don't think you will be able to get it working as is.

 

 

Thanks for taking the time to have a look, and for confirming my suspicion that the surfacemap code might not be complete.

Is there any prospect of an official probe_basic surface grid probing and z-compensation tab? Perhaps using scottalford75's z-compensation code via external offsets:

github.com/scottalford75/LinuxCNC-3D-Pri.../master/compensation

(I think this feature may already be included in QTDragon, although with compensation via g-code ripper rather than external offsets).

Sorry for possibly adding to your already no doubt long to-do list!