Frecuents disconection at startup
-
Hello. I have a duet 3 board. and Im setting it up. Im using octoprint, and at the first try, Im receiving a lot of this:
Offline (Error: Bad command: xð~N0 M110 N0*125)
I have googled about this but all I can see is about marlin.
Anyone has seen this and knows wich can be the cause? The boards connects to octoprint after 2 or 3 tries.
Thanks in advance -
Can you post your config.g?
Do you have the Duet3 set to behave like marlin?
Is there a reason you want to use Octoprint instead of the Duet Web Control? -
also please read https://duet3d.dozuki.com/Wiki/USB_ground_loops
-
@Phaedrux Hi.
Duet3 bhave like Marlin... I havent set that, but also I dont know how to do that. How do I check that? Im not interested duet to behave like marlin (I think...)
Reason to use octoprint: Duet web control is more powerful to my opinion, but I have a previous development where I did a nice rework of octoprint, so I wanted to keep using it. Still Iwill move to duet web interface in the future, but now octoprint is what I have.
I have attached the config file
config.g
Thanks in advance -
Marlin compatibility mode refers to the way USB acknowledgements are sent to be compatible with the way that marlin does it with an OK after each received command.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M555_Set_compatibility
I believe the default is M555 P2 for marlin, but please send M555 in the gcode console and see what it reports back, because you don't have a command for it in your config.g, so you may want to add M555 P2 to config.g.
I haven't used octoprint in quite some time now, so I'm not sure what else if anything needs to change for better compatibility with RRF.
I would suggest that for the initial setup of the printer, you use the DWC directly, and only after things are working correctly add in the connection to octoprint.
Keep in mind that you lose certain functionality when printing over a USB connection rather than the onboard SD card. Such as power loss recovery, filament sensor monitoring, and possibly more. Plus the speed penalty from using the USB bus.
-
M350 X32 Y32 Z32:32 E32:32 I1 ; configure microstepping with interpolation M92 X160.32 Y160.32 Z3200.00:3200.00 E827.22 ; set steps per mm M566 X900.00 Y900.00 Z300.00:300.00 E2400.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z240.00:240.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z20.00:20.00 E500.00 ; set accelerations (mm/s^2) M906 X1700 Y1700 Z1200:1200 E1000:1000 I30 ; set motor currents (mA) and motor idle factor in per cent
Also in this section of your config.g you have multiple values for the Z axis, which is not necessary. There is only one Z axis, even if it is made up of multiple motors, and each motor must be the same, so there can only be a single value.
Z16:16 would become simply Z16 for example.
-
; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 ;M307 H0 B0 D30 S1.00 ; enable PID para camara, deadtime en 30 segundos M307 H0 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit ;M140 H0 ; map heated bed to heater 0 M141 H0 ; map chamber to heater 0 M143 H0 S130 ; set temperature limit for heater 0 to 130C M308 S1 P"temp1" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M308 S2 P"temp2" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 2 as thermistor on pin temp2 M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2 M307 H2 B0 S1.00
For your heaters I notice you define the chamber heater as the second heater. For best compatibility the chamber heater should be defined as the last heater. The order should go bed heater, tool heaters, chamber heater.
-
i dont think you will find many people here who are using octoprint.
in my opinion, it will result in too many drawbacks.
the new 3.2 release will offer plugins which allow you to customize the ui -
@Phaedrux said in Frecuents disconection at startup:
M350 X32 Y32 Z32:32 E32:32 I1 ; configure microstepping with interpolation M92 X160.32 Y160.32 Z3200.00:3200.00 E827.22 ; set steps per mm M566 X900.00 Y900.00 Z300.00:300.00 E2400.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z240.00:240.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z20.00:20.00 E500.00 ; set accelerations (mm/s^2) M906 X1700 Y1700 Z1200:1200 E1000:1000 I30 ; set motor currents (mA) and motor idle factor in per cent
Also in this section of your config.g you have multiple values for the Z axis, which is not necessary. There is only one Z axis, even if it is made up of multiple motors, and each motor must be the same, so there can only be a single value.
Z16:16 would become simply Z16 for example.
@Phaedrux thanks a lot for the help
I have 2 Z motors, connected to 2 drivers in the board. Those configurations were setup by the online tool configurator. -
@Tinchus said in Frecuents disconection at startup:
Those configurations were setup by the online tool configurator.
I doubt that since the configurator is completely unable to create a config for multiple motors on the same axis. The config must be manually edited.
-
M555 reports "marlin".
-
What baud rate is octoprint connecting at?