Octoprint fails to connect after reset or boot of Duet 2

airscapes

I am not sure where to post this but here are the particulars
Duet 2 Ethernet 3.3
Octoprint 1.3.10
Printer converted from Rambo with Marlin

After power up or reset of Duet I connect with OctPrint and get the following error.

Error reported by printer
Your printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: Bad command: Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 110 N0

Looking at the setting in octoprint this is a command being sent to start communication ?
"Hello" command
110 N0
Use this to specify a different command than the default M110 to send to the printer on initial connection to trigger a communication handshake.

If I should use something other than 110 NO, what would it be.
Weird thing is second attempt to connect works.. so I can ignore this .. but would rather fix it if I can.

Mods please more this if there is a better category for it.

PaulHew

Are you aware that Duet / RRF has its own frontend and does not require the likes of octoprint. Its called DWC.

To get octoprint to work with a Duet/RRF board is possible, but after running Klipper, octo, MailSail, Fluiid etc, I found that DWC is my preferred frontend and RRF as a firmware.

airscapes

@paulhew Other than the first failure, Octoprint works fine so far.
I prefer it to the web interface for printing. Old dog and all.. just have a process I have been using for years and don't see a reason to change.. yet.

Would like to correct this if possible but once connected on the second try, no additional problems.

Phaedrux

@airscapes said in Octoprint fails to connect after reset or boot of Duet 2:

If I should use something other than 110 NO, what would it be.

Do you have the option of using nothing?

I suppose you could also try using something basic like G91

But is the initial disconnection from the M110 or from the heater over-powered warning?

jay_s_uk

@airscapes there are a list of features here that don't work when using octoprint
https://duet3d.dozuki.com/Wiki/Firmware_Overview?revisionid=HEAD#Section_Printing_over_USB_connection_Octoprint_Cura_Simplify3D_Etc

dc42

@jay_s_uk said in Octoprint fails to connect after reset or boot of Duet 2:

@airscapes there are a list of features here that don't work when using octoprint
https://duet3d.dozuki.com/Wiki/Firmware_Overview?revisionid=HEAD#Section_Printing_over_USB_connection_Octoprint_Cura_Simplify3D_Etc

To be clear, these are not Duet/RRF limitations, they are limitations that AFAIK affect Octoprint with all control boards/firmware, and all other systems that rely on sending GCode over USB. Some have workarounds, e.g. when running Octoprint on a Pi you could connect your filament sensor to the Pi instead of the Duet.

dc42

@airscapes said in Octoprint fails to connect after reset or boot of Duet 2:

Error reported by printer
Your printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: Bad command: Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 110 N0
Looking at the setting in octoprint this is a command being sent to start communication ?
"Hello" command
110 N0
Use this to specify a different command than the default M110 to send to the printer on initial connection to trigger a communication handshake.

My guess is that the initial letter M is getting lost. You could try changing the command to "\nM110 N0" if Octoprint supports that, or to " M110 N0", or "M105", or "M105 M105".

airscapes

@dc42 Yeah not sure if it is the hello command or in response to something being sent back. However, after I posted this I reset, connected and failed and then reconnected without altering the temp of the duet using the web front end. The next connecte works fine with no heater error so I cam guessing it is it he initall hand shake. I also have a different USB cable coming today but will try you suggestion to start.
Will report back on what happens.
Thanks!!

airscapes

@airscapes Looks like I added to the problem, there was No M in front of the 110 N0 and I think there was more to the command that is not there now. I think it was M110 N0 M110 N*125 and from what I read it is supposed to get a checksum back.. this is what it gets back
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0 M110 N*125*114
Recv: Error: Bad command: Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach

So I am going to just live with this unless anyone has any other suggestions besides don't use Octoprint. I amy eventually move to the gui, it would be the same process just would have to log my Pi into that gui rather than OctP to control the printer manually (no LCD).. Thanks for the ideas!
Doug

dc42

@airscapes what happens if you specify just M110 N0 ?