Hello,
this question is probably best suited for @dc42
1.What is the custom input shaper and how will it be different from the others ?
2.Will it be possible to damp different frequencies on x and y with the a) the same input shaper or b) with different shapers ?
3.When do you think, you release the first beta firmware for duet3 + sbc + lc1 v1.1 with the new shapers?
TiA
Kindly Regards
Frederik
Problem Solved
Yesterday, i got the Replacement Toolboard.
After connecting and power up my machine , everything was lighting up as expected.
Now everything is working as expected and blinks in sync. I`m using now RF 3.2.beta4.3
Thanks for your Help
Regards Frederik
@Veti Thank You SOooooooOO much for your tip with the usb cable....i tried a 10 year old usb2 dvd cable (with dual A Plugs on one side). After connecting the second the firmware flashed perfektly on the first try ;).
I would be so lost without you guys and this forum 
Have a nice Day !
@dc42
perhaps a lot more people would consider using the sbc mode on duet3 boards, if it would offer more features / functionality as right now .
most people dont want to hassle with another level of complexity, only to add wifi and offload the webapplication with a few plugins.
Im personally looking forward what the future will bring. My Duet 3 is Running in sbc Mod + Lc1 v1 almost a Year now with very little trouble, while riding the unstable branch the whole time
WOW, Thank You soooo much.
Now my Z Axis working almost spot on...only minor adjustments needed.
Your Tip with the Extruder E steps was perfekt.
now there is only the error message from the filament Sensor ,
and i have to try if the auto bed leveling with the 3 independet z motors will work as expected with my BLTouch.
What Slicer do you use or recommend ?
I tried
Cura 4.8.0 and Prusaslicer .
Simplyfy 3d looks also realy nice, but i cant find a demmo version or similar. Its a hefty Price Tag for a Slicer and when i am reading the reviews on the internet ,i dont know if it is good at the moment with 4.1 or should i wait till the new update is released ?
@Frederikfor information purposes:
The cable that did NOT work: brand new Ugreen with 3Meters in lenght.
The cable THAT worked: 10 Year old usb2.0 with dual USB-A Plug on one side.
Like the on the external dvd or harddrives. Lenght ~ 40cm
Hello,
i tried the same with my Raspberry Pi 3b+ and the new Pi Cam v2 with 8MP Sensor and the MakerHawk Wide Angle Lens 165°
I used this WebInterface:
https://github.com/silvanmelchior/RPi_Cam_Web_Interface
it works realy well, because you dont have to go in the Linux Terminal to change Camera Settings. It all works over the Duet Webcam Field.
I used port 8081 but that is up to your preferences.
Regards
Frederik
@fcwilt you are right it was a wrong setting from yesterday. its a normal tr8 4 stop with 8 Lead Spindle
so, now to a new start... nozzle free again, probe working (was a light loose crimp pin on the black wire)
@chrishamm hello, are there any news on the accelerometer not found error when using a toolboard v1.1 and sbc?
Kindly regards
Frederik
@dc42 here the same error , accelerometer detected but when trying to perform a data collect, it says acceleromter not found
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta1 (2021-07-10 16:20:28) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6J9DL-3S46S-99AUT
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 62912 of which 24 recycled
Never used RAM 140352, free system stack 146 words
Tasks: SBC(ready,0.7%,308) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,266) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.4%,59) MAIN(running,91.8%,922) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:40:04 ago, cause: software
Last software reset at 2021-07-11 15:33, reason: User, none spinning, available RAM 137420, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 172
MCU temperature: min 31.1, current 33.9, max 47.4
Supply voltage: min 24.0, 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.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 41808, standstill, reads 41390, writes 20 timeouts 0, SG min/max 0/425
Driver 1: position -25728, standstill, reads 41390, writes 20 timeouts 0, SG min/max 0/995
Driver 2: position 3893, standstill, reads 41390, writes 20 timeouts 0, SG min/max 0/852
Driver 3: position 0, standstill, reads 41391, writes 20 timeouts 0, SG min/max 0/280
Driver 4: position 0, standstill, reads 41391, writes 20 timeouts 0, SG min/max 0/825
Driver 5: position 0, standstill, reads 41399, writes 12 timeouts 0, SG min/max 0/0
Date/time: 2021-07-11 16:13:58
Slowest loop: 56.12ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
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, maxWait 1844035ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 13, completed moves 13, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = 2 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet* is idle in state(s) 0
File is idle 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: no data received
=== CAN ===
Messages queued 21655, received 30029, lost 0, longest wait 5ms for reply type 6024, peak Tx sync delay 169, free buffers 49 (min 48), ts 12021/12020/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 29527/29527
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c7a4
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b1
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 39.59, max wait times: 49.2ms/0.0ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 3196/800
m122 b121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2108, free system stack 2789 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,117) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.8%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:01:14 ago, cause: VDD brownout
Last software reset data not available
Driver 0: position 0, 859.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 18391, writes 0, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/5, peak Rx sync delay 192, resyncs 0/0, no step interrupt scheduled
VIN: 24.4V
MCU temperature: min 37.5C, current 39.0C, max 39.0C
Ticks since heat task active 2, ADC conversions started 74496, completed 74495, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 6 ticks ago, loop time 0
CAN messages queued 492, send timeouts 0, received 339, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 9 to 432us
Driver 0: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
m122 b121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2108, free system stack 2789 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,113) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,2.8%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:43:34 ago, cause: software
Last software reset data not available
Driver 0: position 0, 859.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 23, reads 5309, writes 0, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/6, peak Rx sync delay 212, resyncs 0/0, no step interrupt scheduled
VIN: 24.4V
MCU temperature: min 38.8C, current 40.0C, max 40.3C
Ticks since heat task active 129, ADC conversions started 2614124, completed 2614122, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 134 ticks ago, loop time 0
CAN messages queued 8362, send timeouts 0, received 6006, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 9 to 433us
Driver 0: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
regards
@dc42
perhaps a lot more people would consider using the sbc mode on duet3 boards, if it would offer more features / functionality as right now .
most people dont want to hassle with another level of complexity, only to add wifi and offload the webapplication with a few plugins.
Im personally looking forward what the future will bring. My Duet 3 is Running in sbc Mod + Lc1 v1 almost a Year now with very little trouble, while riding the unstable branch the whole time
@dc42 That are great news I'm excited
independent shapers for the duet 3 would be an amazing feature !
Wouldnt it be possible to offload more task to the raspberry ?
Hello,
this question is probably best suited for @dc42
1.What is the custom input shaper and how will it be different from the others ?
2.Will it be possible to damp different frequencies on x and y with the a) the same input shaper or b) with different shapers ?
3.When do you think, you release the first beta firmware for duet3 + sbc + lc1 v1.1 with the new shapers?
TiA
Kindly Regards
Frederik
Picture with v1.0, v1.1 is mounted exactly the same
Frederik
Hello,
would it be possible to probe with the Probepin always in the down position and only retract when finished ?
Using a bltouch 3.1 with the standard P9 config and deployprobe.g and retractprobe.g files
What would i need to change to use the probe in this mode ?
Kindly Regards
Frederik
@nuramori Thanks for the Info. Looking real nice ! What buildvolumoe do you have ? my vcore Pro is around 430x430x400mm and until now, i managed up to 410mm/s wiht a genuine BMG and a mosuqito magnum with 0.4mm Nozzle at 0.25mm Lh and 0.46mm Lw
@martin7404 i will have a look at the specs. since im using a Lc1 v1.1, i already have 24v,12v and even 5v to choose from, but i wanted to run the probe with 24V so i get a little bit better readings and distance