Simplify3d + Duet2 wifi
-
not sure but i think the duet needs to be in marlin compatibility mode (
M555 P2) to work with a slicer through a serial port.for the virtual serial port enable telnet on the duet and set the (virtual serial) port to point to the duet ip and telnet port.
-
@revdit Simplify3D only works via an USB comport. It doesn't know WiFi or ethernet.
-
@revdit, what do you hope to achieve? Uploading sliced gcode files from s3d to duet via wifi? Anything else?
-
@zapta Hello. I just want to solve the connection problem.
-
@stephen6309 Hello. very easy to connect to Large-K. The same actions on Duet do not give a result.
-
They is no problem, just don't use the "connection" in S3D and upload files via Duet Web Control from browser.
Printing over USB/directly from slicer is just a bad idea. -
Elaborate on why its a bad idea? When i tried vitrual serial port with telnet the only reason i scrapped it was it wouldn't be able to support powerloss and resume like printing from SD would. On the other hand, I haven't setup any recovery yet, and printing from S3D was convenient.
-
@bearer Hello. Thanks for the advice. I will check.
-
@bearer said in Simplify3d + Duet2 wifi:
Elaborate on why its a bad idea? When i tried vitrual serial port with telnet the only reason i scrapped it was it wouldn't be able to support powerloss and resume like printing from SD would. On the other hand, I haven't setup any recovery yet, and printing from S3D was convenient.
- Accidentally unplugging the USB cable.
- Accidentally closing the slicer
- Hard to slice a second model, especially if it's for a different printer
- Can't print to multiple printers
- Computer can't sleep on overnight prints.
I used to print directly from S3D but it took only 1 accidental USB cable disconnect on a long print to convince me otherwise. There's a thread somewhere about having S3D automatically upload gcode to the Duet and start a print. Combined with DueUI it's just as convenient as printing directly from S3D.
-
USB disconnects isn't going to be an issue with the virtual serial port, but i'll get onboard for the two last points, although computer never sleeps (negligible difference in idling with monitor off and actual sleep state, and doesn't break sockets)
Still automatic upload and starting would be preferable to streaming g-code, absolutely. The virtual serial port could still allow controlling things like homing, extruding, heating and so on from within the slicer, even though you could argue its just as convenient in the DWC. At the end of the day best we can do is help OP make an informed decision.
-
@bearer Oh yeah, the VSP, I forgot. On Linux, S3D doesn't consider virtual serial ports to be legitimate so you can't select them.
-
@bearer said in Simplify3d + Duet2 wifi:
Still automatic upload and starting would be preferable to streaming g-code, absolutely.
You can achieve that using the S3D completion script feature. Write a script that upload the gcode to duet via the http server and starts the printing, in a sense, simulating what the web interface does.
I did something similar once for a FlashAir SD card and the automatic uploading from S3D was flawless.
-
Last time I tried it, S3D could control a Duet over USB if you set flow control to Hardware and selected the correct GCode flavour.
See https://forum.duet3d.com/topic/1020/uploading-code-files-from-simplify3d-to-duetwifi-using-scripts for how to upload over WiFi form S3D.
-
@bearer said in Simplify3d + Duet2 wifi:
USB disconnects isn't going to be an issue with the virtual serial port, but i'll get onboard for the two last points, although computer never sleeps (negligible difference in idling with monitor off and actual sleep state, and doesn't break sockets)
I wouldn't trust a virtual serial port too, computer network aren't designed for such critical things they have dynamic latency with can change depend on the network load and also sometime they can just drop packets. It is just a bad idea to live stream g-code from computer in any way.
-
I ditched a lot of time and achieved nothing. Connection failed. Thank you for your help and participation.
