home.social

Search

396 results for “drfootleg”

  1. Success! Hard won over 29 hours with my on my Trident AWD 350.
    No false filament runouts triggered, so my redesign of the hot-end switch is working. Just a few clogs, the usual filament unload fails and a blocked nozzle which I dealt with by just putting a new nozzle on. Amazed I saved this after so long on the print bed.

  2. I think my new hot-end rebuild has passed the test. Really happy with this result.

  3. New customised Hot-end reassembled and working. So far it is all behaving.

  4. After several iterations I think I have achieved filament detection switch geometry perfection. Now to print the whole part and see if this fixes my false triggers problems on my Voron Trident Galileo Filametrix print head.

  5. It's a good job I am doing this for a hobby. If I charged myself my hourly wage for building my Trident and auto filament changer and getting it working (mostly) then it would have cost me around £30,000 to date.

  6. Today’s project. I added a nozzle wiper to my Voron Trident. Mount design was off Printables but I had to design a custom block to hold the silicone brushes. The sticky pads on them were hopeless so I designed a custom 2 part block which clamps them with a triangular ridge which grips them firmly. Initial prints have been looking good now I have written a wiping macro.

  7. After much problem solving I have completed a 4 colour print on the with just a single wrong colour (green layer on the blue X). I think that was me manually selecting the wrong gate when the printer paused due to a filament unload not fully completing. But no clogs (a first for a long print on this MMU), no filament tangles and no incorrectly selected colours where the printer continued without realising there was a problem.

  8. I think the ERCFv3 is now functionally complete! This rebuild only drew blood 3 times. Calibration next.

  9. Tuning my Voron Trident for quality at speed. This is the start of a 3D benchy aiming for under 20 minutes.

  10. Finally nailed the bugs from my refactoring of this game code. They were mainly due to hard coded assumptions about screen resolution in the original which I had not spotted. I now have it running beautifully in Pygame in any window size I want. More rocks!

  11. Example of Game of Life with residual footprint and competing colours in my RGB animations library.

  12. Pico C++ graphics fans may be excited to hear I just pushed my example of using psram for a full screen double buffer on the to my repo. See the readme here for details as the checkout of submodules is a bit messed up in a dependency. github.com/Footleg/rpi-pico/tr

  13. A productive day sorting out all my C++ code and publishing it finally. Including my touchscreen and accelerometer drivers and a set of example projects to show them in use. See the presto-projects folder here:
    github.com/Footleg/rpi-pico/tr

  14. This is a curse of compromises but at least I now have options. Using PSRAM , I converted my bouncing balls simulation to run at the full screen resolution of 480x480 with my anti-aliasing code. Graphics look beautiful, but screen refresh rate dropped to 10 fps due to the time taken to copy the drawing buffer in PSRAM to the screen buffer in the main RAM. Compare this to using a 240 x 480 resolution for buffers all in main RAM where I get 56 fps.

  15. Now I have confirmed my design works in operation, I have published my custom mounting bracket design which I needed to enable the ERCT filament buffer to work with the
    printables.com/model/1554025-e

  16. Took some investigation, but I have solved the binding problem of the linear rods/bearings which the selector runs along. Took out the rods to check for straightness. Rolling them on a marble slab confirms a subtle bend in both of them. But by marking the face on the inside of this curvature on both rods I was able to reinsert them so they both curve in the same plane, and now the selector does not bind at points along the axis.

  17. Some minor modifications and I have my Siboor ERCFv2 kit LED pcb working in the ERCFv3. I think I have solved the ERCT filament buffer mounting too. Just some wiring modifications to finish and I can do the final assembly.

  18. Now the ERCFv2 is in pieces, assembly of the ERCFv3 can commence. Most of the components apart from the 3D printed parts will be reused in this upgrade.

  19. Attempting to make nice labels for my ERCFv3 with my ERCFv2 before I start the conversion.

  20. The next challenge is the software set up. This seems very poorly documented compared to the build guide. I may have to get involved in helping improve that. I have not found anywhere that mentioned you need to build and flash firmware to the board. I guessed this was needed from having run into this headache on my Voron 0.2 build. Found the manual for the BTT MMB board online which details how to do this, but no mention this was needed in the kit or ERCF documentation.

  21. The LEDs provided in the Siboor ERCFv2 kit have had me stumped for a while, but no more. The kit came with 3 LED chains but only one socket to plug them into. They need to be chained to all work so with some soldering on of extra wires I have built a Franken lead to run them all off the one socket.

  22. ERCF progress. Almost fully assembled now. Just wiring and LED mounting to do and I can start working on the software configuration.

  23. It took some thinking, but I have found pins for both my filament sensors, the PZ Revo probe, X end-stop and made a custom lead so I can plug the Revo heater core and thermistor in to the CAN bus BTT EBB tool head board. Lots of crimping connectors and now the rest of my problems will be in the software config.

  24. Progress with my custom Trident hot-end build. Piezo Revo cold side mounted and filament cutter mod fully assembled.

  25. The UK is having a Rep. Rap. Festival! Tickets booked for in 2-3 Dec.
    Planning to exhibit my custom there. I may be launching my first Footleg Robotics product there too!

  26. @drfootleg Another tip that has been plaguing me for a month!

    If you have processes inside a Docker container and other processes outside the Docker container that need mutex protection such as I2C bus or SPI bus accesses, you need to map the bus (obviously) **and** the mutex folder!

    I had the sensor access working great but could not figure out why my inside and outside "mutex protected" accesses were colliding...

  27. Met this beautiful beast on a walk yesterday.