Help with HTTP Error 500 on Duet 3D

A Former User

@Jim46 said in Help with HTTP Error 500 on Duet 3D:

I ran the CMG with the code you gave me. It says no device found on COM3, yet the BOSSA says it connected and recogonizes the chip.
What next

if you try both at the same time, then that would be the reason, cannot access COM3 form two applications at the same time.

First do as dc42 suggested, click refresh in the graphical BOSSA to re-identify the Duet. Then click write.

If it fails again close the graphical BOSSA window and retry the command please.

(hmm, the error message is a bit ambiguous as it points to the problem being the target, I'll file an issue with the BOSSA developer to help make it clearer as I tested you get a different (more) output if the port is free but has no target)

Jim46

Hey Bearer,
I've shut down BOSSA as it would just sit there after the write command.
Its probably a good idea to share the experience with the BOSSA developer. I''ve ordered new USB 3.0 microUSB cables and should have them on Monday to hopefully remove the current cable as being a potential problem.
It would be a good idea also to let them see the BOSSA screen as I saw it on 29 Apr 2020, 18:32 ...Potential progress... as the screen is all crunched up on the bottom and you can't see the check boxes. I'm running an HP Pavillion Elite e9220y (with Windows 10) APCI x64 based PC with AMD Phenom II x4 910 Processors (4).

Jim46

Just ran the BOSSA screen again with the boxes checked, I launched it. and it came back with the Error File Operation Exceeds Flash size.

Jim46

I shut down the BOSSA screen and went to CMG and ran the given code.
it ran and gave the following...

did it work and what next?
thanks
Jim

A Former User

de ja vous?
https://forum.duet3d.com/post/142914

can you find that USB cable and try it again?

Jim46

New 2.0 cable arrived today. This the result of the CMG commands

Looks like it made progress. what next?

Jim46

Bearer,
I've lost your message,
J

Jim46

Motor wiring verified with paperclip test
G92 X0 Y0 Z0 performed
Motors do not turn
They do spin freely when turned by hand

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Mon May 04 2020 10:26:28 GMT-0600 (Mountain Daylight Time)

; General preferences
G90                            ; send absolute coordinates...
M83                            ; ...but relative extruder moves
M550 P"My Printer"             ; set printer name

; Network
M552 P0.0.0.0 S1               ; enable network and acquire dynamic address via DHCP
M586 P0 S1                     ; enable HTTP
M586 P1 S0                     ; disable FTP
M586 P2 S0                     ; disable Telnet

; Drives
M569 P0.0 S1                   ; physical drive 0.0 goes forwards
M569 P0.1 S1                   ; physical drive 0.1 goes forwards
M569 P0.2 S1                   ; physical drive 0.2 goes forwards
M584 X0.0 Y0.1 Z0.2            ; set drive mapping
M350 X16 Y16 Z16 I1            ; configure microstepping with interpolation
M92 X53.33 Y53.33 Z53.33       ; set steps per mm
M566 X900.00 Y900.00 Z12.00    ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00    ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 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 X1000 Y1000 Z1000 S0      ; set axis maxima

; Endstops
; WARNING: No endstops configured

; Z-Probe
M558 P0 H5 F120 T6000          ; disable Z probe but set dive height, probe speed and travel speed
M557 X0:1000 Y0:1000 S20       ; define mesh grid

; Heaters

; Fans

; Tools

; Custom settings are not defined

Phaedrux

Hi Jim, glad to see that Bearer was able to get you sorted on the firmware front. Also, sorry to see you're having some issues with the motors.

At this point, due to the very long nature of your journey to get to this point the info needed is rather spread out. Can I ask that you create a new thread and include the following details up front so that we can take a fresh run at your new issue.

Please include details on which Duet board you have, how things are connected (photos would be great), firmware versions for the Duet, DWC, and Pi if used. Include your config.g as well. And details on what the problem is and what you've so far tried in trouble shooting. Since there is a possibility of hardware failure please also provide some high res well lit close up photos of both sides of the board so that we may be able to spot any burnt up components.

Phaedrux

Also, on a lark, please try adding an endstop definition to config.g and trying G92 X0 Y0 Z0 again.

; Endstops
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop"
M574 Z1 S1 P"zstop"