RRF 3.01-RC10, DWC 2.1.5 and DSF 2.1.1 released
-
very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?
Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.
-
@Garfield said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?
Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.
Other than the M55x network commands, it should work. Make sure they're not commented out when in standalone mode.
-
Don't have any M55x commands - have never had any ...
-
@Garfield I think you'd need at least M552 S1 to enable networking. It should get a DHCP address. You should then be able to reach the printer via the name set in M550 P. Http://printername
-
Gone from bad to worse ... can't even boot the DWC in the Pi now .... Pi boots OK ... sytemctl status reports DWC is running but can't access it.
-
@Garfield I thought you were trying to go standalone to get around the DCS issue, no?
-
@Garfield said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?
Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.
it won't unless you copy the config from /opt/dsf/sd/sys to /boot/sys before removing it from the Pi. (moving the config to /boot/sys/config.g and symlinking it back to /opt/dsf/sd/sys/config.g would be an interesting exercise though (and adding M552 S1))
i.e. duet can only read the first fat32 partition, raspbian uses it for /boot and the duet is unable to read the config file the pi normally uses.
-
I was trying to boot stand alone - couldn't - put it into the Pi and although DWC reports running it can't be accessed, I can access SSH.
Never been a Linux fan ..... never will be until it ceases to a 19th century OS accessible only to those prepared to waste days on a basic config (I am not one of those - I have a life)
-
@bearer said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
@Garfield said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?
Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.
it won't unless you copy the config from /opt/dsf/sd/sys to /boot/sys before removing it from the Pi. (moving the config to /boot/sys/config.g and symlinking it back to /opt/dsf/sd/sys/config.g would be an interesting exercise though (and adding M552 S1))
i.e. duet can only read the first fat32 partition, raspbian uses it for /boot and the duet is unable to read the config file the pi normally uses.
Can't symlink in that case but yeah, I keep forgetting about people running their SBC from an SD card since I run from SSD. When I need to go standalone, I just copy the /opt/dsf/sd/ directory contents to a freshly formatted SD card.
-
@gtj0 said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
Can't symlink in that case
not if you move the config to the /boot parition and link from the ext4 parition?
(i cant test in a duet3, but think it should work)pi@rpix:/opt/dsf/sd/sys $ ls config.g pi@rpix:/opt/dsf/sd/sys $ sudo mkdir /boot/sys pi@rpix:/opt/dsf/sd/sys $ echo M552 S1 | tee cat - >>config.g pi@rpix:/opt/dsf/sd/sys $ sudo mv config.g /boot/sys mv: failed to preserve ownership for '/boot/sys/config.g': Operation not permitted pi@rpix:/opt/dsf/sd/sys $ ln -s /boot/sys/config.g pi@rpix:/opt/dsf/sd/sys $ ls -l total 1460 lrwxrwxrwx 1 pi pi 14 Apr 26 22:44 config.g -> /boot/sys/config.g pi@rpix:/opt/dsf/sd/sys $ echo M552 S1 | sudo tee -a config.g pi@rpix:/opt/dsf/sd/sys $ cat config.g ; Duet 3 Configuration File ; It is recommended to replace the contents of this file with a preset from https://configtool.reprapfirmware.org M550 P"Duet 3" ; set machine label M552 S1(although i suspect doing the whole sys, gcode, macro folders might be more convenient.. and throwing in the stand alone dwc not as a link)
-
@bearer Oh, that direction.
Yeah that works. -
Well my system is now totally borked - can't access DWC, can't access SSH, doesn't get an IP.
So I re-imaged the SD from the links in the 'getting started with duet 3' Dozuki and .....
it still doesn't work - starting to get a tad grumpy.
I'm only thankful that I have a config backup ....
-
@Garfield said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
it still doesn't work - starting to get a tad grumpy.
understandable, does the ribbon cable attached make a difference? (or detached would be more to the point)
-
None whatsoever ... Pi won't respond, definitely does something - lots of green LED flickering which says it is healthy, can't connect it via hdmi because some jokers thought it would be a laugh to add yet another poxy standard for which I have no cable - got 6 or 7 Pi 3's - ask me how many I can find ....
Trying to do a boot eeprom rebuild but I don't have a microSD small enough but I don't think it is that.
-
@Garfield said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
Trying to do a boot eeprom rebuild but I don't have a microSD small enough but I don't think it is that.
Id try a serial (3.3v ttl) if possible before that, just to be able to see what's going on.
Don't think the actual size of the card matters as long as the partition is small enough?
(Also, shouldn't this have it's own topic?) -
@dc42 said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
@Silrocco said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:
Uploading DuetMaestroAP.bin didn't work either, getting an infinite upload status for minutes that I have to cancel out.
Is that repeatable? What is the file size of the DuetMaestroAP.bin file on your PC?
@dc42
I'm having the very same issue.
Upload status does not finish "circling", file does not get uploaded at all.What puzzles me is that uploading any other file (including DWC.zip) does work like a charm.
Duet2CombinedIAP.bin file size is 40804 byte.
I am currently running
Board: Duet 2 WiFi (2WiFi) Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC7 (2020-04-14b3) Duet WiFi Server Version: 1.23 Duet Web Control 2.1.2 -
I've just noticed that the layer displayed in DWC is incorrect. I'm using Slic3r++ and the layer height of the print is 0.1mm but 3.01-R10 reports 0.2mm.
I've also tried this with Prusaslicer and it works correctly, so it probably isn't a Duet issue.
Can any one tell me how the layer height displayed is determined?
-
As many of you have ignored my request at the top of this thread to start a new thread for any issues with these releases, I am locking this thread and I will not be reading it. Threads with multiple issues from different users in them waste too much of my time due to the difficulty in finding the posts relevant to each individual issue.
