Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. jakeblat
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 5
    • Best 0
    • Controversial 0
    • Groups 0

    jakeblat

    @jakeblat

    0
    Reputation
    1
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    jakeblat Unfollow Follow

    Latest posts made by jakeblat

    • RE: 4.3 inch PanelDue v2.0

      @dc42 said in 4.3 inch PanelDue v2.0:

      @jakeblat yes that processor upgrade would work, however you would still be limited to running the version 2 firmware, which at some point we are likely to stop updating because the later version 3 has more RAM available.

      You may wish to consider purchasing a new version 3 PanelDue Controller board to use with your existing display.

      I was going by https://github.com/Duet3D/PanelDueFirmware/blob/master/whatsnew.md#limitations which suggested ATSAM3S4B could at least run v3.2.11 although not as fast as the ATSAM4S4B

      I hadn't actually noticed the controller board was available on the shop standalone so I might just replace that with the latest version.

      posted in PanelDue
      jakeblatundefined
      jakeblat
    • 4.3 inch PanelDue v2.0

      I'm currently re-purposing a 4.3 inch PanelDue v2.0 for use in an MPCNC build and realised v2.0 doesn't have enough flash to run the latest firmware (or a CNC specific alternative I've found). Does anyone know if it's possible to do a straight swap of the ATSAM3S2B processor for the ATSAM3S4B? It would only be a ~£5 upgrade for the part to get it running the latest version if so.

      Looking at the datasheet they have identical packages and the only difference is the flash size. I assume I could use Bossa to flash it after swapping it out?

      posted in PanelDue
      jakeblatundefined
      jakeblat
    • RE: Issues with v1.17a+ on CoreXY

      At this point I do think it's something machine specific rather than a firmware issue, I definitely had some settings wrong to start with and after a lot of tweaking recent prints have been at a good quality. It's the first printer I've built so I suspect there will be mechanical issues where I've not got everything lined up perfectly. In the future I might replace the printed corner brackets with metal ones to increase the rigidity of the printer as it does shake a bit more than I'd like at the moment.

      I'm using a 0.4mm nozzle at the moment but also have a 0.6mm. In my previous tests the larger nozzle showed much more exaggerated over-extrusion at the start of each line/layer. I think this was primarily caused by a slicer setting I had enabled "Adjust printing speed for layers below x sec" which paused at the start of each layer when printing small objects.

      I've decided to leave to the extruder value at 837 for now and just tweak the multiplier in Simplify3D, I get good infill and top layers with 98% extrusion with this particular filament so it's very close.

      The only settings I change for my other printer in Simplify3D are retraction speed, retraction distance and temperature (around 20 degrees higher due to the hotend and dodgy electronics that don't maintain temperature accurately) . I think this eliminates the as a slicer issue but I will do another test print on my other printer to make sure.

      I have printed a temperature tower recently with this filament (FilaPrint Premium PLA) and I've got it set at 202 degrees. Oozing is definitely more of an issue with the E3D hotend compared to the Micro Swiss All Metal Hotend I have on my other printer, which is why I've tried to keep the temperature down.

      My printing speed is normally 40-50mm/s depending on what I'm printing, I'm usually after a reasonably good finish rather than speed.

      posted in Firmware installation
      jakeblatundefined
      jakeblat
    • RE: Issues with v1.17a+ on CoreXY

      @dc42 I'm using relative extruder coordinates. I've just done a test print, here's gcode file and photo of the print:

      https://jakeblatchford.com/3dprinting/xyzCalibration_cube.gcode

      Next to a red cube printed on my Duplicator i3 (stock electronics)

      I've bumped my acceleration up 1200mm/s for Z and Y axes but that doesn't appear to have made any difference.

      @deckingman

      I've increased my jerk speed for the extruder to 300, I must have set that really low at some point during my troubleshooting.

      I am using a 0.9 degree stepper motor as that's what came with the Titan Extruder (specifically a 42BYGHM208P4.5-15-X2 & 0.9deg/step as noted on http://wiki.e3d-online.com/wiki/Titan_Assembly)). I used the calculation on that wiki page to reach a value of 837 steps/mm.

      I noticed that the current for my X/Y/Z motors were set too low, I've increased them to 1428mA as the motors are rated at 1.68A.

      Here's my new config file:

      https://jakeblatchford.com/3dprinting/config-revised.g.txt

      After making the above changes I printed a new test cube and it looks identical to the first pink one. Anything else I might have missed/misconfigured?

      posted in Firmware installation
      jakeblatundefined
      jakeblat
    • RE: Issues with v1.17a+ on CoreXY

      Just wanted to add that I'm experiencing a similar problem, but it's no-longer as extreme as PProvost's issue.

      My setup is a CoreXY D-Bot with Titan Extruder and E3D 24v hotend. I'm currently running 1.17d but I've been having issues since I built the printer (one of the v1.16beta's was the first version I used).

      Initially I thought the problem was caused by a long bowden tube (600mm) so I moved the extruder to the gantry and now have a 60mm tube between the extruder and hotend. This change made a significant improvment, but as you can see from the photos below there's still over-extrusion at the start of each line and on sharp corners.

      Here's some examples of the problems I'm having at the moment:


      My config file: https://jakeblatchford.com/3dprinting/config.g.txt

      I don't have an example gcode file to-hand but I get the same results regardless of slicer used.

      posted in Firmware installation
      jakeblatundefined
      jakeblat