Over the past several years I have had different 3D printers and controllers, Melzi, MKS... I have used Marlin and repetier firmware, all with success and generally I have always been able to print what I needed.

My latest is a TronXY X5SA Pro, I really like the mechanics of this printer, it's solid and works well. The stock controller was not terrible, but I wanted better ( to me anyway ). I replaced the controller with a Duet WiFi and 5" paneldue display.

For the most part the new setup just worked. Had to change my way of thinking from what I did in the past, but it was not a big deal.

For what issues I did have questions about, folks on this forum provided quick and useful help and made things that much easier.

So thanks to the developers of this hardware and firmware and to the folks that helped me and the many others I see in the forum.

Joel

@tomasl

I had issues trying to set a static IP as well. I finally got it to work with some suggestions. The steps seems to be very picky. See this thread,

https://forum.duet3d.com/topic/22703/duet-3d-wifi-set-ip-address/7?_=1621469740585

@droftarts

I did think of that, but I notice my MCU just never gets hot and I think it is too far removed from the drivers.

@fcwilt

If I ever open up my controller case, it would not be horrible to glue a thermistor to one of the drivers.

Thanks

OK, I think I got it, was not hard to figure out. Seems M584 is order driven. I just changed Z2:4 to Z4:2 and it seem to be working.

Joel

@Phaedrux

The macro sets the Z height offset which I do before every printing run.

Removing that line you pointed out fixed the issue.

S3D did refund my V5 without any hassle. I still use V4 sometimes, I have been using superslicer and prusaslicer 2.6 Alpha 0 with success. I need to play with a test model for a bit to see which gives me the best results. I did print some model plane parts with fair results. I think it's just a matter of dialing in settings. Once I got used to the differences in how Prusa/Super slicer works vs S3D, there are some aspects I like about them better than S3D. The only thing that is only slightly annoying is the lack of an easy way to change the part fan speed by layer. I wish it were an option in the height range modifier. As it is, you can change the part fan speed but inserting the gcode command easy enough with the insert feature. You just have to remember to change it back to the default or original value when done. I would think that could be handled automatically in the height range modifier.

Anyway, I think I have found something I like better than S3D. S3D is not horrible, but I think they have lost track of what is important and are falling behind.

@dc42

Hi,

Pretty sure I upgraded from a 3.3 flavor, that's the last backups I have.

Joel

Hi,

I recently updated to 3.4.5. I update via the web interface. What I notice is it takes much longer to connect to the printer and have the web interface ready to go. Something that has happened before but now seems more frequent, the web control page stops loading and is blank.

Did I leave out something in the update?

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.27
Duet Web Control 3.4.5

Joel

I figured I didn't have to really uninstall. I did anyway, I'm going to pass on V5 and just keep using V4. I also loaded SuperSlicer which I'll try out.

I did confirm that I cannot install V5 on 2 systems. When I tried to run it on a second system, it barked at me and said I had to uninstall the other.

I was able to reinstall and run V4.x on the second system without issue.

I haven't tried to print anything with V5 yet.

Some of the changes are they moved things around in the UI, they did get rid of the fw config stuff, but for the most part I don't notice a loss. One annoying thing is it is now a single instance license whereas 4.x was 2. Annoying, but does not affect me much. Auto supports seem to work better.

This weekend I will probably try and print something with it.

Worth the cost, eh, for me it just fell into the category of keeping SW up to date.

I did try Superslicer and Cura, I still like Simplify3d better despite its faults. The main thing I dislike is its over use of the windows registry for things that should be in local config files.

@phaedrux

That's the thing, it did not trigger at the last point. It flagged the error, but it should have moved the table away from the nozzle before going to its homing point and not assumed anything about where the nozzle was.

@phaedrux

The setup is a TronXY X5SA Pro updated to Duet2 WiFi. Has been running fine for a very long time.

Crashed into bed, I guess that's true. I have it set up so worse it can do is 1/2mm or so. Not sure why the probe didn't trigger ( newest TronXY probe ). The missed trigger is not the biggest issue. What is is the behavior after that. At worst, software should have reported the mesh level failed. It really should have lowered the bed before moving regardless of having missed the trigger or not.

Hi,

Today I went to print something. I did a mesh level. For some reason the last probe point did not trigger. Not triggering is not the biggest issue. Instead of dropping the build surface and making the last move it left the nozzle on the table and made the last move. This left a big gouge in my build surface.

Seems the code that does the mesh level needs to be looked at. I would think instead of just stopping at where it thinks Z = 0 was, it should still lower the table like any successful probe before making any more moves.

running Duet WiFi 3.3

@phaedrux

yes, is still present in 3.4 beta

Here are the files

homez.g
homey.g
homex.g
homeall.g
config-override.g
config.g
bed.g