@ Frank833

oh yeah, this works great. I'll try with multiple printers in the near feature and trying to copy the file to SD card and see what's happening. Thanks!

Got the problem figured out. There are jumper that should be on the back Z connector that were not there on my board. I pulled out my other machine so that I could get to the board to see if that LED was on for that one when I noticed it had the jumpers.

It can refer to both the speed of the toolpath and the speed of the filament entering the hot end, depending on context. It's never referring to the speed of the filament coming out of the hot end. When commanding extruder moves, it refers to the movement of filament into the hot end.

Whatever steps/mm setting is, retract/unretract should be in sync: length might be incorrect, but it should be the same in both directions.

Did you try at a lower speed? It may miss a few steps when doing unretract…

Could you also try to slowly increase the retract/unretract value, and see if there is a point when it suddenly start to fail?

Also, have a look at the G-Code fil to check if both values are the same! Don't you have an additional unretract negative value which may mess up things? If all seems ok, try to send both commands by hand, and measure how the filament moves after each command.

I recently changed to 0.9 degree steppers for the X and Y motors on my CoreXY - that made a huge difference to the noise level. The Duet board drives them properly and quietly. Not just that they are quiet in themselves, but the assorted resonances I was getting from the frame and its panels have also gone completely.

Yes I've been trying that already i use to manually probe each point few times and applay the described formula in the wiki for counting the end value. Ofcourse i added the values atm only for the right side back and front points from my bed.g file but there is still noeffect… after G32 and G29.

Thanks everyone for the info. I tried a new micro sd card, and that didn't help. I then setup Octoprint on an rpi3, plugged that into the duet via USB, and my file upload to the rpi3 is extremely fast.

Conclusion: there is something either by the Universities network or the Duet's wifi firmware causing issues with uploading to the Duet.

Now I have Octoprint setup, which I wanted anyways for the webcam streaming. The only problem is I liked DWC more than the Octoprint interface.

Is there any method of transferring files from the RPI3 running Octoprint to the Duet over USB? That'd be clunky, but if possible then I could use the DWC for everything but uploading files.

Also out of curiosity, are there plans to sell the Duet Ethernet's daughter board as a standalone? I've seen mention of that on the forums, but I couldn't find anything in the shop. I might just buy the W5500 and make my own circuit in the meantime.

"https://youtu.be/KwugXGwiroM"

The peak current you can use in practice will depend on how well the chip is cooled.

TBH though guys, it isn't really a problem just driving the extruder carriage the way I do. i.e map the drives so that the Duet treats both gantries as one. Like I said, I have around 4kg moving in Y at 1,000 mm above the floor, so a very high centre of gravity and it really isn't an issue, even the short zigzag moves. Just a very slight rock if the feet aren't levelled and there is some "give" in floor. Even then, the entire printer, including the bed moves as one so I haven't noticed any artefacts with the prints. I guess it might be an issue if the frame wasn't rigid but it all seems like a lot of complication to get around a problem that doesn't really exist IMO.

Edit. Another approach might be to use flexible drives like the nimble for example, and stick with a single gantry. My pockets aren't deep enough for me to now abandon my 5 E3D Titans and replace them with 5 off Nimble flexi drives. Actually, I did briefly look into it but getting them to fit a diamond hot end was just going to take up too much X and Y travel for my liking.

@dc42:

If you PM me later this week I may be able to help.

I sent a message (I think), hope you got it.

If you've removed the old regulator without damaging the PCB traces, you've done the difficult bit.

Wasn't really a problem. I have an iPad I just leave by the printer. Phone works fine too.

I know a few of us had this problem and most did not.

Looks like the problem isn't loss of torque during travel moves then.

Check that you have downloaded the file correctly, it should be a little over 300kb in size. In Bossa check boxes Erase all, Lock and Boot from Flash before pressing Write. After writing the firmware, press Reset or power the board off then on, and the Duet port should appear in p!ace of the Bossa port.

It might be worth reformatting the SD card to FAT32 in case it's currently in a format that the firmware doesn't understand.

@fcwilt:

@thomaspj:

I set the Duet Ethernet to do Marlin output which was successful in connecting to octoprint but It only sends back the bed temperature and not both the bed and Hotend. Does anyone know why and how I could fix this? Thanks

Given the first rate web interface the Duet firmware provides why do you need/want OctoPrint?

Frederick

Im used to send stuff from slic3r directly to octoprint… and i really miss that feature.

I've just updated to version 2.7.0 - yes, I was that far behind!

I will soon see if it behaves nicely…