Single Setup for Duet 3

Dougal1957

@T3P3Tony said in Single Setup for Duet 3:

@Dougal1957 they are shipping! Will know more by the end of tomorrow.

cheers for info

Doug

dc42

When you receive your Duet 3 main boards, please note the following (hopefully it will be moved to the wiki documentation soon):

There are some known issues with the RRF3 build that is programmed on them. In particular, bed levelling using independent leadscrews doesn't work, temperature readings may be noisy, and Z probes don't work. I expect to release a new firmware built later today that fixes these.
You can run the Duet 3 in standalone mode with an SD card, or with an attached RPi as we expect most users to do. The same firmware supports both configurations. On power up or reset, if the firmware detects that there is an SD card in the Duet and it is able to read the config.g file from it, then it runs in standalone mode and runs an on-board web server using the Ethernet port. If the firmware doesn't detect an SD card, or config.g isn't found, then it assumes that files will be served by the RPi.
We do not supply a SD card for running the Duet 3 in standalone mode. If you wish to run in standalone mode then you will need to supply your own SD card and populate it with files as you would for a Duet 2, taking account of the differences between RRF3 and RRF2.
The correct firmware filename for these Duet 3 main boards (revision 0.6) is Duet3Firmware_MB6HC.bin. For the version 0.5 beta boards that we have supplied to a few users, it is Duet3Firmware_MBP05.bin.
Each board has a different IAP filename (the IAP file is needed when doing firmware updates). Also there are different versions depending on whether you are updating via the RPi or standalone. If you are using the RPi then the correct IAP files are included in the package image. If you run standalone then the IAP files are Duet3iap_sd_MB6HC.bin and Duet3iap_sd_MBP05.bin (in fact these are the same file under different names).
If you are upgrading a Duet 2 system to Duet 3 then you will need to take account of the changes in RRF3, see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview. After making changes to config.g and rebooting, it's a good idea to run M98 P"config.g" so that you can see any error messages raised by commands in config.g.
The 40-pin header on the RPi is not polarised, so be careful to connect it the right way round! Pin 1 (indicated by the red stripe on the cable) is at the end most distant from the USB connectors.
Please note, the pinout of the IO connectors is not the same as the pinout of the Z probe connector on the Duet Maestro. We've put the +5V and +3.3V power outputs on opposite ends of the connector, to reduce the risk of damage if they are shorted together.

Dougal1957

@dc42 David

Is there an Image available for a PI4 that we can download and burn? Or relatively simple build instructions for those that are Linux illiterate

Doug

T3P3Tony

@Dougal1957 the same image should work on both

dc42

Further to my previous post, new firmware for Duet 3 is now available at https://github.com/dc42/RepRapFirmware/releases/tag/3.0beta10.

4lathe

Ok. Thx David and Tony! Mine just left UK.

4lathe

@4lathe So I just setup my rpi4 in advance of receiving my duet 3 this week. No errors were thrown using the oem duzuki instructions. However when I http://127.0.0.1 on the pi I get
This page isn't working
127.0.0.1 is currently unable to handle this request.
Http error 500

When I run the journal I can see some errors but I have no idea what to do with any of it.
Any help much appreciated!

A Former User

Maybe post some of the errors?

4lathe

@4lathe error shown in journal was
Cannot assign requested address /var/run/duet.sock

4lathe

@4lathe that came right after
Request starting HTTP/1.1 GET http://127.0.0.1/

4lathe

@4lathe actually others are just a repetition of that error.

A Former User

@4lathe said in Single Setup for Duet 3:

Cannot assign requested address /var/run/duet.sock

i think that would suggest you either don't have permissions, or its already in use. did you use sudo to run as root?

4lathe

@bearer I was logged in as pi when I executed all the dozuki instructions. Many of those use sudo. I did have to add sudo in front of one of the commands though.

T3P3Tony

@4lathe DSF wont serve anything is the Duet is not connected.

4lathe

@T3P3Tony ahhhhh. What was that error? Any good way to test that the web server is running?

A Former User

@4lathe said in Single Setup for Duet 3:

So I just setup my rpi4 in advance of receiving my duet 3 this week

Ah, as tony says, thats not gonna work. everything depends on DuetControlServer, and it won't start without the Duet3 connected.

4lathe

@bearer ok so just leave it for now?

A Former User

@4lathe said in Single Setup for Duet 3:

so just leave it for now?

yeah, might as well, you won't be able to verify the software anyways.

Although I'm puzzled by the fact that you say you get a HTTP 500 error if the Duet3 isn't connected, which is why I glossed over that bit initially.

4lathe

@bearer no idea.

gtj0

@bearer said in Single Setup for Duet 3:

@4lathe said in Single Setup for Duet 3:

so just leave it for now?

yeah, might as well, you won't be able to verify the software anyways.

Although I'm puzzled by the fact that you say you get a HTTP 500 error if the Duet3 isn't connected, which is why I glossed over that bit initially.

The DuetWebServer will start but it communicates with the DuetControlServer via that /var/run/duet.sock socket which is created by the DuetControlServer and that won't even start if it doesn't get a response from the Duet3 via the SPI bus. So when you access the web server, it responds with a 500 because it can't connect to that socket.