Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Tags
    3. dashboard
    Log in to post
    • All categories
    • curt.dariusundefined

      Sending sensors data from RPi/Arduino to Duet Dashboard?

      Duet Web Control
      • duet2wifi arduino raspberry pi sensor acceleration pt1000 dashboard • • curt.darius
      7
      0
      Votes
      7
      Posts
      670
      Views

      jay_s_ukundefined

      @curt-darius unless a custom plugin is produced, correct.
      You may want to look into whether BtnCmd can provide that https://github.com/MintyTrebor/BtnCmd/releases

    • mogfrogundefined

      Stepper motors and endstops not appearing in dashboard

      Firmware installation
      • dashboard • • mogfrog
      5
      0
      Votes
      5
      Posts
      287
      Views

      mogfrogundefined

      Hi, Thank you all for the responses! I have checked all the above over the past few days and it turned out it hadn't updated and upgraded the firmware files. I started again and followed the following link to the letter and everything is working fine!
      https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3

      Thanks again,

      Mogs

    • Royassasundefined

      DWC - dashboard move buttons: using G1-movements for XYZ-moves?

      General Discussion
      • laser duet web control move buttons dashboard • • Royassas
      3
      0
      Votes
      3
      Posts
      340
      Views

      dc42undefined

      @Royassas said in DWC - dashboard move buttons: using G1-movements for XYZ-moves?:

      Might this be because of the sticky S setting in laser mode definition?

      Yes. If you set the sticky feature then the S parameter is remembered across G0 moves. This is IMO a dangerous thing to do, but unfortunately it's what the programs that generate GCodes for laser cutters and engravers expect. I'd much rather those programs generated the S parameter on every G1 move that needs the laser on, which would be the safe thing to do.

      You can use command G1 S0 at the end of your GCode file (or in your stop.g file, if your program ends with a M0 command) to reset the laser power to zero.

      It's occurred to me that the firmware could remember the laser power setting separately for each input channel, so I may implement this in a future firmware version. I'll also change it to reset the remembered laser power to zero automatically at the end of a job, if it doesn't already.