@pm7399

OK so first off, what Duet board do you have?

The only config tool will get you to 95% of the way, it can't set up dual Z as far as i understand this is done once you have the files it generates on the Duet. The config.g is a text file and will make a lot more sense once you have it and can view it.

The 3rd page of the config tool is not specifically for expansion boards, that's where you tell the tool you have them, the rest of the page is asking what connectors are you using i.e If you have a Duet 3 mini 5+ is says Driver 0 is your X axis, and it asks where are you plugging in the endstop? It also asks where are you plugging in the fans? and then heaters.

The next pages asks you specific question about things like motors, endstops, heaters and fan etc. You can find this information from datasheets for the hardware you have but also use general numbers at this stage.

If you take a look on Youtube Chris Riley (Chris' basement) did a video on setting up a duet with the config tool, his might be a little old now but there might be other. Here's Chris' Video: https://youtu.be/6nqddfxHla0

Once you have a basic config, come back and post it here.

@togmore said in Duet 3 SD 0 card not recognised:

Duet 3 Mini5plus Ethernet (SBC mode)

Can you confirm that it's not actually connected to a raspberry Pi?

Okay sorry guys I just found the problem even though I dont know how this could be.

It seems like the grounding point was not strong enough. I measured the VIN and it was only around 2-3V. So I used another ground point and not it works.
The old ground point was directly connected to the ground of the plug that goes into the printer. Now I connected it to the ground coming out of the power supply.

I did not knew that there could be any difference?
I mean the ground point from the plug also goes into the power supply.

But now it works, thank you anyways @jay_s_uk !

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@jay_s_uk Oh wow, I looked but did not see, thanks.

I asked about similar feature here:Terminate movement but not by M112

Once all the firmware was the same all works, thanks for the help!

@signpostman With the help of our internal developer, we got it work. to make it work. ON the RasPi, change file permissions on the wp_supplicant.conf file read & writeable by everyone. we then changed the "|" character to a "}". We then were able to connect.

ok much playing with but i got it Q ended up to be Q1.25 and the switching is just like the oem original now and only +/-.5c spread the R was set to R0.030 which auto tune suggested R0.027 was close but the D was suggested to D159 by auto tune and D28 worked best for me

thank you to all whom guided me here the D,R and Q was the issues i was having and is a ok now!

@phaedrux said in Mesh Bed Compensation Does Not Seem to Work:

M566

Wow... talk about not seeing the forest from the trees.

I went over my settings 5 times, tried a bunch of things, and not ONCE did I even notice that. Probably changed my jerk and accidentally deleted the 5 from the 50 without noticing.

Thank you @Phaedrux!

If you don't mind I'll go get some rum and go feel stupid in my corner now.

The X,Y drivers should actually be called A,B, to avoid confusion with Cartesian kinematic.

2b75e0fe-c671-4928-9bca-5bfe0c7fec1e-image.png

@jay_s_uk
Thank you, problem solved. Have a nice Sunday.

Thanks for the tip...
I've already installed the update, but haven't gotten around to testing it again yet.

@tom1 It needs to be URL-encoded, so e.g. http://duet2/rr_gcode?gcode=G1 X10.

@sph711 I suggest you check the 1A fan fuse on the Duet for continuity.

@trev133
You should give the Duet a fixed IP in your router.
Otherwise it can happen if your Duet is switched off and a new device dials into your WLAN, the Duet will be assigned a new IP the next time it is started.

If this is the case, look in your router menu for the devices that have connected via WLAN.
There you will also see the newly assigned IP for the Duet and you can connect to the DWC via browser.

If your Duet has a fixed IP in your router, this will no longer happen if other or new devices take the IP away from the Duet.

Have a look on YouTube how to assign a fixed IP to a device in your router.
I'm almost certain there is such a video.

Google Translate
----- Original Text -----

Du solltest in Deinem Router dem Duet eine feste IP vergeben.
Sonst kann es passieren wenn Dein Duet ausgeschaltet ist und sich ein neues Gerät in Dein WLAN einwählt, dem Duet beim nächsten Start eine neue IP zugewiesen wird.

Sollte das der Fall sein, sehe in Deinem Router Menü nach den Geräten die sich per WLAN verbunden haben.
Dort siehst Du dann auch die neu vergebenen IP für das Duet und Du kannst Dich per Browser mit dem DWC verbinden.

Hat Dein Duet eine feste IP in Deinem Router, dann passiert dieses nicht mehr, das andere oder neue Geräte dem Duet die IP wegnehmen.

Guck mal bei YouTube nach wie man in Deinem Router einem Gerät eine feste IP zuweist.
Ich bin mir fast sicher das es so ein Video gibt.

@phaedrux
UPDATE :

Your suggestion of replacing M226 with M600 manually in gcode - actually worked! 🙂

The printer paused correctly, inserted the nuts and resumed the print.... 🙂

Guess this is a workaround for now, until I figure out why M226 is not working.

Thanks again!

Just a quick update if anyone stumbles across this thread - I've just completed my first successful print with a 6HC as an expansion board. The printer has XY and Z motors on a 3HC expansion board, U and V motors on a 6HC main board, and 6 extruders connected to a 6HC as an expansion board. The end stops for X U and Z are connected to the 6HC expansion board and these will stop the corresponding motors connected to other boards with no noticeable latency. The two hot end heaters and their corresponding thermistors are connected to the 6HC expansion board which all work as they should. The hot end liquid coolant pump is connected to the 6HC main board but works thermostatically with the sensor that is connected to the 6HC expansion board. So everything appears to be communicating with everything else as it should. This latest firmware update had to be done via Bossa/USB but from now on, all future firmware updates should work over CAN.

In summary, this being the first use of a 6HC as an expansion board "in anger", some glitches and issues were to be expected but these have all now been resolved (at least for my particular machine). I will continue to monitor and report back anything to the Duet guys.

@phaedrux
I'll test that, thanks !