@Danal said in Duet 3 Standalone RRF3 Package?:
@Hornetrider said in Duet 3 Standalone RRF3 Package?:
@Danal
used this files right before my last post...
Still got the error and then tried it by renaming the IAP, and then something worked..kind of..
Yeah, depending on what release you are coming FROM, there may be some renaming involved.
There should be no need to do any renaming. But you should have both the old and new IAP files present. They have different names deliberately because they are not compatible.
In standalone mode, to upgrade from any published version of RRF3 for Duet 3 RRF prior to 3.0RC1, file Duet3iap_sd_MB6HC.bin must be present in /sys.
To upgrade or downgrade from any published version of RRF3 for Duet 3 RRF at or after 3.0RC1, file Duet3_SDiap_MB6HC.bin must be present in /sys.
If you have used M505 to put the system files in a subdirectory of /sys, when you upload the IAP or firmware files you make sure that you are viewing /sys in DWC, because firmware files (unlike config.g, homing files etc.) must always go in /sys regardless of the M505 setting.
The requirements for upgrading/downgrading via an attached RPi are similar except that the IAP files are Duet3iap_sbc_MB6HC.bin (when upgrading from older firmware) and Duet3_SBCiap_MB6HC.bin (when upgrading/downgrading from 3.0RC1 or later). These files are normally installed by apt-get-upgrade.