Probe Basic ATC Setup Problems

More
2 years 9 months ago #291594 by PeterSi
Yes, the commands are remapped according to the probe basic install guide. The .ini is attached to the original post.
And when I just use the "M6" command (which should mean the same thing as "T0 M6" when the machine is started) it works. The toolchange.ngc gets executed and the tool in the spindle gets transferred into the ATC.
But when I type "T0 M6" (or any other tool number) it doesn't work. It starts the execution of something but nothing happens and all I can do is stop the cycle.

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #291620 by CNC_ANDI
do you have the tools saved in the tooltable?
click on load spindle insert a tool with the number where you select... and click store tool.

you can only change tools where are in the atc stored.

toolchanger homed?

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #291649 by PeterSi
The tool table is filled correctly, I also tried it with the tooltable from the sim.The "store tool in tool changer" button doesn't work because that one also just calls a "T0 M6".The toolchangers homes correctly with M13 and updated the tools it has stored. I made some screenshots of the Linuxcnc log to try and better explain the problem.

In the following logs the spindle had no tool loaded and the ATC had T1 stored in Pocket 1.

Using the "T1 M6" Command resulted in this log: 
 
At this point, nothing happens and all I can do is stop the cycle resulting in this  error:
 

This would suggest to me that there is a problem in m24 and that there are generally problems with the subroutines not being callable.

But if I use the command "T1"  

and stop that cycle again manually:
 

And then using the "M6" command, the full tool change procedure gets executed without any problems with the following log resulting in a successful tool change.
 

That should mean, that the subroutines can be called and work correctly. So I don't understand why the same toolchange call doesn't work if I use "T1 M6". It should do the exact same thing.

I also had this error at some point but I don't know how related it is:
 

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #291904 by Lcvette
always test against the atc_sim if it is working then you know the issue is found in your configuration or subroutine modifications. no probe basic macro calls for T0 anywhere if the spindle is to be emptied M61 Q0 is used to do so. i would start by going through and comparing your altered subroutines to the simulation subroutines and find where the issue is breaking.

unknown word errors are triggered when incorrectly formatted syntax is used, ie a o where a 0 should be or vice versa. make sure you do not have any typos in your subroutines.

you cut off the error data that would show you or give a clue where the error originated from in the subroutine. i recommend investigating if you can repeat the error in debug.

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #292078 by PeterSi
Thanks for the answer!
What I meant with the "T0 M6"  is that the "store_tool_in_carousel.ngc" subroutine calls a "T0 M6".
I tried to test out if my subroutine modifications caused a problem, so I replaced everything with the stock subroutines that work in the sim and tried the simplest case:
T0 is in the spindle and I call a "T0 M6". 
All I changed was a PRINT statement to see if the program executes the right "if" statement.
 
I would expect that upon calling "T0 M6" the toolchange.ngc file checks if the selected tool is already in the spindle and, if so, exits the subroutine.
But the execution starts and then never ends. The subroutine never Exits. Looking at the log, the Variables are correct and the if statement successfully checked that the tool is already in the spindle but the endsub doesn't get executed for some reason.
 
It just gets stuck here and I don't understand why.

I am sure you are right and it's some kind of problem with my config but I can't figure out what. I even made a new machine config with minimal features but I still get the same problem.

You mentioned that my error Date is cut off. What exactly do you mean and how do I get more debug data? 

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #292083 by Lcvette
i was referring to your screenshot, the information for the offending code was higher up than where you cut the image off at.
The following user(s) said Thank You: PeterSi

Please Log in or Create an account to join the conversation.

Moderators: KCJ, Lcvette
Time to create page: 0.229 seconds
Powered by Kunena Forum