Duet3/pi DCS is unavailable after wiring 24V
-
@bearer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
[error] Failed to connect to Duet
System.IO.IOException: Error 2. Can not open SPI device file '/dev/spidev0.0'.Can an error 2 on open happen because the device does not exist?
Delta / Kossel printer fanatic
-
@Danal said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Can an error 2 on open happen because the device does not exist?
that what happened on my Pi. (same with lacking permission).
OP gets
[error] Duet is not availablewhich implies SPI is OK. (maybe there is room for making the two clearer as the first has nothing to do with the Duet as such, but still) -
I think I misread your post a couple up. You were pointing out the error that occurs if the device is missing. I read it as "op is getting this error". Now I see what you were saying vs what is happening on OP's Pi, and agree, the device is available. Sorry for the rabbit hole...
Should OP still
echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.confI don't believe we have proof either way that is correct.
-
@Danal said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Should OP still echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.conf
you get a warning if that is missing. so no.
-
Got it. Thanks!
-
@fractalengineer Line 4 I sort of expected. That is why we may need to bossa the board one more time. Maybe.
Anyway, after we get everything in sync, future upgrades will take care of this and keep things in sync.
Not finding /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin is a little concerning. Can you please:
ls -al /opt/dsf ls -al /opt/dsf/sd ls -al /opt/dsf/sd/sysAnd post the results here?
-
@Danal Will do in the next hour
I didn't know you meant on the pi command; I can probably get there through SSH but I woudn't know what to do from there; would you mind clarifying what you meant?
Likewise, I did double, triple check the SPI was activated in the settings, even in @chrishamm 's image; it's on
-
From the things you posted before, it looks like you've been issuing commands on the Pi... in the same way you did those in the past, just copy paste the "ls" commands.
-
Ultimately it doesn't matter; board is updated to RC9 and installing the latest unstable DSF should work as hes tried time and time again.
(Not having the correct firmware would only be a problem if the latest available apt packages aren't compatible)
-
@bearer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Ultimately it doesn't matter; board is updated to RC9 and installing the latest unstable DSF should work as hes tried time and time again.
(Not having the correct firmware would only be a problem if the latest available apt packages aren't compatible)
Agreed... but... what should he do next?
-
@Danal said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
what should he do next?
try the other pi he'll be borrowing any time now (and hope if the orignal Pi was damaged with the original Duet, the borrowed Pi didn't suffer the same fate).
following that I guess either call an exorcist or attempt to try another SPI slave (maybe there is a bit banged SPI slave for a Pi out there?)
-
Ok guys I'm just absolutely confused; the RPi 4 that worked last time on the standard image SD card won't connect to Wifi with chris's image no matter if I redo the wpa supplicant file.
It is not a Pi4 hardware issue because it works just fine with my other SD card flashed with Octopi
I'm rebuilding an image from scratch following this guide again; don't know what else to do at this point.
Duetpi lite this time; as if it changed anything
I'll report back once I get the new image setup on the pi4 with wifi working and everything up do date
Thanks for the help
-
Send me a message if you'd want a second pair of eyes on it. If you can connect the Pi to wired Ethernet and provide remote access (e.g. ngrok) I can take a stab at it.
prime suspect is missing country code in the config or somehow strange whitespace in the config preventing it from being parsed.
this was one of the more detailed guides I could find to share https://wiki.archlinux.org/index.php/wpa_supplicant
-
@bearer thanks;
Well it's all fixed now with the new image...the wifi connection it is...Still unable to connect to DCS
On a separate pi...
On a new board...
Maybe we can try that pin by pin connection to double check the issue wasn't the ribbon?
I can go buy jumpers tomorrow; how many we need?
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
how many we need?
Minimum 9, but didn't you get a new cable?
-
@bearer no I think I got a refurb; there was only the board and SD card in it
-
@Danal That error occurred because SPI wasn't enabled at that point, hence no /dev/spidev.0.0. It's always possible to define module options in /etc/modprobe.d, that doesn't require the driver(s) to be loaded.
It must be the connection from the Pi to the Duet 3 (ribbon cable?). The SPI link uses pins 19-24 (see https://pinout.xyz/pinout/pin22_gpio25#) so I'd once more check continuity between these pins on both sides. The error you see in the log without any extra comment (more verbose in v2.1.0) means that no signal could be transferred over pin 22 (BCM25). DSF expects this pin to be high when it starts.
Duet software engineer
-
@chrishamm said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
It must be the connection from the Pi to the Duet 3
of curiosity what does DCS say if it gets a response, but the wrong due to say wrong firmware or spi clock?
-
It's also worth starting DCS with
-l debugto see a few more details. If the SPI clock is too high, you usually see warnings about failed transfers and/or checksum errors. -
@chrishamm said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
It's also worth starting DCS with
-l debugto see a few more details. If the SPI clock is too high, you usually see warnings about failed transfers and/or checksum errors.-l debugshows the difference, no difference without it.#with 22 low pi@raspberrypi:~ $ /opt/dsf/bin/DuetControlServer -l debug [debug] Lost connection to Duet System.OperationCanceledException: Timeout while waiting for transfer ready pin ... [error] Duet is not available #with 22 high pi@raspberrypi:~ $ /opt/dsf/bin/DuetControlServer -l debug [debug] Lost connection to Duet System.OperationCanceledException: Board is not available (no header) ... [error] Duet is not availableMaybe change the first to Duet is not ready?
edit: sudo wasn't needed (at that point in starting up at least)
edit2: whops, wasn't testing the latest version, error changed to fatal, but same string.
