• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Time estimates not working [SOLVED]

Scheduled Pinned Locked Moved
Firmware installation
3
13
2.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    percar
    last edited by 11 Nov 2018, 17:15

    One other note that I forgot to mention. The filament amount is displayed when I initially start the print however it is depleted about halfway through the print and that is when this issues as explained come up

    1 Reply Last reply Reply Quote 1
    • undefined
      percar
      last edited by 11 Nov 2018, 23:18

      As another note on this issue here are two screen shot of the Paneldue and one of the DWC . These were taken only seconds apart and as you can see the DWC is showing 84% complete while the paneldue is showing more like 25% complete. The panel due is more correct. The filament count on both of these is incorrect.
      0_1541978075097_7c61e490-23d7-4931-aa8b-aea911de4452-image.png
      0_1541978149956_d87becaf-1477-4f25-80a3-7f578f96efca-image.png

      1 Reply Last reply Reply Quote 0
      • undefined
        percar
        last edited by 11 Nov 2018, 23:34

        Here again are the screen shots of Panel Due and DWC but further along in the print
        One weird item to look at is that the layer count is screwy on the DWC it states 42 of 33 so perhaps not all layers are being counted. Note also the progress bar shows completed. In the paneldue the progress bar is more or less correct but the filament is n/a
        0_1541979128388_c71b71ee-9468-4212-9a5f-74eb359b754e-image.png
        0_1541979257439_a98ee594-e313-4053-8654-3da98f8b066b-image.png

        undefined 1 Reply Last reply 12 Nov 2018, 08:12 Reply Quote 0
        • undefined
          deckingman @percar
          last edited by deckingman 11 Dec 2018, 08:13 12 Nov 2018, 08:12

          @percar The drive mapping you have in M584 simply assigns drive 3 and 4 to extruders 0 and 1. The important thing is how the tools have been set up to use those drives. How have you set up the tool(s) (M563)? It might be best if you post your config.g file.

          Ian
          https://somei3deas.wordpress.com/
          https://www.youtube.com/@deckingman

          1 Reply Last reply Reply Quote 0
          • undefined
            dc42 administrators
            last edited by 12 Nov 2018, 09:05

            @percar, please make available to me (via Dropbox or similar) the GCode file that gives these results. It appears that the firmware is either mis-reading the filament requirement, or mis-calculating the filament consumption.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            • undefined
              percar
              last edited by 13 Nov 2018, 02:28

              My Configuration file
              ; General preferences
              M111 S0 ; Debugging off
              G21 ; Work in millimeters
              G90 ; Send absolute coordinates...
              M83 ; ...but relative extruder moves
              M555 P2 ; Set firmware compatibility to look like Repetier
              M208 X-25 Y0 Z-2 S1 ; Set axis minima
              M208 X565 Y300 Z280 S0 ; Set axis maxima

              ; Endstops
              M574 X0 Y0 Z0 S0 ; Define active low and unused micro-switches
              M307 H7 A-1 C-1 D-1 ; assign heater H5 to servo for probe
              M558 P9 X0 Y0 Z1 H2 F100 T4600 A20 S0.01 ; BL touch Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 4600mm/min, 2 measure average, tolerance 25µm (assuming mm as the unit)
              G31 P1 X43 Y0 Z1.88 ; Set Z probe trigger value, offset and trigger height

              ; Drives
              M569 P0 S1 ; Drive 0 goes forwards
              M569 P1 S1 ; Drive 1 goes forwards
              M569 P2 S1 ; Drive 2 goes forwards
              M569 P3 S1 ; Drive 3 goes forwards
              M569 P4 S1 ; Drive 4 goes forwards
              M569 P5 S1 ; Drive 5 goes forwards
              M569 P6 S1 ; Drive 6 goes forwards
              M569 P7 S1 ; Drive 7 goes forwards
              M569 P8 S1 ; Drive 8 goes forwards

              M584 X3:4 Y0 Z2:1 E5:6 ; Apply custom drive mapping
              M350 X16 Y16 Z16 E16 I1 ; Configure microstepping without interpolation
              M92 X80 Y80 Z1600 E430.5 ; Set steps per mm
              ;M566 X2000 Y2000 Z60 E1800 ; Set maximum instantaneous speed changes (mm/min)
              M566 X1500 Y1500 Z50 E2000 ; Set maximum instantaneous speed changes (mm/min) This is temporary test
              M203 X4000 Y4000 Z240 E4000 ; Set maximum speeds (mm/min)
              M201 X2000 Y2000 Z25 E3500 ; Set accelerations (mm/s^2)
              M906 X1200 Y1200 Z1000 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
              M84 S30 ; Set idle timeout

              ;Bed Leveling
              M671 X-85:745 Y152:152 S5 ; Z leadscrews are at (-15,220), (100,-20) and (215,220)

              ; Heaters
              M143 S280 ; Set maximum heater temperature to 280C
              M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
              M305 P3 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
              M570 H3 P40 T40
              M570 H0 P500 T40

              ; Tools
              M563 P0 D0:1 H3 ; Define tool 0
              M567 P0 E1:1 ; set mix ratio 100% on both extruders
              M568 P0 S1
              G10 P0 X0 Y0 ; Set tool 0 axis offsets
              G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

              ; Network
              M111 S0 ; Debug off
              M550 PMakerSlide ; Machine name (can be anything you like)
              ;Mac Address 60:01:94:0c:58:84
              M552 S1 ; Enable WiFi
              M555 P1 ; Set output to look like Marlin
              M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)

              ; Fans
              M106 P0 S1 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
              M106 P3 S1 I0 F500 H3 T60 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
              ;M106 P3 S1 I0 F500 H4 T60; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

              ; Custom settings are not configured
              ;M280 P3 S90 I1 ; retractprobe
              ; Miscellaneous
              T0 ; Select first tool
              M140 S80
              ; to stop ringing trial
              M593 F34.78 ; cancel ringing at 34.78Hz
              ;load configuration override
              M501

              1 Reply Last reply Reply Quote 0
              • undefined
                percar
                last edited by 13 Nov 2018, 03:03

                Link to gcode file
                https://1drv.ms/u/s!ArsUUgUVyLkdhaoqAlyU8KNCKd0yBA

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators
                  last edited by 13 Nov 2018, 10:23

                  The layer count is out because of the G1 Z10 command in your end GCode. For now, the workaround for that is to add a comment starting with ;E or ; E at the end of that line.

                  Duet WiFi hardware designer and firmware engineer
                  Please do not ask me for Duet support via PM or email, use the forum
                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators @percar
                    last edited by 13 Nov 2018, 10:43

                    @percar said in Time estimates not working:

                    The remaining filament shows N/A however the paneldue shows time remaining
                    I am wondering if it is because I am using 2 drives for the extruder ( The filament is quite far from the pinter and I had discover that 2 drives prevents any issues ( I had put the drives in series however now I am using 2 separate drives mapped as below

                    Yes, that's the reason. You have set the filament mix to 1:1 so it will count filament usage twice as fast as it should. Possible workaround: set the filament mix to 0.5:0.5 and double the extruder steps/mm.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      percar
                      last edited by 16 Nov 2018, 19:24

                      @dc42 said in Time estimates not working:

                      ;E
                      Just another tidbit I also have a laser filament monitor. I had to double the % count from 92% error to 184% error as everything else has doubled

                      1 Reply Last reply Reply Quote 0
                      13 out of 13
                      • First post
                        13/13
                        Last post
                      Unless otherwise noted, all forum content is licensed under CC-BY-SA