Duet 2 Ethernet and SBC
-
ah ok. you already orderd it
I just see that the Boards from @deadwood83 still have R1 and R2 in place in the easyeda files -
@arhi Fair enough
-
@smoki3 said in Duet 2 Ethernet and SBC:
Any news about a firmware fix for SBC and Duex5?
Sorry, no news yet. Once I finish the PanelDueFirmware 3.2 release (hopefully the coming week) I will get back to investigating the problem with DueX attached. Though since I last tested a lot has happened in the firmware. Have you tested RRF 3.2-beta1? Is it still broken?
-
Testet today again with latest official release.
Still not able to home all axis at once (simple G28 command). The printer hang forever.
All axis are homes with stall detection.Firmware flashing now seams to work well.
Sometimes homing is working now. I will try a print later
-
30.9.2020, 08:31:36 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)This is what I get when trying to start a print. It happens when the first move is requested
Tried it a few times. Always the same issue
-
@smoki3 Thanks for reporting back the current state. I hope to get back to this sooner than later but I need to rearrange my hardware chaos on my desk.
-
arrived ... few days over 2 weeks, looks like I'm going to be using this jlcpcbp in future
I'm satisfied with the results. @oliof one packed for you will be sent tomorrow so you can test, my hand is still in bad shape so not sure I'll be able to solder the headers these days so you might get to test it before me paneldue connector is in the way so is the probe connector, they are high so the normal headers won't work if I do not remove those two connectors... this is bad, but for the test it will be ok as I do not need the paneldue with sbc and I can live without probing for the test
but next iteration should solve this, for now I'll just use the "Double length" pinheaders so I can test it.The board is also covering the piece of the expansion port but since duet+sbc don't work with duex if I understood correctly that;s also not a big deal but I might make a cutout for that too
-
got the 7yo to help me solder this, one handed soldering is a ^#^#%*)^#@ .. anyhow another issue, the excess pcb I left to not have sbc connector right on the edge (kill me why) is a problem with a heatsink .. not a huge issue but something to be aware ..
good thing is with these long headers I can easily attach probes to sniff signals if required
-
so far, not working
RepRapFirmware for Duet 2 + SBC Version 3.2-beta2 dated 2020-10-05b2 Executing config.g... Error: Networking is not supported on this hardware Error: Networking is not supported on this hardware Error: Networking is not supported on this hardware Error: Networking is not supported on this hardware Warning: Sensor numbClearly I need to remove networking stuff from the config but I doubt that's a too big of a deal, dunno if I need to add something for the SBC ?
Oct 05 20:34:35 raspberrypi systemd[1]: Started Duet Control Server. Oct 05 20:34:36 raspberrypi DuetControlServer[782]: Duet Control Server v3.2.0-beta2 Oct 05 20:34:36 raspberrypi DuetControlServer[782]: Written by Christian Hammacher for Duet3D Oct 05 20:34:36 raspberrypi DuetControlServer[782]: Licensed under the terms of the GNU Public License Version 3 Oct 05 20:34:37 raspberrypi DuetControlServer[782]: [info] Settings loaded Oct 05 20:34:37 raspberrypi DuetControlServer[782]: [info] Environment initialized Oct 05 20:34:38 raspberrypi DuetControlServer[782]: [fatal] Could not connect to Duet (Board is not available (no header)) Oct 05 20:34:38 raspberrypi systemd[1]: duetcontrolserver.service: Succeeded. Oct 05 20:34:43 raspberrypi systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart. Oct 05 20:34:43 raspberrypi systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 7. Oct 05 20:34:43 raspberrypi systemd[1]: Stopped Duet Control Server.I didn't edit any config, only thing I did is increase SPI buffer to 8k on the pi
will hook up the scope in a bit
-
M122 "DSF" === Diagnostics === RepRapFirmware for Duet 2 + SBC version 3.2-beta2 running on Duet 2 1.02 or later + SBC (standalone mode) Board ID: 08DJM-9178L-L4MSN-6J9F0-3S46J-KT16P Used output buffers: 1 of 24 (10 max) === RTOS === Static ram: 23252 Dynamic ram: 78280 of which 4920 recycled Exception stack ram used: 256 Never used ram: 24364 Tasks: HEAT(blocked,365) MAIN(running,427) IDLE(ready,19) Owned mutexes: USB(MAIN) === Platform === Last reset 00:09:17 ago, cause: software Last software reset time unknown, reason: User, GCodes spinning, available RAM 22932, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0x00 MCU temperature: min 31.3, current 31.7, max 32.2 Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no Driver 0: position 0, ok, SG min/max not available Driver 1: position 0, ok, SG min/max not available Driver 2: position 0, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 1970-01-01 00:00:00 Cache data hit count 946232882 Slowest loop: 5.29ms; fastest: 0.11ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 12.0MBytes/sec SD card longest read time 0.8ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 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 USB is ready with "M122 "DSF"" in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. ok -
@arhi said in Duet 2 Ethernet and SBC:
SD card 0 detected, interface speed: 12.0MBytes/sec
try without the sd card or config.g on the card?
-
@bearer said in Duet 2 Ethernet and SBC:
try without the sd card or config.g on the card?
that did it
Connection to Linux established! Executing config.g... Done! RepRapFirmware for Duet 2 + SBC is up and running.Oct 05 20:58:02 raspberrypi systemd[1]: Started Duet Control Server. Oct 05 20:58:03 raspberrypi DuetControlServer[698]: Duet Control Server v3.2.0-beta2 Oct 05 20:58:03 raspberrypi DuetControlServer[698]: Written by Christian Hammacher for Duet3D Oct 05 20:58:03 raspberrypi DuetControlServer[698]: Licensed under the terms of the GNU Public License Version 3 Oct 05 20:58:04 raspberrypi DuetControlServer[698]: [info] Settings loaded Oct 05 20:58:04 raspberrypi DuetControlServer[698]: [info] Environment initialized Oct 05 20:58:04 raspberrypi DuetControlServer[698]: [info] Connection to Duet established Oct 05 20:58:05 raspberrypi DuetControlServer[698]: [info] IPC socket created at /var/run/dsf/dcs.sock Oct 05 20:58:05 raspberrypi DuetControlServer[698]: [info] Starting macro file config.g on channel Trigger Oct 05 20:58:06 raspberrypi DuetControlServer[698]: [error] M550: Machine name must consist of the same letters and digits as configured by the Linux hostname Oct 05 20:58:06 raspberrypi DuetControlServer[698]: [info] Finished macro file config.gwhere is the "filesystem" now for the duet on the sbc?
any script to "test the communication" ?
Connection to Linux established! Executing config.g... Done! RepRapFirmware for Duet 2 + SBC is up and running. M122 "DSF" === Diagnostics === RepRapFirmware for Duet 2 + SBC version 3.2-beta2 running on Duet 2 1.02 or later + SBC (SBC mode) Board ID: 08DJM-9178L-L4MSN-6J9F0-3S46J-KT16P Used output buffers: 1 of 24 (11 max) === RTOS === Static ram: 23252 Dynamic ram: 99132 of which 20 recycled Exception stack ram used: 292 Never used ram: 8376 Tasks: Linux(ready,71) HEAT(blocked,370) MAIN(running,399) IDLE(ready,19) Owned mutexes: USB(MAIN) === Platform === Last reset 00:03:10 ago, cause: software Last software reset time unknown, reason: User, GCodes spinning, available RAM 24332, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0x00 MCU temperature: min 41.4, current 41.9, max 42.2 Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no Driver 0: position 0, ok, SG min/max not available Driver 1: position 0, ok, SG min/max not available Driver 2: position 0, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2020-10-05 21:00:22 Cache data hit count 430062158 Slowest loop: 135.58ms; fastest: 0.10ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 30.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 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 USB is ready with "M122 "DSF"" in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === SBC interface === State: 0, failed transfers: 0 Last transfer: 20ms ago RX/TX seq numbers: 4497/4498 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 ok -
@arhi said in Duet 2 Ethernet and SBC:
where is the "filesystem" now for the duet on the sbc?
/opt/dsf/sd/and f.ex./opt/dsf/sd/sys/config.g -
This post is deleted! -
missed the second part of the https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3 page
sorry .. everything works ... so must boot duet2 without sd card to work with sbc - great
-
@arhi said in Duet 2 Ethernet and SBC:
so must boot duet2 without sd card to work with sbc - great
or remove/rename
sys/config.g- sd card in itself isn't a problem, but valid config file is. -
@bearer yes, but in that case better remove the card completely
is the "simulate job" doing some spi communication here talking between sbc and duet or is executed on the sbc only? I connected everything on my spare duet that's not in any of the printers so simulation is the best I can do (running one 50MB file right now)
-
@arhi said in Duet 2 Ethernet and SBC:
anyhow another issue, the excess pcb I left to not have sbc connector right on the edge (kill me why) is a problem with a heatsink .. not a huge issue but something to be aware ..
could you get away with using a regular right angle connector and solder it smd style to pads on the top and bottom of the board?
-
started simulation (2%)
M122 === Diagnostics === RepRapFirmware for Duet 2 + SBC version 3.2-beta2 running on Duet 2 1.02 or later + SBC (SBC mode) Board ID: 08DJM-9178L-L4MSN-6J9F0-3S46J-KT16P Used output buffers: 1 of 24 (11 max) === RTOS === Static ram: 23252 Dynamic ram: 100992 of which 40 recycled Exception stack ram used: 292 Never used ram: 6496 Tasks: Linux(ready,59) HEAT(blocked,135) MAIN(running,435) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:04:56 ago, cause: software Last software reset at 2020-10-05 21:21, reason: User, none spinning, available RAM 6580, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task Linu Error status: 0x00 MCU temperature: min 31.9, current 32.1, max 32.5 Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no Driver 0: position -3403, ok, SG min/max not available Driver 1: position -122, ok, SG min/max not available Driver 2: position 5600, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2020-10-05 21:26:52 Cache data hit count 643706022 Slowest loop: 128.72ms; fastest: 0.12ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 30.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 130ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 35273, completed moves: 35273, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is ready with "G1 X-41.571999 Y-2.496000 E0.125000" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: no data received === SBC interface === State: 0, failed transfers: 0 Last transfer: 6ms ago RX/TX seq numbers: 8893/8895 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 72/552-0 === Duet Control Server === Duet Control Server v3.2.0-beta2 File: Buffered code: G1 X-41.835 Y0.737 E0.0751 Buffered code: G1 X-42.029 Y0.931 E0.0251 Buffered code: G1 X-42.025 Y0.993 E0.0057 Buffered code: G1 X-41.947 Y1.264 E0.0259 Buffered code: G1 X-41.938 Y1.313 E0.0045 Buffered code: G1 X-41.883 Y1.592 F4200 Buffered code: G1 X-41.874 Y1.623 Buffered code: G1 X-41.784 Y1.676 Buffered code: G1 X-41.728 Y1.620 Buffered code: G1 X9.712 Y-0.323 F9000 Buffered code: G1 X9.775 Y-0.386 E0.0082 F4200 Buffered code: G1 X10.561 Y-0.698 E0.0775 Buffered code: G1 X10.830 Y-0.827 E0.0274 Buffered code: G1 X12.013 Y-1.633 E0.1312 Buffered code: G1 X11.223 Y-0.844 E0.1024 Buffered code: G1 X11.562 Y-0.957 E0.0327 Buffered code: G1 X11.968 Y-1.178 E0.0424 Buffered code: G1 X12.814 Y-1.444 E0.0813 Buffered code: G1 X13.857 Y-2.487 E0.1352 Buffered code: G1 X14.666 Y-2.525 E0.0743 Buffered code: G1 X14.851 Y-2.491 E0.0172 Buffered code: G1 X14.101 Y-1.742 E0.0971 Buffered code: G1 X14.761 Y-1.806 E0.0608 ==> 1088 bytes Code buffer space: 2552 Configured SPI speed: 8000000 Hz Full transfers per second: 29.92 File /opt/dsf/sd/gcodes/belly-4-repaired.gcode is selected, processing, simulating50%
M122 === Diagnostics === RepRapFirmware for Duet 2 + SBC version 3.2-beta2 running on Duet 2 1.02 or later + SBC (SBC mode) Board ID: 08DJM-9178L-L4MSN-6J9F0-3S46J-KT16P Used output buffers: 1 of 24 (20 max) === RTOS === Static ram: 23252 Dynamic ram: 100992 of which 40 recycled Exception stack ram used: 292 Never used ram: 6496 Tasks: Linux(ready,31) HEAT(blocked,135) MAIN(running,435) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 01:05:19 ago, cause: software Last software reset at 2020-10-05 21:21, reason: User, none spinning, available RAM 6580, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task Linu Error status: 0x00 MCU temperature: min 31.8, current 32.7, max 33.1 Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no Driver 0: position 1514, ok, SG min/max not available Driver 1: position -4643, ok, SG min/max not available Driver 2: position 183680, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2020-10-05 22:27:15 Cache data hit count 4294967295 Slowest loop: 157.10ms; fastest: 0.11ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 30.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 217ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 813549, completed moves: 813549, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is ready with "G1 X18.978001 Y-58.014999 E0.005600" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: no data received === SBC interface === State: 0, failed transfers: 0 Last transfer: 9ms ago RX/TX seq numbers: 52153/52155 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 1008/1512-0 === Duet Control Server === Duet Control Server v3.2.0-beta2 File: Buffered code: G1 X19.514 Y-57.642 E0.0406 Buffered code: G1 X20.322 Y-57.460 E0.0759 Buffered code: G1 X20.667 Y-57.806 E0.0447 Buffered code: G1 X21.102 Y-57.712 E0.0408 Buffered code: G1 X21.441 Y-57.589 E0.0330 Buffered code: G1 X21.008 Y-57.156 E0.0561 Buffered code: G1 X21.162 Y-57.084 E0.0156 Buffered code: G1 X21.778 Y-56.936 E0.0581 Buffered code: G1 X22.168 Y-57.326 E0.0506 Buffered code: G1 X22.516 Y-57.201 E0.0339 Buffered code: G1 X22.527 Y-57.198 E0.0010 Buffered code: G1 X22.875 Y-57.043 E0.0349 Buffered code: G1 X22.570 Y-56.738 E0.0396 Buffered code: G1 X22.922 Y-56.598 E0.0347 Buffered code: G1 X23.303 Y-56.482 E0.0366 Buffered code: G1 X23.569 Y-56.747 E0.0344 Buffered code: G1 X24.290 Y-56.479 E0.0706 Buffered code: G1 X24.049 Y-56.237 E0.0313 ==> 860 bytes Pending code: G1 X24.257 Y-56.166 E0.0202 Pending code: G1 X24.765 Y-55.963 E0.0501 Pending code: G1 X25.017 Y-56.216 E0.0327 Pending code: G1 X25.163 Y-56.167 E0.0141 Pending code: G1 X25.760 Y-55.969 E0.0577 Pending code: G1 X25.471 Y-55.680 E0.0375 Pending code: G1 X25.906 Y-55.483 E0.0437 Code buffer space: 1868 Configured SPI speed: 8000000 Hz Full transfers per second: 30.03 File /opt/dsf/sd/gcodes/belly-4-repaired.gcode is selected, processing, simulatingduring simulation:
-
@bearer said in Duet 2 Ethernet and SBC:
could you get away with using a regular right angle connector and solder it smd style to pads on the top and bottom of the board?
yes, that would work but I hate those comb soldering + it would require thicker board to properly work, also I don't think I ever seen 90 degree female double header, usually male is 90 degree and we need female here.
Thing is, there's nothing important between connector and edge of the board, I can just move the connector closer to the edge (cut the edge closer to connector) but for now it's not a big deal since I just used another rpi that does not have active cooler on it and the passive heatsinks are more than enough as this will be in a box with duet that will have active cooling anyhow so air movement will happen for sure
... also, dunno when plugins will come but for now load is very low so rpi is rather cold
