Maestro connection/guide halp!
-
Ok So I finally got the board connected.
Grabbed the guide on the web found that I needed YAT and ran it via the com4 checked the IP
Typed the IP in my browser... . …. … Nothing
tried the duettest.local … ….. .. .. NothingQuickly went to the configuration setup tool online. Made a brand new setup with a static ip, BLtouch (I might need help with this later on) printer size all the shizzle!
Typed the newly made IP.... …. Nothing.
Now I after reading some more, realize that the page hasn't been updated since april?
Cause it states a specific maestro guide will be needed, and that the online config tool does not support the maestro?So I reach out with my hands soaked in tears! How do I move on from here ?
-
We have not started shipping the Maestro yet. However:
- The online config tool does support the Meastro
- Setup for the Maestro is the same as for the Duet Ethernet.
You probably need to change the IP address in the M552 command in config.g to 0.0.0.0 so that your router can allocate one that is value for your network.
-
Tried that, no dice.
Both 0.0.0.0 and the config tool.So I need to take support to M3D ?
Meh here's for me thinking Plug and play lol
-
If both are 0.0.0.0 then your router is not allocating an IP address for the Maestro. Have you tried a different Ethernet cable? Do the LEDs on the Ethernet socket blink?
-
Oh aye they all the lights acts as expected. I'll try a different approach on the router, I might have had the same issue when I installed the pi.
Ill keep you updated, 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
-
That message usually means that you do not have the DuetWebControl files in the /web folder of the SD card.
-
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 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.
-
I think you may want to have another crack at the online configurator and see if you can provide some more accurate details.
You can also post your config.g here along with a description of your printer details so we can point out what needs to be changed.
Perhaps this would be of help:
https://duet3d.dozuki.com/Wiki/Step_by_step_guide
https://duet3d.dozuki.com/Wiki/Going_from_Marlin_on_Arduino_to_RepRapFirmware_on_Duet
https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter
-
@fizban said in Maestro connection/guide halp!:
-If I trigger Y the fans stops running and the board disconnects it self from the DWC and shuts down the USB.
You have the endstop switch wired incorrectly. It's shorting +3.3v to ground when it is triggered.
-
-
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!
-
@fizban said in Maestro connection/guide halp!:
Now to setup that BLtouch, but I see I'm not the only one having issues,
It's really not that bad.
Did you follow the setup guide?
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
-
@Phaedrux
Nah not yet, I have more important errors to look into as of nowGetting 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 problemsI wanted to try extruding on E1 instead of E0 but it wouldn't let me, I think put in the wrong code for it...
-
That may help you to reconfigure your tool to use a different extruder drive.
Do you still get that error if you disconnect the motor and issue a movement command to the driver? If you no longer get the error that would hint that it is a wiring problem.
-
@phaedrux The thing is, it's not complaining till second layer. I can issue ten 100mm extrusions without issues.
-
What firmware version are you using?
I believe this thread may apply to your issue.
https://forum.duet3d.com/topic/6607/frequent-short-to-ground-on-z-and-extruder
You may need to upgrade to 2.02RC2 if you aren't already and tune your stealth chop / spread cycle setup.
-
2.01beta I'll update and look into this. Thank you very much!
-
This can't be right.
Besides it's cloning all my macros/Gcodes all the time. Trying to revert this lol