Controversial posts made by rflulling

@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.

@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?