the issue with this approach is: the interpreter is the wrong place to apply
initial tool state start conditions
assume you somehow set the initial tool number in the interpreter and then you
turn the machine on:
- you have state of the machine, and state of the interpreter.
- the interpreter
This looks too complex for me now. Besides, it may be useful to save
some parameters without using remap.
Can I save / restore toolnumber using Parameter saver component? I can't
find any hal input pin to which I could connect paramsaver.outvalueS-000
for example.
http://wiki.linuxcnc.org/cgi-
Am 21.07.2013 um 11:43 schrieb Andy Pugh :
>
>
> On 21 Jul 2013, at 09:19, propcoder wrote:
>
>> tried to
>> add #5400 (tool_in_spindle) to .var file. It does update the tool number
>> on the file, but it does not take this value on start-up.
>
> I don't know if this will work, but I would
I added one line to my .ini file like this:
[RS274NGC]
RS274NGC_STARTUP_CODE = M61 Q2
And it does not start:
Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-2.6.32-122-r
On 21 Jul 2013, at 09:19, propcoder wrote:
> tried to
> add #5400 (tool_in_spindle) to .var file. It does update the tool number
> on the file, but it does not take this value on start-up.
I don't know if this will work, but I would be trying an M61 T#5400 in the
STARTUP_GCODES in the INI.
I almost finished my rack tool changer setup using development branch
and remap of M6.
What I miss now is tool number persistence between sessions. I tried to
add #5400 (tool_in_spindle) to .var file. It does update the tool number
on the file, but it does not take this value on start-up.
I th
