Duet 3 6hc and raspberry pi 3 B+ DCS not started

chrishamm

I suggest you follow this post and check what happens: https://forum.duet3d.com/topic/15551/duet3-pi-flashing-diag-led-after-wiring-24v-dcs-is-unavailable/119?_=1590153541635

A Former User

@Macgyver1307 you can probably copy/paste the text from the terminal and save some bandwidth.

Presumably you're using the DuetPi image?

Lacking another Pi to test, as you already have the du-pont style wires ready you could try to use the SPI1 bus and edit /opt/dsf/conf/config.json. The SPI loopback testing doesn't test the clock signal from the Pi so its possible it could be bust I guess, but its hard to definitively point at one or the other without tools or replacements.

ref pinout.xyz's nice pinout:
alt text

(Or wait for the Pi4 come Tuesday)

Macgyver1307

yes sir! I started with that and did all of the testings from that post before I started this one. I can try the pin process again?

A Former User

@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:

I can try the pin process again?

If you do, copy paste the output so we can catch anything amiss along the way. If using putty just use the mouse to drag and select text, which will automatically be copied to the clipboard ready to paste in the forum. Then highlight the text (in the forum post editor) and use the Code formatting button (5th button from the left after bold, italics etc).

Macgyver1307

ok sounds good ill start the process again and display the outputs. thanks for the help!

Macgyver1307

pi@duet3:~/spidev-test $ RDY=22 CS=24 ; {
gpio -1 mode $CS out
> gpio -1 mode $CS out
> gpio -1 mode $RDY in
> gpio -1 write $CS 1 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"
> gpio -1 write $CS 0 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"
> { ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.0 && echo RX should equal TX. ;} | tail -n3 | cut -b-100 ;}
(Pin RDY/22) 1 should equal 1 (Pin CS/24)
(Pin RDY/22) 0 should equal 0 (Pin CS/24)
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D
RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RX should equal TX.

* list item

Macgyver1307

well I tried 22 to 28 ad 24 to 28 with the same output. I would post it but the form says its spam.

Phaedrux

@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:

I would post it but the form says its spam.

3 posts in a row to the same thread in a short amount of time probably flagged you. Please try again.

Macgyver1307

I'm going to wait till Tuesday and loaded up a fresh pi -4 and see if I still have issues. thanks, Phaedrux!

A Former User

The first bit looks to confirm your Chip Select, and Ready pins are working but the next bit would suggest a problem with the jumper between MISO and MOSI or a problem with the Pi. Did you place a jumper over (physical) pins 19 & 21 as well as 22-24?

TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D 
RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

This is also in line with the error from DSF.

Macgyver1307

here is the output .

Macgyver1307

sorry I had to snip it because it gets flagged as spam if I put it in as code. jumpers installed on 19-21 and 22-24 . pi is on my desk with nothing attached.

A Former User

@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:

jumpers installed on 19-21 and 22-24 . pi is on my desk with nothing attached.

you only need to run it once with RDY=22 CS=24; the test for 19 and 21 is defined by the -D /dev/spidev0.0 parameter to the spidev_test command.

So it would look like the SPI bus isn't working on the Pi. You can try to move the jumper (will require a wire) to 35 and 38 (and repeat test with -D /dev/spidev0.1 to see if the other SPI bus is working, which you could then use.

A Former User

Just to be 110% sure; you placed the jumper like shown on the picture right, both at the same time?

@bearer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

Macgyver1307

Macgyver1307

@bearer said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:

-D /dev/spidev0.1

pi@duet3:~/spidev-test $ RDY=35 CS=38 ; {  gpio -1 mode $CS out; gpio -1 mode $RDY in; gpio -1 write $CS 1 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"; gpio -1 write $CS 0 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"; { ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.1 && echo RX should equal TX. ;} | tail -n3 | cut -b-100 ;}
(Pin RDY/35) 0 should equal 1 (Pin CS/38)
(Pin RDY/35) 0 should equal 0 (Pin CS/38)
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D
RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RX should equal TX.
pi@duet3:~/spidev-test $

Macgyver1307

A Former User

the spidev_test utility test the MISO and MOSI pins from the SPI bus, so by defining them as RDY and CS you're maybe messing with the results?

the white jumper is on MISO and MOSI for ~~spi0.0~~ spi0.n and the red jumper is on ~~spi0.1~~ spi1.n so, but that doesn't really matter as your previous run showed RDY and CS is okay (so the white jumper is less important in the context of testing ~~spi0.1~~ spi1.n)

Leave wires as is (on the last picture), reboot pi to ensure any settings to the GPIO pins are cleared and run

sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.0

to test MISO/MOSI from spi0.0. (white wire) and

~~sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.1~~
sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2

to test MISO/MOSI from ~~spi0.1~~ spi1.2. (red wire)?

Either your enviroment or your hardware is failing the SPI loopback test as it stands now. The first line will test MISO/MOSI from spi0.0 and the last line will test MISO/MOSI from ~~spi0.1~~ spi1.2 - ignoring RDY/CS for now.

A Former User

Hmm, spidev0.1 won't work. that is still the same spi bus, but CE1 instead of CE0.

To enable spidev1.0:

To also enable the auxiliary SPI device (three slave selects) add the line dtoverlay=spi1-3cs to /boot/config.txt.

in other words echo dtoverlay=spi1-3cs | sudo tee -a /boot/config.txt && sudo reboot

and run sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2 (the .2 part only signifies it should use BCM pin 16 (physical pin 36 for CE)

then it should allow testing the other SPI bus, (sorry for the confusion, I must have misunderstood the devicetree stuff for that as I've been using that spibus only with an custom overlay for the intended chip, which doesn't seem to create a device node but still works.)