Posts made by Fizban

Ok so I came across the M540 and found the mac. Forced it to 112 in router and now it is working. However!
It's still not showing on the mac list having access to the router. What gives ?

So due to my old router being a dinosaur, i replaced it. When I went in to set the maestro ip to a fixed one the mac address isn't showing.

Maestro finds it self being at 103, I want it to be 112 and since I can't set the meastro to run on a static IP. I need to do it via the router.

Now why would it stop showing it's MAC on another router?
It's the same brand and same model just with 10th rev. improvements =D

Or if someone can tell me exactly how to set a static ip in the board I'd take that as well. But the written guide all ways leaves me without access to it.

Sorry I can actually see now that I just read across it. The M280 line is clearly stated above the Meastro section, it just wasn't bling enough for my eyes to catch it. you have specified adding P64 removing I3 I apologize!

The probedeploy/retract I think I missed out for this one reason. I wasn not ready to toy with the probe when I did the online configuration tool, setting Z a switch.

I then later manually added the Bltouch as Z probe, giving me a very messy and generic deploy/retract.g where I removed all the lines adding the M280
This was the key factor that made it work for me. I can't find anything that even relates to these very important .g to even make the probe work

Or I'm just being to hasty when doing stuff /shrugs

So as the title indicates I'm a happy man now.
-Well there's some minor hiccups but I think I know what's causing them - see the bottom of the post.

TLDR, Probedeploy/proberetract.g needs more documentation as I haven't stumbled upon it yet doing endless hours of searching the web trying to troubleshoot my BLtouch. Added pictures to show how Meastro and Bltouch is wired along with the propper M280 P64 S10/S90 for this particullar board.

This post is more for the wikiwriters and I guess other that might have had same problems as me.

First it's worth noting that the meastro supports that you plug the probe directly into the Zprobe pins, but you'll endup having a spare wire that if you're like me dont know where to put. And if you read the guide for the wifi/eth you end up being even more confused. (Well i did)

the wiring should look like this, atleast with the BLtouch I'm using.

You'll notice that the 3v is unused and that you would ahve 2x GND
What I did after reading a post form DC42 is that black/brown can be soldered together. and just go with one GND for the both of them.

So I did, no luck, probe clicked 3 times on reboot, when I tried to home it crashed and the probe woulnd't reploy or do anything.

Yesterday I had my breakthrough and found the most critical and underdocumented function of the BLprobing issue.
Probedeploy.g
Proberetract.g

I've maybe not read all the pages thoroughly enough but I missed it, this was pointed out by a dude on fb.
Going through these two did my nut in as well.
Again most I could find was for the duetwifi indicating that one should do S280 P3 S10 I1 ... no luck

I fidnout that I1 obsolete atleast for this particular setup, and that I should use P64 - I think i saw this from comment DC42 made.

So my macro and deploy/retract ended up looking like this. M280 P63 S10 // M280 P64 S90 and now my probe was responding! Success!

Off to do the leveling, firstly i think my offsets are interpreted wrong as it keeps ramming X towards the front and wont probe the back bit of my bed.
But with a mesh with S20 it would fail to probe on the second row - this happened same spot every time i ran a mesh. Increasing the distance to S40 made me do a 80% mesh the last 60mm of the bed on X was unprobed.

I see now that RC3 is out and it might have a fix for my probe stopping during a mesh, it looked like it did not deploy and went to fail.

@Duckle Makes sense, before upgrade it was ninja silent, now it resonates a wee bit.
Gotta say I thought my 8825 was quiet, but this is wonderful. I do however miss not being able to hear if it actually runs

Anyways first test print of the cube was good.

Think I need to tune my PID, get the BLtouch sorted and fully calibrate the extruder it's off by +.07mm on the cube, and figure out some non duet stuff like why I still get vertical bands after upgrading to linear rails.

I will undoubtfully return with more questions later haha.

Success!
I'm now printing again, it sounds different so I take it that the firmware altered something.

I'll look into the interpolation/stealthchop thingie tomorrow.

Right now I'd better get downstairs to the missus! She feels neglected the past days

Thanks @Phaedrux you know your duet! t's much appreciated!!

I have, I'll re-slice it file lol. I think klipper did similar to me before I switched tbf.

@Phaedrux

what the actual f.. Oo

Ok nevermind, Now it actually updated. I had to drag and drop to make it work.

Lol I guess I'll learn this DWC some day =D
It's also a lot more responsive now on the interface!

these

This can't be right.
Besides it's cloning all my macros/Gcodes all the time. Trying to revert this lol

2.01beta I'll update and look into this. Thank you very much!

@phaedrux The thing is, it's not complaining till second layer. I can issue ten 100mm extrusions without issues.

@Phaedrux
Nah not yet, I have more important errors to look into as of now

Getting a new one and I see it's been up quite a few times!

I had a somewhat successful print last night. Massive over extrusion and skipping. I did the math wrong, I later realized that I forgot that I some weeks back went from 32 > 16 stepping on the extruder and forgot to take this into account.

Anyways, I'm now getting this error !

Fun fact I'm doing a test cube XYZ it lays down the first layer perfect, starts the second layer, does one round then it stops extruding and this comes up.

I did for a brief moment set a higher motor current, cause there's little to no holding power on the steppers. Im used to them being locked down and immoveable!

It shortly popped up on Driver2 but I somehow set the direction as reverse by mistake /shrug reverting this fixed it.
I checked Vin it's stable.
The drivers Arent hot, it extruders 10x100mm no problems

I wanted to try extruding on E1 instead of E0 but it wouldn't let me, I think put in the wrong code for it...

Ok so I took it all apart and started over.

I got all my endstops working, I connected them side by side and not most two outer pins. My bad.
I even made my optical endstops working!
Bed and hotend heats up!
It homes and runs correctly in all directions!

Now to setup that BLtouch, but I see I'm not the only one having issues, but I'll take this elsewhere, for now

Thanks all!

@Phaedrux
Going through it all now. I'll post specs and config after my next attempt.

@dc42
I might have, Man this board is nowhere what I'm used to work with
Im going through it again now, hopefully I can run a test later today.

Thanks

Ok so erhm. Good news! and bad new! I've got the DWC working. On another computer for some reason.
Now I just got a ton of other issues lol.

My parts fan is running constantly.
BLtouch is triggered physically, but hardware is not detecting it.

All my endstops wont trigger, or rather.
-If I trigger Y the fans stops running and the board disconnects it self from the DWC and shuts down the USB.

The steppers do however work, I tried to home X and strangely all three axis moved all together. With the classical back 'n forth move of 10mm when no endstop is triggered.

Seems like I got a long day ahead of me tomorrow, going to unplug it all and try over. However everything seems in order.

Hmm by glance the SD looks like it got all I need. I'll grab a new package and move on to it.
Thanks

Ok so I made progress. I might have put the files in the wrong place form the start. They are now located in /sys

I doublechecked that it's connected to my router at .106 via DCHP however I would like to set it as static later on.

But I stil can't conncet via duettest.local and if I type the ip 192.168.0.106 i get a white screen now with the message:

Your Duet rejected the HTTP request: page not found