Duet 3 and jetson Nano?

gtj0

hanshogeland

@gtj0 thx again for you help!

JLM4751

@gtj0 I hate to reply to such an old thread but this is the only one i could find that described the set up of the jetson nano as a SBC with the duet 3. My issue is I am following the steps that Hans nicely wrote out in his post here https://forum.duet3d.com/post/212946 . however when i add the single-spidev.dtbo file to /boot/ I cannot get this option to show up in jetson-IO under "configure for compatible hardware". I've also tried manually adding the .DTB file to /boot/ and having the extlinux.conf file point to that .dtb file, but when i run duet control server i still get the waiting for transfer ready timeout error. I've tried both a a02 board as well as a b00 board. any insight would be greatly appreciated, thanks for all the info providing in this thread its been a huge help.

gtj0

@JLM4751 said in Duet 3 and jetson Nano?:

@gtj0 I hate to reply to such an old thread but this is the only one i could find that described the set up of the jetson nano as a SBC with the duet 3.

No worries

First,let's see if the spi device is actually there or not. Try...

# ls -al /dev/spidev*
crw-rw---- 1 root gpio 153, 0 Jun 19 14:55 /dev/spidev0.0
crw-rw---- 1 root gpio 153, 1 Jun 19 14:55 /dev/spidev1.0

If you see the devices then the most probable issue is that the /opt/dsf/conf/config.json file is incorrect. The SPI related stuff should look something like this...

...
  "SpiDevice": "/dev/spidev0.0",
  "SpiBufferSize": 8192,
  "SpiTransferMode": 0,
  "SpiFrequency": 8000000,
  "SpiConnectTimeout": 500,
  "SpiTransferTimeout": 500,
  "SpiConnectionTimeout": 4000,
  "GpioChipDevice": "/dev/gpiochip0",
  "TransferReadyPin": 13,
  "MaxSpiRetries": 3,
...

The waiting for transfer ready timeout error is directly related to the GpioChipDevice and the TransferReadyPin settings.

If you can't get it going, the output of gpiodetect might help.

JLM4751

@gtj0 thanks for the reply, this is the output from running "ls -al /dev/spidev*"

mr_solderem@Mr:~$ ls -al /dev/spidev*
crw-rw---- 1 root gpio 153, 0 Jun 19 15:59 /dev/spidev0.0
crw-rw---- 1 root gpio 153, 1 Jun 19 15:59 /dev/spidev0.1
crw-rw---- 1 root gpio 153, 2 Jun 19 15:59 /dev/spidev1.0
crw-rw---- 1 root gpio 153, 3 Jun 19 15:59 /dev/spidev1.1

so you were right, I forgot to change the data transfer ready pin to pin 13. Now i have a connection over SPI.

mr_solderem@Mr:~$ sudo /opt/dsf/bin/DuetControlServer
Duet Control Server v3.4.5
Written by Christian Hammacher for Duet3D
Licensed under the terms of the GNU Public License Version 3

[info] Settings loaded
[info] Environment initialized
[info] Connection to Duet established
[info] IPC socket created at /run/dsf/dcs.sock
[info] Starting macro file config.g on channel Trigger
[error] M550: Machine name must consist of the same letters and digits as configured by the Linux hostname
[info] Finished macro file config.g

though it seems like it is hanging, I'm heading out the door now, so ill have to see whats causing the hang up tomorrow, but this is a huge step forward. thank you again for the help.

JLM4751

@gtj0 so running duet control server with debug returns

mr_solderem@Duet3:~$ sudo /opt/dsf/bin/DuetControlServer -l debug
Duet Control Server v3.4.5
Written by Christian Hammacher for Duet3D
Licensed under the terms of the GNU Public License Version 3

[info] Settings loaded
[info] Environment initialized
[info] Connection to Duet established
[info] IPC socket created at /run/dsf/dcs.sock
[debug] Updated key limits
[debug] Requesting update of key boards, seq 0 -> 635
[debug] Updated key boards
[debug] Requesting update of key directories, seq 0 -> 0
[debug] Updated key directories
[debug] Requesting update of key fans, seq 0 -> 0
[debug] Updated key fans
[debug] Requesting update of key global, seq 0 -> 0
[debug] Updated key global
[debug] Requesting update of key heat, seq 0 -> 0
[debug] Updated key heat
[debug] Requesting update of key inputs, seq 0 -> 136
[debug] Updated key inputs
[debug] Requesting update of key job, seq 0 -> 5
[debug] Updated key job
[debug] Requesting update of key move, seq 0 -> 2
[debug] Updated key move
[debug] Requesting update of key network, seq 0 -> 2
[debug] Updated key network
[debug] Requesting update of key sensors, seq 0 -> 0
[debug] Updated key sensors
[debug] Requesting update of key spindles, seq 0 -> 0
[debug] Updated key spindles
[debug] Requesting update of key state, seq 0 -> 0
[debug] Updated key state
[debug] Requesting update of key tools, seq 0 -> 0
[debug] Updated key tools
[debug] Requesting update of key volumes, seq 0 -> 0
[debug] Updated key volumes
[debug] Requesting update of key inputs, seq 136 -> 138
[debug] Updated key inputs
[debug] Requesting update of key inputs, seq 138 -> 140
[debug] Updated key inputs
...
...
...
[debug] Requesting update of key inputs, seq [some high num] -> [some higher num]
[debug] Updated key inputs
repeat forever...

running sudo systemctl status duetwebserver returns

mr_solderem@Duet3:~$ sudo systemctl status duetwebserver
● duetwebserver.service - Duet Web Server
   Loaded: loaded (/usr/lib/systemd/system/duetwebserver.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

I noticed i was getting an error about my host name not matching the M550 assigned name so i changed it to "Duet 3" and that seemed to fix that, though I'm still not sure why duet web server still is not active. Any thoughts?

chrishamm

@JLM4751 It's disabled, you need to enable it via systemctl enable duetwebserver. I recommend you turn off debugging again in the DCS settings to avoid excessive logging during prints.

JLM4751

@chrishamm thanks Chris, sorry if that should have been obvious, Im still very new. which also makes me feel anxious having to ask this now. so after enabling duet web server and running "sudo systemctl status duetwebserver" I get the following. my question is why is it showing "inactive". thanks again for your help.

mr_solderem@Duet3:~$ sudo systemctl status duetwebserver
● duetwebserver.service - Duet Web Server
   Loaded: loaded (/usr/lib/systemd/system/duetwebserver.service; enabled; vendor preset: enabl
   Active: inactive (dead)

chrishamm

@JLM4751 No worries - you also need to start it via systemctl start duetwebserver. Then the web interface should be available. The enable command before ensures that the service is automatically started on boot but it doesn't start it right away.

JLM4751

once again thank you gtj0 and chrishamm, couldnt have done it without you.

Screenshot from 2023-06-20 14-28-40.png