Taking a break



  • Hi everyone,
    I'm taking a break from the hobby for a while, and I want to thank everyone who was ever so helpful in the last two-ish years. This community is one of the most helpful and friendly I've encountered online in the last 25+ years.

    Keep the spirits up! I will likely return some day.


  • Moderator

    Hope to see your return soon. Good luck out there!



  • @oliof Good luck. I've kind of been forced into joining you in taking a break but I hope to get back up and running at some point in the future - maybe............

    But the more I see and read about the way things are heading, I'm not sure. Do I invest the time and effort in learning about SBCs which in turn means learning a whole bunch of 'nix commands, and probably Python too? Or is it time to call it a day? Not sure.......


  • Moderator

    @deckingman said in Taking a break:

    Or is it time to call it a day? Not sure.......

    The other day I helped an 88 year old chiropractor learn fusion360 so they can 3d print MRI data for spinal research. Apparently old dogs can learn new tricks.



  • @deckingman said in Taking a break:

    @oliof Good luck. I've kind of been forced into joining you in taking a break but I hope to get back up and running at some point in the future - maybe............

    But the more I see and read about the way things are heading, I'm not sure. Do I invest the time and effort in learning about SBCs which in turn means learning a whole bunch of 'nix commands, and probably Python too? Or is it time to call it a day? Not sure.......

    I dunno... it is certainly possible to get deep into the command line, but I'm thinking that the D3+SBC can be treated like any other configuration real soon now. With the possible exception of two commands, the update/upgrade thing. That is beginning to work REALLY well, and I think it is going to be worth the trade to "break out" of the Gcode only universe for those specific commands. Other than that, it really should be like any other Duet. Maybe even simpler (no figuring out which file to download for upgrades, etc. )

    RE: Python. I see absolutely no reason whatsoever for the average, or even power, Duet 3D Printer user to learn Python itself. No more than it is necessary to learn C and build the firmware today. Again, this will become even more true as the transition smooths out.



  • @Phaedrux said in Taking a break:

    The other day I helped an 88 year old chiropractor learn fusion360 so they can 3d print MRI data for spinal research. Apparently old dogs can learn new tricks.

    You may want to look here, a community and tools for 3D medical data. https://www.slicer.org/wiki/New_users



  • @Danal Maybe you right, I don't know (and that's the problem). But there are an increasing number of threads where you guys are talking a language that I don't understand. And it's not just the SBC side of things. Take conditional gcode for example. Such documentation as exists seems to be written by programmers for programmers. What the hell is an object model anyway? (well I know now because I did an internet search to find out). But that's the problem. I've got to learn a bunch of terminology just to understand what these new "features" can do.
    Meanwhile, my Duet3 expansion boards still don't have the basic functionality that my old Duex5 had. If I had more knowledge, I could take time lapse pictures of a print for example, but I'd be more impressed if I could actually tune a heater connected to an expansion board.
    A week or so ago, I was asked if I could live with a limit of 50 tools. I can't at the moment think of a reason why not but who knows what might happen in the future? Previous versions of firmware had no such limit.
    That's what I mean when I talk about the direction that things are going.
    That's also the end of my rant you'll be pleased to know.🙂



  • @oliof said in Taking a break:

    Keep the spirits up! I will likely return some day.

    stay safe!


Log in to reply