WiFi issues with 3.5.4

fcwilt

Thanks. Will do that.

Frederick

fcwilt

Thanks for the feedback.

I did not realize the size of the object model could affect WiFi.

Not knowing that I have made extensive used of the object model to create data driven code which allows the code to be used on any printer by having the values that are unique to the printer in the object model, rather than in the code itself.

I would not like to have to abandon that approach.

And I am using both FTP and Telnet so disabling them would be a bummer.

I will make the settings change and update the firmware.

Frederick

droftarts

@fcwilt I don't know exactly what data is requested from the OM for DWC and PanelDue, I think only the changing data, so I doubt it will be affected by your use of data driven code. It's more the increase in the number of sensors and configured drives, whose positions are frequently updated, ie whatever is displayed in DWC and PanelDue. @dc42 and @chrishamm will know better than me, though.

Ian

fcwilt

@droftarts

That does make sense. Why would any thing other than my code need to know that values in the object model.

Frederick

fcwilt

@droftarts

Hi,

I made all the changes I could:

Retry setting
PanelDue firmware
DuetWiFiServer firmware

The DWC reports the new version number. The PanelDue reports the new version number.

The WiFi still disconnects.

This is not good.

I suppose I could create a temp config.g file with a bare minimum of items just for testing.

Is is possible to revert firmware back to the previous versions?

Any other ideas?

Frederick

droftarts

@fcwilt Try it with the 3.6.0-beta.4. Or revert everything to 3.4.6.

Ian

fcwilt

@droftarts said in WiFi issues with 3.5.4:

@fcwilt Try it with the 3.6.0-beta.4. Or revert everything to 3.4.6.

Ian

I know how to upgrade.

How do I revert if that is what I have to do?

Thanks.

Frederick

jay_s_uk

@fcwilt same way

fcwilt

@jay_s_uk said in WiFi issues with 3.5.4:

@fcwilt same way

So I upload the old version files and it will ask if I want to install?

Frederick

droftarts

@fcwilt Reverting is easier, because you just upload the 3.4.6 release zip file. But 3.6 isn't too far away from being released, and it would be good to get your feedback if anything is broken for you before we release!

And people that have had WiFi issues have found the latest 3.6 beta (along with the other suggestions) fixes them.

Ian

fcwilt

@droftarts said in WiFi issues with 3.5.4:

@fcwilt Reverting is easier, because you just upload the 3.4.6 release zip file. But 3.6 isn't too far away from being released, and it would be good to get your feedback if anything is broken for you before we release!

Ian

Glad to help.

In the past I have avoided the betas and rcs as I did not realize it was possible to go back to an older version.

Knowing that I will give the beta a go.

Frederick

fcwilt

@droftarts

I went to the site to download the beta files but I don't see the ZIP file of all of the Duet 3 files I am used to using.

So I guess I need some of the files list.

Which ones?

Thanks.

Frederick

droftarts

@fcwilt assuming you’re running standalone, the ones whose name matches your board(s), so probably Duet3Firmware_Mini5plus.uf2, and DuetWebControl-SD.zip. Upload them as-is.

Ian

fcwilt

@droftarts

Thanks much.

I will give that a try and let you know.

Frederick

fcwilt

@droftarts

I gather the Duet WiFi Server at version 2.2.1 doesn't need to change?

Thanks.

Frederick

droftarts

@fcwilt no, as that’s the version that’s distributed with 3.6.0-beta.4

Ian

fcwilt

@droftarts

Well I updated to 3.6.0 BETA 4 and the WiFi connection failed even sooner than it did under 3.5.4.

The features of 3.6 sound interesting but not at the expense of no WiFi connection.

I was able to revert to 3.4.6 so that is good for now.

Thanks.

Frederick

droftarts

@fcwilt it would be good to work out why it disconnects for you. I’ll ask @dc42 what information he needs to troubleshoot, if you’re willing to give it another go. Otherwise you’re going to be stuck on 3.4, because as far as we’re concerned, the issue is fixed.

Ian