Your Duet rejected the HTTP request: page not found
-
@sleepless said in Your Duet rejected the HTTP request: page not found:
tried a test print
and got Error: Z probe already triggered at start of probing move
Error: G29: No valid grid defined for bed probing -
@dc42 Error: Z probe already triggered at start of probing move
Error: G29: No valid grid defined for bed probing -
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors i think i was supposed to do this calibration not the other probe calibration i was doing?
-
not sure where in config.g this goes
M584 X0 Y1 Z2:5:6 ; three Z motors connected to driver outputs 2, 5 and 6
M671 X-15
215 Y190:-10:190 S0.5 ; leadscrews at rear left, front middle and rear right -
@sleepless said in Your Duet rejected the HTTP request: page not found:
@dc42 Error: Z probe already triggered at start of probing move
That means what it says. The Z probe reading at the start of the probing move, before the probe triggers, should be zero. If it's 1000, change I1 to I0 or vice versa in your M558 command.
Error: G29: No valid grid defined for bed probing
That means you haven't used M557 to define the probing grid. See https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Sleepless,
I'm not related to Duet3D or Think3dPrint3d , but I read this thread and felt strongly enough to respond. Please do not take this to anything other than a post to try to educate and not any attempt at chastisement (nor am I trying to derail the thread.)
Im not tech savvy like that and dont understand what alot of that is talking about.
Then you've put yourself in an interesting position by attempting this replacement.
can i please get a direct line with a support member this forum takes way too long
The support provided for the Duet boards is second to none IMHO. I think that Duet and T3P3 have been extremely patient since the start of the thread.
Well every other 3d printer company offers support and I can spend time chatting with them learning about their machines. And recieve normal troubleshooting help and not have to use a forum to wait for a response. I know how my printers work. I know how the fw works, but this is another level of knowledge, and I am admitting my ignorance and requesting someone to take me by the hand and walk me through this like any other companies support would do if requested of them.
I don't understand, you buy an (extremely complicated) part , and expect the part manufacturer to walk you through installing it into existing printer (and there are are many,many, many different types out there).
To draw and analogy - If you had bought a car, I can well understand that you would expect support on the product in regards to how to use it (e.g. how to use the lights, turn on the stereo etc). However, would you buy a generic car engine to put into say, a BMW and then expect that car engine manufacturer to sit on the phone, helping you install it and answering questions the whole way?
No, they would expect you to have the pre-requisite knowledge before attempting the installation (or at least to have fully read the manual) and really only ask for some kind of support if the product wasn't doing what was expected due to a suspected product fault.The Duet is very cheap for what it does, and I can well understand that offering the kind of phone support service you're asking for would double the cost of the board at least.
Ive been reading docs for the past week, so i am frustrated from hunting through them for answers when someone can quickly tell me an answer. I unfortunately dont have free time to sit around reading the docs, as it is the setup has had this machine down and my attention away from for for 4 days which I cant afford so it must get up and running today.
No-one can "quickly tell [you] an answer" when the information you provide is limited. Your first post was two lines, you had not explained what the full initial situation was, nor how you got there, nor the troubleshooting steps you'd performed to that date, and you've been drip feeding information since.
If you had started with a more comprehensive post a week ago, you'd have this resolved a lot quicker.
I highly recommend that you read http://www.catb.org/esr/faqs/smart-questions.html to assist you in the future.I do have to wonder why you would attempt this replacement if you didn't understand fully what you were doing , don't have the free time and when you obviously require the machine working so badly...
-
@dc42 thaqnks ill give it a shot
-
@cheeseandham
Thank you for the advice. I have changed boards on printers before and built 2 custom printers. The documentation on this board for my particular type of auto leveling is rather confusing. With every other company, I was able to talk in a chat or on the phone with them and have my answers immediately (even if the answer is sometimes "you have a loose connection somewhere") .
Perhaps you are right maybe the phone will cost too much, however, there are other options such as community chat rooms, a few companies are actually using Discord to host the chats. -
@dc42
probe was zero and the probe error still occured when trying to run bed autolevel before the test print. I think it might be because I am using the z endstops to trigger when the nozzle touches the bed and lifts the x axis gantry. I saw somthing that it might be that I need to put P0 instead of p4 in the zprobe area. But I wanted to double check this with you before I changed anything -
damn config.g file disappeared or turned into config.bak cant edit it on the web interface anymore what can I do to fix this?
-
Is it still gone after a power cycle?
You can right click on config.bak and rename it config.g. it should be a backup of the file from last time it was saved.
-
it seems to have disappeared after I made a change to the file and saved it. thanks bud. I actually just created a new file and named it config.g and reloaded the code i am restarting now
-
so i saw this "If you don't have a Z probe, set type P0 in your M558 command." but when i change to p0 the endstop doesnt trigger
-
am I supposed to use P0?
am I supposed to set up my z motors in separate drivers or just use z endstops a and b? and plug z endstop to e0 like I currently have it?
there are a lot of contradicting articles so I am trying to get clarity on the matter.
Do i need to create something like this M584 X0 Y1 Z2:3 E4 P3 ; Dual Z Homing
M671 X-67:328 S0.5 ; leadscrews offset for leveling
in my config.g? -
Do you actually have a Z probe on your printer, and if so, what type? Or do you have a Z endstop switch instead? Or do you have both? Maybe you have already told us; but I am not prepared to read all 166 posts in this thread (which started out on a complely different topic) to find out.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 If I'm skimming the posts correctly, he has two "z-endstops", one on each side of the bed. Then during bed probing, the printer jams the nozzle into the bed until the bed deforms enough to trigger the endstop, and in this manner a crude "9 point" leveling is possible.
-
it is as elmoret says. No z probe just z enstop switch as seen in the youtube video
-
@dc42 though you have your answer now, in the future, if its too much trouble to go through the posts then perhaps you can give me a call or text and we can get everything answered in just a couple of minutes.(hell we could probably have the machine up and running in under an hour) Just looking for support on your board and the documentation is contradicting and confusing.
-
@sleepless said in Your Duet rejected the HTTP request: page not found:
The problem was solved previously as shown in this thread. So it would seem to be possible.
-
I agree unfortunately I started there doing the troubleshoot as recommended however it wasnt very clear and then I was sent to about 6 different pages 4 of which seem to be for calibration all contradicting each other. So i am really confused on what needs to be done. currently i have it plugged into the e0 endstop and have p4 i1 in the config.g. the xyz all trigger when homed ( great news). everything seems to move at a proper speed now(more good news). but when i try to run autolevel before a test print i ran into those previously mentioned error codes. right now i am going throuhg the mesh bed calibration process. I hope this gets everything working. it seems once the autolevel is working I should be able to print again. well I do have a small fan problem but it should be an easy quick fix in the config.g file.
