Posts made by strohm81

I ran the scan while loading the file again and it failed again. I think I did it right; the file was ~70mb and still ~25mb zipped so I put the zip file in dropbox.

https://www.dropbox.com/scl/fi/6hhhsxv4j7ftcclj6fxua/Capture-9-22-23.zip?rlkey=3a4mmt2g418hataytddbkqz03&dl=0

I am not familiar with this but I will try.

Duet Console 9-22.txt

I just finished running the ~850mb file that was transferred directly onto the SD and it ran fine.
So I tried M122 P0 with file sizes up to 500 and they all passed, and a ~60mb file was able to upload successfully but a ~400mb file failed again approximately 5-10% through.

Ok, I had done that with S10 and captured it in the log, I can try it with a bigger number. I just put the file in the gcode folder on the SD using my pc with an SD adapter and it is running now. I will try further troubleshooting when it is done. What is the remediation if it fails, or passes?

For future reference can I eject and reinsert the SD card from the Duet while it is powered on to transfer files? This is how I transferred files to the Smoothieboard that the Duet replaced.

Thanks.

Thanks! I just tried the .dummy file and it uploaded fine with speeds of around 7 to 9 mbits/sec. I am running a Windows 7 PC.

Hi, I seem to be having the same problem as some other people have reported with transferring large files to my 6XD but nothing I have tried has fixed it including multiple SD cards. The Duet disconnects (HTTP request time out) usually 3-10% of the way. I thought I was having the same issue as this post but like I said different SD cards and same issue:

https://forum.duet3d.com/topic/30045/large-files-uploading-fail?_=1694740251985

First I thought it might be a router issue (ethernet only) so I hooked it directly to the PC with a static address. Then I got a new 32G sandisk ultra card, copied the files from the one that came with the Duet, and loaded it, ran M122, seemed good, tried to copy a big file, it failed, ran M122 again, write time went through the roof, ran M39, checked out ok, ran M122 P104 S10, fast read and writes. I looked at the board as referenced in the SD diagnostics page and don't see any soldering defects. This board was just fired up this past weekend so it has extremely new firmware and DWC. Please take a look at the console log and help, I'm out of ideas other than transferring the file directly on to the SD.

Thanks!

Duet Console 9-15.txt

Great. Thanks!

Sure thing. Let me know if you need anything else.

Hi, I was fitting my printer with a new 6XD, distribution board, and 2 tool boards, and one of the tool boards was blinking slowly as expected and the other was blinking quickly. I swapped the cables around and which port on the distribution board they were plugged into to see if one of them was bad but it did not resolve the issue. I had a spare 1LC from a different printer and plugged that in and it worked correctly, and that is what's currently fitted on the printer. The one I believe to be faulty is serial 202305-085. Thanks.

@phaedrux it's not ideal but the robots always took priority; if there was any silver lining in the past year we finally had capacity to get to other things that had been languishing

@phaedrux it was bought it from Filastruder, I'll see if the order info can be tracked down but it was at least a couple years ago.

Thanks, we have 5v available so I will try using an external source with fresh firmware.

I am helping my high school robotics team build a new printer with a Duet 2 Ethernet and expansion board to drive Clearpath servos. We had everything hooked up and configured and were ready to run a test print when during bed leveling a dial indicator showed there was a dip in the middle of the bed. We acquired a genuine BLtouch off Amazon and installed it according to the wiki with the input pins in the dedicated inputs next to the expansion header and the +5, gnd,and pwm pins on heater 7 of the expansion board.
After powering up to configure the probe we were unable to connect to the board via ethernet and only the blue LED was lit on the board. Unplugging the probe wiring had no effect. After unplugging the printer and connecting a usb cable the 5v, 3.3v, and diag LEDs were flashing but we were unable to establish connection.
After searching the forums U3 regulator failure kept coming up as a potential culprit and it appears that U3 on our board is damaged though nothing we found indicated why this might have happened. The board was purchased for the project more than 6 months ago but was just now being commissioned. Any help and insight on how to prevent this from happening again would be appreciated. Thanks in advance.

@phaedrux will do, thanks.

I just had the exact same thing happen and found this post when looking for solutions; I had everything hooked up and working on a Duet 2 Ethernet w/ expansion board to run external drivers, then plugged a genuine BLTouch in according to the directions on the wiki and now it appears I have the same fried board that OP has. Everything I read indicated that even if something on the probe was backwards it shouldn't have smoked the board. I was confident it was correct to begin with and it was nowhere near any 24v pins. Very frustrating. The board is more than 6 months old but was just now being commissioned. Any remediation available and how to prevent this from happening again? Thanks in advance.