Input Shaper Unsupported Error 3.4b7 - User Error Probability

[Notepad]

Hi all,

Quick question as I'm excited to try input shaping. I just upgraded from 3.3 to 3.4b7.
Its probably just me doing something wrong during the upgrade, so any help would be much appreciated.

Electronics firmware Duet2 wifi 3.3
DWC 3.4.0b7

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SD-6J9D4-3SJ6J-TBQRK
Used output buffers: 3 of 24 (11 max)
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address e8:db:84:f7:29:8d
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25376
WiFi IP address 192.168.1.123
WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

Just to confirm my upgrade procedure is to download Duet2CombinedFirmware.bin, and DuetWebControl-SD.Zip. upload the combined firmware, then upload the zip, and let the machine do its magic.

I'm excited to see the differences by using input shaping, so any help would be much appreciated.

[dc42]

@notepad you have probably enabled daa input shapingjn your M593 command. That sort is no longer supported because all the supported types are more effective.

[Notepad]

@dc42
Wow that was a fast response.

Thats what I thought at first as well. I changed the config.g to -> M593 P"ZVD" F45 ; input shaping
When I reset and then type into the console, this is what happens:

not sure if the firmware version is also supposed to say 3.4.0b7

hope this helps!

[Phaedrux]

@notepad said in Input Shaper Unsupported Error 3.4b7 - User Error Probability:

not sure if the firmware version is also supposed to say 3.4.0b7

yes it is. You've got an updated web control, but not the main firmware.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0beta7

See her for the updated firmware files.

[Notepad]

@phaedrux what's interesting, is when I upload a "duet2CombinedFirware.bin" to the DWC and click install, the PanelDue I have plugged in says "could not find file 0;/firmware/Duet2CombinedFirmware.bin" before the system resets and the popup disappears.

[Phaedrux]

I think you've got yourself into a corner where DWC has been updated and assumes the firmwares should be in the firmware folder, but your firmware has not.

At this point I suggest uploading the full zip file for 3.3 and see if that can get you back to a stable starting point for updating to the 3.4 betas.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

Also, it just occurred to me that you may be uploading the bin file to the system tab and not to the firmware tab. It may not be obvious, but when you're in the system tab, you can actually switch it to display the firmware folder by clicking on <system> above the file listing. Maybe try uploading directly there first.

[Notepad]

@phaedrux Humm, interesting. I uploaded the .zip to revert to 3.3, and it did the update fine, but on the panelDue after all the popups of its % complete, it quickly showed a "could not find file" for the firmware before resetting. DWC shows everything is normal now though, and fully rolled back to 3.3

Ive recorded the process here and the weird popup https://youtu.be/VHhirrkjG34

I also tried to replace the combined firmware in the zip with the 3.4.0b7 to fool it into updating but again, same error message.

[Notepad]

@phaedrux @dc42 Found a solution but it may indicate a bug.
I tried this process on 3 different machines. 2 with unofficial duet2wifi's and one with, and all were experiencing the same issue. the problem persisted even if plugged via USB, all said they couldn't find the file path needed.

So out of frustration, I whipped out a fresh official board that came preloaded with 3.1.1(the others were older and got retroactively updated to 3xx) Set it up, and when I got to the point to update to 3.4x I got an error saying that the firmware file directory doesn't exist (on this new board) - easy enough to add the directory by creating an empty folder, and itll populate the parent folder with the correct name. Then delete the empty folder and upload the combined firmware and the IAP file.
And low and behold it worked!

At least I now have 1 board with 3.47b updated, so removing the SD card and swapping them out with the problem boards, I was able to push the firmware update to the other machines.

What I noticed during this process, is the official SD cards, I actually replaced with 32GB patriot (class 10, U1) sd cards, while the fresh SD card was a 8GB SanDisk(Class 4). Additionally, the SanDisk had an extra folder for 'System Volume Information' while the larger Patriot card didn't.

[Phaedrux]

Yes I have seen that once before when updating myself. I'm not exactly sure what the conditions are to trigger it, but as you found putting the file it thinks is missing in the right place seems to get it going again.