Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. oliof
    • Profile
    • Following 2
    • Followers 12
    • Topics 149
    • Posts 2,823
    • Best 719
    • Controversial 6
    • Groups 0

    oliof

    @oliof

    978
    Reputation
    413
    Profile views
    2.8k
    Posts
    12
    Followers
    2
    Following
    Joined Last Online
    Website haraldwagener.com/ Location Germany Age 51

    oliof Unfollow Follow

    Best posts made by oliof

    • RE: Rep Rap vs. Klipper

      @Ebbesendavis The microstepping between klipper and RepRapFirmware is the same since that's part of what the stepper drivers deliver, and apart from Bambu's proprietary solution most if not all printers use Trinamic drivers today.

      There is literally no upside from using 64bit processors. The 6HC or the STMH723/743 printer boards supporting RRF are perfectly capable of producing high enough steprates comparable to klipper setups, without necessarily introducing the dependency on a USB connection and an operating system lacking real-time control, which leads to a number of question marks about operational security when (not if) the 3d printer has some controls failure.

      In terms of print quality, the "magic sauce" in klipper based printers mostly is Input Shaping. RepRapFirmware supports that too, but the results don't match klipper's and Marlin's implementations today (it's getting better though with some improvements in the latest 3.5 prereleases and future changes in 3.6 that will match klippers approach where speed is attained in exchange for lack of sharp corners).

      I cannot speak for Modix' setup because I don't know about it, but in a commercial machine I would prefer a fully supported open source hardware solution over the race-to-the-bottom boards we find in most cheap offerings, often with bad or even unsafe klipper configs and not necessarily an easy way to modify those configs without losing vendor support.

      Bambu provides 3d printing appliances where you relinquish control over your machine mostly to a third party. I won't judge you if you go for that, but it's not how I want my 3d printers to work.

      posted in Duet Hardware and wiring
      oliofundefined
      oliof
    • Colinear Tripteron Progress

      Some of you may remember I reserved a kinematics type number back in August 2019.

      And some of you remember I wanted to take a break from 3d printers.

      Well, I failed either so far. But as of today, I have a prototype machine built that I can implement for. Luckily, someone did it for Smoothieware (the same person whose prototype build I copied, with his blessing and help).

      Here is a first photo:

      IMG_20200524_181505.jpg

      And here is a short video of me abusing delta mode and absolute tower moves to show that it's only mostly dead:

      https://photos.app.goo.gl/c4ptuJajXeWNc8di9

      Still missing are endstops, belt tension, anything on the effector to do useful stuff, a surface to do stuff on ... but for implementing the kinematics this should be sufficient. Let's see if I can get to there in less than nine months (-:

      posted in My Duet controlled machine
      oliofundefined
      oliof
    • RE: Deckingman's passing

      deckingman was one of the staunchest supporters and harshest critics of Duet3D and RepRapFormware. I believe RRF wouldn’t be where it is today without him and he is a true loss to the community. Godspeed, and may all his hotends flow fast and even on the other side

      posted in Off Topic
      oliofundefined
      oliof
    • Feature request: Add diameter sensing

      Tom Sanlanderer has designed and published a cheap diameter sensing setup (see https://www.youmagine.com/designs/infidel-inline-filament-diameter-estimator-lowcost-10-24) -- it would be great to see that included in a future filament sensor design -- and to add a feature to adjust extrusion rate with the sensed diameter of course for those of us that like the last tiny bit of precision.

      posted in Filament Monitor
      oliofundefined
      oliof
    • Support job.LastFile* in standalone mode

      Hi,
      as requested, I am reposting this as a firmware wishlist item.

      If possible, I would like to see

      job.lastFileAborted
      job.lastFileCancelled
      job.lastFileSimulated

      to be made available in standalone mode.

      posted in Firmware wishlist
      oliofundefined
      oliof
    • toolboard to match nema14 motors

      Hi,
      The 1LC format is nice to mount on a Hemera, but people use other extrusion systems as well ...

      it would be great to see other toolboard form factors like the pancake board to fit on the back of one of the currently popular mini extruders with round nema14s ... sadly I lack the time and skills to adopt the 1LC toolboard myself, but if anyone feels inspired, let me know (-:

      c8cc33f5-156f-40ed-9392-aab315222328-image.png

      PS: Yes, I know, chip shortage makes this hard.

      posted in Hardware wishlist
      oliofundefined
      oliof
    • E acceleration has to be limited to to E jerk/PA

      @dc42 dropped this absolute truth bomb in discord today:

      E acceleration has to be limited to the value of E jerk divided by pressure advance

      I really would like to have this enshrined in the documentation.

      Also, it would be great if the firmware warned on acceleration exceeding this limit, and allowing for an E acceleration setting that autocomputes accel by dividing jerk by PA.

      posted in Documentation
      oliofundefined
      oliof
    • RE: Question about the quality of the Duet software..

      @natthapol-vanasrivilai I would suggest before you start with software development 101 you look up the developers background who you are trying to lecture here. @dc42 is also behind eschertech.com, which has a formal C++ verifier in its product portfolio. If you do more than a glancing view on the github repo, you see that the code is at times adjusted to allow for the verifier to run.

      Formal verification may not be a common way to ensure software quality, but it's an approach that can cover a lot of issues that unit testing and integration testing cannot, or can only do at very high cost.

      You should also consider that automotive control systems usually apply to systems that have a (mostly) fixed configuration, while RepRapFirmware does allow free-form reconfiguration of the system. I posit that no amount of unit and integration testing will be able to catch all errors in such a system. They also have hundreds of millions of monetary units in development budget which allows for large and cumbersome software development processes to be run.

      As such, the release of beta and release candidate systems -- which by definition aren't supported deemed production ready releases are another way to gather more input about new changes, their performance, bugs, unintended side effects, etc. One of the reasons that 3.4 is still not in release is exactly that there are known issues that need to be analysed, the root cause found, fixed, tested, integrated, and released.

      PS: I've seen "reasonably sized" software with unit tests and a code coverage quotient well beyond 90% in my 20+ years career in IT that simply didn't work in practice. So I completely disagree with you that the existence or absence of unit tests allows any guess about the quality of the software under test.

      posted in General Discussion
      oliofundefined
      oliof
    • Velocity based extrusion

      I recently ran across a concept from 2014 that seems to have been implemented in LinuxCNC and MachineKit, but none of the main printer firmwares around: Velocity based extrusion.

      In short, the extruder is not an axis controlled by the GCode directly, but the firmware is instructed about target line width and height and controls extrusion speed according to nozzle movement. This is similar to volumetric extrusion but different (extruder is still an axis) and should basically result in pressure equalization similar to Pressure Advance, but based on nozzle movement velocity rather than as a heuristic adjusting the extruder movement.

      Further reading:
      https://basdebruijn.com/2014/05/machinekit-and-additive-manufacturing/
      https://basdebruijn.com/2014/09/velocity-extruding-revisited/
      Post processing script for slic3r:
      https://github.com/machinekoder/Machinekit-Slic3r-postprocess/blob/master/velocity-extrusion.py

      posted in Firmware wishlist
      oliofundefined
      oliof
    • RE: toolboard to match nema14 motors

      For closure, the MKSTHR36 2040 based toolboard fills this gap in the product line-up. I will be able to report how it works probably end of next week.

      posted in Hardware wishlist
      oliofundefined
      oliof

    Latest posts made by oliof

    • RE: Use IR probe as filament switch?

      @o_lampe if you just want to know whether the filament is loaded, you can try using stall detection on the extruder for that.

      posted in IR Height Sensor
      oliofundefined
      oliof
    • RE: Use IR probe as filament switch?

      @o_lampe rq3 also developed an LED driven filament sensor that allegedly (I never used it myself) works better than the usual IR approach especially with filaments like PETG which are invisible to IR.

      posted in IR Height Sensor
      oliofundefined
      oliof
    • RE: KINEMATIC ?

      @rkutun See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m669-set-kinematics-type-and-kinematics-parameters

      As @dc42 writes in https://forum.duet3d.com/post/296209 you will need to specify Cartesian or Mark Forged kinematics using the K parameter, then modify the matrix using the X Y Z and U parameters. You can also reference the MULDEX config at https://github.com/3dprintingworld/MULDEX/blob/master/Firmware/sys/config.g

      posted in General Discussion
      oliofundefined
      oliof
    • RE: I think I would like a variation on M208

      @T3P3Tony I would adjust the M208 limits in the tool change macros but I can see how that's fraught to errors if a tool change fails or tool change with P0 is required.

      posted in Firmware wishlist
      oliofundefined
      oliof
    • RE: I think I would like a variation on M208

      @fcwilt if you set the tool offsets with G10, they should apply towards the reference head point, which is Tool 0, to which M208 applies. Is that not sufficient in your case?

      posted in Firmware wishlist
      oliofundefined
      oliof
    • RE: Select a default tool in a toolchanger arrangement

      You could add T0 P0 at the end of config.g to have a default tool selected, or in start.g which is executed before the gcode file (P0 to avoid running the pre and post macros, so leave out if you want to but at the end of config.g without being homed it'll likely throw an error).

      posted in Gcode meta commands
      oliofundefined
      oliof
    • RE: My new simplified printer design

      @T3P3Tony that needs just a couple of led lit cable guides (-:

      posted in My Duet controlled machine
      oliofundefined
      oliof
    • RE: My new simplified printer design

      @droftarts maybe do something like the test rig one of the FluidNC devs came up with

      1000036000.jpg

      posted in My Duet controlled machine
      oliofundefined
      oliof
    • RE: Duet 2/Duex5 looking for a good home

      @elmoret those used Duet2s seem to be a gateway unto RRF for a bunch of people with tight budget that get fed up with barrel scraper boards failing on them. Its a great service you provide.

      posted in 3D Printing General Chat
      oliofundefined
      oliof
    • RE: [FW 3.5.2] High jerk good for circular path not for corners

      @Triet the smoothing is a side effect of effective input shaping.

      posted in Tuning and tweaking
      oliofundefined
      oliof