Duet3/pi DCS is unavailable after wiring 24V

chrishamm

Do you have a spare Raspberry Pi? If you can confirm proper connectivity between the Pi and the Duet 3, then the only option left is a damanged SPI controller on the Pi itself.

fractalengineer

@chrishamm We tried another pi on the previous board already, that's why I'm so confused

I can try again on the new one

A Former User

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

2-Flashed the board to 3.01 RC7 using Bossa

did you confirm the new firmware version with M115 or M122 after flashing?

(not that it'd matter, but they have released RC9 since last time.)

fractalengineer

@bearer yep

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC7 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-04-14b3

I'll try RC9 fwiw

Edit: Yeah RC9 no luck

A Former User

Not to make light of the situation, but I did say you should get the volcano insurance..

So you've tried new pi, new cable, new duet.

That leaves power supply?

fractalengineer

@bearer lol

Well so far I tried different USB ports, including the 3A charging port, and powersupply when powered through VIN is a brand new MeanWell 350W 24V

The 5 and 3.3V power lights on the Duet are on as they should when plugged in usb

A Former User

Unless you've got a scope or a logic analyzer I'm out of ideas; sorry.

fractalengineer

@bearer yes I'm looking forward to try another pi

One thing happened to me once on a quadcopter

It used a separate board for ESC connected to the flight controller board by pwm

One day I plugged in and one motor started acting funny; then after trying to connect to the firmware front end it got worse, and eventually, the flight controller became unresponsive.

A couple messages back and forth with the FC designer (used an STM32 F7 chip; wasn't junk) he told me he had experiences of shorts happening on the ESC, running back to the FC board and frying sectors of the chip

Anyway I have no clue what's going on, but if anything I would like to try if there's a possibilty something on the old board may have fried the SPI capability of my pi on top of it's own

New duet and new pi must do something

Danal

@fractalengineer said:

pi@duet3:~ $ apt list 2>/dev/null | grep duet
duetsoftwareframework/now 1.3.2 armhf [installed,local]

Flashed the board to 3.01 RC7 using Bossa

I believe those two won't talk to each other. I would do a standard

sudo apt update
sudo apt upgrade

And let the system move itself to DSF 2.1.0. That should fix things... but... it may not be able to auto-flash the board.

If, after the update/upgrade, your apt-list shows duetsoftwareframework/now 2.1.0 armhf [installed,local], and things are still not working, then bossa the board with the file /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin
If, after the update/upgrade, your apt list shows anything else for DSF itself, ask again here.

You are very close. We'll get you going.

fractalengineer

@Danal Thank you;

So I just updated the packages and I saw this message while it was running: (line 4)

Setting up duetwebserver (2.1.0) ...
Setting up git (1:2.20.1-2+deb10u3) ...
Setting up reprapfirmware (2.1.0-1) ...
[fatal] Duet is not available
Setting up rpi-eeprom (5.8-1) ...
Setting up duetsoftwareframework (2.1.0) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...

pi@duet3:~ $ apt list 2>/dev/null | grep duet
duetcontrolserver/unstable,now 2.1.0 armhf [installed,automatic]
duetruntime/unstable,now 2.1.0 armhf [installed,automatic]
duetsd/unstable,now 1.0.6 all [installed,automatic]
duetsoftwareframework/unstable,now 2.1.0 armhf [installed]
duettools/unstable,now 2.1.0 armhf [installed,automatic]
duetwebcontrol/unstable,now 2.1.4 all [installed,automatic]
duetwebserver/unstable,now 2.1.0 armhf [installed,automatic]

Still not working.

I can't find this location /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin But the board is already flashed in 3.01 RC9.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC9 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-04-21b1

I'll borrow my friend's pi 4 in a couple hours; keep you posted

fractalengineer

Man I don't get it anymore...

On the other Pi the wifi now doesn't work; I triple checked the wpa supplicant and it still won't show on network

Meanwhile, even through the HDMI it still shows DCS not started

Halp

A Former User

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

On the other Pi the wifi now doesn't work

i'm sure we can figure that out, maybe do a new thread after having tested the new pi

Danal

Progress! Clearly upgraded to 2.1.0

Line 4 I sort of expected. That is why we may need to bossa the board one more time. 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 /opt/dsf
ls /opt/dsf/sd
ls /opt/dsf/sd/sys

And post the results here?

Danal

Chris built your image, so the following SHOULD be OK, but just for triple-check:

Run
sudo raspi-config

Navigate to 5 Interface options
Go to P4 SPI
Confirm to enable the SPI interface

Once done, run ls /dev/spidev*and verify that /dev/spidev0.0 exists.

Then run this command:

echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.conf

And reboot

A Former User

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

Chris built your image, so the following SHOULD be OK, but just for triple-check:
Run
sudo raspi-config

Navigate to 5 Interface options
Go to P4 SPI
Confirm to enable the SPI interface
Once done, run ls /dev/spidev*and verify that /dev/spidev0.0 exists.

Then run this command:
echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.conf
And reboot

no need. DCS specifically says

[error] Failed to connect to Duet
   System.IO.IOException: Error 2. Can not open SPI device file '/dev/spidev0.0'.

if thats the case; the shown error Duet not available as such confirms the SPI device is accessible.

Danal

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

A Former User

@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 available which 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)

Danal

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

I don't believe we have proof either way that is correct.

A Former User

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

Danal

Got it. Thanks!