Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. JairoRB
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 9
    • Best 0
    • Controversial 0
    • Groups 0

    JairoRB

    @JairoRB

    0
    Reputation
    1
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    JairoRB Unfollow Follow

    Latest posts made by JairoRB

    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      @bearer Excellent, thank you

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      @dc42 I am as sure as I think I can be, for what it's worth. I flashed for myself at first from github, then from the link provided by Phaedrux and then again from github, making sure it was indeed version 1.23. After running M997 S1, it completes no problem but the issue comes up.

      Is there a way to make sure it is the hardware side?

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      @Phaedrux that looks great! thanks. I have access to ESP-12E, does that work or does it have to be ESP-12S? I guess I can get an Adafruit HUZZAH or maybe a NodeMCU with the ESP-12S and salvage the module from that board, but if the E version is compatible that would be ideal.

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      Well, that is unfortunate. I will send an email to that address as you suggested, thank you for the help.

      I do have access to soldering tools. Haven't worked with SMD before, but I have other scrap boards I can practice with before I replace this, or I can ask someone else perhaps. Are there any instructions on how to replace this? As in, specific to the duet? Or do I just find the module itself and solder it back on and then run M122 and that's it?

      Thank you for the help!

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      It is about one year old. I would need to contact the sales department for the exact payment date, but I can confirm we received the package on October 18th, 2019. Judging from some emails, it was probably purchased on September 27th, 2019. It was purchased from Filastruder. However, it has been in storage since March, when the pandemic hit. Do you think it got damaged while unused? That would suck, I really hoped it was a software issue.

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      @Phaedrux Here is the result after doing exactly what you asked:

      M552 S-1
      ok
      M552 S0
      ok
      WiFi module started
      Error: Failed to initialise WiFi module, code -10
      M997 S0:1
      Trying to connect at 230400 baud:  success
      Erasing 4096 bytes...
      Erasing 212992 bytes...
      Uploading file...
      5% complete
      10% complete
      15% complete
      20% complete
      25% complete
      30% complete
      35% complete
      40% complete
      45% complete
      50% complete
      55% complete
      60% complete
      65% complete
      70% complete
      75% complete
      80% complete
      85% complete
      90% complete
      95% complete
      Upload successful
      M552 S0
      ok
      WiFi module started
      Error: Failed to initialise WiFi module, code -10
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
      Board ID: 08DGM-917NK-F2MS4-7JTDL-3S86K-TWTJF
      Used output buffers: 1 of 24 (1 max)
      === RTOS ===
      Static ram: 25712
      Dynamic ram: 93552 of which 0 recycled
      Exception stack ram used: 256
      Never used ram: 11552
      Tasks: NETWORK(ready,1408) HEAT(blocked,1256) MAIN(running,3816) IDLE(ready,160)
      Owned mutexes:
      === Platform ===
      Last reset 00:00:25 ago, cause: power up
      Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11488 bytes (slot 1)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
      Error status: 0
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 0.0ms, max retries 0
      MCU temperature: min 101.3, current 110.0, max 110.2
      Supply voltage: min 35.9, current 35.9, max 35.9, under voltage events: 0, over voltage events: 0, power good: no
      Driver 0: ok, SG min/max not available
      Driver 1: ok, SG min/max not available
      Driver 2: ok, SG min/max not available
      Driver 3: ok, SG min/max not available
      Driver 4: ok, SG min/max not available
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 38785090
      Slowest loop: 99.45ms; fastest: 0.05ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Move ===
      Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === DDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = 3 -1
      === GCodes ===
      Segments left: 0
      Stack records: 1 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 ready with "M122" 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 ===
      Slowest loop: 1.03ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 0 of 8
      - WiFi -
      Network state is disabled
      WiFi module is disabled
      Failed messages: pending 0, notready 0, noresp 0
      Socket states: 0 0 0 0 0 0 0 0
      ok
      
      
      posted in General Discussion
      JairoRBundefined
      JairoRB
    • RE: Error: Failed to initialise WiFi module, code -10 on 2.05

      Hello again @bearer @Phaedrux . I don't have access today to the 3D printer, I will try your recommendations tomorrow morning but I just wanted to maybe help clarify something.

      Wifi worked perfectly until yesterday, where mid-homing it just disconnected. Every time I send M552 S0 or S1, it gives the error Error: Failed to initialize WiFi module, code -10.

      Since I saw there were some updates to the firmware, I tried installing them to see if that fixed it. However, the issue persisted.

      I had the problem before I updated, so I don't think the update was the issue. However, I don't know enough so I will try reinstalling it and check again. Thanks!

      posted in General Discussion
      JairoRBundefined
      JairoRB
    • Error: Failed to initialise WiFi module, code -10 on 2.05

      Hello.

      After a few months (since march due to covid), I am back at my university working on a 3d printer with duet2 wifi. After I turned the board on, it all went fine, but after about 2 minutes it disconnected. No matter how many times I have reset the board, it still won't connect. The Wifi module light flashes once very briefly. When I try M552 S0, it throws the error shown on the title. I tried updating from 2.02 to 2.05, and everything went correctly but I still get the same error. What does error -10 mean? I will revert to my previous install, but I still don't know what happened.

      Thank you.

      posted in General Discussion wifi duet 2 wifi error wifi module duet 2 wifi
      JairoRBundefined
      JairoRB
    • Electrical failure caused issues on heater 2 channel

      Hello.

      I am using the Duet 2 Wifi with 2 DyzeEND-X and DyzeExtruders which are working just fine. I needed to get 12v from the board, so I connected a LM2596 based step down buck converter to get 12V. However, while I was tuning the potentiometer to get the desired 12 volts, something shorted (maybe?).

      There were some sounds that sounded like shorts, but no sparks or anything similar. I instantly turned everything off, and did a visual inspection. Nothing looked burnt at all, nothing was abnormally hot. Disconnected the buck converter, turned everything back on and everything was working perfectly from the dashboard, except for the heater 2 temperature readings. It is stuck reading about 1100-1400°C while heater 1 reads about 25°C, ambient temperature. I disconnected the thermistor and switched ports, and yet again it was heater 2 reading 1400°C. The thermistors themselves are not the issue, I think, so I believe something did burn.

      I am not sure tho, how does everything else work except the temperature readings from heater 2? I would've thought that many more things would be destroyed before it got to the thermistor channel.

      This is the config.g:

      ; Configuration file for Duet WiFi (firmware version 2.03)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2.1.3 on Thu Nov 28 2019 14:12:19 GMT-0600 (Central Standard Time)
      
      ; General preferences
      G90                                             ; send absolute coordinates...
      M83                                             ; ...but relative extruder moves
      M550 P"CubeProEIE"                              ; set printer name
      
      ; Network
      M551 P"delta"                                   ; set password
      M552 S1                                         ; enable network
      M586 P0 S1                                      ; enable HTTP
      M586 P1 S0                                      ; disable FTP
      M586 P2 S0                                      ; disable Telnet
      
      ; Drives
      M569 P0 S1                                      ; physical drive 0 goes forwards
      M569 P1 S1                                      ; physical drive 1 goes forwards
      M569 P2 S1                                      ; physical drive 2 goes forwards
      M569 P3 S1                                      ; physical drive 3 goes forwards
      M569 P4 S1                                      ; physical drive 4 goes forwards
      M584 X0 Y1 Z2 E3:4                              ; set drive mapping
      M350 X16 Y16 Z16 E16:16 I0                      ; configure microstepping without interpolation
      M92 X87.90 Y87.90 Z1066.60 E420.00:420.00       ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00:120.00      ; set maximum instantaneous speed changes (mm/min)
      M203 X15000.00 Y15000.00 Z1200.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z250.00 E250.00:250.00      ; set accelerations (mm/s^2)
      M906 X1500 Y1500 Z800 E800:800 I30              ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                         ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                                ; set axis minima
      M208 X200 Y270 Z190 S0                          ; set axis maxima
      
      ; Endstops
      M574 X1 Y1 Z1 S0                                ; set active low and disabled endstops
      
      ; Z-Probe
      M558 P0 H5 F120 T6000                           ; disable Z probe but set dive height, probe speed and travel speed
      M557 X15:200 Y15:195 S20                        ; define mesh grid
      
      ; Heaters
      M140 H-1                                        ; disable heated bed
      M305 P1 T4606017 B5848 C5.548428e-8 R4700       ; set thermistor + ADC parameters for heater 1
      M307 H1 A580.4 C256.6 D6.4 S0.50
      M143 H1 S490                                    ; set temperature limit for heater 1 to 490C
      M570 H1 P4 T25 					; Allow 25°C variation from setpoint  
      M305 P2 T4606017 B5848 C5.548428e-8 R4700       ; set thermistor + ADC parameters for heater 2
      M307 H1 A580.4 C256.6 D6.4 S0.50
      M143 H2 S490                                    ; set temperature limit for heater 2 to 490C
      M570 H2 P4 T25 					; Allow 25°C variation from setpoint  
      
      ; Heated chamber
      M141 H3 ; Assign chamber heater to heater 0
      M143 H3 S100 ; Set temperature limit for heater 0 to 120C
      M307 H3 A50 D60 B1 ; use bang-bang control for the chamber heater with 60 seconds dead time
      M305 P3 T100000 B4400 C9.486166e-8 R4700 ; Set thermistor + ADC parameters for chamber
      
      ; Fans
      
      ; Tools
      M563 P0 S"Extrusor 1" 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
      M563 P1 S"Extrusor 2" D1 H2 F0                  ; define tool 1
      G10 P1 X0 Y0 Z0                                 ; set tool 1 axis offsets
      G10 P1 R0 S0                                    ; set initial tool 1 active and standby temperatures to 0C
      
      ; Custom settings are not defined
      

      And here are the best pictures I could the of the board.

      20191204_160737.jpg
      20191204_160807.jpg

      There's a bit of gunk from adhesive / hand grease on the bottom side, that's not burn marks or anything like that.

      Any ideas? Thank you

      posted in Duet Hardware and wiring thermistor power management measurement
      JairoRBundefined
      JairoRB