Duet3/pi DCS is unavailable after wiring 24V
-
Oh, do make a note of what the speed was before reducing it.
grep "SpiFrequency" /opt/dsf/conf/config.json sed -i 's/^ "SpiFrequency": [0-9]*,/ "SpiFrequency": '500000',/' /opt/dsf/conf/config.json grep "SpiFrequency" /opt/dsf/conf/config.jsonshould give you
pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 8000000, pi@duet3:~ $ sed -i 's/^ "SpiFrequency": [0-9]*,/ "SpiFrequency": '500000',/' /opt/dsf/conf/config.json pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 500000, pi@duet3:~ $showing it changed from 8mhz to 500khz - if it works try increasing it until it stops working and back off say 1mhz.
if not, verify the board still does respond to
M122on the serial terminal, no sd card in the duet (should be clear from M122 output as well) and call in the cavalry. -
@bearer Hi,
Ok so today I tried on another RPi 4. Had to power the Duet back on VIN to supply enough juice for both the Duet and Pi, but still no luck. Even on the HDMI screen, shows DCS unavailable.
Spi Freq was:
pi@duet3:~ $ grep "SpiFrequency" /opt/dsf/conf/config.json "SpiFrequency": 2000000,Changed it to 500kHz
Still no luck.
Here's the M122 result.
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0 running on Duet 3 MB6HC Board ID: 08DJM-956L2-G43S4-6J9F6-3S86T-KA5LD Used output buffers: 1 of 32 (12 max) === RTOS === Static ram: 152720 Dynamic ram: 148548 of which 0 recycled Exception stack ram used: 308 Never used ram: 91640 Tasks: NETWORK(ready,1984) HEAT(blocked,1416) CanReceiv(suspended,3808) CanSender(suspended,1476) CanClock(blocked,1424) TMC(blocked,212) MAIN(running,3652) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:11:35 ago, cause: power up Last software reset at 2020-04-04 15:59, reason: User, spinning module LinuxInterface, available RAM 79620 bytes (slot 0) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 43.9, current 44.2, max 44.3 Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Driver 0: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 1: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 2: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 3: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 4: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 12938, writes 0 timeouts 0, SG min/max not available Date/time: 1970-01-01 00:00:00 Slowest loop: 0.28ms; fastest: 0.09ms === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 1 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is ready with "M122" in state(s) 0 aux is idle in state(s) 0 daemon* is idle in state(s) 0 0, running macro queue is idle in state(s) 0 lcd is idle in state(s) 0 spi is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.28ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 0 of 8 - Ethernet - State: 0 Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 0, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 695578ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 okSomething must be wrong with the board; it worked fine until I first powered it through VIN; I never shorted it either the fuses are mint.
Railcore II ZL
-
Maybe @dc42 can share some insight?
-
We hope to have new RRF 3.01RC7+DSF+DWC released later today, so probably best to wait for those.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
Changed it to 500kHz
I think mine was 8mhz, in any case when the update is published, be it to the stable or unstable list you'll get a prompt similar to, simplest approach would be to install the package maintainer's version and when that still doesn't work maybe try lowering the rate again (this way you find the new default without dealing with diffs and merging)
Configuration file '/opt/dsf/conf/config.json' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** config.json (Y/I/N/O/D/Z) [default=N] ? -
@dc42 @bearer
But shouldn't it work anyway on the stable release? RRF 3.0 is known to be working fine on raspberry Pi isn't it?
-
@fractalengineer Yes it should but in any case that will require a working SPI link between the Duet 3 and your SBC. From the RRF diagnostics I can see that this is not the case.
To be sure: You must not have a SD card in the Duet 3 to use the SBC interface. Are you sure there is none in the Duet?
Duet software engineer
-
@chrishamm said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
You must not have a SD card in the Duet 3 to use the SBC interface. Are you sure there is none in the Duet?
thats why I asked him to add the M122 output that shows no sd card.
-
No SD card in the duet 100%; only have one so it’s in the pi
-
anyways, update is live on the unstable package feed; so switch to that and update - fingers crossed
-
I rather suspect that you have a broken cable or a misconfigured SPI device - you should be seeing at least a few transfers from DSF in the RRF diagnostics. I'll get back to this.
Are you using DuetPi or the stock Raspbian image?
-
The output does indeed look identical to a (correctly configured) Pi without a Duet3 attached. (And yeah, DuetPi image confirmed)
-
@fractalengineer, we suspect a problem with either the Duet or the ribbon cable. However we would like you to try with the latest firmware first. @chrishamm is building a new firmware image, and will post to this thread when it is ready.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
@fractalengineer, we suspect a problem with either the Duet or the ribbon cable. However we would like you to try with the latest firmware first. @chrishamm is building a new firmware image, and will post to this thread when it is ready.
Got it; will try the image, thanks to you both for your answer.
I will check continuity on the ribbon in the meantime
Edit: All strands of the ribbon show continuity from one side to the other (tested by probing the sockets pins on the pi and duet)Railcore II ZL
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
I will check continuity on the ribbon in the meantime
measuring could provide enough pressure on pins to make a connection if poorly terminated connector, but still probaly a worth while test given shipping delays everywhere i suppose.
if you have some supplies you can roll your own; i wanted other stuff in there on the pi, but still a single connector on the Duet3 and the power grouped so mine is a little untraditional perhaps. Still 5 signals + 4 power is all you really need, 1:1 straight connection.
(can use a bunch of single wire female-female jumpers as well) -
@fractalengineer Please flash RRF 3.01-RC7 using bossa and this image on your SD card using Win32DiskImage or Etcher: https://pkg.duet3d.com/testing/image_2020-04-14-DuetPi.zip When you are done, please start the Pi, connect to it via SSH or open a terminal from an attached monitor, and send
sudo journalctl -u duetcontrolserver -e. Once done, please post the output here. -
@chrishamm Hi Chris, thank you for the image; I just completed all the steps, still no luck; same issue.
pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Apr 15 02:56:16 duet3 systemd[1]: duetcontrolserver.service: Succeeded. Apr 15 02:56:21 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Apr 15 02:56:21 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Apr 15 02:56:21 duet3 systemd[1]: Stopped Duet Control Server. Apr 15 02:56:22 duet3 systemd[1]: Started Duet Control Server. Apr 15 02:56:22 duet3 DuetControlServer[1737]: Duet Control Server v1.3.2 Apr 15 02:56:22 duet3 DuetControlServer[1737]: Written by Christian Hammacher fo Apr 15 02:56:22 duet3 DuetControlServer[1737]: Licensed under the terms of the G Apr 15 02:56:25 duet3 DuetControlServer[1737]: [info] Settings loaded Apr 15 02:56:25 duet3 DuetControlServer[1737]: [info] Environment initialized Apr 15 02:56:26 duet3 DuetControlServer[1737]: [fatal] Duet is not available Apr 15 02:56:26 duet3 systemd[1]: duetcontrolserver.service: Succeeded. Apr 15 02:56:31 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Apr 15 02:56:31 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Apr 15 02:56:31 duet3 systemd[1]: Stopped Duet Control Server. Apr 15 02:56:31 duet3 systemd[1]: Started Duet Control Server. Apr 15 02:56:32 duet3 DuetControlServer[1777]: Duet Control Server v1.3.2 Apr 15 02:56:32 duet3 DuetControlServer[1777]: Written by Christian Hammacher fo Apr 15 02:56:32 duet3 DuetControlServer[1777]: Licensed under the terms of the G Apr 15 02:56:35 duet3 DuetControlServer[1777]: [info] Settings loaded Apr 15 02:56:35 duet3 DuetControlServer[1777]: [info] Environment initialized Apr 15 02:56:36 duet3 DuetControlServer[1777]: [fatal] Duet is not available Apr 15 02:56:36 duet3 systemd[1]: duetcontrolserver.service: Succeeded.@bearer thanks; I probed the pins on the underside of the boards with the ribbon connected; that should validate good continuity through the ribbon and contact in the connectors?
Cheers
Railcore II ZL
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
@bearer thanks; I probed the pins on the underside of the boards with the ribbon connected; that should validate good continuity through the ribbon and contact in the connectors?
its hard to say other than "probably" and "maybe". but given the effort already made to troubleshoot i'd think the sensible thing is to replace both.
-
@bearer But is it really? I probed the pins directly on the board like so and they all showed continuity; that is the direct signal from one board to another
@chrishamm any feedback on the image result?
Thanks
-
@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
But is it really? I probed the pins directly on the board like so and they all showed continuity; that is the direct signal from one board to another
unless the probe exert no force on the board and connector, I'll stick to "probaly", or even "most likely" but at the end of the day it doesn't matter, the cable is a fraction of the cost of the board so just get both replaced for good measure even if its most likely not a cable fault.
