@thomasvanderwal said in Duet 2 v1.02 not responding:
;G31 Z-0.700
You'll want to configure the probe offset. In your case the X and Y distance is zero, because the nozzle tip is the probe point. The Z value will need to be calibrated. -0.7 may be accurate. The value is negative because the nozzle is pressing into the surface of the bed slightly.
G31 K0 X0 Y0 Z-0.7
The steps for testing and calibrating a probe are here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing
How are you powering the board?
Have you tried disconnecting everything else from the board and having only power?
Have you seen this? https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond
It should automatically reconnect as far as I can tell.
Doing a quick google for raspberry pi auto reconnect wifi brings up a lot of discussion, so maybe you can find something there that points you in the right direction.
Do you mean the shortcut buttons for the macros on the main display screen beside the tools?
Could you make a short video showing what you're seeing exactly?
You can update all the way to the latest 3.5.4.
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.4
Specifically this bin file. https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.4/Duet2CombinedFirmware.bin
Since you're so far out of date the easiest way to update would be to use a USB connection to a PC and use the Bossa software to flash the firmware directly. https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
You'll then need to prepare an SD card with the latest web control version.
https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.4/DuetWebControl-SD.zip
You won't be able to use the same config files from that old version. The syntax of many commands has changed since 3.x firmware. Creating a new config file set with the web tool would be recommended.
Is there a size requirement that makes you want to use 4 motors instead of just 3?
I assume you have a driver for X Y and extruder, leaving only 3 for Z. Perhaps it would make sense to add a toolboard for the extruder, freeing up a driver for the 4th Z.
If you really want to stick with two motors on a single driver, see here for wiring them in series to a single driver.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting#duet-3
Can you send M122 via the gcode console when connect to DWC and share the results here?
Can you test if a fan on the mainboard will work thermostatically with those heaters?
You may also want to test with 3.6 RC1 as it is nearing release.
https://forum.duet3d.com/topic/37591/firmware-bundle-3-6-0-release-candidate-1-available
What firmware version are you using?
https://docs.duet3d.com/en/User_manual/RepRapFirmware/CAN_limitations
A thermostatically-controlled fan on an expansion board can only be controlled by a temperature sensor on the same expansion board.
But that should be resolved in firmware after 3.3
Not only that, might be a good idea to keep that SD card on hand and use a brand new quality SD card as a fresh start.
Also please share your entire current config.g and homedelta.g and bed.g
I think that's probably a bed attached piezo probe. It detects the nozzle contact tap.
You won't be able to print anything until you have the probe configured and are able to complete a delta calibration and bed mesh. Without an accurate mathematical model of your delta nozzle positioning won't be accurate enough.
Can you get a clearer shot of that little PCB? As well as a photo and description of where the wires from that PCB are connected to your Duet? With that information I can hopefully guide you in configuring it.
Were you able to identify what kind of probe is actually being used? Can you point to a piece of hardware on the printer and say "this is the probe"?
@fcwilt said in Thermostatic controlled fans not working:
so perhaps thermostatic control is simply disabled for bed and chamber heaters.
I don't think so. For instance, it's common to use the bed heater as a proxy to control a case cooling fan, with the assumption being that if the bed heater is on, you're probably running a print and want the Duet to be actively cooled.
@p8blr Are the fans on a different can board than those heaters? I think this may be the reason.
Unfortunately that doesn't tell me much.
Can you try setting a range for T in your commands? T25:50 for instance.
Can you send M98 P"config.g" and M122 in the gcode console and share the results?
; Home X-Axis
G91 ; relative positioning
G1 H2 X0 ; set axes position explicitly to Zero i.e move X and Y-axis Minimum Homing endstop and stop there
G1 H2 X40 F10000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-40 F10000 ; go back a few mm
G1 H2 X0 ; move X and Y-axis Minimum Homing endstop and stop there (first pass)
G90 ; absolute positioning
G1 H2 doesn't do what you think it does here.
G1 H2 X0 means to do a zero movement move regardless if the axis is homed or not. G1 H2 moves are meant to leat you move the axis away from an endstop slightly before a homing move, or to raise the z axis before making an X Y move to prevent scraping.
An actual homing move is done with a G1 H1 movement which needs to be long enough to strike the endstop even from the farthest opposing position. It also must be in the direction of the endstop.
@Stanislav said in PanelDue 7 loses macros after homing or moving rotary axes A/B:
Version of the firmware PanelDueFirmware-5.0i-7.0i.bin
If you look at the setup page on the PanelDue it should say the actual version.