Tool setter setup

More
1 year 10 months ago #317461 by CaspianCmonster
Hi all, like many people out there I am trying to get a tool setter setup. 
I am working from the example files but I think I have issues with file/folder mapping among other problems. 

I get a startup error usr/share/axis/images/axis.ngc: pycall(remap.change_prolog) failed 

I found a similar issue in my searches but haven't been able to figure it out. 

many thanks

Luke 

 

Please Log in to join the conversation.

More
1 year 10 months ago #317464 by MaHa
Replied by MaHa on topic Tool setter setup
The path for python is missing in the ini

linuxcnc.org/docs/stable/html/remap/rema...emap:embedded-python
Code:
[PYTHON] # where to find the Python code: # code specific for this configuration PATH_PREPEND=./ # generic support code - make sure this actually points to Python-stdglue PATH_APPEND=../../nc_files/remap_lib/python-stdglue/ # import the following Python module TOPLEVEL=toplevel.py # the higher the more verbose tracing of the Python plugin LOG_LEVEL = 0

Please Log in to join the conversation.

More
1 year 10 months ago #317470 by CaspianCmonster
Replied by CaspianCmonster on topic Tool setter setup
thank you, that is clearly something I need to fix :)

It would be really nice if I could just start with the demo files and adjust them to my machine's specs but I haven't figured out how to get that to work.

Luke

Please Log in to join the conversation.

More
1 year 10 months ago #317481 by CaspianCmonster
Replied by CaspianCmonster on topic Tool setter setup
Hi, I am making progress I think. 
the error I have now is that when I try test a file with an M6 command it I get an error 
"Program exceeds machine maximum on axis Z" 
It doesn't matter what code I have in there or where the machine is zeroed 

I have found how to sets the locations of the probe but can't find the source for the probing travels (I think the gcode has a reference to the INI but I don't see anything there) 
perhaps this is an inch vs mm thing,again I think that is correct in the file but it is a bit confusing. 

thank you 

Luke 

Please Log in to join the conversation.

More
1 year 10 months ago #317485 by MaHa
Replied by MaHa on topic Tool setter setup
Change position must be 0 or negative value
XYZ change positions are all in machinecordinates G53:

g53 g0 Z #<_ini[change_position]z>

Please Log in to join the conversation.

More
1 year 10 months ago #317492 by CaspianCmonster
Replied by CaspianCmonster on topic Tool setter setup
Thanks, that was helpful. I am still not used to the coordinate system but the locations are now ok and it starts without errors but when I run M6 it goes to the tool change position but stops there with no prompts like there are in the demo.
I think manualtoolchange.glade isn't being used 

thanks
Luke

Please Log in to join the conversation.

More
1 year 10 months ago #317502 by MaHa
Replied by MaHa on topic Tool setter setup
there must be a postgui.hal file, where the digital outputs M64 M65 and analog output M68 are connected, eg. motion.analog-out-00
Maybe from the source of your file, there are more infos.

In the ini file there is an entry for glade tab. Normally this tab should be loaded, when axis starts.  Maybe the tab gladevcp has some display or setting for toolchange

Please Log in to join the conversation.

More
1 year 9 months ago #317817 by CaspianCmonster
Replied by CaspianCmonster on topic Tool setter setup
Happy New year everyone.

I am back in the workshop and have made some progress.
I did a new clean install with the current version and on a much more powerful computer as my original machine was just not happy being a super slow single board computer from 10 years ago. The only other computer I have around with a PCI slot is a massive dual Xeron workstation which is a great heater in the winter :)

I was chatting with some other folks about this and they suggested that using the qtdragon interface would perhaps be a good idea so I made a config with that and it is close to working but there are some errors around calling the python files. I  used the text from the manual and added the "examples" folder step so they should point correctly but I think there is something wrong, either with what I wrote or how the paths are written in the example. (I don't understand the format with the text over two lines with a ":/" but I am no linux expert. 

Any ideas?

thanks

Luke


 

Please Log in to join the conversation.

Time to create page: 0.263 seconds
Powered by Kunena Forum