Saving parameters after shut down

I could use a selector switch,but I will still have to initialize the control and make sure the chuck is matching the switch!! Right now Im using the cycle start button (when in manual mode),to write to a bit,but it is not saved at shut down.It would be much easier if everytime the chuck is opened or closed I set a bit and the bit is retained on shutdown.I also have a tailstock and parts catcher with the same issue,sooo....if it could be done with the lame Acra control,I can do it here!!!!

In all honesty,it would be nice to save the tool # in the turret and on a machine like say my Brown &Sharpe mill,which can have a tool in the spindle,a tool in the ready pocket and the tool pocket on the tool chain,saving what is where saves a bunch of hassle in the morning when firing the beast up.If you get the tools out of sync,it can a while to get them right. Saving them,like modern machines do is the way to go. Ill post the code I have so far.Thanks as usual!!

One of the problems I see without sensors is getting out of sync if you do something with the power off. And your correct you can do almost anything in LinuxCNC. The thing that confuses me is if these devices are controlled with a contactor or solenoid in your G code would it not be prudent to set them as expected in the preamble?

John

Well,Im not sure these are g code type things,they really are misc machine functions.They can be controlled by mcode in MDI or in auto mode.In manual mode they are controlled by by buttons and switches.

Considering at the end of the day,after the last part is run,you leave the chuck open and the tailstock extended, and the normal position is chuck closed,tailstock back,the machine will be out of sync.My hardinge uses limit switches for everything,this machine,my Mori and my old Ikegai dont,they save the condition of the individual appendage as what it last was.I got the Ikegai confused once with the chuck,and it was a bear to get it right.

ArcEye wrote: One easy way to side step the problems of accessing devices from a realtime module, would be to write a userspace component whose sole function is to read parameters at start up and write them to disc when signalled at close down.

You could then just connect the userspace to the realtime component, via suitable HAL pins for your data type, and have a signal pin to trigger a read or write.

How would one signal the file to read or write at close down or startup?

Hi

You seem to be trawling through my back numbers today :laugh:

How would one signal the file to read or write at close down or startup?

The simplest would be to create bit pins in the component which trigger read / write and these could just connect to pyvcp buttons.

A bit more advanced would be to link pins to say halui.machine.is-on and halui.joint.<n>.is-homed
At startup the module can test if(machine-on && axis-homed)
This going true triggers a read of the file, to use the saved parameters or whatever they are.
Thereafter machine-on going to 0 would trigger a file write.

This would however be dependent upon an orderly shutdown sequence.

The best solution would be to hook into the GUI to trigger the file read and write, so that it will be done even if the operator does Alt F4 to close it

Do you have a particular application in mind?

Told you I am on too many things at the same time. :laugh: And it is good to know that the clever guys already worked the problems out. The only thing I like Bill Gates for is "copy and paste". :lol:

I am busy with a plasma machine and I want to save the tip voltage setting. It is changed from time to time on the spinbox and I don't want the user to re-adjust it at every startup. There are about three or four settings like that.