I have 3 sd cards that I have been using with identical contents and have been copying the config.g from online generator to the sd cards thru my laptop.

I'll try to copy the working sd card contents to the other 2 sd's and see if it still works.

Im happy and pleased to report back that I have not experienced a bad bootup for about 96 hour printing time and about more than 50 reboots manually.

Still not sure why creating the config.g file using the web interface made a difference.

@droftarts What I meant about homing is, if i push the home button right away after power up, it homes 100% of the time but during the failed bootup im talking about the home or any other functions does not work.

Homing always finishes if triggered early enough, either on success or failed boot. Thats why i mentioned that the external comms to paneldue and usb diaappers.

So it seems to me that it always successfully loads the limits and home configuration.

@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!

@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!

not sure if they're clones. I just needed to get it same day when I bought it.

@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.

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.

@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.

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.