How to make a tool changer move to home

Thanks for the compliments but really I'm a numpty myself.

As for the B encoder signal:
I haven't followed as to why you have the encoder but I presume it's on the spindle.
If you just need the spindle speed then you don't need the second encoder signal. If you need to know which way the spindle is turning you would need both signals.

[edit]

s it out of your remit

I dabble in almost anything and everything

Aciera wrote:

Thanks for the compliments but really I'm a numpty myself.

As for the B encoder signal:
I haven't followed as to why you have the encoder but I presume it's on the spindle.
If you just need the spindle speed then you don't need the second encoder signal. If you need to know which way the spindle is turning you would need both signals.

[edit]

s it out of your remit

I dabble in almost anything and everything

Yes I know you are into PnP with ethercat
.
Yes It needs to be able to thread which needs Z+A but ridged tapping needs AB+Z so I might try it with just A+Z. I have a 100 slot disc with 3 slotted opto,s with one extended for the Z. I have that on my own lathe as well but with a 5i25+7i76 so no prob. with inputs.

Update:

I have now got back to this little lathe and would like to know if it is possible for the axis gui to remember the last position of the tool changer on start-up. As it is easy to forget to input the tool number after a reboot.

forum.linuxcnc.org/49-basic-configuratio...home?start=10#190038

There was a discussion about that here:
forum.linuxcnc.org/38-general-linuxcnc-q...ve-variables?start=0

Bed time reading is here:
linuxcnc.org/docs/html/gcode/overview.html#gcode:parameters


So it seems that you could save the tool number in a parameter using gcode like this:

IIRC you have a tool change remap, so maybe that could just be added to it?

So it seems that you could save the tool number in a parameter using gcode like this:
#3000=#5400

IIRC you have a tool change remap, so maybe that could just be added to it?

Many thanks.
From what I have read using the var. file cannot be relied upon because it can get corrupted in linuxcnc exits unexpectedly.

Thinking aloud could the message on screen asking for the tool position to stop motion until it was deleted ?

If it could be done in the toolchanger comp that would be good but then if the var file got corrupted then there would have to have a way to input the correct tool position.

I have learnt such a lot by doing this little lathe with your help.

Ha, we've both learned a lot!

Thinking aloud could the message on screen asking for the tool position to stop motion until it was deleted ?

Not quite sure what you mean there.

I don't know of any other way to store values other than the .var file.

Aciera wrote:

Ha, we've both learned a lot!

Thinking aloud could the message on screen asking for the tool position to stop motion until it was deleted ?

Not quite sure what you mean there.

I don't know of any other way to store values other than the .var file.

When linuxcnc starts up, it puts a message on screen saying to input the tool number that is actually in position.

If this is not done (it is easy to forget) then running some code could end in disaster

I agree the var file is the way to go but if it got corrupted then there would have to have away to correct what the correct tool number is.

I notice that the tool number is displayed at the bottom of the axis gui.

Could the comp pass the number to the var file and read it on startup ?

IIRC the parameters cannot be accessed through the hal file directly. They are accessed through Gcode. But since you run special gcode in your toolchange remap we could write the toolnumber to the paramater as outlined above.

There is also a .var.bak file. Both of those are just text files with the parameter number and the values. I'm not sure how and when .var and .var.bak get created.

What could be done of course is to have a big reminder displayed at startup to check if the tool in the toolchanger and the loaded tool are the same.

Yes that sound like a plan. I believe that the var backup gets written to each time the main one is done, This would mean that the backup would not get corrupted with a bad shutdown.

Would you be happy to alter the comp to do this, obviously I will do any testing as usual for my mentor.

I am not in any hurry as I am aware that you are into bigger and better projects.

No need to alter the comp. We need to alter the M6 remap. that is a .ngc file. So see if you can find that and attach it please.

[edit]
Which GUI are you using? Axis or gmoccapy?