Posts made by jcv1977

@b3njam1n Hey! just use the code snipet and paste your gcode inside it.

I am glad to report that now it's working. But just because i am a control freak i 've modified my bed so its better now and i am assuming that once i've done the compensation and save the height map the only thing that i need to do is just load that map at the beginning of the print.

Thanks guys

@Phaedrux no, it's behind the nozzle, maybe i wrongly put positive 6 when it is negative? That's why i am sure that every single coordinate can be reach i've saw myself the whole measurement and the probe can reach all of them fine.

@Veti

Config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)

; General preferences
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"Ender 3 Pro"                           ; set printer name

; Network
M552 S1                                       ; enable network
M586 P0 S1                                    ; enable HTTP
M586 P1 S0                                    ; disable FTP
M586 P2 S1                                   ; 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 S0                                    ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                              ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping without interpolation
;M350 E16 I1                                   ; configure microstepping with interpolation

M92 X80.00 Y80.00 Z397.44 E449.62              ; set steps per mm
M566 X900.00 Y900.00 Z24.00 E180.00           ; set maximum instantaneous speed changes (mm/min)
M203 X7000.00 Y7000.00 Z5000.00 E500.00      ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z150.00 E350.00         ; set accelerations (mm/s^2)
M906 X900 Y900 Z900 E900 I60                  ; set motor currents (mA) and motor idle factor in per cent
M84 S40                                       ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                              ; set axis minima
M208 X230 Y210 Z200 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
M950 H3 C"nil"                                 ; Disable heaters h3-h7 to free up pins
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" H6 F200 T2000           ; set Z probe type to bltouch and the dive height + speeds

M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0

;Bed Height adjustments

G31 P500 X-46 Y6 Z3.34   ; set Z probe trigger value, offset and trigger height
M557 X47:205 Y20:230 S20                      ; define mesh grid
;M557 X47:205 Y20:230 S32                      ; 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
M307 H0 R0.304 C437.7 D7.20 S1.00 V24.0


M140 H0                                       ; map heated bed to heater 0
M143 H0 S80                                   ; set temperature limit for heater 0 to 80C
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
;M307 H1 R2.305 C156.6 D6.40 S1.00 V24.0
M307 H1 R2.303 C154.7 D6.52 S1.00 V24.0
M143 H1 S250                                  ; set temperature limit for heater 1 to 250C



; Fans
M950 F0 C"fan0" Q500                          ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H T45                              ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500                          ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                             ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Hotend" 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
T0                                            ; select first tool
G28


;M558 P9 H5 F100 T2000
;M558 P9 C"^zprobe.in" H5 F100 T2000  ; BLTouch connected to Z probe IN pin
;M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 pin on expansion connector
...

;G31 X-46 Y6 Z3.02 
;M501

M208

1/31/2021, 11:22:02 AM	M208
Axis limits X0.0:230.0, Y0.0:210.0, Z0.0:200.0

G31

1/31/2021, 11:23:07 AM	G31
Z probe 0: current reading 0, threshold 500, trigger height 3.340, offsets X-46.0 Y6.0

@Veti But when i defined the grid i used the probe as point of reference thats why in reality all that coordinates are indeed reachable.

Well trying again to set the bltouch right. I did some modification to the bed, i 've replaced the springs for m3 spacers so the bed is really steady also there where a severe difference between the spacers been used in the bed gantry i don't know how did that machine pass the "quality test" but now the bed has little margin of error

BUT yep there is always that frightening word, the freaking compensation is not working when i run the bed compensation i get this on some mesh parts:

