Posts made by DaveA

@timschneider
Is it possible you have a variation of my problem which has been solver?

https://forum.duet3d.com/topic/37329/3-6-0-beta-3-duet-2-issues-lost-communication/3

@dc42
Bingo! DWC comm is back. I had to pull the printer apart to get to the Duet so I can't try a print for a while. Thank you for the quick response.

@droftarts
Here is the beta 2 M122
Beta2M122.txt

@droftarts
I'd like to include the M122 output but I can't. When I issue M122 I get no text on TeraTerm for about 15 seconds then the board reboots.
If I issue M115 I immediately get the board name and firmware version.
So something is running.

@dc42
Here's the config file. Last changed on 8/24.

config.g

@droftarts

New results. With beta.3 I can get results from M115 but M122 just hangs for maybe 15 seconds then the Duet reboots. I did have a recent Duet2_SDiap32_WiFiEth.bin but I noticed that the 3.54 release area had a few hours old version so I put it on the SD card. No change. I'm hardwired so no wifi in use. I'm back to beta.2 via bossa and M122 works fine.

Are there known instances of stand alone duet2 boards working with this release?

@droftarts

A little more info. I pulled the SD card and copied 3.6.0-beta.2 into the firmware directory. No matter how many time I ran M997 S0 on reboot it aways reported 3.6.0-beta.3 when I entered M115 and there is no DWC connection. I did an erase and used bossa to write the beta.2. file. On boot M115 reports 3.6.0-beta.2 and I have a DWC connection. I then used the system update from DWC to update again to beta.3. Same results with no DWC connection.

So something is awry with either the duet2combinedfirmware.bin file or my system. I didn't see anything obvious in the release notes that I need to update anything else first.

I'm away for some time but I'll try any tests later today.

@chrishamm

Has there been any reports of this release causing problems? For the first time in years an update has left me with a dead printer.
I have a Duet2 on a delta. After the update I've lost any ability to connect via DWC. There is something alive as the extruder fan spins for a few seconds on power up. I can also do a G28 from the Panel but it doesn't home right. It does go to the top but then jerks around for 3 or 4 times then stops.
I was updating from beta2+4 I think.
I don't have time to do more investigating right now but I guess I need to brush up on Bossa to get back.

@dc42

A set of adapters to mount deck railing lights on new deck.
Prototype plastic brackets to mock up an air conditioner compressor on a 1967 MGB. After several iterations the plastic was used as a template to cut brackets in aluminum.
Oil catch can mount for a1946 MG-TC
Several fabric holders for wife's sewing machine.
Timing gauge for wife's long arm quilting machine
Jewelry display mounts
Housing for an O2 sensor display.
And, of course, parts to update my other printer

@Leonard03 I noticed that too. I've been meaning to go back over the release notes to see if it was intentional.

@Phaedrux Bingo! I reverted back to 3.5.4 and the Jobs list shows the file as 1mm high. I deleted the file and reinstalled 3.6.0-2. I reloaded the file and the height is displayed with a object height of 800mm.
Edit to add that 3.6.0-1 appears to display the height correctly so beta 2 has the fault.

@oliof As this is on a delta I just use the G28 to move the effector up to the max height.

@oliof No stop.g file and no end macro. What I do have is the following from Simplify3d at the end of a print.
G1 E-.5 ; retract filament
G28 ; home all axes
M104 S0 ; turn off extruder heater
M140 S0 ; turn off bed heater
M106 P0 S0; turn off fan

Should I have a stop.g?

I think this started with 3.6 but I'm not absolutely sure. I have a simple .stl of a 1mm thick spacer created via openscad. It is sliced by Simplyfy3d. In both of these apps the layer count is displayed correctly as 5 .2mm layers. When I bring the .gcode into DWC 3.6 beta2 it shows that there are 4000 layers. It prints correctly but seeing printing 3 of 4000 seem a bit weird.
I'm including the .gcode file sliced for my delta printer if anyone wants to look at it. Thanks.
ReservoirSpacer-1mm.gcode

@jay_s_uk I just walked by the printer and tried G32 again. Got several service unavailable messages plus a new one in the middle of the G32:

9/22/2024, 2:50:07 PM Warning: Driver 0 warning: phase B may be disconnected

Never saw that before. .Everything was moving properly.

@jay_s_uk I think you're right. I just noticed the DWC thread also mentioning service unavailable. It appears I can make this happen so I'll be happy to try anything you guys need.

@gloomyandy I guess I was a bit premature. I had a few other things to and left the printer on and idle. After lunch I walked past the printer and issued a G32 from another PC. Here's the result:

9/22/2024, 1:44:49 PM: Connected to 192.168.1.117
9/22/2024, 1:45:03 PM: G32: Starting bed calibration
9/22/2024, 1:45:21 PM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/22/2024, 1:45:21 PM: Connection established
9/22/2024, 1:45:30 PM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/22/2024, 1:45:31 PM: Connection established
9/22/2024, 1:45:31 PM: : Calibrated 9 factors using 10 points, (mean, deviation) before (-0.012, 0.012) after (-0.000, 0.007)
9/22/2024, 1:45:32 PM: : Calibrated 9 factors using 10 points, (mean, deviation) before (-0.012, 0.012) after (-0.000, 0.007)
9/22/2024, 1:45:33 PM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/22/2024, 1:45:33 PM: Connection established
9/22/2024, 1:45:34 PM: : Auto calibration successful, deviation 0.007mm
9/22/2024, 1:45:35 PM: : Auto calibration successful, deviation 0.007mm
9/22/2024, 1:45:35 PM: : Auto calibration successful, deviation 0.007mm
9/22/2024, 1:45:36 PM: : Auto calibration successful, deviation 0.007mm

M122.txt

@gloomyandy Well, I guess it's never mind. I had the printer and pc off overnight. When I tried the G32 this morning all ran fine. I ran G32 a number of time with no error messages. I do notice a very slight stutter at some points when the head will move to a position and just slightly hesitate before probing.
I reverted back to 3.5.1 and don't see this hesitation.
But, anyway, I can't reproduce my original issue. Do you happen to know what "Service Unavailable" means?

Thanks

I just updated to 3.5.3 and noticed the following issue when I do a G32 Delta calibration. I have never seen this before. I have not tried to print so I don't know if this is just with G32. The Duet is Duet 2 Ethernet.

9/21/2024, 10:25:11 AM: G32: Starting bed calibration
9/21/2024, 10:25:23 AM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/21/2024, 10:25:23 AM: Connection established
9/21/2024, 10:25:30 AM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/21/2024, 10:25:30 AM: Connection established
9/21/2024, 10:25:34 AM: : Calibrated 9 factors using 10 points, (mean, deviation) before (-0.012, 0.052) after (0.000, 0.000)
9/21/2024, 10:25:36 AM: : Calibrated 9 factors using 10 points, (mean, deviation) before (-0.012, 0.052) after (0.000, 0.000)
Auto calibration successful, deviation 0.000mm
9/21/2024, 10:25:37 AM: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
9/21/2024, 10:25:37 AM: Connection established
9/21/2024, 10:25:38 AM: : Calibrated 9 factors using 10 points, (mean, deviation) before (-0.012, 0.052) after (0.000, 0.000)
Auto calibration successful, deviation 0.000mm

Dave

Dumb question but where is this debug.log that you are referring to?