Topics created by Macgyver

@Macgyver it's only ever returned one reply. However, you can view the state of the filament monitor in the Object Model Browser within DWC.

Update to this post

I replaced the SD card with a new 16GB card, Formatted and reinstalled all the setup files.

It did give me an error message of mismatched firmware versions although I could not find evidence of anything mismatched. I did reflash the entire package of 3.5.2 and everything now is working as it should.

I can now edit and save changes to the config.g file, As an extra did modify some of the macro files as well as they no longer dissapear.

I would mark this one as resolved.
Just as an additional information I checked the previous SD card in a windows PC, Checked it for errors and no errors were picked up. Still a weird problem but I am chaulking it upto a problem with the origional SD card.

HI @jay_s_uk , thanks for the reply

After installing just the Wifi update, Came up with the same scrolling error and then a message connected to the access point, IP address 255.255.255.255,

That was weird because that is a broadcast address. Anyway did the S0 and S1 again and it connected properly. Error is basically still happening.

I updated the DWC as a separate step to help anyone else troubleshoot,

First time I power cycled the printer, Came up perfectly, Connected properly and gave me the proper IP address.
Power cycled it again and back to the same error message.
However, If I just do nothing Eventually it does come online itself. Sometimes takes 2 mins to connect and give me the IP.

So I started thinking maybe there may be some other networks in the configuration that is toying with it. I ran the procedure listed in this Post
https://forum.duet3d.com/topic/9888/how-to-erase-remembered-networks/4

basically the M588 S"*"
I set up my network again from scratch with the M587 and now after 10 power cycles, It seems to be working ok.

If I was to guess what may be going on as you apply firmware versions it may be adding "default" or "beta" networks that it has to scan and see that they are not there before it will move on to the next one. That is strictly my guess but the version of the DWC definitely had the biggest effect.

For me, I just like to try and understand the source of the error but for anyone else troubleshooting this error take @jay_s_uk 's advice and ensure your firmware versions match.

HI @Phaedrux

Thanks for the info, that's why I wanted to do a sanity check first. Sooner ask now than blow it up.

you can mark this thread as solved, Hopefully, someone else can find it and make use of the information.

Thanks again for your help guys Truly appreciate it.

@macgyver Glad you got it all sorted

Hi Guys

Sorry, I missed the update, Yes all is working now. thanks again for your help.

Up to the last tests I was doing it was a coding issue, as it turns out somewhere along the line the BLtouch sensor went bad. I wrote a script to probe 10 times and report the divination. the number was never the same, or even close for that point. turned out the touch was bad.