DuetWifi-error: filename too long
-
Thanks @dc42 -- would I be able to continue to use all my config.g, homex/y/z.g, etc. files?
-
@printHorst Not without modification. I would suggest baking up your current configuration, and then using the web configurator tool to generate a new config file set for 3.0 using your settings for testing. They may still need some manual tweaking as well for 3.0. If it doesn't work out you can reflash to the 2.x firmware and restore your config backup.
-
Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
Simon -
@Trideo said in DuetWifi-error: filename too long:
Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
SimonSorry there is a number of issues discussed in this thread. I suggest you create a new thread of your own and detail your issue specifically. Include all the relevant information like duet type, firmware and dwc versions, config files, etc.
-
Thanks for answering.
I'll do that.
Actually some of our clients (we are selling printers) are experimenting this issue. Communication isn't that smooth with them so, I'll do my best!Thanks
Simon -
@Phaedrux said in DuetWifi-error: filename too long:
@Trideo said in DuetWifi-error: filename too long:
Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
SimonSorry there is a number of issues discussed in this thread. I suggest you create a new thread of your own and detail your issue specifically. Include all the relevant information like duet type, firmware and dwc versions, config files, etc.
If you are referring to the "Filename too long" messages in response to OCSP-over-HTTP requests made by Kaspersky AV with very long pseudo-filenames, RRF 3.1 and later include code to recognise these requests and ignore them.
-
@dc42 Exactly! I'm referring to it "Filename too long" when connected in access Point Mode. We are currently preparing a "migration" to RRF 3.x but it wont be ready until several weeks.
I would like to give a quick solution to mi clients.
One of them answered me that he doesn't use Kaspersky AV....
Thanks for your support !
Simon -