TOOL T0 IS NON ACTIVATED IN config.g

danzaywer

if you run

M98 P"config.g"

what result do you have?

Gianluca

@danzaywer said in TOOL T0 IS NON ACTIVATED IN config.g:

if you run
M98 P"config.g"
what result do you have?

Reload the config.g without errors and Tool 0 becomes correctly active ...

This does not happen on the first boot just turned on.

cosmowave

@gianluca Do you have a sys/config-override.g file?
Eventually there is a command which disable the tool...

danzaywer

@cosmowave I don't see M501 in config.g, @Gianluca can try to add T-1 prior of T0 and see what happen? or try to put T0 in an external macro and call it at the end of config.g. Anyways i believe this is SBC firmware glitch

Gianluca

@cosmowave said in TOOL T0 IS NON ACTIVATED IN config.g:

@gianluca Do you have a sys/config-override.g file?
Eventually there is a command which disable the tool...

I havn't config-override.g file

Gianluca

@danzaywer said in TOOL T0 IS NON ACTIVATED IN config.g:

@cosmowave I don't see M501 in config.g, @Gianluca can try to add T-1 prior of T0 and see what happen? or try to put T0 in an external macro and call it at the end of config.g. Anyways i believe this is SBC firmware glitch

T-1 prior of T0 does not work, T0 is always off on first boot ...
I try with M501...
Could it be because my Raspberry P4 starts from USB and not from MicroSD?

danzaywer

@gianluca I think You don't need M501 if you not have any setting stored with M500. Have you tried M98 P"SelectT0.g" and put "T0" into it? Obviouslyit it is "Una pezza a colore".......

Gianluca

@danzaywer said in TOOL T0 IS NON ACTIVATED IN config.g:

@gianluca I think You don't need M501 if you not have any setting stored with M500. Have you tried M98 P"SelectT0.g" and put "T0" into it? Obviouslyit it is "Una pezza a colore".......

mystery ... the T0 doesn't work, even with a call from a macro from config.g (only on first boot) ... But if I run an emergency stop, or call the macro, T0 becomes active good.

deckingman

@gianluca I'm wondering if using M300 to play a 3 second beep just before the "T0" command in your config.g is having an effect? Try commenting that M300 out just to see. Or you could try putting a pause of (say) 4 seconds after the M300 and before the "T0" e.g. G4 S4.

Gianluca

@deckingman said in TOOL T0 IS NON ACTIVATED IN config.g:

@gianluca I'm wondering if using M300 to play a 3 second beep just before the "T0" command in your config.g is having an effect? Try commenting that M300 out just to see. Or you could try putting a pause of (say) 4 seconds after the M300 and before the "T0" e.g. G4 S4.

The M300 is not the problem, and 4 sec. delay did not solve the problem. I solved by update the firmware from 3.3 to 3.4 b7.
The beta version worked better than a stable one