Duet3/pi DCS is unavailable after wiring 24V
-
@bearer well I don't know what to say;
-The duet is wired to my laptop using an ethernet cable
-Laptop is connected to wifi router
-I set M552 with a static address becauseM552 S1 P0.0.0.0doesn't return a dynamic IP; nothing shows on my IP scanner either
-I chose 192.168.0.11 because that's the one Octoprint was always dynamically assigned to on this rpi
-Even with the static IP, every second time I enter it in the browser I get the DWC loading screen, or a timeout
-The wireshark filter doesn't return any match
-route printdoesn't show any 192.168.0.11So it looks like all I can do is half access DWC on my browser, but it doesn't show any traffic?
-
@bearer here; I can see the DWC loading on my browser, but see the route print:
C:\Users\titan>route print =========================================================================== Interface List 21...00 ff fb 38 05 34 ......TAP-ProtonVPN Windows Adapter V9 9...04 ea 56 1b 04 f5 ......Microsoft Wi-Fi Direct Virtual Adapter #5 10...06 ea 56 1b 04 f4 ......Microsoft Wi-Fi Direct Virtual Adapter #6 20...c4 65 16 9c a3 44 ......Intel(R) Ethernet Connection (7) I219-LM 12...00 ff 97 d1 70 ad ......Kaspersky Security Data Escort Adapter 8...04 ea 56 1b 04 f4 ......Intel(R) Wireless-AC 9560 160MHz 17...04 ea 56 1b 04 f8 ......Bluetooth Device (Personal Area Network) 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.12 50 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 169.254.0.0 255.255.0.0 On-link 169.254.241.188 291 169.254.241.188 255.255.255.255 On-link 169.254.241.188 291 169.254.255.255 255.255.255.255 On-link 169.254.241.188 291 192.168.0.0 255.255.255.0 On-link 192.168.0.12 306 192.168.0.12 255.255.255.255 On-link 192.168.0.12 306 192.168.0.255 255.255.255.255 On-link 192.168.0.12 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 169.254.241.188 291 224.0.0.0 240.0.0.0 On-link 192.168.0.12 306 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 169.254.241.188 291 255.255.255.255 255.255.255.255 On-link 192.168.0.12 306 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 331 ::1/128 On-link 11 331 2001::/32 On-link 11 331 2001:0:2851:b9f0:28b2:445:3433:563f/128 On-link 8 306 fc00::/7 fe80::be3e:7ff:fe67:de22 8 306 fd00:bc3e:767:de22::/64 On-link 8 306 fd00:bc3e:767:de22:686c:fd82:6fb9:1280/128 On-link 8 306 fd00:bc3e:767:de22:c463:3c86:4104:a35c/128 On-link 20 291 fe80::/64 On-link 8 306 fe80::/64 On-link 11 331 fe80::/64 On-link 11 331 fe80::28b2:445:3433:563f/128 On-link 20 291 fe80::8dc5:6603:e8cd:f1bc/128 On-link 8 306 fe80::c463:3c86:4104:a35c/128 On-link 1 331 ff00::/8 On-link 20 291 ff00::/8 On-link 8 306 ff00::/8 On-link 11 331 ff00::/8 On-link =========================================================================== Persistent Routes: None -
(And this is why we say "If you don't like the weather in Bergen wait 5 minutes" ... its snowing now)
Aaanyways, I suspected something like that after briefly looking at the capture.
The computer doesn't have any network configured for the wired ethernet interface, so you'd have to set a static IP on the computer as well (and on a different network than 192.168.0.11) OR see if you can connect the ethernet cable from the Duet to your wifi router.
As to why you can load the front page I can only put down to caching somehow, which I hoped to avoid by using a private or incognito browser window.
So run the cable to the router or set static IPs for both the duet and the computer, choose something like 192.168.1.11 and 192.168.1.12 for the two (note 0 changed to a 1)
-
@bearer hey you're from norway
I visited Oslo once for a weekend while I lived in Sweden; I know what you mean lolWell chief at last we made some progress
Connected the duet to the router, dynamic IP assignment worked for the first time, and DWC is FINALLY loading properly, at least locally:
How would I move forward making sure it works when running it through the RPi now?
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
How would I move forward making sure it works when running it through the RPi now?
Not sure, even if the rPi were to suffer similar networking issues it still didn't find the Duet on the SPI bus so we're not gonna make much more progress on that front I suspect.
I'd proceed to getting things set up and running as is while the Duet people are working on getting RRF 3.01 to a stable release. The config you make for the Duet in stand alone mode should transfer to using with a pi afaik.
-
@bearer but it worked fine over the pi before; I can't leave the machine wired to the router, I don't need the latest 3.01 either
Is there a way to make it work with the pi with RRF 3.0?
-
It should have worked with the clean Pi image and RRF3.0 afaik.
I think I missed that it previously worked; what happened when it stopped working?
You can go back to the pi and we can chase down the network if thats the problem, but I wouldn't hold my breath.
If you don't make any progress on using the Pi as intended, we can turn it into a wifi bridge so you can get on with things without having the cable running to the router. (Or you could set a static ip for your computer - possibly even use internet sharing if your windows has that feature)
-
@bearer thanks, I'd be keen to troubleshoot the network issue on the pi first.
I don't think I did anything crazy since it last worked; I had to plug/unplug the ribbon a few times as I was still using that pi for octoprint on another printer while waiting for the final parts of that new printer to show up
I never unplugged the ribbon while powered, and only noticed the DWC connection issue when I first powered the Duet through VIN
Railcore II ZL
-
I don't think the pi issue is network related, but if you capture the traffic with wireshark I'll take a look.
do make sure to not try to access the pi 5 minutes before starting the capture (should ensure wireshark picks up the ARP traffic, or run
arp -d *in an elevated command prompt)If you still find
Apr 12 15:58:56 duet3 DuetControlServer[4530]: [error] Duet is not available
when running
journalctl -u duetcontrolserver -e(don't think you should needsudofor that, but stick sudo in front if it doesn't work) then its not going to work no matter what we do to the network. -
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
only noticed the DWC connection issue when I first powered the Duet through VIN
so it never worked through VIN?
-
@bearer Ok I plugged the pi back, changed sd card and replace the config file, as well as flash the board back to rrf3.0
- Still not working
- I don't know how to run that arp command; here's what I get:
pi@duet3:~ $ arp -d * Desktop: Unknown host pi@duet3:~ $ sudo arp -d * Desktop: Unknown host pi@duet3:~ $-
Journal command still reports unavailable Duet
-
Either way here's the capture; pi's IP is 192.168.0.11, I start by logging in SSH, then try to launch DWC in browser, first normal then private session. That's what's in it: https://we.tl/t-2T4XTTek8p
-
A friend of mine will let me borrow his Pi 4 tomorrow to narrow down whether the issue comes from the duet or the pi
-
It powers up through VIN but behaves just like powered through USB; DCS unavailable
Thank you
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
I don't know how to run that arp command; here's what I get:
my bad, instructions uncear. that would be a windows command, as we'd want to clear the arp cache on the host running wireshark. (but its moot point, no doubt about which host the pi is, and seems to be no firewall issue)
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Journal command still reports unavailable Duet
thats a problem between the pi and the Duet over the spi bus. can you do
ls -l /dev/spi*on the pi?@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
A friend of mine will let me borrow his Pi 4 tomorrow to narrow down whether the issue comes from the duet or the pi
i might be paranoid, but i'd get Peter Griffins volcano insurance just in case.
I'll have a (closer) look at the wireshark log a bit later, but when DCS reports the Duet is unavailable then thats where the problem is.
-
@bearer
my bad, instructions uncear. that would be a windows command, as we'd want to clear the arp cache on the host running wireshark. (but its moot point, no doubt about which host the pi is, and seems to be no firewall issue)
thanks for clarifying; I can try the arp command again if that capture doesn't work
thats a problem between the pi and the Duet over the spi bus. can you do ls -l /dev/spi* on the pi?
Sure here's what I get; I did remember very clearly enabling SPI during the setup process
pi@duet3:~ $ ls -l /dev/spi* crw-rw---- 1 root spi 153, 0 Apr 12 15:45 /dev/spidev0.0 crw-rw---- 1 root spi 153, 1 Apr 12 15:45 /dev/spidev0.1i might be paranoid, but i'd get Peter Griffins volcano insurance just in case.
Lol what do you mean?
And thank you again for all the support; looking forward to hear what you see in that capture
Cheers
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
thanks for clarifying; I can try the arp command again if that capture doesn't work
No need, and capture looks about as expected, computer connects to Pi they switch to websockets and everyone is happy as far as I can tell.
Problem likely lies in that DuetWebControl which runs on the pi and cannot connect to DuetControlServer because its cannot find the Duet on the SPI bus and doesn't start.
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Sure here's what I get; I did remember very clearly enabling SPI during the setup process
You're not using the image from here? https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3 (it should have SPI and other stuff ready to go)
In any case I don't think I can pinpoint problems any further than its beetween DCS and the Duet3 board. Maybe dropping the SPI speed could be worth a try, if no one beats me to it I'll see if I can't post some instructions later.
-
@bearer
You're not using the image from here? https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3 (it should have SPI and other stuff ready to go)
Seems to be the same as the one linked in the "get started" guide, so I'd say yes
I have no clue how to do the spi speed thing so I'll be on the lookup; thanks
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
I have no clue how to do the spi speed thing so I'll be on the lookup; thanks
neither did I..
and a few quick searches didn't bear fruits, however https://forum.duet3d.com/post/109561
the config.json file would be
/opt/dsf/conf/config.json -
Oh, do make a note of what the speed was before reducing it.
grep "SpiFrequency" /opt/dsf/conf/config.json sed -i 's/^ "SpiFrequency": [0-9]*,/ "SpiFrequency": '500000',/' /opt/dsf/conf/config.json grep "SpiFrequency" /opt/dsf/conf/config.jsonshould give you
pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 8000000, pi@duet3:~ $ sed -i 's/^ "SpiFrequency": [0-9]*,/ "SpiFrequency": '500000',/' /opt/dsf/conf/config.json pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 500000, pi@duet3:~ $showing it changed from 8mhz to 500khz - if it works try increasing it until it stops working and back off say 1mhz.
if not, verify the board still does respond to
M122on the serial terminal, no sd card in the duet (should be clear from M122 output as well) and call in the cavalry. -
@bearer Hi,
Ok so today I tried on another RPi 4. Had to power the Duet back on VIN to supply enough juice for both the Duet and Pi, but still no luck. Even on the HDMI screen, shows DCS unavailable.
Spi Freq was:
pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 2000000,Changed it to 500kHz
Still no luck.
Here's the M122 result.
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0 running on Duet 3 MB6HC Board ID: 08DJM-956L2-G43S4-6J9F6-3S86T-KA5LD Used output buffers: 1 of 32 (12 max) === RTOS === Static ram: 152720 Dynamic ram: 148548 of which 0 recycled Exception stack ram used: 308 Never used ram: 91640 Tasks: NETWORK(ready,1984) HEAT(blocked,1416) CanReceiv(suspended,3808) CanSender(suspended,1476) CanClock(blocked,1424) TMC(blocked,212) MAIN(running,3652) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:11:35 ago, cause: power up Last software reset at 2020-04-04 15:59, reason: User, spinning module LinuxInterface, available RAM 79620 bytes (slot 0) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 43.9, current 44.2, max 44.3 Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Driver 0: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 1: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 2: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 3: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 4: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Date/time: 1970-01-01 00:00:00 Slowest loop: 0.28ms; fastest: 0.09ms === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 1 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is ready with "M122" in state(s) 0 aux is idle in state(s) 0 daemon* is idle in state(s) 0 0, running macro queue is idle in state(s) 0 lcd is idle in state(s) 0 spi is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.28ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 0 of 8 - Ethernet - State: 0 Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 0, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 695578ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 okSomething must be wrong with the board; it worked fine until I first powered it through VIN; I never shorted it either the fuses are mint.
Railcore II ZL
-
Maybe @dc42 can share some insight?
-
We hope to have new RRF 3.01RC7+DSF+DWC released later today, so probably best to wait for those.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com