1/31/2021, 10:11:05 AM	Warning: Skipping grid point (47.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (67.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (87.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (107.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (127.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (147.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (167.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (187.0, 220.0) because Z probe cannot reach it
70 points probed, min error -0.034, max error 0.477, mean 0.251, deviation 0.152
Height map saved to file 0:/sys/heightmap.csv
1/31/2021, 10:11:04 AM	Warning: Skipping grid point (47.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (67.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (87.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (107.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (127.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (147.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (167.0, 220.0) because Z probe cannot reach it
Warning: Skipping grid point (187.0, 220.0) because Z probe cannot reach it
70 points probed, min error -0.034, max error 0.477, mean 0.251, deviation 0.152
Height map saved to file 0:/sys/heightmap.csv
1/31/2021, 10:10:45 AM	Warning: Skipping grid point (187.0, 180.0) because Z probe cannot reach it
Warning: Skipping grid point (187.0, 200.0) because Z probe cannot reach it
1/31/2021, 10:10:05 AM	Warning: Skipping grid point (187.0, 140.0) because Z probe cannot reach it
Warning: Skipping grid point (187.0, 160.0) because Z probe cannot reach it
1/31/2021, 10:09:26 AM	Warning: Skipping grid point (187.0, 100.0) because Z probe cannot reach it
Warning: Skipping grid point (187.0, 120.0) because Z probe cannot reach it

The thing is that all of that coordinates can indeed be reached by the prove i've seen all the measurement itself and i can tell you that non of that coordinates are unreachable. So there might be something else wrong.

this is my actual G31 part:

G31 P500 X-46 Y6 Z3.34   ; set Z probe trigger value, offset and trigger height

If a run a test print the print is ok but i don't want to try a really big print if i am not sure that the bltouch is working the way it should.

Any ideas?

@Phaedrux I 've been asking the same question for a couple of days now, today i will get a caliper and i will be able to measure it correctly.

Sometimes it's the little things that get overlooked

Amen to that!!!!

I'll make a video of it.

I 've had it with this, it keeps happening the same all over again. I guess there is something wrong with the bltouch. I have done a manual level of the freaking bed that i thing it would be perfect. Then i follow the guide again and the result is that the homing of the z axis is in the middle of the bed but the damn nozzle is really way too up to even try an auto level .

@Phaedrux said in Ender 3 Pro BL Touch Trigger Height:

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

I've already done it but then when i home z it is way upper than the picture. The best way to describe it it would be imagine the same picture but with the bltouch deployed so the nozzle would be even far from the bed.

@Phaedrux Seems ok but i don't think its 8mm between the bltouch/nozzle and the bed.

Hmmm i think i am going to rely it but this is what i got


@Veti I am using Reprap 3 and i don’t see any function to show a geaphic of the heightmap do you know where it is?

I just tried a print test but i have to cancel it because the nozzle is still scratching the bed. Also i 've got a doubt ( one more lol) should i pre level the bed manually before even do the auto level? Does it helps?

@Phaedrux Thanks Guys for the reply! I got it like that, apparently 8mm (i don't have my caliper with me, but it's close. I would swear that it is some parameter issue but i i am not that gcode savy myself. I am probing at the center with printing temperature. Every time i tried to get one this is what it says:

G29
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
88 points probed, min error 0.240, max error 1.130, mean 0.766, deviation 0.229
Height map saved to file 0:/sys/heightmap.csv

and this is the results dumped on height map.csv:

RepRapFirmware height map file v2 generated at 2021-01-19 17:27, min error 0.240, max error 1.130, mean 0.766, deviation 0.229
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
47.00,205.00,20.00,230.00,-1.00,20.00,20.00,8,11
  0.240,  0.303,  0.428,  0.543,  0.683,  0.800,  0.885,  0.960
  0.275,  0.352,  0.460,  0.590,  0.692,  0.793,  0.900,  0.945
  0.300,  0.380,  0.502,  0.618,  0.717,  0.832,  0.915,  0.975
  0.365,  0.440,  0.562,  0.675,  0.780,  0.908,  0.977,  1.038
  0.415,  0.517,  0.615,  0.717,  0.808,  0.915,  1.008,  1.055
  0.488,  0.570,  0.655,  0.733,  0.855,  0.952,  1.062,  1.087
  0.500,  0.582,  0.685,  0.772,  0.827,  0.940,  1.020,  1.087
  0.545,  0.605,  0.697,  0.827,  0.873,  0.955,  1.050,  1.105
  0.600,  0.660,  0.728,  0.825,  0.875,  0.960,  1.043,  1.090
  0.610,  0.695,  0.788,  0.858,  0.918,  0.977,  1.065,  1.092
  0.673,  0.750,  0.798,  0.900,  0.945,  1.013,  1.082,  1.130

Hi guys i am having issues installing my BLTouch correctly. I have followed the wiki tutorials:

This one

The thing is that the freaking blotch is triggered before the nozzle touch the bed, i 've tried re calibrating the z height several times but the result is always the same, when i try to run a Mesh compensation it start doing the process but in all the measure points the blotch is triggered but none of the times the nozzle touch the bed.

Printer: Ender 3 Pro V1
Bltouch Smart V3.1

Duet info:

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-01-05

Config Files:

config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)

; General preferences
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"Ender 3 Pro"                           ; 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 S0                                    ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                              ; set drive mapping
M350 E1 I0                                    ; configure microstepping without interpolation
M350 X16 Y16 Z16 I1                           ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00              ; set steps per mm
M566 X600.00 Y600.00 Z60.00 E300.00           ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z7200.00 E6000.00      ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z120.00 E5000.00         ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 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 X235 Y235 Z260 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
M558 P9 C"^zprobe.in" H2 F100 T2000           ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"exp.heater3"; create servo pin 0 for BLTouch
M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0
G31 P500 X-46 Y6 Z0.12                           ; set Z probe trigger value, offset and trigger height
M557 X47:205 Y20:230 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
M307 H0 R0.304 C437.7 D7.20 S1.00 V24.0


M140 H0                                       ; map heated bed to heater 0
M143 H0 S80                                   ; set temperature limit for heater 0 to 80C
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
;M307 H1 R2.305 C156.6 D6.40 S1.00 V24.0
M307 H1 R2.303 C154.7 D6.52 S1.00 V24.0
M143 H1 S250                                  ; set temperature limit for heater 1 to 250C

M307 H3 A-1 C-1 D-1

; Fans
M950 F0 C"fan0" Q500                          ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H T45                              ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500                          ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                             ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Hotend" 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
T0                                            ; select first tool



;M558 P9 H5 F100 T2000
;M558 P9 C"^zprobe.in" H5 F100 T2000  ; BLTouch connected to Z probe IN pin
;M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 pin on expansion connector
...

;G31 X-46 Y6 Z3.02 P25

Deployprobe.g

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
M280 P0 S10 ; deploy BLTouch

Retractprobe.g

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
M280 P0 S90; retract BLTouch

homeall.g

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-240 Y-240 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000       ; go back a few mm
G1 H1 X-240 Y-240 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X50 Y20 F6000        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91                    ; relative positioning
;G1 Z5 F100             ; lift Z relative to current position
;G90                    ; absolute positioning

homex.g

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-240 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-240 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

homey.g

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 Y-240 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000    ; go back a few mm
G1 H1 Y-240 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

home.g

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G90              ; absolute positioning
G1 X50 Y20 F6000 ; go to first probe point
G30              ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91             ; relative positioning
;G1 Z5 F100      ; lift Z relative to current position
;G90             ; absolute positioning

bed.g

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Tue Jan 12 2021 22:19:26 GMT-0500 (EST)
M561 ; clear any bed transform
G29  ; probe the bed and enable compensation

height map.scv

RepRapFirmware height map file v2 generated at 2021-01-19 17:27, min error 0.240, max error 1.130, mean 0.766, deviation 0.229
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
47.00,205.00,20.00,230.00,-1.00,20.00,20.00,8,11
  0.240,  0.303,  0.428,  0.543,  0.683,  0.800,  0.885,  0.960
  0.275,  0.352,  0.460,  0.590,  0.692,  0.793,  0.900,  0.945
  0.300,  0.380,  0.502,  0.618,  0.717,  0.832,  0.915,  0.975
  0.365,  0.440,  0.562,  0.675,  0.780,  0.908,  0.977,  1.038
  0.415,  0.517,  0.615,  0.717,  0.808,  0.915,  1.008,  1.055
  0.488,  0.570,  0.655,  0.733,  0.855,  0.952,  1.062,  1.087
  0.500,  0.582,  0.685,  0.772,  0.827,  0.940,  1.020,  1.087
  0.545,  0.605,  0.697,  0.827,  0.873,  0.955,  1.050,  1.105
  0.600,  0.660,  0.728,  0.825,  0.875,  0.960,  1.043,  1.090
  0.610,  0.695,  0.788,  0.858,  0.918,  0.977,  1.065,  1.092
  0.673,  0.750,  0.798,  0.900,  0.945,  1.013,  1.082,  1.130

When i try to run a bed compensation it just tells:

G29
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
88 points probed, min error 0.240, max error 1.130, mean 0.766, deviation 0.229
Height map saved to file 0:/sys/heightmap.csv

The wiring seems to be ok, the probe deploy, retract and trigger as it should but it seems to me that every time that the bl is triggered and i check the nozzle it is not touching the bed.

I've tried to re calibrate the z height and modified the G31 command but it is exactly the same result, it is like the height was never modified.

@dc42 I think i found it! Evidently there is a bug:

https://forum.duet3d.com/topic/15207/duet-wifi-wlan-vs-wpa2-connection-error/8

https://forum.duet3d.com/topic/14993/cannot-connect-duet-wifi-to-new-wifi-router

@bearer You aked me if its a vodafone and its not, but in one of the post it says its an Arris router and mine is Arris too. I gues this freaking router has something that is not compatible. Just for starters i can't turn off dhcp nor update the router's firmware wich is BS. So i guess by now i'll just use it on AP mode until y buy a proper UNIFI Gear.

@bearer said in I am erasing duet but which firmware can I use?:

@jcv1977 said in I am erasing duet but which firmware can I use?:

but the ip was still on the router pool.

arp on the computer won't affect the router, just where the computer will send and IP packet; i.e. trying to force the computer to direct the packets to the duets mac address for either address. bit if ping failed then moot point.

Great!

would probably need big cheese to evaluate the debug info (or maybe run wireshark if your wifi adapter can do promiscuous mode capture, but few on windows does)

We will wait for him!!!! Thanks Bearer!!!!

@jcv1977 I did run the arp command as admin, and the commands were accepted but the ip was still on the router pool.

This is debbugging result with dhcp i just cut a whole lot of Network scan failed :

Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
ok
ok
ok
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : null
WiFi: wifi evt: 1
WiFi: STA disconnect: 8
WiFi: wifi evt: 8
WiFi module is idle
ok
WiFi: mode : sta(b4:e6:2d:52:ff:37)
WiFi: add if0
WiFi: wifi evt: 8
WiFi: scandone
WiFi: ../src/SocketServer.cpp(353): found network DIRECT-0c-HP M29 LaserJet
WiFi: ../src/SocketServer.cpp(353): found network ATTevrXIVS
WiFi: ../src/SocketServer.cpp(353): found network ATTBCVg3dS
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR94
WiFi: ../src/SocketServer.cpp(353): found network MYWIFI
WiFi: ../src/SocketServer.cpp(353): found network Area 51
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR76
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR50
WiFi: ../src/SocketServer.cpp(353): found network DIRECT-C5-HP OfficeJet 3830
WiFi: ../src/SocketServer.cpp(353): found network Torresnunez
WiFi: ../src/SocketServer.cpp(353): found network VIZIOCastDisplay0071
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR64
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR21
WiFi: ../src/SocketServer.cpp(353): found network NETGEAR78
WiFi: ../src/SocketServer.cpp(353): found network belkin.fac
WiFi: ../src/SocketServer.cpp(353): found network belkin.fac.guests
WiFi: ../src/SocketServer.cpp(353): found network Internetmine
WiFi: ../src/SocketServer.cpp(353): found network ACCA31
WiFi: ../src/SocketServer.cpp(353): found network ARLO_VMB_1570254913
WiFi: ../src/SocketServer.cpp(353): found network ARRIS-FD86
WiFi: ../src/SocketServer.cpp(353): found network 8831B2
WiFi: ../src/SocketServer.cpp(353): found network Bchehade24
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 2
WiFi: cnt 
WiFi: 
WiFi: connected with MYWIFI, channel 6
WiFi: dhcp client start...
WiFi: wifi evt: 0
WiFi: pm open,type:2 0
WiFi reported error: Timed out while trying to connect to MYWIFI
WiFi module is idle
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : null
WiFi: Fatal exception 28(LoadProhibitedCause):
WiFi: epc1=0x4000df2f, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000033, depc=0x00000000
WiFi: 
WiFi: Exception (28):
WiFi: epc1=0x4000df2f epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000033 depc=0x00000000
WiFi: 
WiFi: ctx: sys 
WiFi: sp: 3ffffc90 end: 3fffffb0 offset: 01a0
WiFi: 
WiFi: >>>stack>>>
WiFi: 3ffffe30:  3ffeface 3fff4d4c 40223f10 40105dd8  
WiFi: 3ffffe40:  40216def 00000006 00000005 402298d9  
WiFi: 3ffffe50:  00000033 00000010 40217705 3ffee6bc  
WiFi: 3ffffe60:  3fff4d4c 00000000 3ffe9ff8 3fff516c  
WiFi: 3ffffe70:  3fff4d4c 4021762d 3ffee6bc 4020b004  
WiFi: 3ffffe80:  3ffe9ff8 00000002 00000022 00000000  
WiFi: 3ffffe90:  3fff4dce 3fff4ec4 00000000 00000000  
WiFi: 3ffffea0:  3ffe9ff8 3ffe9ff8 00000033 4021957b  
WiFi: 3ffffeb0:  3ffeedc0 40219174 4020b004 3ffeedc0  
WiFi: 3ffffec0:  40218cf0 402344e0 3ffee740 00000000  
WiFi: 3ffffed0:  00000001 00000001 00000000 00000000  
WiFi: 3ffffee0:  402191af 3ffeeeb8 3ffeeeb8 40106df4  
WiFi: 3ffffef0:  4021b11c 3ffeeeb8 ffff8000 00000001  
WiFi: 3fffff00:  3ffee740 4021b0e0 3ffee6bc 00000002  
WiFi: 3fffff10:  40219164 40219138 3ffee740 00000002  
WiFi: 3fffff20:  40219103 3ffee6bc 00000002 40106c5e  
WiFi: 3fffff30:  402196b4 3ffee6bc 3ffee838 4020b004  
WiFi: 3fffff40:  402190e1 3ffee838 00000003 3ffee838  
WiFi: 3fffff50:  40218e84 3ffeee78 3ffef5a0 f3ecd39c  
WiFi: 3fffff60:  60000600 0000010f 00000001 00000000  
WiFi: 3fffff70:  4022dfa9 3ffef5d4 3ffef5a0 f3ecd39c  
WiFi: 3fffff80:  4022dfee 3fffdab0 00000000 3fffdcb0  
WiFi: 3fffff90:  3ffef5b0 3fffdab0 00000000 00000005  
WiFi: 3fffffa0:  40000f49 40000f49 3fffdab0 40000f49  
WiFi: <<<stack<<<
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi: ⸮nP|!-1K5⸮К⸮⸮XK!⸮~)Q*!⸮⸮ "pkt⸮E,-⸮@⸮⸮P⸮1%(⸮yh=⸮nzA⸮ )i⸮⸮P1⸮N⸮⸮fP1⸮N⸮R⸮t⸮1Z⸮Q⸮
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi: epc2:0x00000000 epc3:0x00000000 excvaddr:0x00000033 depc:0x00000000
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi: mode : sta(b4:e6:2d:52:ff:37)
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi: add if0
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi: wifi evt: 8
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle
WiFi reported error: network scan failed
WiFi module is idle