• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

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

Scheduled Pinned Locked Moved Solved
Duet Web Control
4
47
2.3k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Macgyver1307
    last edited by 22 May 2020, 14:23

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

    1 Reply Last reply Reply Quote 0
    • undefined
      Macgyver1307
      last edited by 22 May 2020, 15:05

      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
      ? 1 Reply Last reply 23 May 2020, 03:33 Reply Quote 0
      • undefined
        Macgyver1307
        last edited by 22 May 2020, 15:16

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

        undefined 1 Reply Last reply 22 May 2020, 22:34 Reply Quote 1
        • undefined
          Phaedrux Moderator @Macgyver1307
          last edited by 22 May 2020, 22:34

          @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.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • undefined
            Macgyver1307
            last edited by 23 May 2020, 02:04

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

            1 Reply Last reply Reply Quote 0
            • ?
              A Former User @Macgyver1307
              last edited by 23 May 2020, 03:33

              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.

              1 Reply Last reply Reply Quote 0
              • undefined
                Macgyver1307
                last edited by 23 May 2020, 14:09

                here is the output .
                db5e9633-53a1-42d1-ac95-99e3b5f9ed32-image.png

                1 Reply Last reply Reply Quote 0
                • undefined
                  Macgyver1307
                  last edited by 23 May 2020, 14:11

                  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.

                  ? 1 Reply Last reply 23 May 2020, 15:59 Reply Quote 0
                  • ?
                    A Former User @Macgyver1307
                    last edited by A Former User 23 May 2020, 15:59

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • ?
                      A Former User
                      last edited by 23 May 2020, 19:06

                      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:

                      9ff41e90-9272-4588-bceb-75e5acf19c86-image.png

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Macgyver1307
                        last edited by 24 May 2020, 04:15

                        3b8e1147-2f7f-426c-9b3c-6fe05fd0c022-image.png

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Macgyver1307
                          last edited by 24 May 2020, 04:24

                          @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 $
                          1 Reply Last reply Reply Quote 0
                          • undefined
                            Macgyver1307
                            last edited by 24 May 2020, 04:26

                            e6a632e9-4fae-4c11-bd11-02a167ab24d4-image.png

                            1 Reply Last reply Reply Quote 0
                            • ?
                              A Former User
                              last edited by A Former User 24 May 2020, 06:09

                              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.

                              1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User
                                last edited by 24 May 2020, 11:22

                                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.)

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  Macgyver1307
                                  last edited by 24 May 2020, 14:09

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

                                  should

                                  pi@duet3:~ $ sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2
                                  spi mode: 0x0
                                  bits per word: 8
                                  max speed: 8000000 Hz (8000 KHz)
                                  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 | ................................
                                  pi@duet3:~ $
                                  ? 1 Reply Last reply 24 May 2020, 14:24 Reply Quote 0
                                  • ?
                                    A Former User @Macgyver1307
                                    last edited by A Former User 24 May 2020, 14:24

                                    @Macgyver1307 I'm not sure what would cause that to fail on both SPI ports, which is why I dragged out the logic analyzer and double checked the test setup, and its does work both with the software and the hardware.

                                    It could be there is something wrong with the Raspberry Pi image, but given you used the DuetPi image that is pre-configured it shouldn't matter.

                                    If the rPi4 doesn't work come Tuesday, you're best bet is probably to either download the DuetPi image afresh - or you can get a jump on it now if you can find the inclination to do so.

                                    pi@duet3:~ $ sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2
                                    spi mode: 0x0
                                    bits per word: 8
                                    max speed: 8000000 Hz (8000 KHz)
                                    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 | 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 | ......@....▒..................▒.
                                    pi@duet3:~ $

                                    2020-05-24 16_45_12-Logic 2 [Logic Pro 8 - Connected].png
                                    IMG_20200524_164430925.jpg

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Macgyver1307
                                      last edited by 24 May 2020, 14:39

                                      yeah crazy it's not working. the sd card is the one from the duet 3 box I got last week. my duet 3 is working in standalone mode for the moment. this pi had a gpio header touch screen the image before I used it as a duet pi. the question is do I wait till Tuesday with the new PI 4 and just try the sd card in it or do I flash a new complete fresh start on it?

                                      ? 1 Reply Last reply 24 May 2020, 14:48 Reply Quote 0
                                      • ?
                                        A Former User @Macgyver1307
                                        last edited by A Former User 24 May 2020, 14:48

                                        @Macgyver1307 hard to say, it won't take long to test the same card, and it'll give you an indication as to weather or not the issue is the Pi or the card - on the other hand, you could get the same answer by just formatting the card and getting a fresh image. I guess it comes down to what you feel like spending your time on

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          Macgyver1307
                                          last edited by 27 May 2020, 17:35

                                          New pi came in today and I reloaded a fresh image and the issue is resolved ! Thank you for your help !

                                          ? 1 Reply Last reply 27 May 2020, 17:38 Reply Quote 0
                                          32 out of 47
                                          • First post
                                            32/47
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA