Your Duet rejected the HTTP request: page not found

Phaedrux

Yes it could auto level the x axis, but that's not the same as probing the bed.

sleepless

@phaedrux hmmm i am confused would you mind clarifying the difference for me. Sorry and thank you

Phaedrux

A probe is normally attached to the print head and is movable to all areas of the bed so it can find the height of the bed across its whole surface. This can be used to get an idea of how the bed lays in relation to the print head.

What you have is two end stops in line with the x axis. This lets you adjust the tilt of the x axis to match the bed. But this is just a straight line between the two z motors. This lets you keep the z axis level on both sides, but that's about it.

Does that make sense?

dc42

@sleepless said in Your Duet rejected the HTTP request: page not found:

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?

S20 is the spacing (in mm) between probing points.

Homing speeds are set by the F parameter in the G1 S1 commands in the homing files; except that if you home Z using a Z probe, then you will use a G30 command to home Z and the speed is the same as for all Z probing moves, as defined by the F parameter in the M558 command.

sleepless

But they both take multiple points from the bed to adjust for any misalignment so I guess I can see the difference in the way the do their calibrating based off those points, but in the end both styles (probe or microswitch) should go through the autolevel procedure. It seems you are saying the robo cant do this with the microswitch?

sleepless

https://www.youtube.com/watch?v=eFywzPM9lfA here is a link to the robo3d autolevel for reference

sleepless

@dc42 thank you.

sleepless

@dc42 would you mind if you have a moment looking at the config.g and bed.g file i uploaded and let me know why my I am getting a error code for autolevel when i try to print I also have a fan issue but will get to that later. I want to finish with autolevel .

dc42

@sleepless said in Your Duet rejected the HTTP request: page not found:

@dc42 would you mind if you have a moment looking at the config.g and bed.g file i uploaded and let me know why my I am getting a error code for autolevel when i try to print ...

What error message are you getting?

sleepless

@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

sleepless

@dc42 Error: Z probe already triggered at start of probing move
Error: G29: No valid grid defined for bed probing

sleepless

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?

sleepless

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-15215 Y190:-10:190 S0.5 ; leadscrews at rear left, front middle and rear right

dc42

@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.

cheeseandham

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...

sleepless

@dc42 thaqnks ill give it a shot

sleepless

@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.

sleepless

@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

sleepless

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?

Phaedrux

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.