Your Duet rejected the HTTP request: page not found
-
@sleepless we do not offer phone support. We are trying to help you resolve the issues. There are a huge number of 3D printers out there, your Robo R1 is not something we have any experience on and appears to have some weird features (such as two endstops under the bed??).
We are trying to work though it step by step with you.
-
I have uploaded pics of the endstops for you and my codes. what seems to be wrong with the code? What am I doing wrong? As i mentioned before you have please give me a direct answer and not a link to documentation. The links arent always clear and have left me even more confused.
-
Let me know which of my answers isnt fully answered and I will try to make it more clear.
-
@dc42 I have gone through this but there wasnt a troubleshooting section on what to do if the z axis doesnt stop. So if my print head crashes and i turn the printer off, now what do I need to do to fix this?
-
reading back through everything yet again. I think mode 8 will be best since it involves mode 5 and seems to offer more control but there wasnt much information so I was wondering what you thought?
Mode 4
The trigger signal is read from the E0 endstop circuit. You can choose whether the signal is high or low when triggered. In firmware 1.15 and earlier this is done by using M574 E0 S1 to select active high, or M574 E0 S0 to select active low. In firmware 1.16 and later, use I1 in the M558 command to select active low, otherwise it defaults to active high. The device connected to the E0 STP pin must be able to sink 1.5mA for the Duet 2 WiFi and Duet 2 Ethernet, 0.3mA for the Duet 2 Maestro, or 2.1mA for the Duet 0.6 or 0.8.5.Mode 5
A switch or digital output device connected between the IN and GND terminals of the Z probe connector. Similar to mode 4 except that the Z probe connector is used. The input must be active high when triggered, or in firmware 1.16 and later you can use the I1 parameter in the M558 command to select active low. The only pullup resistor is the 100K nominal pullup in the microcontroller so the sink current requirement is tiny. -
anyone home?
-
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)
