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

    New firmware 1.21RC3 available

    Scheduled Pinned Locked Moved
    Firmware installation
    31
    159
    24.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.
    • dc42undefined
      dc42 administrators
      last edited by

      @Mike:

      I'm getting "Error: Attempt to seek on a non-open file." upon trying to print files from slic3r PE on 1.21RC3. The same files work OK on 1.20.

      I can't reproduce this, nor find a reason for it. Can you share the GCode file? What is the filename? Does the print go ahead, or not?

      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
      • resamundefined
        resam
        last edited by

        Weirdly I also just got this "Error: Attempt to seek on a non-open file." error.
        The first line (G28 X Y) is executed, and the the print stops with this error.

        I have to mention, this is not a regular gcode file from a slicer. It was generated by LaserWeb and should utilise a laser with M452 to cut paper. I tried to "fake" a few expected magic comments like layer height, slicer name, etc. but it still errors.

        Here is my gcode file (manually reduced, but still shows the fault for me): https://www.dropbox.com/s/5mczpuy9vzst7jb/pew-pew.gcode?dl=0

        Here my debug:

        18:45:47 M122
        === Diagnostics ===
        Used output buffers: 3 of 32 (14 max)
        === Platform ===
        RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21RC3 running on Duet WiFi 1.02 or later
        Board ID: 08DDM-9FAMU-JWNSW-6J9F2-3S46N-KLJRT
        Static ram used: 16144
        Dynamic ram used: 100584
        Recycled dynamic ram: 2056
        Stack ram used: 1224 current, 8496 maximum
        Never used ram: 3792
        Last reset 00:01:47 ago, cause: software
        Last software reset at 2018-03-09 18:43, reason: User, spinning module GCodes, available RAM 3792 bytes (slot 1)
        Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
        Error status: 0
        Free file entries: 10
        SD card 0 detected, interface speed: 20.0MBytes/sec
        SD card longest block write time: 0.0ms
        MCU temperature: min 40.6, current 40.9, max 41.2
        Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0
        Driver 0: standstill, SG min/max 0/37
        Driver 1: standstill, SG min/max 0/34
        Driver 2: standstill, SG min/max 0/148
        Driver 3: standstill, SG min/max not available
        Driver 4: standstill, SG min/max 0/160
        Date/time: 2018-03-09 18:45:47
        Slowest main loop (seconds): 0.155312; fastest: 0.000113
        === Move ===
        MaxReps: 2, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 61748ms, Underruns: 0, 0
        Scheduled moves: 6, completed moves: 6
        Bed compensation in use: none
        Bed probe heights: 0.000 0.000 0.000 0.000 0.000
        === Heat ===
        Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
        Heater 1 is on, I-accum = 0.0
        === GCodes ===
        Segments left: 0
        Stack records: 2 allocated, 0 in use
        Movement lock held by null
        http is idle in state(s) 0
        telnet is idle in state(s) 0
        file is idle in state(s) 0
        serial is idle in state(s) 0
        aux is idle in state(s) 0
        daemon is idle in state(s) 0
        queue is idle in state(s) 0
        autopause is idle in state(s) 0
        Code queue is empty.
        === Network ===
        Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(1) Telnet(0)
        HTTP sessions: 1 of 8
        - WiFi -
        Network state is running
        WiFi module is connected to access point 
        Failed messages: pending 0, notready 0, noresp 0
        WiFi firmware version 1.21RC4(08b3)
        WiFi MAC address ec:fa:bc:0b:fb:94
        WiFi Vcc 3.33, reset reason Turned on by main processor
        WiFi flash size 4194304, free heap 14944
        WiFi IP address 10.0.0.42
        WiFi signal strength -48dBm, reconnections 0, sleep mode modem
        Socket states: 2 2 0 0 0 0 0 0
        === Expansion ===
        18:45:41Error: Attempt to seek on a non-open file.
        
        
        1 Reply Last reply Reply Quote 0
        • Mikeundefined
          Mike
          last edited by

          @dc42:

          @Mike:

          I'm getting "Error: Attempt to seek on a non-open file." upon trying to print files from slic3r PE on 1.21RC3. The same files work OK on 1.20.

          I can't reproduce this, nor find a reason for it. Can you share the GCode file? What is the filename? Does the print go ahead, or not?

          I did, it got buried earlier in the tread. Here it is again:

          ; generated by Slic3r Prusa Edition 1.39.1-beta1-prusa3d-win64 on 2018-03-06 at 18:25:08
          
          ; 
          
          ; external perimeters extrusion width = 0.45mm
          ; perimeters extrusion width = 0.45mm
          ; infill extrusion width = 0.45mm
          ; solid infill extrusion width = 0.45mm
          ; top infill extrusion width = 0.40mm
          ; first layer extrusion width = 0.45mm
          
          M107
          M106 P1 S0.1 I0 F500 H-1; 
          M140 S110;
          G28 X Y
          G1 X150 Y100
          M190 S110;
          G30 X150 Y100
          G1 X150 Y100 Z25
          M104 S267 T0; 
          M109 S267 T0;
          M106 P1 S0.2 I0 F500 H-1; 
          ; Filament gcode
          ;M290 S0.05
          G21 ; set units to millimeters
          G90 ; use absolute coordinates
          M83 ; use relative distances for extrusion
          G1 Z0.300 F10500.000
          G1 E-1.20000 F2280.00000
          G1 X125.225 Y99.725 F10500.000
          G1 E1.20000 F2280.00000
          G1 F600
          G1 X174.775 Y99.725 E2.38319
          G1 X174.775 Y100.275 E0.02645
          G1 X125.225 Y100.275 E2.38319
          G1 X125.225 Y99.785 E0.02357
          G1 X125.625 Y99.726 F10500.000
          G1 X125.418 Y100.000 F10500.000
          G1 F600
          G1 X174.582 Y100.000 E1.00800
          G1 E-1.20000 F2280.00000
          ; Filament-specific end gcode 
          ;END gcode for filament
          M104 S0 ; turn off extruder
          M140 S0 ; turn off bed
          M107; Turn off fans
          G91
          G1 Z50 ; lift z
          G90
          ;G28  Z; home all axes
          M84 ; disable motors
          M106 P1 S0.5 I0 F500 H-1; dim lights
          
          

          It's a tiny test object, just 2 lines. The same job sliced in S3D or Slic3r PE doesn't start on the CoreXY - the execution stops after finishing the G28 command.

          Edit: As for the filename it was something very generic - test_line.gcode or something similar. No special characters. The file shows up in the "G-codes" tab in DWC, no issues there.

          1 Reply Last reply Reply Quote 0
          • resamundefined
            resam
            last edited by

            dc42: did you consider simulation mode and unhomed moves? I think I found a bug in RC3:
            Simulating a print fails everytime with: "Error: G0/G1: insufficient axes homed".

            I know that the file in question prints fine, because I successfully printed it the day before yesterday.

            1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators
              last edited by

              Yes, that's a known issue.

              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
              • nytundefined
                nyt
                last edited by

                @dc42:

                Yes, that's a known issue.

                So how about double tap homing on G30? Possible to add behavior to match bed leveling?

                1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators
                  last edited by

                  @nyt:

                  @dc42:

                  Yes, that's a known issue.

                  So how about double tap homing on G30? Possible to add behavior to match bed leveling?

                  I am looking at this now. It would be easier if I change the behaviour of G30 with no P parameter so that after probing it moves the probe up to the dive height, just as it does when there is a P parameter. Can anyone see a reason why I shouldn't make this change?

                  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
                  • resamundefined
                    resam
                    last edited by

                    @dc42:

                    It would be easier if I change the behaviour of G30 with no P parameter so that after probing it moves the probe up to the dive height, just as it does when there is a P parameter. Can anyone see a reason why I shouldn't make this change?

                    Sounds good for my CoreXY. It would also be nice if I could do a fast-slow Z-home with G30. Currently the probe speed is fixed in M558 - and I don't really like copy-pasting my M558 lines to get different speeds.

                    Either M558 can take two parameters: a slow and a fast speed,
                    or G30 takes a new parameter to override the probe speed for the single probing move.

                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators
                      last edited by

                      Another possibility I have considered is to keep G30 behaving as now (but possibly with a speed override), but to make G30 P0 Z-9999 S1 do "1-factor calibration" on all machine architectures, i.e. set the Z height. Then in homez.g you would do G30 followed by G30 P0 Z-9999. The G30 with P parameter would support multi tap.

                      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
                      • nytundefined
                        nyt
                        last edited by

                        Speed override would be great, could do a normal home like that, then whatever multi tap command.

                        1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators
                          last edited by

                          I have changed the code so that G30 by itself can do multi tap. Only G30 S-1 and S-2 now do single tap on!y.

                          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
                          • okerchoundefined
                            okercho
                            last edited by

                            @dc42:

                            I have changed the code so that G30 by itself can do multi tap. Only G30 S-1 and S-2 now do single tap on!y.

                            Great!! When is expected the next beta? 😄

                            Okercho
                            Custom Prusa i3 Hephestos with Duet Wi-Fi
                            E3d V6 with Bondtech BMG DirectDrive and PrecisionPiezo Sensor
                            Rebuilding Hypercube Evolution

                            1 Reply Last reply Reply Quote 0
                            • dc42undefined
                              dc42 administrators
                              last edited by

                              Tomorrow or Monday.

                              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
                              • garyd9undefined
                                garyd9
                                last edited by

                                Recent code changes have changed z-probe "multi-tap" to use an average instead of aborting when none of the taps are within a specified tolerance. Is there a parameter to get the old (aborting) behavior?

                                The reason I'm asking is that I had a bltouch (since returned) that would trigger at seemingly random places in a range of almost .2mm. When that happens, I don't trust even an average and would prefer that the entire operation be aborted.

                                "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

                                1 Reply Last reply Reply Quote 0
                                • nytundefined
                                  nyt
                                  last edited by

                                  @garyd9:

                                  Recent code changes have changed z-probe "multi-tap" to use an average instead of aborting when none of the taps are within a specified tolerance. Is there a parameter to get the old (aborting) behavior?

                                  The reason I'm asking is that I had a bltouch (since returned) that would trigger at seemingly random places in a range of almost .2mm. When that happens, I don't trust even an average and would prefer that the entire operation be aborted.

                                  It doesn't just use an average. If two parameters are outside of the specified value, it keeps probing until they're within tolerance. I'm using 0.005 with the IR sensor.

                                  1 Reply Last reply Reply Quote 0
                                  • xnaronundefined
                                    xnaron
                                    last edited by

                                    I have 2 duet ethernets one is fairly recent while the other is at least a year old. I was running 1.21RC1 and upgraded the older one to RC3 with no issue. However the newer one, when upgraded to RC3, lost ethernet connectivity after the upgrade. I ran M552 and it said something like wifi disabled. I thought maybe I renamed the wrong firmware file so I flashed 1.21RC1 to it via Sam2.17 and it connected to ethernet. I carefully downloaded the combined version of RC3 and renamed it DuetEthernetFirmware.bin and uploaded. It upgraded and did the upgrade again and ethernet again wasn't working so I flashed it back to 1.21RC1 with sam2.17. Any idea why it seems to think this one is a duet wifi?

                                    1 Reply Last reply Reply Quote 0
                                    • dc42undefined
                                      dc42 administrators
                                      last edited by

                                      Please confirm that it thinks it is a Duet WiFi after installing RC3, by sending M115. If that confirms it, check that the two pins on the Ethernet daughter board connector nearest the edge of the PCB are properly soldered, both on the socket soldered to the Duet and the pins soldered to the daughter board.

                                      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
                                      • garyd9undefined
                                        garyd9
                                        last edited by

                                        I still have the issue with it skipping/ignoring M116 commands with RC3. 😞 It really bit me in the rear when I tried a print with a non-heated build plate. (The only way I could get it to print was to completely preheat the nozzle before starting the gcode print.)

                                        I'll try to come up with some simple gcode file tomorrow.

                                        "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

                                        1 Reply Last reply Reply Quote 0
                                        • dc42undefined
                                          dc42 administrators
                                          last edited by

                                          If the M116 command is in a tool change file, are you sure that the file is being run? Tool change files are not run if axes have not been homed when you do the tool change.

                                          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
                                          • gideonundefined
                                            gideon
                                            last edited by

                                            hello i just updated my deut to 1.21RC3,
                                            only now I can not get out of it,
                                            that you have to change something now only get error messages when I do home y home and z home
                                            I hereby add my home files
                                            could someone help me with this what I am doing wrong?

                                            ; Configuration file for Duet WiFi (firmware version 1.20 or newer)
                                            ; executed by the firmware on start-up
                                            ;
                                            ; generated by RepRapFirmware Configuration Tool on Tue Jan 02 2018 16:42:45 GMT+0100 (West-Europa (standaardtijd))

                                            ; General preferences
                                            M111 S0 ; Debugging off
                                            G21 ; Work in millimetres
                                            G90 ; Send absolute coordinates…
                                            M83 ; ...but relative extruder moves
                                            M555 P2 ; Set firmware compatibility to look like Marlin
                                            ; Automatic saving after power loss is not enabled

                                            M667 S1 ; Select CoreXY mode
                                            M208 X0 Y0 Z0 S1 ; Set axis minima
                                            M208 X400 Y400 Z550 S0 ; Set axis maxima

                                            ; Endstops
                                            ;M574 S1 Z0
                                            M574 X1 Y1 S0 ; Set active low endstops
                                            M574 Z1 S2 ; Set endstops controlled by probe
                                            ;M307 H3 A-1 C-1 D-1 ; bltouch
                                            ;M558 P5 X0 Y0 Z1 H3 F100 T5000 ; bltouch
                                            M558 P5 X0 Y0 Z1 F100 T3000 I1 H1
                                            G31 X0 Y0 Z1.05 P1000 ; bltouch
                                            M557 X5:395 Y5:395 S95 ; Define mesh grid

                                            ; Drives
                                            M569 P0 S1 ; Drive 0 goes forwards
                                            M569 P1 S1 ; Drive 1 goes forwards
                                            M569 P2 S0 ; Drive 2 goes forwards
                                            M569 P3 S1 ; Drive 3 goes forwards
                                            M350 X16 Y16 Z16 E16 ; Configure microstepping without interpolation
                                            M92 X80 Y80 Z400 E100 ; Set steps per mm
                                            M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
                                            M203 X6000 Y6000 Z180 E400 ; Set maximum speeds (mm/min)
                                            M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
                                            M906 X1200 Y1200 Z800 E1400 I30 ; Set motor currents (mA) and motor idle factor in per cent
                                            M84 S30 ; Set idle timeout

                                            ; Heaters
                                            M305 P0 T100000 B3988 C0 R4700 ; Set thermistor + ADC parameters for heater 0
                                            M143 H0 S120 ; Set temperature limit for heater 0 to 120C
                                            M305 P1 T100000 B3988 C0 R4700 ; Set thermistor + ADC parameters for heater 1
                                            M143 H1 S280 ; Set temperature limit for heater 1 to 280C

                                            ; Tools
                                            M563 P0 D0 H1 ; Define tool 0
                                            G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
                                            G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

                                            ; Network
                                            M550 PHypercube gideon ; Set machine name
                                            M552 S1 ; Enable network
                                            M587 S"gidbeneden" P"gidbeneden" I192.168.0.35 J192.168.0.1 K255.255.255.0 ; Configure access point and IP addresses. You can delete this line once connected
                                            M586 P0 S1 ; Enable HTTP
                                            M586 P1 S1 ; Enable FTP
                                            M586 P2 S1 ; Enable Telnet

                                            ; Fans
                                            M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
                                            M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
                                            M106 P2 S1 I0 F500 H1 T60:140 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

                                            ; Custom settings are not configured

                                            ; homeall.g

                                            ; Sensorless Homing test file
                                            M400 ; make sure everything has stopped before we make changes
                                            M915 X Y S3 F0 R0 ; configure stall detection
                                            M574 X0 Y0 S2 ; set endstops to use motor stall
                                            M913 X50 Y50 ; reduce motor current to 50% to prevent belts slipping
                                            G91 ; use relative positioning
                                            G1 S2 X-400 Y-400 F3600 ; move right/back 325mm, stopping at the endstop
                                            G1 X5 Y5 ; move away from home
                                            ; X or Y is homed at this point, now home the other axis
                                            G1 X-400 F3600 ; move towards axis minimum
                                            G1 Y-400 F3600 ; move towards axis minimum
                                            G1 X1 Y1 ; move away from home
                                            M400 ; make sure everything has stopped before we reset the motor currents
                                            M913 X100 Y100 ; motor currents back to 100%
                                            G90 ; back to absolute positioning
                                            M574 X1 Y1 S1 ; define active low microswitches

                                            ; homex.g

                                            M915 X Y S3 F0 R0 ; configure stall detection
                                            M574 X1 Y1 S3 ; set endstops to use motor stall
                                            G1 S2 Z5 F2000 ; lower bed
                                            M913 X50 Y50 ; reduce motor current to 50% to prevent belts slipping
                                            G91 ; use relative positioning
                                            G1 X-400 F3600 S12 ; course home X
                                            G1 X1 ; move away from end
                                            G90 ; back to absolute positioning
                                            M400 ; make sure everything has stopped before we reset the motor currents
                                            M913 X100 Y100 ; motor currents back to normal
                                            M574 X1 Y1 S1 ; set endstops back to normal

                                            ; homey.g

                                            M915 X Y S3 F0 R0 ; configure stall detection
                                            M574 X1 Y1 S3 ; set endstops to use motor stall
                                            G1 S2 Z5 F2000 ; lower bed
                                            M913 X50 Y50 ; reduce motor current to 50% to prevent belts slipping
                                            G91 ; use relative positioning
                                            G1 Y-400 F3600 ; course home Y
                                            G1 Y1 ; move away from end
                                            G90 ; back to absolute positioning
                                            M400 ; make sure everything has stopped before we reset the motor currents
                                            M913 X100 Y100 ; motor currents back to normal

                                            ; homez.g
                                            ; called to home the Z axis
                                            ;
                                            T0 ;select tool
                                            G91 ;relative coordinates
                                            G1 S2 Z5 F2000 ;lower bed
                                            G4 P500 ;wait for the bed to lower
                                            G90 ;absolute positioning
                                            G1 X200 Y200 F3000 ;move to center
                                            ;M401 ;deploy the probe
                                            G30 ;calibrate Z-axis
                                            ;M402 ;Retract Probe

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