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
-
@peirof post your config and homedelta files so we can see what's going on.
Are you calling homedelta.g from config? If so that's a bad idea!
-
For obtain the files i must unplugg motors.... they was infinite homing...
I must remember i have erased config-over
Another thing i have try, its tower endstops seems works, the light turns off when manual activates
CONFIG.G
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Jul 29 2020 06:26:06 GMT+0200 (hora de verano de Europa central) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"TLM Duet 2 FW3" ; set printer name M665 R157 L397.1073 B125 H491 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M587 S"P1_2" P"a1b2c3d4" I192.168.1.25 ; Configure access point. You can delete this line once connected M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S1 ; enable Telnet ; Drives M569 P0 S0 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S0 ; Drive 3 goes forwards M350 X256 Y256 Z256 E32 I0 ; Configure microstepping without interpolation M92 X1280.00 Y1280.00 Z1280.00 E830.00 ; Set steps per mm M566 X1000.00 Y1000.00 Z1000.00 E900.00 ; Set maximum instantaneous speed changes (mm/min) M203 X10980.00 Y10980.00 Z10980.00 E3600.00 ; Set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; Set accelerations (mm/s^2) M906 X1000.00 Y1000.00 Z1000.00 E1000.00 I60 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop ; Z-Probe M558 P8 C"!zprobe.in" R1 F300 Z1 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z0.2 ; set Z probe trigger value, offset and trigger height M557 R85 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ; M305 P0 T100000 B4350 R4700configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H1 R1.885 C176.8 D11.62 S1.00 V23.8 ; enable bang-bang mode for the bed heater and set PWM limitM307 H0 A139.8 C532.3 D4.7 S1.00 V24.1 B0 M140 H0 ; map heated bed to heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 100C M308 S1 P"e0temp" Y"thermistor" T100000 B4750 R5200 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 C"Capa" S0 H-1 ; set fan 0 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 C"Heatsink" S1 H1 T45 ; set fan 2 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings M501 ; load saved parameters from non-volatile memory T0 ; select first tool ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory T0 ; select first tool
Homedelta.g
; homedelta.g ; called to home all towers on a delta printer ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Jul 29 2020 06:26:06 GMT+0200 (hora de verano de Europa central) G91 ; relative positioning ;*** Slow homing has been configured. Change F180 to F1800 below when your configuration is working G1 H1 X550 Y550 Z550 F1800 ; move all towers to the high end stopping at the endstops (first pass) G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm ;*** Slow homing has been configured. Change F180 to F360 below when your configuration is working G1 H1 X10 Y10 Z10 F180 ; move all towers up once more (second pass) G1 Z-5 F300 ; move down a few mm so that the nozzle can be centred G90 ; absolute positioning G1 X0 Y0 F6000 ; move X+Y to the centre
-
@peirof Something I notice in your config is your microstepping is set very high (M350). Usually best to do 16 with interpolation on (
I1
) so as not to overload the CPU. If you change it, you'll need to change your steps per mm (M92) to match. That's not gonna cause your issue though...I can't see anything else obvious in config.g, though you are calling config-override.g (M501) twice near the bottom. Your homing file looks okay as well (though might be worth changing the feedrate back to F180 while you're getting through this issue?).
I think there must be something in that file (maybe you didn't delete it?). Can you see if you can find config-override.g in your /sys folder?
You can always take the SD card out of the printer and use a reader on your PC to have a look at the files if that's easier than unplugging the motors!
-
@peirof
You only set Zmin axis limits, no other limitations??? -
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?
-
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
-
@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_filesWhat 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!).
-
@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.
-
@peirof said in I'll be back after a long time, and issues...:
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.
-
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
-
a long time a go.... i do the same question:
-
@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
-
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
-
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.