G-code buffer "file" overflow???

[daoust]

@norder I just upgrade to the new firmware by doing 3.0 first than the newer version. I redo a new configuration with the config tool while using same parameter as before.

Now my z end stop is not working properlly

When I try to home, the bed lift some milimeter than goes down untill colision but if I touch the Z endstop, the bed stop moving.

So it look like the endstop is now inverted from N/C to N/O and vise versa. I try to install a "!" Before the zendstop. The X and Y axis work fine, only the Z axis that is not working. Any I idea???

Thank you

[dc42]

@daoust please post your config.g and your homing files.

[daoust]

@dc42 so I was able to fix my end stop problem, it was just the rotation side of my stepper motor the problem.

but here I have a small tuning to do to my config file. first, it say I have a error with heater 3, 4, 5, 6, 7... they are not found

second, I have setup a heated chamber, but I would like to have acces on my panel due. is there a way to enter a g-code comande to configure a heated chamber?

lastly, I have trouble with the wifi connection. is it possible that the wifi modul can be defective or it will mostly be my router that are too far. sometime it work fast and other time, it wont connect.

Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sun Oct 02 2022 20:41:52 GMT-0400 (Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"createbot max" ; set printer name

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z640.00 E430.85 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X900.00 Y900.00 Z100.00 E2000.00 ; set accelerations (mm/s^2)
M906 X950 Y950 Z850 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X280 Y250 Z400 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

;Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure 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 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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
M143 H1 S350 ; set temperature limit for heater 1 to 350C
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2
M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2 ; map chamber to heater 2
M143 H2 S100 ; set temperature limit for heater 2 to 100C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2 T70 ; set fan 1 value. Thermostatic control is turned on

; 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 are not defined

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

[Phaedrux]

@daoust said in G-code buffer "file" overflow???:

it say I have a error with heater 3, 4, 5, 6, 7... they are not found

Where do you see that? You only have 3 heaters defined. 0, 1, 2

@daoust said in G-code buffer "file" overflow???:

second, I have setup a heated chamber, but I would like to have acces on my panel due. is there a way to enter a g-code comande to configure a heated chamber?

What firmware version is on your PanelDue? You'll likely need to update it.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue#firmware-update-via-usb

@daoust said in G-code buffer "file" overflow???:

lastly, I have trouble with the wifi connection. is it possible that the wifi modul can be defective or it will mostly be my router that are too far. sometime it work fast and other time, it wont connect.

Please send M122 in the gcode console and copy and paste the results here. Perhaps your wifi module firmware didn't get up to date? Perhaps your signal strength is poor? M122 will tell us more.

[daoust]

@phaedrux here is the m122 for the heater and a print screen where it say that my heater 4 5 6 7 . . . Have problem

Also when I activate my heated chamber, the temperature rise up to 40 deg c and the heater came in fault because the tempereture rise to slow. The chamber is big so it is normal to rise slow. How can I fix this safety?

For the panel due firmware update, I will try it this week. Thank you

[Phaedrux]

Can you post your config-override.g?

Can you send M122 from the web control gcode console tab instead of the paneldue? Then you can see the full report and copy and paste the result here.

[daoust]

@phaedrux config.override.g
; config-override.g file generated in response to M500 at 2021-01-31 19:35
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
M307 H1 A698.9 C331.5 D11.3 S1.00 V25.0 B0
M307 H2 A28.8 C511.4 D4.7 S1.00 V25.1 B0
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

M122 from the web interface on the computer = responce too long, see console (edit... ok it is fine)

now try on the cellphone and it work well. look like a trouble with my computer. I will edit this message with the picture of the m122 from my cellphone

[daoust]

[Phaedrux]

@daoust said in G-code buffer "file" overflow???:

M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0

Delete these lines from config-override.g and that should remove the heater error messages.

@daoust said in G-code buffer "file" overflow???:

responce too long, see console

That just means you have to go to the gcode console window. It's a button on the left side.

But from what I can see from your screen shots I think you should update your firmware and other files by uploading this zip file to the system tab in DWC from a PC.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.3/Duet2and3Firmware-3.4.3.zip

That should get everything up to date.

[daoust]

@phaedrux thank you, I will delete those line.

do you have any clue why, I can t use my heated chamber anymore. The temperature rise is not fast enougth so the heater switch in fail mode. There should be a way to make it understand that the temperature will not rise as fast because the heated chamber is big?

[Phaedrux]

Have you PID tuned the chamber heater?

[daoust]

@Phaedrux I belive my heated chamber is in bang-bang mode. Does it need auto tune? Alsl, before the update, I never have touble

[Phaedrux]

You can try to tune it. The heater model has changed in recent versions. It may be able to handle slow chamber heaters better now.

[daoust]

@Phaedrux I will give it a try. Now when I use my heated chamber, it is slower than ever to heat up

[dc42]

@daoust said in G-code buffer "file" overflow???:

I belive my heated chamber is in bang-bang mode. Does it need auto tune?

Yes. Auto tuning not only sets up the PID parameters, it also informs the firmware of how the heater normally behaves, so that it can better detect when something has gone wrong with the heater or temperature sensor.

[daoust]

@dc42 so I try a PID autotune and it a fail.
The firmware is the new one.

I snen the comande M303 H2 S50 and the heater was not able to heat fast enougth

Is there something wrong with my comande?

Thank you

[dc42]

@daoust the standard workaround for slow bed/chamber heaters not heating up fast enough during auto tuning is to use M307 to set the dead time very high, for example 60 seconds.

[daoust]

@dc42 so it fix my initial problem but when I try to do pid autotune of the heatead chamber, it take a full day and than fail.

Before the firmware update, my heated chamber was really fast, not even comparable. Now it is so slow and it can t finish a PID autotune without failling. Whan should I try???!

Thank you20221121_172239.jpg

Thank you

[dc42]

@daoust that R value is much lower than it should be (0.028). It means that even when the temperature is only just above ambient and the heater has been on for 10 or 20 seconds, the temperature rise is only 0.028C per second. So I think something has gone wrong with the chamber heater, or the wiring to it. Perhaps the wire has broken and it isn't working at all? Can you measure a voltage across the chamber heater when it is supposed to be turned on?

If this problem persists, please start a new thread because the problem not related to the title of this thread.