Omg, I can’t believe it. I somehow managed to plug in EXP2 into the Duet 3 Mini 5+ reversed (it’s dark back there) and I also didn’t think I needed the M150 command. Fixed those and now it works.
Best posts made by blt3dp
-
RE: BigtreeTech MINI 12864 V1.0 - Duet 3 Mini 5+
-
RE: Duet 3 Mini 5+ and Loud Hiss from Z Motor
Well, LOL. I ended up cutting the leadscrew off of the "bad" motor and attached it to the other motor I had tested with. It's completely silent now.
-
RE: Multiple temp sensors report open when using resistor
I believe @droftarts was going down the correct path. Looks like you're running RRF 2.05.1 but the sensors/heaters excerpt you posted was for a RRF 3 config.
Try replacing your heaters section with this.
; Heaters M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C
Also 4138 for your bed thermistor is probably wrong.
-
RE: Voron-0 Display to Duet Mini 5+
@wayneosdias @jay_s_uk, I think we might be talking about different BTT screens. The one I'm using successfully, after tweaking the menu files to my liking is this one.
It's basically a standard non touch screen, 12864 display using a ST7567 controller
@R4ffers, thanks, looks like I'll be doing the upgrade to a v0.2, I'll probably tweak something to fit afterwards.
-
RE: Here's my printable optical encoder wheel filament sensor!
I’ve been looking to add something like this to my printers for a while. I was wondering if maybe a non-printed wheel might improve things. Thinking it’d take out any potential inconsistencies that may exist using a printed part.
Maybe something like this?
https://www.adafruit.com/product/3782?gclid=EAIaIQobChMIoajljtm37wIVaR-tBh3jyAO0EAQYAiABEgIQAvD_BwE -
RE: Duet 3 DCS not starting and unresponsive Duet
What’s it look like if you don’t have the usb on the Duet connected to anything? You don’t need it at all for it to work. What Vin are you supplying the Duet, how is the Pi being powered and how are 5v jumpers set on the Duet? Also, no as card in the Duet, correct?
Edit: I see no sd card in the Duet, you should only have one in the pi. Looks like you have 5v enable and Duet —> SBC set. All you should need is the ribbon cable between the Duet and Pi. I’d pull the usb cable and confirm the 26 pin cable is connected correctly. DCS is complaining the transfer pin isn’t ready.
-
RE: How to change something in file resurrect.g?
How are you testing? Manually pausing or pulling the power? If your pausing it, what you're looking for might be in pause.g pause.g
-
RE: Upgrading to RFF 3.0RC2 issues
I'm having issues with this too. I think the documentation is lacking. I don't believe uploading stuff like new firmware applies to us anymore.
The documentation on github states:
You should also upload the new IAP file for your system. You will need it when upgrading firmware in future. These files are called Duet2CombinedIAP.bin, DuetMaestroIAP.bin, Duet3_SBCiap_MB6HC.bin (for Duet 3+SBC)
For the Duet and PI combination, you would believe that we should use Duet3_SBCiap_MB6HC.bin
But it's not one of the files in the releases.I had been told that the updated firmware is installed when you update the duetsoftwareframework package on the pi using the unstable branch on the package server (since it is RC)
Which did successfully update to the most current at the time, which was 3.0RC1
But now that RC2 is out, I'd like to update to it and when I go to update duetsoftwareframework it states it's already up to date.
I'd like cleared documentation on how to actually upgrade the firmware on a Duet+SBC machine.
For your issues, to get you a little closer,
SSH into your pi and and run these to get the unstable repository
wget -q https://pkg.duet3d.com/duet3d.gpg wget -q https://pkg.duet3d.com/duet3d-unstable.list sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/ sudo mv duet3d-unstable.list /etc/apt/sources.list.d/duet3d-unstable.list sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg sudo chown root:root /etc/apt/sources.list.d/duet3d-unstable.list
Then do
apt-get update apt-get upgrade duetsoftwareframework
Edit: in your original post
/opt/dsf/sd/sys/
Instead of doing it via the web interface, maybe put it into that location on the pi directly?
-
RE: Smart Effector separating heatsink fan from LEDs
Thanks, I did see that part of the schematic, just wanted to double check and see what i figured was correct.
-
RE: Smart Effector delta auto calibration speed
You're not sending G29 or G32 while the towers are homed are you? Generally what I do is G28 to home all towers. Then move the nozzle down manually, it will respect that movement speed. I usually do something link G0 X0 Y0 Z5 F1800. Then I will do a G30 to make it aware of the zero point. Then you do your G32 or G29. I don't really use G29, I couldn't tell you about its use.
Latest posts made by blt3dp
-
RE: SE unable to probe portions of bed
Could this have been the feedrate too low? Not sure where I got F300 from, but I bumped it to 1200 and it seems to be working.
-
SE unable to probe portions of bed
I'm having a problem with the Smart Effector.
Of course a Delta, running a MB6HC in SBC mode with RRF 3.4.6
It triggers properly when tapped, is able to perform a G30 without issue, but when I go to do a G32, it is able to probe some spots but not others. It just crashes into the bed.
The machine is able to move to all the probing points without problem, doesn't seem to be a problem with anything interfering with motion.
I originally had an SE v2 and my cable bundle too tight and i found it was pulling on the wires. I went ahead and rewired the whole thing, ensured crimps are good and there is plenty of slack and the cables are pretty flexible. I'm pretty sure that's not the issue.
I just swapped over to a SE v4 thinking it was a problem with the actual SE, maybe some solder joints got broke or something from the previous cable pulling. This forced me to rewire it with the JST PH connector. I bought pre-crimped cables and housing. I connected it all up and it is still the same.
I thought to adjust the sensitivity but when I send M672 S105:050:255, I don't get flashes on the SE
But I can send the reset M672 S131:131 and I get the proper 5 flashes
It's still the same after a reboot.Any ideas? Here's my config.g
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.4 on Tue Dec 24 2019 21:00:59 GMT-0800 (PST) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Delta" ; set printer name M665 R179.423 L360.250 B150.000 H368.045 ; set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X200.00 Y200.00 Z200.00 E415 ; set steps per mm - Bondtech M566 X600.00 Y600.00 Z600.00 E2400.00 ; set maximum instantaneous speed changes (mm/min) M203 X15000.00 Y15000.00 Z2400.00 E2400.00 ; set maximum speeds (mm/min) M201 X3000.00 Y3000.00 Z3000.00 E7200.00 ; set accelerations (mm/s^2) M906 X1700 Y1700 Z1700 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"io1.in" ; configure active-high endstop for high end on X via pin io1.in M574 Y2 S1 P"io2.in" ; configure active-high endstop for high end on Y via pin io2.in M574 Z2 S1 P"io3.in" ; configure active-high endstop for high end on Z via pin io3.in ; Z-Probe M558 P8 R0.4 C"io4.in+io4.out" H5 F300 T1800 ; set Z probe type to effector and the dive height + speeds G31 P100 X0 Y0 Z-0.1 ; set Z probe trigger value, offset and trigger height M557 R110 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3590 R2200 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 Q10 ; create bed heater output on out0 and map it to sensor 0 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 R0.241 C905.6 D22.78 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 R3.597 K0.426:0.000 D2.66 E1.35 S1.00 B0 ; disable bang-bang mode for the nozzle heater and set PWM limit ; Fans M950 F0 C"out7" Q75 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 B0.5 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency M106 P2 C"LEDs" S0 H-1 ; set fan 2 name and value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets M568 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings M575 P1 S1 B57600 ; enable support for PanelDue M207 S4.5 F2400 Z0.40 ; set firmware retraction length, speed and z-lift M572 D0 S0.0 ; set pressure advance ; Miscellaneous M911 S21.9 R22.9 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
-
RE: daemon.g failed to parse major G-code number (lobal)
Looks like it only happens when I reload the page.
-
daemon.g failed to parse major G-code number (lobal)
Running Duet 3 6HC in SBC mode w/3.5.0-beta.4 (RRF, DSF, DWC) and have a daemon.g setup. Maybe I'm missing something, but I'm receiving this message whenever the daemon.g runs. More specifically, it's line 6 that it mentions.
Here's daemon.g
; daemon.g if global.ledToggle == 1 && {state.status} == "idle" M150 E0 R255 U255 B255 P128 S174 ; white set global.ledToggle = 2 elif global.ledToggle >= 1 && {state.status} == "processing" M150 E0 R0 U255 B0 P128 S174 ; green else ; do nothing
The global variable ledToggle is defined in config.g
global ledToggle = 0
And it's toggled 1 or 0 via a macro.
Any ideas on what might be the cause?Also here's an M122
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.0 or earlier (SBC mode) Board ID: 08DGM-9T66A-G63SJ-6JTDL-3SD6P-TS0HA Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 155012 Dynamic ram: 80988 of which 2904 recycled Never used RAM 103128, free system stack 134 words Tasks: ACCEL(6,nWait,0.0%,348) SBC(2,rWait:,1.2%,390) HEAT(3,nWait,0.0%,323) Move(4,nWait,3.5%,218) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,9.2%,61) MAIN(2,running,86.0%,444) IDLE(0,ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 02:46:14 ago, cause: software Last software reset at 2023-08-24 16:24, reason: User, Gcodes spinning, available RAM 103032, slot 1 Software reset code 0x6803 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU temperature: min 38.0, current 38.3, max 38.7 Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0 Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1788/1752, gc cycles 10 Events: 0 queued, 0 completed Driver 0: ok, SG min 0, mspos 280, reads 6760, writes 0 timeouts 0 Driver 1: ok, SG min 0, mspos 917, reads 6759, writes 0 timeouts 0 Driver 2: ok, SG min 0, mspos 583, reads 6760, writes 0 timeouts 0 Driver 3: standstill, SG min 0, mspos 200, reads 6760, writes 0 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 6760, writes 0 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 6760, writes 0 timeouts 0 Date/time: 2023-08-24 19:10:33 Slowest loop: 4.28ms; fastest: 0.07ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 46, maxWait 767ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 1.00 next step interrupt due in 17 ticks, disabled === DDARing 0 === Scheduled moves 833246, completed 833225, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.5 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X-68.708000 Y48.910000 E0.602210" 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 File2* is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 1, axes/extruders owned 0x80000007 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 11055, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 6142/0/0 Tx timeouts 0,0,6142,0,0,4913 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 27704/27704 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x25ce8 Buffer RX/TX: 1836/3284-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-beta.4 (2023-06-09 10:49:49) File /opt/dsf/sd/gcodes/Saved_G-codes/filename_sanitized.gcode is selected, processing File: Buffered code: G1 X-68.708 Y48.91 E0.60221 Buffered code: G1 X-68.708 Y51.787 E0.09021 Buffered code: G1 X-49.501 Y51.787 E0.60221 Buffered code: G1 X-49.501 Y52.254 E0.01462 Buffered code: G1 X-46.624 Y52.254 E0.09021 Buffered code: G1 X-46.624 Y54.664 E0.07559 Buffered code: G1 X-68.708 Y54.664 E0.69242 Buffered code: G1 X-68.708 Y57.075 E0.07558 Buffered code: G1 X-51.445 Y57.075 E0.54125 Buffered code: G1 X-51.445 Y57.542 E0.01463 Buffered code: G1 X-46.462 Y57.542 E0.15625 Buffered code: G10 ; retract Buffered code: G1 X-5.668 Y57.542 F15000 Buffered code: G11 ; unretract Buffered code: G1 F4320 Buffered code: G1 X-5.668 Y54.874 E0.08363 Buffered code: G1 X-2.791 Y54.874 E0.09021 Buffered code: G1 X-2.791 Y51.997 E0.09021 Buffered code: G1 X0.086 Y51.997 E0.09021 Buffered code: G1 X0.086 Y49.12 E0.09021 Buffered code: G1 X2.963 Y49.12 E0.09021 Buffered code: G1 X2.963 Y46.243 E0.09021 Buffered code: G1 X5.84 Y46.243 E0.09021 Buffered code: G1 X5.84 Y43.366 E0.09021 Buffered code: G1 X8.717 Y43.366 E0.09021 Buffered code: G1 X8.717 Y40.489 E0.09021 Buffered code: G1 X14.471 Y40.489 E0.18042 Buffered code: G1 X14.471 Y37.612 E0.09021 Buffered code: G1 X22.682 Y37.612 E0.25746 Buffered code: G1 X22.682 Y40.069 E0.07704 Buffered code: G1 X19.805 Y40.069 E0.09021 Buffered code: G1 X19.805 Y42.946 E0.09021 Buffered codes: 1472 bytes total Code buffer space: 1836 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 53.48, max time between full transfers: 58.8ms, max pin wait times: 45.3ms/7.3ms Codes per second: 109.58 Maximum length of RX/TX data transfers: 4560/3172
-
RE: does not completely finish the last layer of the print 3.5.0-b4
I noticed this same symptoms. Job would complete and complete all my end gcode, heaters would be off, head positioned as requested. But web interface would still say printing. I noticed that I’d I closed my browser, cleared the cache with just google loaded, then launched dwc and it showed normal.
-
RE: RRF 3.5 beta 4 not respecting axis limits
True, that particular job took up much of the print bed but not enough to push it past the printable radius. I think my main concern is with manually moving the effector and crashing things hanging off the effector like fans into the belts and towers.
I guess my point would be, say a company wanted to use Duets in their delta printers sold commercially to end users, yet wanted to prevent any scenario like I described above, shouldn’t that be possible?
-
RE: RRF 3.5 beta 4 not respecting axis limits
Understood with M208,
But isn't the B value in M665 supposed to be a safe printing limit? From center I would expect either gcode moves or manual moves to not be able to move any farther than that limit. Regardless if the delta radius and arm length physically allow it, if I'm limiting it to less than, it should respect that no?
-
RRF 3.5 beta 4 not respecting axis limits
Hi, have a Delta with Duet 3 MB6HC in SBC mode w/Raspberry Pi 4 running RRF 3.5 beta 4 and I noticed today that It's not respecting the machine limits.
This is after it's been homed as well as G30, G32 has not been run
This is my M665 command which sets the radius to 150mm. Doing a pure X or Y move lets me go beyond that 150mm
M665 R179.423 L360.250 B150.000 H368.045
Here's M450, M208 and M564
Also here's M122, it's printing right now.
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.0 or earlier (SBC mode) Board ID: 08DGM-9T66A-G63SJ-6JTDL-3SD6P-TS0HA Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 155012 Dynamic ram: 80940 of which 2976 recycled Never used RAM 103536, free system stack 136 words Tasks: ACCEL(6,nWait,0.0%,263) SBC(2,rWait:,1.9%,422) HEAT(3,nWait,0.1%,323) Move(4,nWait,0.2%,224) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,18.6%,61) MAIN(2,running,79.2%,444) IDLE(0,ready,0.1%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 02:53:17 ago, cause: software Last software reset at 2023-08-02 21:05, reason: User, Expansion spinning, available RAM 107088, slot 2 Software reset code 0x6012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,1,0 MCU temperature: min 36.2, current 39.0, max 39.6 Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0 Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/28/4, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min 0, mspos 986, reads 10489, writes 101 timeouts 0 Driver 1: ok, SG min 0, mspos 972, reads 10489, writes 101 timeouts 0 Driver 2: ok, SG min 0, mspos 932, reads 10489, writes 101 timeouts 0 Driver 3: ok, SG min 0, mspos 754, reads 10569, writes 21 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 10579, writes 11 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 10579, writes 11 timeouts 0 Date/time: 2023-08-02 23:58:43 Slowest loop: 92.65ms; fastest: 0.06ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 28, maxWait 4419377ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 1.00 next step interrupt due in 31 ticks, disabled === DDARing 0 === Scheduled moves 8432, completed 8429, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 76], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.5 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X-55.341000 Y-132.442001 E0.010550" 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 File2* is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 1, axes/extruders owned 0x80000003 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 93566, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 51988/0/0 Tx timeouts 0,0,51987,0,0,41577 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 19497/19497 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x25ce8 Buffer RX/TX: 192/1704-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-beta.4 (2023-06-09 10:49:49) File /opt/dsf/sd/gcodes/frieza_base.gcode is selected, processing File: Buffered code: G1 X-55.341 Y-132.442 E.01055 Buffered code: G1 X-15.511 Y143.707 E14.62679 Buffered code: G1 X-15.052 Y143.737 E.02411 Buffered code: G1 X-54.903 Y-132.56 E14.63462 Buffered code: G1 X-54.476 Y-132.754 E.02459 Buffered code: G1 X-14.592 Y143.767 E14.64649 Buffered code: G1 X-14.132 Y143.797 E.02417 Buffered code: G1 X-54.047 Y-132.938 E14.65783 Buffered code: G1 X-53.613 Y-133.088 E.02407 Buffered code: G1 X-13.671 Y143.836 E14.66784 Buffered code: G1 X-13.208 Y143.89 E.02444 Buffered code: G1 X-53.181 Y-133.251 E14.67933 Buffered code: G1 X-52.939 Y-133.352 E.01375 Buffered code: G1 X-52.756 Y-133.46 E.01114 Buffered code: G1 X-12.745 Y143.944 E14.69326 Buffered code: G1 X-12.282 Y143.998 E.02444 Buffered code: G1 X-52.327 Y-133.639 E14.7056 Buffered code: G1 X-52.133 Y-133.707 E.01078 Buffered code: G1 X-51.898 Y-133.827 E.01383 Buffered code: G1 X-11.82 Y144.046 E14.7181 Buffered code: G1 X-11.359 Y144.086 E.02426 Buffered code: G1 X-51.462 Y-133.96 E14.72726 Buffered code: G1 X-51.027 Y-134.101 E.02397 Buffered code: G1 X-10.89 Y144.178 E14.7396 Buffered code: G1 X-10.804 Y144.201 E.00467 Buffered code: G1 X-10.43 Y144.207 E.01961 Buffered code: G1 X-50.599 Y-134.287 E14.751 Buffered code: G1 X-50.417 Y-134.365 E.01038 Buffered code: G1 X-50.164 Y-134.432 E.01372 Buffered code: G1 X-9.974 Y144.215 E14.7591 Buffered code: G1 X-9.517 Y144.223 E.02396 Buffered code: G1 X-49.73 Y-134.576 E14.76715 Buffered codes: 1536 bytes total Code buffer space: 2392 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 46.00, max time between full transfers: 101.6ms, max pin wait times: 58.8ms/18.7ms Codes per second: 37.80 Maximum length of RX/TX data transfers: 7344/2256
Any ideas?
-
6HC w/SBC upgrade to specific unstable version?
Edit: nm, decided to go ahead and do the dist-upgrade and it's going to go to 3.5.0~beta.4
-
RE: 3.5b3+MB6HC+Smart Effector Probe Triggering at Standstill
It's fixed, turned out it was my cabling. I must have tweaked it somehow when I installed the filament runout sensor. Crimped a whole new set for the 8 pin and is all good now.