3.3b2 sbc install help with Duet3_SDiap32_Mini5plus.bin
-
Forgot to mention I updated DWC to 3.3b2 unstable also by terminal to the sbc.
Thanks to @Phaedrux for the details on that. -
Hang in there brother ... they'll get you sorted soon ... not seen this issue yet myself sorry.
Hanging out on the bleeding edge gets messy at time ... Hold the Line!
-
@SputnikOC3d
I'm getting some horrid under extrusion so increased EM to 1.2 to overcome it in slicer but its far from nice, at least it sticks to the bed now and looks something right but just under 8mm under on a 100mm extrude short from entering the gcode in console. I was going to change my steps but they're set on the dx 3:1 aren't they. -
@SputnikOC3d said in 3.3b2 sbc install help with Duet3_SDiap32_Mini5plus.bin:
Hang in there brother ... they'll get you sorted soon ... not seen this issue yet myself sorry.
Hanging out on the bleeding edge gets messy at time ... Hold the Line!
Hoping it is this IAP file is the culprit...
-
and finally the test cube at 1.2EM
-
@carcamerarig said in 3.3b2 sbc install help with Duet3_SDiap32_Mini5plus.bin:
Hoping it is this IAP file is the culprit...
Not likely. The IAP file allows the firmware to be flashed. That's all. In Application Programming.
I think what's happened is that you've done a manual firmware update method when using the SBC. So it's expecting there to be the SBC programming file, which only comes from doing the update via the SBC update process (sudo apt update).
At this point I would suggest switching to standalone mode if you want to experiment with beta releases. If you're new to duet and SBCs in general, the combination can be rather confounding, especially when you throw beta releases into the mix.
-
@Phaedrux said in 3.3b2 sbc install help with Duet3_SDiap32_Mini5plus.bin:
@carcamerarig said in 3.3b2 sbc install help with Duet3_SDiap32_Mini5plus.bin:
Hoping it is this IAP file is the culprit...
Not likely. The IAP file allows the firmware to be flashed. That's all. In Application Programming.
I think what's happened is that you've done a manual firmware update method when using the SBC. So it's expecting there to be the SBC programming file, which only comes from doing the update via the SBC update process (sudo apt update).
At this point I would suggest switching to standalone mode if you want to experiment with beta releases. If you're new to duet and SBCs in general, the combination can be rather confounding, especially when you throw beta releases into the mix.
Fair point, before I concede is there any way to tell which IAP bin file is installed?
When I did the manual update wasn’t that for updating dwc only, following your info earlier? -
You can see which files are present in the system tab.
Though recently there is a new folder specifically for firmware files just to keep the system tab from getting too confusing with both config files and firmware files all together.
-
@Phaedrux
Perfect I’ll go check, would the manual update have updated that file at the same time or did I need to do it as a separate task? -
This ones out to bed, following tour guide installed and updated the complete release. Thanks @Phaedrux
-
@carcamerarig see the guide here about file locations, but remember this is in standalone mode: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_File_locations_on_the_Duet_SD_card
As you have Mini 5+, you can always update via USB using this method: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet
This guide has only recently been updated, so it may change. I’ve removed the ‘location’ part in “ You will get a message if it is missing, with the filename and location it expects” as it does not tell you where it expects the file to be, though I will suggest it!
Ian
