Input Shaper Plugin - hangs on "Record Motion Profile"
-
I just installed a LIS3D(S?)H accelerometer to my corexy. When I try to use the input shaper plugin to collect data, the collection process starts with the first move, but then hangs forever there waiting for something to happen. It does not matter how many moves I configure, it just hangs after the first move.
When I press cancel and reload the motion profiles, a motion profile has been collected, and I'm able to display the data and work from there. Is there anything I can do, to get the collection functionality to correctly work or to find out where it's stuck?
I'm using SBC mode and firmware 3.4.6
I did check the accelerometer "run counter" through the object model browser, and the runs are counting up, the number of collected samples is also correct (1000)
Thank you for your help!
Some debugging informations:
Accelerometer config:M955 P0 C"spi.cs1+spi.cs0" I21 S1600 R16
Feedback: M955 P0
Accelerometer 0:0 type LIS3DH with orientation 21 samples at 1344Hz with 12-bit resolution, SPI frequency 2000000
M122
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.0 or earlier (SBC mode) Board ID: 08DJM-956BA-NA3TN-6J1F4-3SD6L-KBB6T Used output buffers: 1 of 40 (22 max) === RTOS === Static ram: 153252 Dynamic ram: 69892 of which 0 recycled Never used RAM 124264, free system stack 154 words Tasks: ACCEL(notifyWait,0.0%,348) SBC(resourceWait:,0.6%,478) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,260) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,343) TMC(notifyWait,7.8%,58) MAIN(running,91.3%,923) IDLE(ready,0.3%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:10:23 ago, cause: power up Last software reset at 2024-03-15 19:27, reason: User, GCodes spinning, available RAM 124060, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 135 MCU temperature: min 22.3, current 40.7, max 40.9 Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.4, current 12.2, max 12.3, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0 Events: 1 queued, 1 completed Driver 0: standstill, SG min 0, mspos 312, reads 5488, writes 20 timeouts 0 Driver 1: standstill, SG min 0, mspos 248, reads 5488, writes 20 timeouts 0 Driver 2: standstill, SG min 0, mspos 24, reads 5488, writes 20 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 5493, writes 15 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 5493, writes 15 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 5497, writes 11 timeouts 0 Date/time: 2024-03-17 10:22:30 Slowest loop: 52.10ms; 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, segments created 17, maxWait 66684ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 11, completed 11, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === 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 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 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 5508, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 3116/0/0 Tx timeouts 0,0,3115,0,0,2391 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 24579/24579 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ab5c Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.6 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 27.11, max time between full transfers: 147.0ms, max pin wait times: 91.4ms/9.6ms Codes per second: 0.11 Maximum length of RX/TX data transfers: 3340/3424
-
@flaviocu Is the version number of DWC the same as the version number of RepRapFirmware (3.4.6 according to your M122 report)?
Ian
-
@droftarts Yes, the DWC/DSF is also 3.4.6
and the Input Shaper Plugin is also 3.4.6:
-
-
anybody got an idea or a pointer for my problem?