Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. duetino
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 23
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by duetino

    • duetinoundefined

      Is it possible to use Telnet on DUET2 for slicer?

      Third-party software
      • • • duetino
      5
      0
      Votes
      5
      Posts
      223
      Views

      dc42undefined

      @duetino said in Is it possible to use Telnet on DUET2 for slicer?:

      Well the question is CAN I somehow use it as serial communication line in repetier host or ANY other software?

      In theory, yes. However it's not something I would recommend because if it turns out to be not 100% reliable when GCode is streamed via Telnet, we wouldn't be very interested in fixing to because the Telnet capability is so rarely used. It would also have the same disadvantages as streaming over USB, e.g. taking longer to execute a pause because all commands queued via the interface would have to be completed first.

    • duetinoundefined

      Mesh Bed looks like this dualWave... no matter what

      Tuning and tweaking
      • • • duetino
      6
      0
      Votes
      6
      Posts
      266
      Views

      droftartsundefined

      @duetino if you suspect errors due to the offset probe, try running a calibration and then mesh compensation with M558 P0. Yes, that’s manual probe, but measuring from the nozzle tip will give an accurate reading, especially if your nozzle hangs down a long way below your effector. It’ll take a while, but you’ll see the true results ‘at the nozzle‘. Don’t forget to set G31 offsets to 0.

      Offset probes on deltas are just not great. Calibrating deltas is hard enough, adding an extra variable is unwanted. Get some kind of piezo or contact probe.

      Ian

    • duetinoundefined

      S3D rendered and WebControl always shows full Printer height ?

      Tuning and tweaking
      • • • duetino
      8
      0
      Votes
      8
      Posts
      915
      Views

      MoS-tekknixundefined

      @dc42:

      @MoS-tekknix:

      Okay, i know what you mean and i've done the same.

      At the End of my Print, i've setup'd Simplify3D to completely lower my Bed down to Maximum (365mm). Therefore Simplify3D delivers this Value into the gcode and the Firmware reads the maximum in the gcode and calculates the Layer-Hight to this. It assumes always that the Print is 365mm (in my configuration).

      I've deleted everything and put it into a Macro in /sys and call this Macro. The same is done and interpreted but Simplify3D cannot deliver it into the gcode.

      Therefore everything works as before but the Layerhight is calculated or interpreted correct!

      You can get round this by putting a comment starting with ;E or ; E at the end of the G1 Z command line that moves the bed down at the end of the print.

      Thanks David, that wasn't known by me and i assume a lot of others!

      Thanks
      MoS-tekknix

    • duetinoundefined

      Calibration Cube XYZ is off, how to adjust Axis length

      Tuning and tweaking
      • • • duetino
      9
      0
      Votes
      9
      Posts
      2.5k
      Views

      fmaundefined

      Duetino, if your problem is really a scaling problem, when moving 200mm you should measure 202mm, which is easy to see. If you still have 0.2mm more, this means this is not a scaling problem! In this case, if you correct the scale for 20mm, a 200mm print will be something to 198.2mm…

      So, first, move your axes as far as you can (200mm), and measure with a ruler.

    • duetinoundefined

      Paneldue shows strange Values for Time, Layers and Filament

      PanelDue
      • • • duetino
      5
      0
      Votes
      5
      Posts
      929
      Views

      garyd9undefined

      @dc42:

      PanelDue provides 3 estimated of how much longer the print will take, just like the web interface. One is based on the layer count, another is based on what proportion of the file has been processed, and one is based on what proportion of the total filament needed has been consumed. So in your image, the estimate based on the later count was 9 hours 31 minutes.

      After searching, I finally found this thread. Please add this information to the wiki. The display is really confusing otherwise. (I was trying to figure out why a single layer would take almost as long as the entire print, and how filament was being measured in minutes/seconds.)

    • duetinoundefined

      PanelDue is not starting any print job [SOLVED]

      PanelDue
      • • • duetino
      13
      0
      Votes
      13
      Posts
      1.4k
      Views

      duetinoundefined

      Actually I want to leave it like this but for everybody to visualize the difference of a little misconfiguration…
      The (left) part with line numbers is correct, the other is as well just without carriage return and linefeed uploaded as one big line.

      all the best duetino