Your Duet rejected the HTTP request: page not found
-
I think it might help if you start a new thread with a new title more specific to your current problems. Perhaps "Help converting a Robo R1 to duet." Include as much information as you can about where you're at. The current thread title is about http connection problems which most people are probably ignoring.
There are other people who have converted this printer by the looks of it from that older forum post, so perhaps someone can provide a working config file set.
I think mode 8 would be a good choice as well from the description, but I'm not really sure as I haven't used it myself.
-
@phaedrux said in Your Duet rejected the HTTP request: page not found:
"Help co
will do thanks for the advice
-
Nothing seems to do the trick. I ran mode 4 but no luck seems I need to invert the a trigger but I am not sure how to do that.
-
You invert the Z probe trigger using the I1 parameter in the M558 command. Example:
M558 P5 I1
Note, that's uppercase-letter-i (not the vertical bar character) followed by digit 1.
-
I'll give it a shot ty
-
ok were moving along here... I raised the z 100 then homed x then y then sent g30 command and used my hand to lift the x axis and test trigger the z probe/endstop. that worked. when I homed x and y then ran g30 again to allow it this time to reach the bed it didnt get to the bed and sent an error message that the z probe couldnt trigger
-
Was the Z probe over the bed when you ran G30 again? Typically in homez.g and homeall.g you would use a G1 command to move the head to a suitable XY position (e.g. the centre of the bed) before the G30. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_probe.
-
it was not over the center the x and y were homed and then i sent the g30 command. I did try something while I was waiting for a response and it seems to have worked. I added G28 to the bed.g and m574 to the zprobe area in the config.g I will post copies
-
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Sun Oct 28 2018 16:32:40 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G28 ;
; Probe the bed at 4 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y239 H0 Z-99999
G30 P2 X215 Y239 H0 Z-99999
G30 P3 X215 Y15 H0 Z-99999 S; Z-Probe
M574 Z1 S2 ;
M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z-0.85 ; Set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:239 S20 ; Define mesh grid -
-
got Z-0.85 and i put that in the config.g
-
How do i run a auto level test to make sure its working properly?
-
@sleepless said in Your Duet rejected the HTTP request: page not found:
got Z-0.85 and i put that in the config.g
That doesn't sound right, because it means that the Z probe triggered when the nozzle was 0.85mm below the bed surface. If it triggered when the nozzle is 0.85mm above the bed surface, then use Z0.85 in the G31 command in config.g.
-
it actually triggered -1.38 but that was too close to the bed so i raised it until the paper had a little friction going under. i loaded a test gcode and it seems the auto level is way off. it is probibing 11 points across the x axis and i lost count on the y axis. it is also only going about 60% of the way on the x axis when running the auto level.It started around the center of the bed instead of the front corner of the bed. (Side question how do i increase the movement speed for homing)
-
It sounds to me that your Z=0 level was off when you started. before you measured the trigger height, did you lower the nozzle until it was just touching the bed and then send G92 Z0, as described at https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_height ?
-
no i misunderstood the directions. I raised the z axis 10 each time before running G31
-
M557 X15:215 Y15:239 S20 I was curioius if the S20 in this code from the Zprobe area in the config.g file was the number of probing points? Also how do i increase my homing speed?
-
I am trying to run the test and calibrate again as your recommended. But I am running into an issue. I centered the nozzle over the bed using the jog controls, i lowered the z until the nozzle gripped a piece of paper, then sent command G92 Z0. Then tried G30 S-1 and i would receive error message insufficient axises homed. What am I doing wrong?
-
I think my steps are wrong. When i am homed on the x it is 230 but when i move the x with the jog 100 or so it zeros out the x and im only at the center of the bed, its the same for the y
-
// default settings
#define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,800,723.38} // default steps per unit for RoBo 3D R1
I used the above when creating the config in the reprap website. I believe i chose 32steps
; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M350 X32 Y32 Z32 I0 ; Configure microstepping without interpolation
M350 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z800 E723.38 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z300 E1500 ; Set maximum speeds (mm/min)
M201 X500 Y250 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
