I'll be back after a long time, and issues...

o_lampe

@peirof
You only set Zmin axis limits, no other limitations???

peirof

@o_lampe

no... its a Delta

I can only think of doing a kind of soft reset ...

Start configuring it as if it were a new Duet installation.

To do this ... how should I do it?

What files should I delete?

This website: "https://configtool.reprapfirmware.org/Start"

Is it still used to generate the initial configuration?

peirof

@peirof

mmm.... can be this?

in actual config.g

; Endstops
M574 X1 Y1 Z1 S1                            ; set active high endstops

but in new config.g, generated by the web....
i can read this

; Endstops
M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                            ; configure active-high endstop for high end on Z via pin zstop

Seems endstops config has changed in Firm 3.... not sure

engikeneer

@peirof yes, in RRF3 there have been some rather dramatic changes in syntax when defining which pins things work on. Basiacally now you have to define which pin you want to use for everything by it's name, but it means that you can map things to other pins for which they weren't originally intended (e.g. you can use a heater pin to drive a big fan etc). You can read more on it here:
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

What firmware version do you have on your duet? Send M115 to check. You can then generate a fresh config using the config tool, or you can go through the link and do it manually (took me about 15 mins for mine and helped me understand what was going on a lot better!).

dc42

@peirof said in I'll be back after a long time, and issues...:

Greetings to all,

Well, it was a long time since I connected to the forum, and I had not used the printer, I did not have much free time.

The first thing I have done has been to install the new firmware 3.3, from 3.2 .... and the first reboot fine ... but after the second reboot ... problems.

I have to say that after the first reboot, I have deleted the config-override.g file, and since I have done that, when I do HOME or turn on the printer (which I suppose it will do a HOME), the 3 towers go up, but they DO NOT stop in the end they keep trying to go up, and I have to stop it as quickly as possible manually.

How can I solve that?

Thanks

Upgrading from 3.2 to 3.3 is not major, but check the upgrade notes for version 3.3 to find out what you may need to change.

dc42

@peirof said in I'll be back after a long time, and issues...:

@peirof

mmm.... can be this?

in actual config.g

; Endstops
M574 X1 Y1 Z1 S1                            ; set active high endstops

but in new config.g, generated by the web....
i can read this

; Endstops
M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                            ; configure active-high endstop for high end on Z via pin zstop

Seems endstops config has changed in Firm 3.... not sure

Your "in actual config.g" M574 command is incorrect for all versions of RRF. But the M574 commands in the config.g file you posted in the third post in this thread are different and look OK.

peirof

one thing that I realized this morning ...

Each tower (it is a Delta printer), has an Endstop, well.

Of the 3 Endstops, 1 of them remains with a light on, and the other two are with the light off.

The one with the light on, if you raise that tower manually, and activate the limit switch, it turns off ... the others remain off.

Is there a way to know the state that Duet detects of the Endstops? if they are activated at that moment or not?

I suspect a problem with the limit switches, what I am not clear about is whether the Hardware (they are damaged) or the software ...

I prefer more another thing that misses me ...

It is because as soon as the printer is turned on, the towers go up, trying to do a HOME, when before, this did notit is a software problem, since yesterday, they worked well ...

One option is to do a SOFT RESET.

What would be the procedure for this?

Thank you

P.D.: I love Google M999

peirof

@peirof

a long time a go.... i do the same question:

https://forum.duet3d.com/topic/11856/soft-reset-procedure

o_lampe

@peirof said in I'll be back after a long time, and issues...:

Is there a way to know the state that Duet detects of the Endstops? if they are activated at that moment or not?

Yes, it's M119, but there is also a way to let the Web interface show you the status. I never tried it, so can't explain how

peirof

Some interesting breakthroughs ... I think I'm close ...

Well, as I have commented before, here are the steps that I have followed:

1- Delete the SD and copy the content, which I have put in the previous post, which are the default files of DUET, when it comes from the factory.
2- Then, following the guide on the web, I have configured Duet by Telnet to connect it to the WiFi network
3- Once connected to the WiFi network, I have updated DUET, from Firmware 3.3, which I installed yesterday, to Firmware 3.4, by the DWC.

** At this point I have to say, that the ENDSTOPS have worked correctly again, they lit up when they were not activated, and they turned off when they were activated "

4- The first thing has been to edit the file "HOMEDELTA.G" and copy the content of the one it had before.
5- I have been editing the Config.g file, from its default state. I have copied and pasted sections of the Config.g that I had before, to this new config.g. I was doing it by sections, when I changed a section I reset and checked that everything works. I have reached the point of being able to do a HOME, but at some point later, the failure from before has been reproduced. After resetting, the towers went up, and they ignored the ENDSTOPS ... then I will continue, now it is very hot in the printer.

From these initial tests, a Hardware failure can be ruled out, I think, since the problem has been repeated at some point that I have edited the CONFIG.G

When I make more progress I will post them, in case someone can help me or be useful for something

Phaedrux

You can post your current config files homedelta, etc so we can see what you are using now.

Also verify the firmware version with M122.

You can send M98 P"config.g" which may show some error messages from your config.