Topics created by SpeedyDad

@SpeedyDad If you can find the MCU on the PanelDue, you can check which version it is, see https://docs.duet3d.com/Duet3D_hardware/Accessories/PanelDue#version-history

Early version 2 - ATSAM3S2B processor (64MHz, 32kb RAM, 128kB flash)
Version 2 (Manufactured from August 2016) - ATSAM3S4B processor (64MHz, 48kb RAM, 256kb flash).

Most likely it's over 9 years old, which isn't a bad run!

Ian

Success! After restarting the printer, I was also getting errors "G90: Probe was not triggered during probing move" after it finished its homing moves. I looked in homeall.z and it ended in a G90. That really shouldn't have impacted it so I commented it out and ran it again. This time, no errors. To test it again, I removed the ; to comment it out and it still ran fine. No errors. Go figure. I am now able to get it to home properly, do a 4 motor gantry level and run mesh compensation. Mesh compensation takes forever now because it probes the bed twice at each point and, over a 400mm square bed, that takes a lot of time. I'll tweak its settings.

Thanks all for the help. This forum is one of the best out there for solving issues.

@droftarts Thans. I'll have a look.

@SpeedyDad said in Voron Trident XY configuration:

A=X and Y=B

Just go with this.

@jay_s_uk OK, that explains it. Thanks

As far as the rest go, I feel really stupid now. Out3 and Out4 are fine. Somewhere along the way in testing, I must have confused the two connectors and I was testing with the lead which I believed to be the part fan. It was not. It was the lead going to the disconnected hotend fan. Dumb! I made an assumption and it bit me. That and the misunderstanding about "Tool Fan" led me down the wrong path.

@T3P3Tony said in Duet Mini 5+ Temp1 failure?:

@SpeedyDad can you ground that?

I'd basically have to grind the powder coating off the cold side and run a ground wire to it.

@jay_s_uk Yup, that was it. Thanks! It's odd. I can't recall ever changing that but it is possible.

OK, Got it. I figured it was a "I'm on a Mac" thing. Instead of just downloading the file, I right-click on the download link and did a "save As". It downloaded it with a longer name and that zip file worked fine.

@SpeedyDad
Maybe this helps:

; Drives ........ M569 P0.2 R0 S1 T5:5:10:0 ; Z0 drive 0.2 goes backwards M569 P0.3 R0 S1 T5:5:10:0 ; Z1 drive 0.3 goes backwards M569 P0.4 R0 S1 T5:5:10:0 ; Z2 drive 0.4 goes backwards M569 P0.5 R0 S1 T5:5:10:0 ; Z3 drive 0.5 goes backwards M569 P1.0 R0 S0 T5:5:10:0 ; extruder drive 1.0 goes forwards M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E1.0 ; set drive mapping M671 X-70:-70:670:670 Y70:530:530:70 S0.5 ; POSITION OF LEADSCREW FRONT LEFT, RL, RR, FR M208 X0:524 Y0:600 ; Xcarriage move, Ycarriage move

I actually figured out my problem. I have a couple crimping tools I use for RC stuff (servo wires, etc). Nice ratcheting ones. When I would crimp the wire, the wire would break where the insulation was crimped. After looking at it, I found the long legs of the connector itself that are supposed to crimp the wire insulation was curling in on itself and cutting the wire. My remedy was to cut the little legs shorter. No problems now.

@Herve_Smith said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@SpeedyDad said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@Herve_Smith said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@SpeedyDad said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

OK, sorry for being a noob but how do I "switch" the negative pin on? I've looked through the documentation but must have missed it.

I tried the M950 followed by the M106 but get "Error: Pin 'out5' is not free"

looks like you are attempting to control a fan, if so This documentation should help you

Yes, I know that. That's where I got the info to use M950 and M106 as stated above

then please show the EXACT code you have created from reading that so we can see what you have done.

Pretty much copy/pasted the lines from the connecting a fan page and substituted my fan number and the pin number.

M950 F2 C"out5" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P2 S0 H-1 ; set fan 0 value. Thermostatic control is turned off

@droftarts said in Duet 3 Mini 5+ Dual Z homing not working:

@SpeedyDad

Both on the "out" pin and GND pin. I had them on the "in" pin first but that made the machine think they were homed before trying.

You can use the ‘out’ pin as an input, but be aware that they are only 3.3V tolerant, ie if you short the endstop to higher voltage (entirely possible), you’ll destroy the main processor on the board! Better to use the ‘in’ pins, which are 30V tolerant. If they were marked as already homed, add a '! to the pin name to invert the logic. Though this means your endstops are NO, not NC.

Oh,, and I'm also getting "Error: bad drive number" noted in console. Related?

Probably because you have commented out the extruder drive in M584, but it still has a drive in the tool definition, M563.

Ian

Ah. Thanks for all that. I'll switch the pins and comment out the extruder.

I took popped one of the mosfets on one of my printers. Rather unfortunate grounding incident 😢

Luckily I had another free PWM output so I was able to move over the connector.

I have also seen fans go weird about PWM after a while. 25mm fans I've gotten I've seen fail to start. So much so that I now put B3 to blip the fan for 3 seconds into my config.

Those mosfets are tiny and I was tempted to repair it (have a hot air rework station) but since my board is actually functional in its current state, unless I fry another I'm not going near it 😄

Thanks. All is good now.

@speedydad Here are a few random thoughts that might or might not have bearing.

You don't actually reference the U axes in the original drive mapping in your config.g but you do end up mapping it to drive 9 at the ed of your home all. I'm not sure but it might confuse the firmware when later in config.g you set accelerations, speeds, motor currents etc, if no drive has been mapped to that axis. So maybe try adding "U9" to your first M584 in config.g.

You haven't set micro stepping for the U axis. AFAIK the default is 16x with interpolation so it should be OK but to be safe, add "U16" to your M350 command. If nothing else, it will serve as a reminder if ever you change it in the future.

This is not really related to the motion issue you describe but you say you engage dual Z stops yet I don't see an end stop configured for the U axis in your M574. But then I'm a little confused by the G1 S1 Z500 U500 because that will stop when either end stop triggers but not both. For individual homing, I'd have thought you then need to add separate G1 moves for both Z and U. At least, that's what I do with my CoreXYUV. That is home X and U together, then X then U individually to their own individual end stops.

Anyway, moving on ... In your original M584 in config.g, you set the number of visible axes to 3 using P3. Which will be X Y and Z. So I think when you re-map the drives using M584 Z2 U3, the U axis might still be hidden and that does more than just hide it from the display. Therefore,I think you need to add M584 P4 to the start of your home all, then set it back to P3 at the end.

HTH

Yes, that's exactly the information I need if the problem happens again when you are using current firmware.