Connectivity
-
-
If you have an Android phone or table, look up the Find My Duet app. You can also give the Duet a static IP address, it's one of the parameters of the M587 command that you used to set the network SSID and password.
-
I believe this is a function of the operating system not handling a rapid disconnect/reconnect of a USB device. We strongly recommend that you print from the SD card, not over USB. There are plugins for both Cura and S3D to upload the generated file to the Duet automatically.
-
-
@dc42 , thank you.
So the default way to locate a Maestro on the network is with a phone? I used the RRF Config tool to reconfigure the settings to static on day one, when it became clear the card would not show up any other way that was detectable, when configured for dynamic (which is default for RRF config tool). However, when setup for dynamic the Maestro was not even showing up to the Router -seems odd. I also found it odd that I either over looked or it is not listed in the vast collections of help files, how to "find" the card for anyone -first run.
- If you have an Android phone or table, look up the Find My Duet app. You can also give the Duet a static IP address, it's one of the parameters of the M587 command that you used to set the network SSID and password.
@dc42 , thank you. I would believe this. I had wondered if there was something I could enter into the config.g that would delay the USB from posting by a few seconds, even while the Web Interface pops up right away. Though don't get me wrong, I much prefer the Reset to the E-Stop given the massive difference in time lost. Observation said that the reset was probably happening too fast and confusing Windows. Maybe I can change something in the USB driver settings, in Windows? ...
- I believe this is a function of the operating system not handling a rapid disconnect/reconnect of a USB device. We strongly recommend that you print from the SD card, not over USB. There are plugins for both Cura and S3D to upload the generated file to the Duet automatically.
Sorry to say, I have already taken grief from some skript kiddy teenage intern at CURA who decided that the USB issues were unimportant, or depreciated, and changed the flag on the forum from bug report to that of a features request. So I am not much a fan of the idea that direct connections should be abandoned. Not when almost no one really supports direct control by any other means, yet.
SD card has it's place, and I have no issue supporting it's use, but I spend a lot of time tweaking and working out behaviors and settings the way I want. I feel abandoning the whole 9 yards in favor of some one else's idea of ideal makes the whole point of open source absurd. Thus, I am no place close to giving up direct control, until everything I do is perfect by my own opinion and the opinion of my customers, and when I can put a file on the SD card and walk away for production without concern of how it comes out (And this is for sure by no means how any of this works from the box). Maybe I should say, when I am ready to run my machine blind folded, then I will be OK with uploading every file to SD card first then running. Until then, as I stop and start often, the concept is understood but a waste of time for me. -I hope you understand my position as a user, as a DIY.
I will offer, when the Web Interface grants me the same level of control as do the M3D and S3D control interfaces, then I may be more inclined to use it. But, as good as it is, I would prefer to use the Web Interface in parallel with, and not replacement too -others.
I want my Slicer to remain a slicer, and my Control to remain a control, and the interface to remain a tool for monitoring the hardware directly. And no, the interface should NEVER be a slicer or a viewer, not unless you are ready to unveil a Duet with Samsung Galaxy class RAM and CPU.
However, yell at S3D to open up their network code so it can see or be set up to find and remember others machines, and I might be able to make use of the control from there. -Then we can talk about abandoning USB.
Bear in mind, that of all my controllers, (and I have 4 now), only Maestro offers any NIC functionality. The rest are all dedicated USB or serial. -Thankfully, none on Parallel Port like the really old CNC hardware.
-
@rflulling said in Connectivity:
@dc42 , thank you.
So the default way to locate a Maestro on the network is with a phone?
That's just one way. I guess you didn't follow the Getting Connected guide, because step 8 tells you to read the IP address in the response to the M552 command, https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang=en#s20
SD card has it's place, and I have no issue supporting it's use, but I spend a lot of time tweaking and working out behaviors and settings the way I want. I feel abandoning the whole 9 yards in favor of some one else's idea of ideal makes the whole point of open source absurd. Thus, I am no place close to giving up direct control, until everything I do is perfect by my own opinion and the opinion of my customers, and when I can put a file on the SD card and walk away for production without concern of how it comes out (And this is for sure by no means how any of this works from the box). Maybe I should say, when I am ready to run my machine blind folded, then I will be OK with uploading every file to SD card first then running. Until then, as I stop and start often, the concept is understood but a waste of time for me. -I hope you understand my position as a user, as a DIY.
I will offer, when the Web Interface grants me the same level of control as do the M3D and S3D control interfaces, then I may be more inclined to use it. But, as good as it is, I would prefer to use the Web Interface in parallel with, and not replacement too -others.
The web interface gives you much more info than any USB host program does, and easier control of many things too. Printing from SD card gives you faster pause functionality than printing over USB can, because the firmware can skip moves that are in the queue, knowing it can re-run them later. Also, printing over USB is often subject to underruns, caused by the host PC failing to send the GCodes fast enough, and resulting in print defects.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
No, I did not. Thank you I have not seen this page. This is what I was looking for, some missing information I had not seen. I thought it odd that everything just jumped into first run without how to get connected.
That's just one way. I guess you didn't follow the Getting Connected guide, because step 8 tells you to read the IP address in the response to the M552 command, https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang=en#s20
When all is working the way I expect and I no longer have to adjust everything. I will go SD card, but for now I need direct control from the slicer or a control program. Info is great control is what I need, for tweaking.
The web interface gives you much more info than any USB host program does, and easier control of many things too. Printing from SD card gives you faster pause functionality than printing over USB can, because the firmware can skip moves that are in the queue, knowing it can re-run them later. Also, printing over USB is often subject to underruns, caused by the host PC failing to send the GCodes fast enough, and resulting in print defects.
-
@rflulling said in Connectivity:
but for now I need direct control from the slicer or a control program.
I don't understand - you have direct control from the web interface anyway, assuming you have a loaded it in a browser tab.
-
@rflulling said in Connectivity:
........................Info is great control is what I need, for tweaking..................
Which is exactly what you get from DWC. You can change any parameter, on the fly, during a print or otherwise. Acceleration, jerk, speed, for any and all axes as well as extruders. Heater parameters, tools, mixing ratios, firmware retraction, linear extrusion advance, pressure advance etc etc. Basically you can input any G or M code, on the fly when printing from SD card. How better to dial in a machine? Make changes and observe the effects "real time".
But hey, who am I too argue. If you insist on using DWC just for monitoring and choose not to use most of the features that Duet give you, then that's entirely up to you I guess.
-
Perhaps you have a misconception on what the Duet Web Control is.
-
@deckingman said in Connectivity:
But hey, who am I too argue. If you insist on using DWC just for monitoring and choose not to use most of the features that Duet give you, then that's entirely up to you I guess.
@deckingman It's not like that. I think you are in your feels bit prematurely. It feels to me like there are a bunch of devs here who have put a lot of work into this and are really defensive of their work the moment I say this doesn't work or I am having an issue. I am not here to tell any of you that you are doing it all wrong and that it doesn't work. But I will ask, as a user for tweaks and improvements, and I will point out what I seem to be bugs. I will provide feedback.
At this time, no one has a one stop solution to everything and the Web Interface is no exception. However I would never wish it to be a one stop solution either. I think that it is great that Duet Products have a web interface. Like any other net-workable product this is a great way to setup, and monitor a device. As said on the parts of my first topic in the web interface forum, there are even a few things I would like to see added that would expand what the interface can offer in terms of data. -Though one of those functions, I have been told is not an option at this time. I have since found some of that data may be useful to display indicators as as Idiot lights via M122 and M305 (this for another topic).
One tool that has been added to the interface is the mixing ratio tool. I do not have a head that Mixes material. So it's a great tool to have but for the moment it would be better to save space and keep it disabled as it does me no use in this setup. Maybe the next. Maybe usefully on a Geetech Rostok Delta?
The web interface is also really huge. I get that it reconfigured itself but it is really good for Touch screen I think. I also don't have a touch screen PC yet. I do have a Leap Motion, but its not much good on my twin 32in, 1920x1080 screens. I think there is much more that can be had on one screen.
If any of the devs here would like to talk about what I think would make the interface better. I think that should probably be best in the proper forum, this conversation would be fully off topic here. -I would be more than happy to list what tools I use and need. Why I do what I do, and maybe all of you can take something from that and the interface can digivolve from really good to even better.
But whatever you are taking away from this, please understand that I have not come here to rip on any of this. I think most of it is really great. But this doesn't mean, it is exactly what I need, and we all need something slightly different. -Have we come to terms?
-
I just think you should give the Duet a chance and explore what it can do for you. Btw, there is only one "dev" for the firmware and that is DC42. The rest of us are just end users like you.
-
@deckingman said in Connectivity:
I just think you should give the Duet a chance and explore what it can do for you. Btw, there is only one "dev" for the firmware and that is DC42. The rest of us are just end users like you.
Actually there are a number of other contributors, in particular chrishamm and more recently wilriker.
-
@deckingman Please believe me, I am. As said I think the Maestro is great and I like just about all of it. This doesn't mean I accept it as perfect or a one stop solution for all needs.
There are things it doesn't have I need, and some of those things as requested were more or less blown off. That's fine. The devs don't want them, and don't feel they are needed. But I do and I do use those features. In the mean time, I have to do things in a way that get done the tasks I am trying to accomplish. Some can be done with Macro. Some require an external controller.
However as said. When the devs are open to constructive criticism, suggestion, and requests, I will be growing a list of things I would like to see added. Capabilities, features, interface, etc. BTW, I was told Duet3 is already under design. I would to contribute "requests and ideas" to that next gen.
@dc42 @deckingman I was able to resolve the USB issue by instructing S3D to disconnect before a reset. Then connect again afterward. This has gone without issue. With this in mind I wonder if there is a command I can add to the Macro that will force a disconnect prior to the reset command, thus removing a step.
-S3D, and Cura do not yet offer a way to SAVE the port like with any other Windows printer (i know, not the same). But as long as S3D is not closed with the port inactive, as of a couple updates back will look to the last good connection to retry before any others.
So if the Macro were to dump the connection a moment before the Reset command, the next time I send an instruction from S3D it will auto reconnect. This isn't a huge thing but it simplifies a few things. If such a command exists.My Wanhao, i3 Mini, is now fully operational. Fully calibrated.
*Ran the file included with the Mini on it's SD card for the CT3D.xyz Benchy. Direct from the Web Interface over night. It is far from perfect but, its a generic slice done by some one else another time, another place. But it is the final test in signing off this machine as being back in full operation.
*I look forward to making all the details available to any one who wants to look at trying out a Duet controller with their i3 Mini.Now moving on to my Folgertech FT-6.
-
If your building an FT-6 consider a proper 1/4 (or thicker) Mic6 or ATP-5 build plate, the stock beds from folgertech are almost useless without glass- I have a FT-5, also I am in the process of bumping the sticks they call Z rods to proper 12mm ones.
I also highly dislike tethered printing, SD card printing is far more reliable, and with the Duet being able to monitor and adjust stuff on the fly with G-code I see no reason not to just put files on the system SD card, With some prints ranging to 2 3 or even 5 days, that is a lot of time for a single hiccup to ruin your efforts.
-
I am aware of the glass sheet issue and it has been my intent to do this but have been unsure how to bind the Glass to the Aluminum without the bonding agent coming loose or burning off.
If your building an FT-6 consider a proper 1/4 (or thicker) Mic6 or ATP-5 build plate, the stock beds from folgertech are almost useless without glass.
The lead screws I have had issues with for Three reasons. The whole Z-Axis drive mechanism seems half baked, and it required changes. With those changes made its is now functional, but due to the lack of accurate mounting holes the bearings brass nuts don't seat square and centered. This makes the rods ride at strange angles. The 4x 8mm rods are fine. But the 2x 8mm ACME screws are not long enough to reach through the guide holes, and I have needed to add flange bearings to catch the rods and stabilize them. But then the bed is unable to rise all the way to the top. So, ya fighting the kit. And this is just a few of several battles in getting the kit to operational.
I have a FT-5, also I am in the process of bumping the sticks they call Z rods to proper 12mm ones.
I agree. However I am not sure the fans understand this. I support the SD card operation. But I do not tweak from there. I will run from a SD card when I think that everything is good and there is no reason for me to be involved. So those big files, no argument in running them from a card, if I am confident it will come out as expected. If not, its going to get run direct.
I also highly dislike tethered printing, SD card printing is far more reliable, and with the Duet being able to monitor and adjust stuff on the fly with G-code I see no reason not to just put files on the system SD card, With some prints ranging to 2 3 or even 5 days, that is a lot of time for a single hiccup to ruin your efforts.
-
@rflulling What do you control from Simplify3D that you can't control from the web interface? I'm genuinely curious, as I don't have S3D.
-
@rflulling I am using 3m MP sheets, I simply put a 2 inch wide strip across two sides. So far so good until my sheet of 1/4 tooling plate comes in. There is a small air gap, but I've had great sucess with hair spray, no problems with bonding or warps.
I like Folgertech, but I see them as a starter kit to add your own parts and ideas. -
What I am missing is a connection for storing g-code files directly from the slicer program (in my case Cura) to the Duet.
Maybe that’s more an issue of windows, cause it’s not possible to mount ftp-recourses as drive without 3-party tools.
There are some freeware tools available to do the job, but I haven’t found one witch fulfils all my requests.
As nowadays it’s more common to use Webdav than FTP, I would prefer a more modern solution. -
@diy-o-sphere Cura has a plugin to upload directly to the Duet. And slic3r PE has it built in.
-
@phaedrux
Thank you, I will try that way.... -
@phaedrux
Great, it works like a charm... -
- I do not have to E-stop or Pause and then Cancel.
- I can just Stop, and raise the heck with two clicks.
-
I can adjust Temp, Rate of extrusion, Speed of movement and execution.
The interface does not offer anything to adjust rates while in progress.Edit: The web interface does offer Speed factor and Extrusion factor, but it is buried, and of course only offers functionality if the file is run from the SD card. I expect to have all the tweaking done before a file is finalized and sen to the SD card. Temp I will assume is adjustable but I am not certain to what level. For now. These tools are, simpler to access and execute from the Controller. -
There are a few more tools I would love to have that neither interface offer. Some, would have me believe it is all perfect and there is nothing that can or should be improved.
-
S3D can upload from the controller screen.
-
I prefer to use the upload function of the Web Interface as the network is far faster for moving the files than the USB port is. And much like the config files, I sometimes edit the gcode files to make tiny tweaks after slicing, and after upload, or to double check markup language for errors based on something I have read, or an observed behavior.
