Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. core3d.tech
    3. Best
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 65
    • Best 4
    • Controversial 0
    • Groups 0

    Best posts made by core3d.tech

    • Timelapse remote control for Duet Wifi

      I created an instructable on how to use a single remote control to connect 1 to many Canon cameras (and some other brands). The remote is powered and operated by the Duet board so you can now send g-codes at layer change to take an image (and do much more).

      This remote covers some 20 plus Canon Cameras and some other brands. I'm sure the principal applies to other remotes as well.

      You can find the instructable here: https://www.instructables.com/id/Duet-Controlled-Timelapse-Video-Using-Camera-Remot/

      posted in General Discussion
      core3d.techundefined
      core3d.tech
    • RE: Pause.g is not working.

      @dc42 Thx, M84 U followed by G92 U0 does the trick

      posted in Firmware installation
      core3d.techundefined
      core3d.tech
    • RE: Stall Guard reporting

      I'm already using the 4th Axis U. U (P4) runs the motor that switches the XYZ belts to operate the bed. Watching the video may clarify that a bit better https://youtu.be/L9pTHMi5SP8.

      The bed is a "virtual" 5th axis. it is moved by XY and Z (P0, P1, P2) when the 4th endstop is triggered X Y and Z need to stop.

      The other issue I run into is that trying to use the E0 or E1 endstop can not be managed by M574 (only 1.16 and below). these seem to be only usable as Z-probes now (using M558)

      It would be nice to be able to assign a gcode file to specific endstop (TriggeredE1.g) in which I can do what I need. Kinda like homeu.g is there for homing axis U.

      posted in Tuning and tweaking
      core3d.techundefined
      core3d.tech
    • RE: Filament Sensor plus timelapse issue

      So for the many tries with different values, it was always the same story. As M42 P60 S255 was executed (at random layers changes) the filament sensor would error out. I can only conclude a "power spike/drop" when powering a relay (3v) to trigger the camera remote was causing this issue.

      I've now redesigned my remote setup and eliminated the relay. The remote is now directly powered via pin CS5 (P60). It now correctly finishes my print and I tested the sensor for stall and all seems to be working.

      I wonder though if it would be possible to check for multiple consecutive before completely stopping the print. Once the power fluctuation is over all works well again.

      case TypeLaserMessageTypeError:
      lastErrorCode = val & 0x00FF;
      sensorError = true;
      break;

      I'm good for now. Thanks for responding.

      posted in General Discussion
      core3d.techundefined
      core3d.tech