Posts made by Phaedrux

Please send M122 and M98 P"config.g" in the gcode console and report the results.

Also test your endstops with M119 to get their status. Check it again with the endstop switch depressed.

Also please share your homeall, homex, homey, homez macros.

This guide might help you out.

https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

DWC is Duet Web Control and is the web interface used to interact with the Duet most of the time.

https://duet3d.dozuki.com/Wiki/Duet_Web_Control_v2_and_v3_(DWC)_Manual

M574 Y1 S0 P"!ystop+!e0stop"

M584 X0 Y5:6 Z2:4

This assumes that Ystop is paired with driver 5 motor, and e0stop is paired with driver 6 motor.

Do you currently have network/DWC access to the printer?

YAT will let you send gcode commands, but not upload files.

If you have DWC access you can upload files that way and then the DWC will hopefully detect that you've uploaded a bin file, and do the update automatically. Otherwise you upload the file and send the M997 command to initiate the flash.

If you don't have DWC, you'd need to manually place the firmware bin files on the the SD card in the /sys/ folder and then send the update command over YAT. M997.

If you don't have network access at all and want to just straight to firmware 3.3 you'd need to use BOSSA to flash the firmware over USB.

Once you're on firmware 2.0 you can upload the combined zip file to DWC and it will handle the update process.

All methods are described in more detail here:
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

It's a complex because there are many ways to update the firmware. This is partly due to legacy, and partly to allow for more recovery options. The normal way to update the firmware these days on a working system is to just upload the full zip file from the latest release.

Your photo didn't upload, or it did but the forum software won't accept .heic photos. I thought it did, so maybe try again with the photo.

I think the driver has failed and would be eligible for warranty replacement. 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.

In the meantime, you could probably swap both your z motors back to the single dual Z port. You'd lose the ability to do tilt correction, but it would likely be enough to get you back up and printing until it's time to send it back for exchange.

The Duex drivers take the next range of numbers. 0 1 2 3 4 are on the Duet. 5 6 7 8 9 are on the Duex.

Which drivers are the Y motors plugged into?

Which endstops are the Y endstops plugged into?

See the example here for Z endstops.

https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors#Section_In_RepRapFirmware_Num_3

It's the same for Y. Put both the endstop pins in the M574 command for Y, and then home Y as normal.

Take a look at this post and see if it helps you out.

https://forum.duet3d.com/topic/18962/firmware-not-updating/4?_=1624395230908

There's basically two ways to do it. USB flash to go straight to the end firmware, or do a few incremental upload updates through DWC. You'll have to decide which is easier for you.

Thanks for the update.

In the endstop dropdown for the Z axis, choose nothing. You'll define the Z probe in the endstops page.

In the Z-Probe section you would choose zprobe.in as the input pin for the bltouch that takes the trigger signal. And the PWM control pin that you want to use for servo control to raise and lower the pin. Usually Heater3 on the expansion header. As you've described.

Then on the endstops page you choose bltouch as the probe and probe for the z axis.

Probe configuration is a bit disorganized in the current version of the tool. It really should have it's own tab with all of the relevant settings there I think. It's complicated though because there are many different kinds of probes that require very different ways of wiring and configuration.

Can you also compare uploading a gcode file to print directly to the SD card internal to the Duet and see if it still resets?

@mrawesome987 said in Duet 2 Wifi Random Resets:

I believe I am running a full size SD card in the PanelDue.

Do you mean to say you are using an SD card in the PanelDue to print from?

Yes that would be a good SD card choice. Be sure to format it as FAT32.

The photo is not high enough quality for me to make out any individual components clearly. A couple close up well lit shots would help.

@pandaym said in [3.3.0] - Folder structure issues?:

In the firmware folder I have 13, but in sys I have 16. Is it safe to delete all 16?

The difference is some IAP files used for older versions of RRF, so if you don't intend to go back to older versions, you can safely delete those files. You'd still be able to go back without them by uploading the combined zip file since they will usually include all required files for that version. (or using bossa to flash directly)

@markgeigel said in Duet 2 Wifi possible defective board?:

I'm really puzzled by this.

Electronics typically fail early on in life, or late in life. It's called infant mortality.

So it is possible that the driver has failed. It does sound that way by your description and troubleshooting by switching the motors around, etc.

Can you please share your config.g as well as the results of sending M122 and M98 P"config.g" in the gcode console?

What is the exact error message that it gives?

Does the driver chip look damaged at all? Photo?

Does it get hot to the touch?

Can you share your full config?

Also might want to update to 3.3.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

Upload to the system tab.

I don't think you need to use M950 at all. There are no default bindings for pins after 3.0, so no need to use "nil" unless it's already been defined previously.

How do you have the power and ground for the Duex wired up?

Should be like this: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

Do any of the other fan/heater/etc ports on the Duex work correctly?

Photos of the board in case we can spot something?

@mrawesome987 said in Duet 2 Wifi Random Resets:

I am not using ferrules on the power connectors, I just used the bare wire.

Might want to give those a tighten, just in case. Bare wire can loosen over time. However the M122 doesn't say that the power was lost, so that might not be it at all.

Will have to see if there is anything useful from that M122 report for DC42.

@pyper said in Duex5 extruder motor error:

I notice on the bottom of the Duet2wifi the pinouts for motors are 1B1A2A2B, but the pinouts on the bottom of the duex5 are A+A-B+B-.. Two different pinouts?

No I think that's just a labeling thing. Either way the pairs are side by side, so as long as you identify the motor pairs they can go on either pair of pins.

https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

Can you try the other drivers on the Duex? Change the M584 to match the drivers being used. Is it all Duex drivers or just 8 and 9?

How do you have the power and ground for the Duex connected?
https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

@testpro said in E 3d BIGBOX Duel head:

Send command G30 S-1. The nozzle will descend or the bed rise until the probe triggers and the Z height at which the probe stopped will be reported.

If you're in the gcode console tab the results should be reported there. Can you take a screenshot and show what you have there?

It would say something like "probe stopped at 1.567mm"

Please post your config.g and the results of sending M122 and M98 P"config.g" in the gcode console.

Check your wiring for any shorts.
Try a different driver and change your M584 driving binding to suit and see if it follows the motor.
Try a different motor on those drivers giving the error.

When and where did you purchase your Duet?
Which Duet is it?

@judgment_kazzy said in Short-to-ground error:

Using Usongshine 0.9° motors.

Which model number specifically?

@diamondback said in Bed mesh correction and tool offsets...:

M208 X-146:159 Y{global.minY}:{global.maxY} C0:250 Z0:290 ; set axis minima & maxima

Can you check that anywhere you have variables and conditional code that it evaluated correctly?

You can send M208 M577 etc by themselves in the gcode console and it will report what the current value is.

So every single driver you try to use reports the same warning?

Do you see any damage to the driver chips themselves? Are they getting hot to the touch?

When and where did you purchase your Duet and Duex?

Can you share your config file (and any called macros?)

Also please post the results of M122.

When and where did you purchase the Duet and Duex?