mini 5+ first impression...

Chriss

Hi *,

I had a strange problem while I configured the wifi.

I used : https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang=en

So I connected to the board via usb/serial, I configured the wifi parameter with "M587 S"....." P"...." and I enabled networking with "M552 S1" and it worked. The board got a IP address and the DWC was reachable.
I copied some config from the configtool to the sd-card and rebooted the board. But the board was not reachable afterwards. There was no dhcp requests according to the dhcp log file.
So i connected to the board via serial again and I saw a "wifi disabled" at the end of the boot process. I was a bit confused because the config tool generated:

[...]
; Network
M552 P0.0.0.0 S1                                   ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet
[...]

So I replaced the "M552 P0.0.0.0 S1" with "M552 S1" and the board is connecting to the wifi since.

So who is wrong now? The configtool? I? Was that a race condition? (Yes I selected the mini in the config tool. )

Cheers, Chriss

Veti

@Chriss said in mini 5+ first impression...:

So who is wrong now? The configtool? I? Was that a race condition? (Yes I selected the mini in the config tool. )

yes the configtool is wrong. if you select duet 2 wifi in generates M552 S1.

@chrishamm

Chriss

I found a possible "typo" in the docu. The outputs for the heaters are labeled as "out 1" and "out 2". I guess that they are actually "out 0" and "out 1" aren't they?

Veti

out0 is the bed heater.

T3P3Tony

@Chriss no they are OUT1 and OUT2. OUT0 is the one nominally for the heated bed.

Edited, thanks @Veti !

Chriss

@T3P3Tony Ahhh... yes... I got the point. I my internal filter system ignored the terminals next to the power connectors. My bad...

Chriss

I updated the board to 3.2-RC2 via the DWC (standalone) , the docu "https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware" asked me to upload "Duet3Firmware_Mini5plus.uf2" and I got informed that "Duet3_SDiap_Mini5plus.bin" was missing. I downloaded "Duet3_SDiap32_Mini5plus.bin" and renamed it to "Duet3_SDiap_Mini5plus.bin" and uploaded it. The update was fine than. I think that some of the docu needs an update here.

Cheers, Chriss

Veti

with the new release you will also need the Duet3_SDiap32_Mini5plus.bin for the next firmware update

Phaedrux

@Chriss said in mini 5+ first impression...:

I downloaded "Duet3_SDiap32_Mini5plus.bin" and renamed it to "Duet3_SDiap_Mini5plus.bin" and uploaded it.

Don't rename files. The firmware is expecting a specific file and when you substitute another file it can cause problems.

You may need the Duet3_SDiap_Mini5plus.bin file from beta 3 since that's the last update. You'd need that file to go back to versions prior to RC1.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2beta3/Duet3_SDiap_Mini5plus.bin

Duet3_SDiap32_Mini5plus.bin will also be required for future releases.

dc42

As @Phaedrux says, never rename IAP files. We change the filename when there is a fundamental incompatibility between the new version and the previous one, so that whatever firmware you are using gets an IAP it can work with.

As it happens, the IAP for the Duet 3 Mini only didn't change significantly in this instance, which is why it worked. The IAPs for all other Duets did change in an incompatible way.

Chriss

@Phaedrux @dc42

I do not get the situation or you got me wrong. Let me explain the excercice a bit better.

The sys folder contained only ".g" files. Could be me when backuped the stock sys folder and copied mine over. I uploaded Duet3Firmware_Mini5plus.uf2, the DWC tried to do a firmware update and complained that "Duet3_SDiap_Mini5plus.bin" was missing. So my reflex was "cool download it than" but exactly this file is missing @ https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2RC2. But there is "Duet3_SDiap32_Mini5plus.bin" and the update worked after I renamed the file to " Duet3_SDiap_Mini5plus.bin" before I uploaded "Duet3Firmware_Mini5plus.uf2".

That may be wrong but I think that this is logical reflex, or do you expect that I should search that file in a other release tree? That makes no sense to me because I do not like mixed firmware files between versions.

So I would propose to have all needed file in every directory or a note on the docu page which explains that.

Cheers, Chriss

Chriss

@dc42

I found a other tiny problem with the docu: https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware#Section_Updating_firmware_with_attached_Single_Board_Computer

Updating firmware with attached 

Single Board Computer

Use 'sudo-apt-get update' and 'sudo-apt-get upgrade'.

NOTE THIS IS NOT YET TESTED

This definitely not yet tested.
I guess you mean:

sudo apt update
sudo apt upgrade

"apt" is the future, apt-get is still supported and will not so fast removed but "apt" is much faster and the future.

Cheers, Chriss

A Former User

@Chriss said in mini 5+ first impression...:

That may be wrong but I think that this is logical reflex, or do you expect that I should search that file in a other release tree? That makes no sense to me because I do not like mixed firmware files between versions.

the problem is you assume the missing IAP file was supposed to be part of 3.2RC2, and by renaming the 3.2RC2 file you've ensured you'll have the same problem at the next update

the IAP file that is needed at the time of an update is only related to the version that is currently running, not the version to be installed, so somewhere after 3.2 beta3 you didn't upload the Duet3_SDiap_Mini5plus.bin file along with the Duet3Firmware_Mini5plus.uf2 file.

so save yourself some headache and reupload Duet3_SDiap32_Mini5plus.bin with its correct name and read the https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md all the way from the currently running version to the version you want to update to to avoid further incidents.

Phaedrux

The IAP files are less of an issue when you're only updating from major version to major version since any required files will be present. In beta and release candidates only changed files are included, for better or worse.