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

    unusual/unnerving noises + error codes

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    6
    76
    4.2k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      I've made a config for you to try using the web configurator tool.

      First make a backup of your /sys folder in DWC by putting check boxes next to all the files and then right clicking and selecting download as zip. Then save it to you computer. That will be a backup of your current config files.

      config.zip.txt

      Here download this and change the extension from .txt to .zip. And then upload the whole zip file as is (don't extract it) to the /sys folder in DWC.

      Reboot and it should be a bit closer to working I think.

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by Phaedrux

        ; Configuration file for Duet WiFi (firmware version 3)
        ; executed by the firmware on start-up
        ;
        ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 16 2020 13:12:28 GMT-0600 (Central Standard Time)
        
        ; General preferences
        G90                                                ; send absolute coordinates...
        M83                                                ; ...but relative extruder moves
        M550 P"Duet2Wifi"                                  ; set printer name
        
        ; Network
        M552 S1                                            ; enable network
        M586 P0 S1                                         ; enable HTTP
        M586 P1 S0                                         ; disable FTP
        M586 P2 S0                                         ; disable Telnet
        
        ; Drives
        M569 P0 S0                                         ; physical drive 0 goes backwards
        M569 P1 S0                                         ; physical drive 1 goes backwards
        M569 P2 S1                                         ; physical drive 2 goes forwards
        M569 P3 S1                                         ; physical drive 3 goes forwards
        M584 X0 Y1 Z2 E3                                   ; set drive mapping
        M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
        M92 X80.00 Y80.00 Z400.00 E93.00                   ; set steps per mm
        M566 X900.00 Y900.00 Z12.00 E1200.00               ; set maximum instantaneous speed changes (mm/min)
        M203 X6000.00 Y6000.00 Z180.00 E1200.00            ; set maximum speeds (mm/min)
        M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
        M906 X600 Y600 Z600 E600 I30                       ; set motor currents (mA) and motor idle factor in per cent
        M84 S30                                            ; Set idle timeout
        
        ; Axis Limits
        M208 X-5.5 Y-10 Z0 S1                              ; set axis minima
        M208 X220 Y220 Z250 S0                             ; set axis maxima
        
        ; Endstops
        M574 X1 S1 P"xstop"                                ; configure active-high endstop for low end on X via pin xstop
        M574 Y1 S1 P"ystop"                                ; configure active-high endstop for low end on Y via pin ystop
        M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z
        
        ; Z-Probe
        M950 S0 C"exp.heater3"                             ; create servo pin 0 for BLTouch
        M558 P9 C"^zprobe.in" H5 F120 T6000                ; set Z probe type to bltouch and the dive height + speeds
        G31 P500 X-31 Y0 Z0.6                              ; set Z probe trigger value, offset and trigger height
        M557 X9.5:215 Y5:195 S20                           ; define mesh grid
        
        ; Heaters
        M308 S0 P"bedtemp" Y"thermistor" T98801 B4185      ; configure sensor 0 as thermistor on pin bedtemp
        M950 H0 C"bedheat" T0                              ; create bed heater output on bedheat and map it to sensor 0
        M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
        M140 H0                                            ; map heated bed to heater 0
        M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
        M308 S1 P"e0temp" Y"thermistor" T98801 B4185       ; configure sensor 1 as thermistor on pin e0temp
        M950 H1 C"e0heat" T1                               ; create nozzle heater output on e0heat and map it to sensor 1
        M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
        
        ; Fans
        M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
        M106 P0 C"Heatsink" S0 H-1                         ; set fan 0 name and value. Thermostatic control is turned off
        M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
        M106 P1 C"PartCooling" S1 H1 T45                   ; set fan 1 name and value. Thermostatic control is turned on
        
        ; Tools
        M563 P0 S"PrintHead01" D0 H1 F0                    ; 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
        
        ; Custom settings are not defined
        
        ; Miscellaneous
        M575 P1 S1 B57600                                  ; enable support for PanelDue
        M501                                               ; load saved parameters from non-volatile memory
        M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
        T0                                                 ; select first tool
        
        

        I took the values from your current config.g. It assumes that your BLTouch is connected to heater pin 3 on the expansion header.

        Z-Bot CoreXY Build | Thingiverse Profile

        PR1ORundefined 1 Reply Last reply Reply Quote 0
        • PR1ORundefined
          PR1OR @Phaedrux
          last edited by

          @Phaedrux

          Error: in file macro line 9: G30: Z probe 0 not found
          Error: Homing failed

          So im still getting this error :s

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            When do you get that error?

            You are using the config file set I posted?

            How is your BLtouch wired?

            If you send M558 in the console what does it reply with?

            Z-Bot CoreXY Build | Thingiverse Profile

            PR1ORundefined 1 Reply Last reply Reply Quote 0
            • PR1ORundefined
              PR1OR
              last edited by

              @PR1OR said in unusual/unnerving noises + error codes:

              M98 P"config.g"

              this is looking alot better though!!

              M98 P"config.g"
              HTTP is enabled on port 80
              FTP is disabled
              TELNET is disabled
              Warning: Macro file config-override.g not found

              1 Reply Last reply Reply Quote 0
              • PR1ORundefined
                PR1OR @Phaedrux
                last edited by

                @Phaedrux

                So when i click home all, it homes X and Y fine then the Z starts going down then stops and put that error up.

                Yeah this was using your Config file you just sent

                wired like in this diagram

                03b18488-8d14-4c16-8f4c-cb6109e302b8-image.png

                And this is what i get in return of M558

                m558
                Z Probe 0: type 9, input pin zprobe.in, output pin nil, dive height 5.0mm, probe speed 120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

                Let me know if i can give you anymore info, im very confused now haha

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Can you go through this testing procedure for the probe and tell me how far you get?

                  https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Static_test_of_the_Z_probe

                  We're getting closer.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  PR1ORundefined 1 Reply Last reply Reply Quote 0
                  • PR1ORundefined
                    PR1OR @Phaedrux
                    last edited by

                    @Phaedrux

                    So i got to step 4

                    'With the Z probe deployed (if applicable) but not close enough to the bed to trigger it, check that the Z probe reading in Duet Web Control is zero or close to zero.'

                    887e8501-3b97-40b4-90ef-d821d9f04d28-image.png

                    its not showing the right distance i dont think

                    1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator
                      last edited by

                      That's not the Z probe reading it's talking about.

                      It should either show 0 or 1000. In the case of the BLtouch it should show 0 most of the time and when it triggers it would very briefly flash 1000.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      PR1ORundefined 1 Reply Last reply Reply Quote 0
                      • PR1ORundefined
                        PR1OR @Phaedrux
                        last edited by

                        @Phaedrux

                        Where would i see that?

                        1 Reply Last reply Reply Quote 0
                        • Phaedruxundefined
                          Phaedrux Moderator
                          last edited by Phaedrux

                          The bottom right corner of that same display box under the heading Z-Probe

                          805ed48a-4b7d-478c-9428-2c520b07ed1c-image.png

                          Z-Bot CoreXY Build | Thingiverse Profile

                          PR1ORundefined 1 Reply Last reply Reply Quote 0
                          • PR1ORundefined
                            PR1OR @Phaedrux
                            last edited by

                            @Phaedrux so im not sure what just happened but it seems to be working now however when homing the x axis it shakes for a couple seconds and then is fine. the y axis homes but stays to far away so i had to manually flick the bl touch probe. But it worked. Is this just playing around with the axis limits?

                            1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined
                              Phaedrux Moderator
                              last edited by

                              Well you should still verify the basics.

                              I suggest you take a look through these guides.

                              https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

                              https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40

                              Z-Bot CoreXY Build | Thingiverse Profile

                              PR1ORundefined 1 Reply Last reply Reply Quote 0
                              • PR1ORundefined
                                PR1OR @Phaedrux
                                last edited by

                                @Phaedrux

                                Thank you for this!!! i now have everything homing correctly and no weird noises or shaking which is great.

                                Apologies for this, i am trying to find pages that help and i really appeciate all the help you have given me to far. But...

                                I have been following this

                                https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

                                Ive got to step 8 and as soon as i get to roughly 30 degree it stops and shows this message

                                Error: Heater 0 fault: temperature rising much more slowly than the expected 1.7°C/sec

                                i did some googling and found this

                                https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control#Section_RRF_3_x_Error_Heater_0_fault_temperature_rising_much_more_slowly_than_the_expected_1_7_C_sec

                                it says i need to do this 'Therefore, you must perform a PID auto tuning to give the firmware a model for bed heater performance. Failure to do so will result in an error message that the heater temperature is not rising fast enough'

                                But i dont know what a PID is or how to run it. Are you able to help with this?

                                1 Reply Last reply Reply Quote 0
                                • Phaedruxundefined
                                  Phaedrux Moderator
                                  last edited by

                                  Pid tuning is part of the calibration guide.

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  1 Reply Last reply Reply Quote 0
                                  • PR1ORundefined
                                    PR1OR
                                    last edited by

                                    So i have no idea what happened but i have tried to connect this morning and it doent seem to be connecting to the wifi. I noticed that when i turn it on. the Blue LED (wifi LED) go straight to a solid blue rather than flickering a bit while connecting. . I have plugged it in with the USB and went into terminal and i dont seem to be able to get it into idle. I can turn it off using M552 S-1 but when checking the status of the wifi using M552 it says 'WiFi module is being started' and when putting M587 it returns 'Error: M587: Failed to retrieve network list'

                                    Any ideas on how i can connect again?

                                    PR1ORundefined 1 Reply Last reply Reply Quote 0
                                    • PR1ORundefined
                                      PR1OR @PR1OR
                                      last edited by

                                      @PR1OR ive advanced. By using M997 S1 however it keeps reverting back again. Is there a code i need to put in to stop it 'forgetting'?

                                      1 Reply Last reply Reply Quote 0
                                      • Phaedruxundefined
                                        Phaedrux Moderator
                                        last edited by

                                        And you have m552 S1 in your config.g?

                                        If you send m122 at the end of the report it should show some wifi info. Post that here..

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        PR1ORundefined 1 Reply Last reply Reply Quote 0
                                        • PR1ORundefined
                                          PR1OR @Phaedrux
                                          last edited by

                                          @Phaedrux said in unusual/unnerving noises + error codes:

                                          m122 at the end of the report it should show some wifi info. Post that

                                          m122
                                          === Diagnostics ===
                                          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
                                          Board ID: 08DJM-9178L-L2MSD-6JKF6-3SD6R-1TDUN
                                          Used output buffers: 3 of 24 (11 max)
                                          === RTOS ===
                                          Static ram: 27980
                                          Dynamic ram: 93936 of which 24 recycled
                                          Exception stack ram used: 264
                                          Never used ram: 8868
                                          Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80)
                                          Owned mutexes: WiFi(NETWORK)
                                          === Platform ===
                                          Last reset 00:03:30 ago, cause: software
                                          Last software reset at 2020-09-18 19:00, reason: User, spinning module GCodes, available RAM 8636 bytes (slot 3)
                                          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
                                          Error status: 0
                                          MCU temperature: min 37.8, current 38.3, max 38.8
                                          Supply voltage: min 23.7, current 23.8, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
                                          Driver 0: standstill, SG min/max not available
                                          Driver 1: standstill, SG min/max not available
                                          Driver 2: standstill, SG min/max not available
                                          Driver 3: standstill, SG min/max not available
                                          Driver 4: standstill, SG min/max not available
                                          Date/time: 2020-09-18 19:04:28
                                          Cache data hit count 369890305
                                          Slowest loop: 5.90ms; fastest: 0.12ms
                                          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                                          === Storage ===
                                          Free file entries: 10
                                          SD card 0 detected, interface speed: 20.0MBytes/sec
                                          SD card longest read time 1.0ms, write time 0.0ms, max retries 0
                                          === Move ===
                                          Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                                          Bed compensation in use: none, comp offset 0.000
                                          === MainDDARing ===
                                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                                          === AuxDDARing ===
                                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                                          === Heat ===
                                          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                                          Heater 1 is on, I-accum = 0.0
                                          === GCodes ===
                                          Segments left: 0
                                          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
                                          USB is idle in state(s) 0
                                          Aux is idle in state(s) 0
                                          Trigger is idle in state(s) 0
                                          Queue is idle in state(s) 0
                                          Daemon is idle in state(s) 0
                                          Autopause is idle in state(s) 0
                                          Code queue is empty.
                                          === Network ===
                                          Slowest loop: 119.41ms; fastest: 0.00ms
                                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                                          HTTP sessions: 1 of 8

                                          • WiFi -
                                            Network state is active
                                            WiFi module is connected to access point
                                            Failed messages: pending 0, notready 0, noresp 0
                                            WiFi firmware version 1.23
                                            WiFi MAC address cc:50:e3:32:51:9f
                                            WiFi Vcc 3.41, reset reason Unknown
                                            WiFi flash size 4194304, free heap 20544
                                            WiFi IP address 192.168.1.145
                                            WiFi signal strength -50dBm, reconnections 0, sleep mode modem
                                            Socket states: 0 4 0 0 0 0 0 0
                                          1 Reply Last reply Reply Quote 0
                                          • PR1ORundefined
                                            PR1OR
                                            last edited by

                                            So it seems to be working ok now which is good. but when going for a test print i reserve this

                                            Error: Fan number 2 not found
                                            Error: Invalid tool number
                                            Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

                                            the Fan i think can probably wait til a little later but the tool i feel is an issue

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