Duet Wifi Hangs up after booting about 1 out of 5 times
-
I thought I was missing something just seeing it so short. Thanks for the advise. Here's the report on v3
Attempting connection at \\.\COM5... Testing plaintext communication protocol... READ: ok Connected to machine! SENT: T0 READ: ok SENT: M105 READ: ok T:2000.0 /120.0 T0:2000.0 /120.0 B:25.5 /0.0 READ: Error: Temperature reading fault on heater 1: unknown sensor SENT: m122 READ: === Diagnostics === READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later READ: Board ID: 08DJM-9178L-L2MSD-6J9DL-3SD6T-KVDYP READ: Used output buffers: 1 of 24 (6 max) READ: === RTOS === READ: Static ram: 30516 READ: Dynamic ram: 91592 of which 28 recycled READ: Exception stack ram used: 256 READ: Never used ram: 8680 READ: Tasks: NETWORK(ready,1676) HEAT(blocked,920) MAIN(running,4124) IDLE(ready,156) READ: Owned mutexes: READ: === Platform === READ: Last reset 00:00:13 ago, cause: power up READ: Last software reset at 2020-02-07 17:53, reason: User, spinning module GCodes, available RAM 8180 bytes (slot 2) READ: Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d READ: Error status: 0 READ: Free file entries: 10 READ: SD card 0 detected, interface speed: 20.0MBytes/sec READ: SD card longest block write time: 0.0ms, max retries 0 READ: MCU temperature: min 30.7, current 34.0, max 34.1 READ: Supply voltage: min 1.2, current 1.6, max 1.6, under voltage events: 0, over voltage events: 0, power good: no READ: Driver 0: ok, SG min/max not available READ: Driver 1: ok, SG min/max not available READ: Driver 2: ok, SG min/max not available READ: Driver 3: ok, SG min/max not available READ: Driver 4: ok, SG min/max not available READ: Date/time: 1970-01-01 00:00:00 READ: Cache data hit count 17245507 READ: Slowest loop: 1.67ms; fastest: 0.07ms READ: I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 READ: === Move === READ: Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms READ: Bed compensation in use: none, comp offset 0.000 READ: === MainDDARing === READ: Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 READ: === AuxDDARing === READ: Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 READ: === Heat === READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 READ: === GCodes === READ: Segments left: 0 READ: Stack records: 1 allocated, 0 in use READ: Movement lock held by null READ: http is idle in state(s) 0 READ: telnet is idle in state(s) 0 READ: file is idle in state(s) 0 READ: serial is ready with "m122" in state(s) 0 READ: aux is idle in state(s) 0 READ: daemon is idle in state(s) 0 READ: queue is idle in state(s) 0 READ: autopause is idle in state(s) 0 READ: Code queue is empty. READ: === Network === READ: Slowest loop: 1.26ms; fastest: 0.00ms READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) READ: HTTP sessions: 0 of 8 READ: - WiFi - READ: Network state is changing mode READ: WiFi module is trying to connect READ: Failed messages: pending 0, notready 0, noresp 0 READ: WiFi firmware version 1.23 READ: WiFi MAC address bc:dd:c2:57:ad:41 READ: WiFi Vcc 3.47, reset reason Turned on by main processor READ: WiFi flash size 4194304, free heap 28104 READ: Socket states: 0 0 0 0 0 0 0 0 READ: ok SENT: M105 READ: ok T:2000.0 /0.0 T0:2000.0 /0.0 B:25.5 /0.0 SENT: M105 READ: ok T:2000.0 /0.0 T0:2000.0 /0.0 B:25.5 /0.0 -
Flashed it to v2.05 with the same issues. Here's the report when on v2.05.
READ: === Diagnostics === READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later READ: Board ID: 08DJM-9178L-L2MSD-6J9DL-3SD6T-KVDYP READ: Used output buffers: 1 of 24 (3 max) READ: === RTOS === READ: Static ram: 25712 READ: Dynamic ram: 93116 of which 0 recycled READ: Exception stack ram used: 264 READ: Never used ram: 11980 READ: Tasks: NETWORK(ready,1664) HEAT(blocked,1324) MAIN(running,3824) IDLE(ready,160) READ: Owned mutexes: READ: === Platform === READ: Last reset 00:00:14 ago, cause: power up READ: Last software reset at 2020-02-07 18:14, reason: User, spinning module GCodes, available RAM 11716 bytes (slot 3) READ: Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d READ: Error status: 0 READ: Free file entries: 10 READ: SD card 0 detected, interface speed: 20.0MBytes/sec READ: SD card longest block write time: 0.0ms, max retries 0 READ: MCU temperature: min 33.5, current 34.2, max 34.2 READ: Supply voltage: min 1.2, current 1.2, max 1.6, under voltage events: 0, over voltage events: 0, power good: no READ: Driver 0: ok, SG min/max not available READ: Driver 1: ok, SG min/max not available READ: Driver 2: ok, SG min/max not available READ: Driver 3: ok, SG min/max not available READ: Driver 4: ok, SG min/max not available READ: Date/time: 1970-01-01 00:00:00 READ: Cache data hit count 55012547 READ: Slowest loop: 3.77ms; fastest: 0.05ms READ: I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 READ: === Move === READ: Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms READ: Bed compensation in use: none, comp offset 0.000 READ: === DDARing === READ: Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 READ: === Heat === READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 READ: Heater 1 is on, I-accum = 0.0 READ: === GCodes === READ: Segments left: 0 READ: Stack records: 1 allocated, 0 in use READ: Movement lock held by null READ: http is idle in state(s) 0 READ: telnet is idle in state(s) 0 READ: file is idle in state(s) 0 READ: serial is ready with "m122" in state(s) 0 READ: aux is idle in state(s) 0 READ: daemon is idle in state(s) 0 READ: queue is idle in state(s) 0 READ: autopause is idle in state(s) 0 READ: Code queue is empty. READ: === Network === READ: Slowest loop: 1.26ms; fastest: 0.00ms READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) READ: HTTP sessions: 0 of 8 READ: - WiFi - READ: Network state is changing mode READ: WiFi module is trying to connect READ: Failed messages: pending 0, notready 0, noresp 0 READ: WiFi firmware version 1.23 READ: WiFi MAC address bc:dd:c2:57:ad:41 READ: WiFi Vcc 3.47, reset reason Turned on by main processor READ: WiFi flash size 4194304, free heap 28176 READ: Socket states: 0 0 0 0 0 0 0 0 READ: ok READ: aux: M408 S0 R4 SENT: M105 READ: serial: M105 READ: ok T:33.0 /0.0 T0:33.0 /0.0 B:27.1 /0.0 READ: aux: M408 S0 R4 READ: aux: M408 S0 R4 SENT: M105 READ: serial: M105 READ: ok T:32.9 /0.0 T0:32.9 /0.0 B:27.1 /0.0 READ: aux: M408 S0 R4 READ: aux: M408 S0 R4 SENT: M105 READ: serial: M105 READ: ok T:32.9 /0.0 T0:32.9 /0.0 B:27.0 /0.0 READ: aux: M408 S0 R4 READ: WiFi module is connected to access point BBB1, IP address 192.168.2.135 READ: aux: M408 S1 SENT: M105 READ: serial: M105 READ: ok T:32.8 /0.0 T0:32.8 /0.0 B:27.0 /0.0 Disconnected. -
My config.g on v3, e0temp pin stopped working. Temperature reads 2000. I flashed v2.05 back and e0temp works.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Feb 07 2020 13:37:35 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"NogMM3" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable 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 S0 ; physical drive 3 goes backwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X256 Y256 Z256 E256 I0 ; configure microstepping without interpolation M92 X1280.00 Y1280.00 Z6800.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.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 X800 Y800 Z800 E800 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 X230 Y260 Z200 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high 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+zprobe.mod" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X-32 Y-26 Z3.3 ; set Z probe trigger value, offset and trigger height M557 X15:230 Y15:260 S15 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"e0temp" Y"pt1000" R4700 ; configure sensor 1 as PT1000 on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S325 ; set temperature limit for heater 1 to 325C 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 S0 H-1 ; set fan 0 value. Thermostatic control is turned off 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 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 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 -
my Config.g on v2.05 where e0temp works for my extruder. Hopefully some simple fix to get v3 working.
; Configuration file for Duet WiFi (firmware version 2.00) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Jan 26 2020 07:53:26 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"MendelMax3Nog" ; set printer name m111 p3 s1 ; Network 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 P4 S1 ; physical drive 4 goes forwards M584 X0 Y1 Z2 E4 ; set drive mapping M350 X64 Y64 Z64 E64 I0 ; configure microstepping without interpolation M92 X320.00 Y320.00 Z1600.00 E1636 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.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 X800 Y800 Z800 E800 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 X230 Y260 Z220 S0 ; set axis maxima ; Endstops M574 X1 Y2 S1 ; set active high endstops M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M307 H3 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch M558 P9 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-33 Y-26 Z3.4 ; set Z probe trigger value, offset and trigger height M557 X15:270 Y15:260 S15 ; defin0 mesh grid ; Heaters M305 P0 T100000 B4800 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S325 ; set temperature limit for heater 1 to 325C ; Fans M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Tools M563 P0 S"Volcano 0.8" 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 -
here's another m122 on v3
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later Board ID: 08DJM-9178L-L2MSD-6J9DL-3SD6T-KVDYP Used output buffers: 3 of 24 (9 max) === RTOS === Static ram: 30516 Dynamic ram: 91832 of which 0 recycled Exception stack ram used: 496 Never used ram: 8228 Tasks: NETWORK(ready,640) HEAT(blocked,816) MAIN(running,4100) IDLE(ready,156) Owned mutexes: === Platform === Last reset 00:03:34 ago, cause: power up Last software reset time unknown, reason: User, spinning module GCodes, available RAM 8512 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 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: 20.7ms, max retries 0 MCU temperature: min 31.9, current 33.5, max 33.9 Supply voltage: min 23.3, current 24.8, max 25.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 58/138 Driver 1: standstill, SG min/max 0/237 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-02-08 12:48:53 Cache data hit count 567632536 Slowest loop: 37.47ms; fastest: 0.09ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 274(0), FreeDm: 169, MinFreeDm: 163, MaxWait: 10023ms Bed compensation in use: mesh, comp offset 0.020 === MainDDARing === Scheduled moves: 25, completed moves: 25, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.5 === 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 === Slowest loop: 73.70ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) 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.23 WiFi MAC address bc:dd:c2:57:ad:41 WiFi Vcc 3.47, reset reason Turned on by main processor WiFi flash size 4194304, free heap 21656 WiFi IP address 192.168.2.135 WiFi signal strength -57dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 -
@gta18 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
Hopefully some simple fix to get v3 working.
Quite a lot of changes to config are needed when changing from RRF2 to RRF3. If your machine has no unusual features, It is simplest to use the online configurator to generate new files. Otherwise, see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files.
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 -
So I have got the v3 running successfully but still suffering from the random bootup hanging up as before in any version. Is there anything wrong with my config?
Everything works now except random bootup issues.
Were u able to see any problems with the m122 report I posted?
Thanks@dc42 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
@gta18 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
Hopefully some simple fix to get v3 working.
Quite a lot of changes to config are needed when changing from RRF2 to RRF3. If your machine has no unusual features, It is simplest to use the online configurator to generate new files. Otherwise, see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files.
-
@gta18 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
except random bootup issues.
I would check things like the power supply and the SD card. As in, perhaps you have flaky PSU, or the SD card is dying.
-
@Phaedrux I have used 3 sd cards and all have failures.
Ill check power supply make sure my input voltage is stable at 24v during startup.
-
I checked power supply during bootup and its rock solid at 24.13 to 24.15v all the way according to my Fluke 789.
Still experiencing bootup hang ups.
-
@gta18 After reading through this thread, it seems likely this is a hardware issue. To confirm, the main issue is now that the board fails to boot reliably every time? The problem of external comms stopping has been solved with firmware updates? Also, how is the board mounted? Is there any possibility of short circuiting the board to it's mounting location (metal enclosure/loose wiring)? Is the board clean, ie no metal filings that could cause shorts on the board (I'd give it a vacuum clean with a soft brush to make sure)? I couldn't see any obvious problems in the M122 reports you posted.
Assuming the above is all fine, I'd guess there is a floating (ie unsoldered or poorly soldered) pin or faulty component somewhere on the board, and could be almost anything connected to the processor. Can you post clear pictures of top and bottom of the board, and particular around this area?
Did any of the M111 reports happen during a freeze? Actually, I'd set
M111 S1to capture all debug info (P3 is just the webserver), though don't leave this on all the time as it can affect printing because of the volume of data sent to USB. Connect USB, and connect to the Duet as quickly as possible after power up, to see if you can catch it when it hangs. This may be able to determine what's causing the hang, and indicate where to look on the board, eg gets stuck waiting for SD card, or initialising Wifi module.Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts Ill check/do what u suggested when I get home tonight.
This is the 2nd board from amazon and did the exact same hanging up.
My board right now just sits on top of an MDF board with nothing below it.
One sign that I see on the paneldue when it is about to hang is that the wifi connection pop up does not show up.
100% of the time I'm able to hit home and the machine finishes the homing though, but one indication that it won't respond to any more commands is that after the homing procedure it does not update where the nozzle final location is (x45 y25,z7.8) for me.
But when I get a successful bootup, I'm able to print for 10hours without any snag and print again and again, just don't reboot it.
It seems like to me, that some part of the external comms of the board quits working or doesn't initialize properly, both wifi and serial.
-
To eliminate issues with the config, try an SD card with a very simple config.g on it, for example M552 S1 to turn on the network and nothing else. Then see whether that boots up reliably. If it doesn't, try without even the M552 S1 and see whether you can connect via USB after each reboot.
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 -
@gta18 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
This is the 2nd board from amazon and did the exact same hanging up.
So they are clone boards?
-
not sure if they're clones. I just needed to get it same day when I bought it.
-
@dc42 I tried the M552 S1 only on the config, I got successful boot 10 out of 10.
Should I just add the config line by line? Or is there an option to step it out?
Thanks!
-
@gta18 said in Duet Wifi Hangs up after booting about 1 out of 5 times:
Should I just add the config line by line? Or is there an option to step it out?
There's no option to step through it. You'd either have to add one line at a time and try booting, or you could connect via USB and send line by line that way. Or you could rename the config.g something else so that it isn't loaded automatically, and then when it's booted up you could send M98 Pconfigcopy.g from USB and see if you get any error messages.
Duet doesn't sell via amazon, so it's definitely a clone.
-
This is the 2nd board from amazon and did the exact same hanging up.
Duet doesn't sell via amazon, so it's definitely a clone.
That begs the question of when asked to confirm the power supply being stable and answering "its rock solid at 24.13 to 24.15v" how does the 3.3v line look? And if the problems started after adding BLTouch does it work without the BLTouch?
And its a moot point to measure the 3.3v line with a multi-meter to reveal any power issues, it would take a oscilloscope to be certain in any case. Removing the BLTouch if not already done might be a better place to start if lacking a scope.
-
@bearer Ill check the 3.3v as well, i have the scope but it doesn't record.
my fluke 789 has the MIN-Max function that can hopefully capture if there is a blip in the 3.3v stage.
So after adding back chunks at a time the config.g and rebooting each time, I probably have about 12 to 15 reboots now without a hitch.
Only difference with my config.g is that I created the file within the web gui.
I will still check the 3.3v tonight when I get back.
Thanks!
-
MIN-MAX won't help as you want to view the part that goes from 0v to 3.3v and possibly back down below some value causing a brownout. Fiddle with the scope trigger settings just below 3.3v until it doesn't trigger in normal use and reduce it a little more, then try starting up to see if it hangs and something triggers the scope.
If unsuccesfull you can always try to see if the BLtouch makes a difference.
