Probe Basic ATC Questions

Hi,

I updated ProbyBasic to the newest dev version and I am facing two Issues. After the update, I deleted all my old folders (user tabs, subroutines, python etc...) with the new folders from the example config. I am currently trying out the ATC Rack tool Changer. 

Issue1:
For this, I am trying to modify my linuxcnc.var file, manually changing the following Parameter:

"3973    10.000000
3979    1.000000
3981    -76.000000
3982    0.000000
3983    1137.000000
3984    615.680000
3985    1137.000000
3986    565.680000
3987    1097.000000
3988    615.680000"

However, when opening Linuxcnc, all the values are still 0. When modifying some values in the GUI, for example X Position for P1 to 1337, I get the error "Error: No Conditions Met, Rack ID Not Set" BUT when hitting "update Rack ATC Parameters" the Value is saved in the linuxcnc file (but all the other values above are overwritten to 0.

So, I would be fine with including all these in the GUI but the only value I can not change is the "ATC Rack ID", which seems to be write protected and, I assume, creates the error above.

EDIT: Okay, I filled now all Parameters and it seems to have created a RACK ID -> 4. And it is working now.

Issue 2:

I set up everything and can now manually clamp and release the tools. The Tool touch off is also working (on both ATC and Tool Tab). However, when clicking "Store Tool in Rack", I get the Error "Unknown m code used: M10" but M10 is in the subroutines folder.
Similar to clicking "Ref Rack Data" (what does it actually do?) I get "Unknown m code used: M13".



 

You need to set the parameters in the UI only

The rack is is calculated automatically based on your pocket location settings in the ui

Thanks!

do you also have an idea for my second issue?

you need the subroutines from the rack atc sim, they are specific to rack atc, the subroutines in the standard probe basic file are default for carousel type. copy over the complete subroutine folder from rack atc config sim folder to your machine config folder. should work then.

Thanks for the quick reply. On installation, I copied the "macros_metric_sim" folder into my "subroutines folder" from the "rack_atc_sim" folder, is this correct?

Manually clamping / unclamping works (so it seems to use the "clamping" and "unclamp" Gcode).

I attached my machine config (currently a bit messy as I switched from a custom Rack tool changer (which worked so far), to the probe basic one and I think I found one issue (which I fixed). For some reason, I had the following line included which broke something.

REMAP=M6   modalgroup=6  prolog=change_prolog   ngc=toolchange  epilog=change_epilog

Removing this at least lets me click "Store tool in Rack". However, it doesn't do anything except for setting the active tool to "No tool loaded". It doesn't move my spindle. Clicking "Ref Rack Data" (still don't know what it does) gives me the "Unknown M Code used: M13").


 

kcjengr.github.io/probe_basic/machine_config.html
in the docs

Thanks for pointing to the Manual, I was not aware that this document changed.

I got it working now. One thing I added was the Airblast when picking up / putting away the tool by rewriting M24 and M25.

However, there is also the Airblast Button in the GUI. Is it actually connected to something?

Another point is that the ATC seems to forget the traverse Feedrate every time I start linuxcnc. When picking up a tool I get the error "Cannot do g1 with zero Feed rate" and have to go into the Rack Setup and click "Update rack parameters" (although the Feedrate is stated correctly here).

I now know that clicking "Ref Rack data"  loads the Tools that are stored in the Rack. Unfortunately, It doesn't use the Tool Table "Rack" coloumn as I understood. 
I assume this would require a Python script to read the tool table and make it usable via Gcode?

Thank you for your patience by the way, really appreciated!

You need to update the var file parameters, also in the docs.

I'm not sure what you mean about the tool table and the rack the rack stores tools the tool data is stored in the tool table. The rack holds whatever tools you put in it they don't have to be in order it tracks them persistently as long as you have the var file set up. When a tool is loaded from the rack and you use the offset for stored in the tool table everything works as expected it works perfectly fine with cheat code. You call the tool not the rack number.

Enter these numbers in your var file...

kcjengr.github.io/probe_basic/probe_basic_parameters.html