SBC Disconnects from Duet 3 Mini - Network error
-
Ok will do but ... damn. Thats a good bit of nix tomfoolery ...
I may need some specific guidance - step by step ... not sudo guru.
-
Well you've got the GUI, so backing up the files you can do with the file manager.
And the updates are usually prompted on first boot of duet pi anyway, so probably won't even have to send a terminal command.
That's really all the tomfoolery involved.
-
@phaedrux - need to understand why ... I now need a new SD card. I will buy one and am as I should have spares ... but ...
I want to be able to control this printer via the Pi - as if I lived on a deserted island and all I had was electricity ... and config updates arrived via a sd card in a bottle. No wifi - no internet - no ancillary BS ... just the SBC and the Duet ... talking to eachother over the 40 pin cable / spi.
I dont want to have to rely on the pi having wifi access in order to control my printer - period. If i get wifi sometimes for misc stuff fine .. but I want to be able to hit the estop button in the dwc and the damn printer STOP - not be dependent if this thing is effectively routing tcpip packet thru some bug ridden interface / stack ...
Is my understanding of how the sbc is to control the duet3 via spi / dicrect connection - not reliant on wifi or ethernet routing and connectivity - errant? Or is the design and fw reliant on networking to the internet in order to function as intend ?
-
Yes that's fine. I use my duet+pi with a direct connect touch display as well. Should be no problem with no network connectivity in that situation.
The reason I suggest trying a new SD card is that perhaps yours is failing and a fresh install is a good way to troubleshoot anyway.
-
@sputnikoc3d I totally agree. If you're connected via localhost, it should not look for the network at all. The whole point of a loopback address is to be able to test and run software without sending data over the network. That's literally what loopback means. Loop to the physical interface, and right back again.
-
@sputnikoc3d it looks like there may be a slight difference between your host name and duet name, Linux is case sensitive, you have Das-voron\das-voron both need to be case exact with Linux. But those permission errors are worrying, either your filesystem is in read-only mode, or that SD is on it's way out. Either way, your quickest repair is as @Phaedrux advised. SD Cards are sometimes bad straight out the packaging, prefer a SSD on USB 3 as a boot device personally but that takes a bit more to setup.
Just to confirm, you are running the following image correct?
-
@shauncro - confirming DuetPi image is being used.
When the machine was all default ...
config.g had "Duet 3"
raspi had duet-3 - iirc since no upper case and no spaces allowed - so stock FW and configurator or whatever - or somehow its been a mismatch from day one. Maybe thats been part of the issue - i dunno.
Whats everybody else doing ?
config.g duet-3
raspi - duet-3 ?Flashing a fresh image now on a new 64GB SanDisk Extreme 170 ms / 90 ms card - hope thats sufficient.
-
@sputnikoc3d Busy with a standalone install on my laser that is frustrating me.
Running Mini 5+ with SBC on Tevo Little Monster
Busy with 2 x 400W servo setup and Duet 3 + SBC on a custom build. -
Flashed new FW Full Duet Pi Image via Belena etcher - as before. 64 GB SanDisk Extreme blah ...
added the wpa_supplicant.conf
Setup guide says to use - http://duet3.local/
failed to connect to duet3.local - network error
failed to connect to duet check your connection ( DCS Not Started )
its showing me dwc - what that looks like when you lose wifi connectivity - it knows its there or was there but - flashes connecting
hdmi screen out from the Pi is dark - dead nada -
updating and upgrading ... guessing dcs not launched and Duet 3 not connecting to pi as its likely mismatched firmware ?
Duet 3 is 3.4 Beta?? whatever was last week
-
pi@duet3:~ $ sudo raspi-config pi@duet3:~ $ ls /dev/spidev* /dev/spidev0.0 /dev/spidev0.1 pi@duet3:~ $ -
The DuetPi when updated will be running 3.3 as it is on the stable branch by default. If you have manually updated the Duet3 to 3.4 beta I suggest you use the firmware update procedure described here to return it to 3.3.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3
Afterwards, you should be able to establish connection between the pi and duet again. Then if you wish to try the beta again you'll need to use the unstable branch on the pi to get pre-release versions.
https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#unstable-package-feed
-
@phaedrux - @ctilley79 - got me thru the hiccups of getting all the right services started and in the proper order.
We got the updates and packages down and running and dcs / dwc is live. Toolboard was on 3.4.oBeta3 - so I went all in there again. We'll see how she goes from here .
I have the hostname and machine name matching [ duet3/duet3 ] in pi / and config.g
So far things are working ... I neglected to save my macros and all my local dwc settings were gone too - but Im getting much closer - network drop outs are better atm as well.
Running on the new SD card 64 GB SanDisk Extreme - fastest they sold at Best Buy.
My pi/nix game is ever so slightly improving ...
If the disconnects continue ... will address and be back.
