InputShaping Plugin shows only zeros with Toolboard 1lc

mfs12

Can you please share a full console log of your browser doing a complete run from start to end.

Heartleander81

@mfs12 with the shaper tool?

Heartleander81

console-export-2021-10-7_9-24-2.txt

mfs12

Does anybody else have this kind of issue? @SilviuZ, @jay_s_uk or @SIam?

Everything looks pretty ok. Can you re-install the inputshaping plugin?

jay_s_uk

@mfs12 been ok for me so far

SIam

@mfs12 here is it working (duetWiFi)

Heartleander81

@mfs12 yes I can do it

mfs12

Hey @Heartleander81, i understand the bug. The rate in the CSV is zero, this is why only zeros are displayed. Apparently something goes wrong on the RRF side.

No, need for you to do any further investigation.

@dc42, do you know why the rate is zero? @Heartleander81 is using a toolboard.

please check @Heartleander81's accelerometer data.

https://forum.duet3d.com/assets/uploads/files/1633528864516-20_2021-10-06_13.00.04.csv

dc42

@heartleander81 please post the results of running M122 and of running M122 B# where # is the CAN address of the tool board.

Heartleander81

@dc42
M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta4 (2021-09-27 11:31:18) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J1DA-3SD6P-KV4H9
Used output buffers: 1 of 40 (15 max)
=== RTOS ===
Static ram: 151080
Dynamic ram: 63896 of which 192 recycled
Never used RAM 131712, free system stack 127 words
Tasks: SBC(ready,61.0%,248) HEAT(notifyWait,1.9%,321) Move(notifyWait,6.9%,238) CanReceiv(notifyWait,0.2%,772) CanSender(notifyWait,0.1%,362) CanClock(delaying,0.8%,339) TMC(notifyWait,79.4%,58) MAIN(running,101.7%,921) IDLE(ready,0.3%,30), total 252.3%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 107:37:24 ago, cause: software
Last software reset at 2021-10-03 21:00, reason: User, GCodes spinning, available RAM 132020, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 18672
MCU temperature: min 30.3, current 33.6, max 46.0
Supply voltage: min 0.2, current 25.2, max 25.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 0.2, current 12.1, max 12.9, under voltage events: 12
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/432/432, gc cycles 0
Driver 0: pos 27529, standstill, SG min/max 0/1023, reads 44026, writes 238 timeouts 1
Driver 1: pos 5114, standstill, SG min/max 0/1023, reads 44016, writes 248 timeouts 1
Driver 2: pos 3729, standstill, SG min/max 0/1023, reads 44016, writes 248 timeouts 1
Driver 3: pos 0, standstill, SG min/max 0/1023, reads 44026, writes 238 timeouts 1
Driver 4: pos 0, standstill, SG min/max 0/1023, reads 44026, writes 238 timeouts 1
Driver 5: pos 0, standstill, SG min/max 0/0, reads 44121, writes 143 timeouts 1
Date/time: 2021-10-08 08:38:24
Slowest loop: 1027.96ms; fastest: 0.03ms
=== 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 39, maxWait 158836857ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 73991, completed 73991, hiccups 0, stepErrors 0, LaErrors 0, Underruns [6, 0, 4], 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 6 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
=== CAN ===
Messages queued 3803959, received 709539, lost 0, longest wait 97ms for reply type 6013, peak Tx sync delay 60699, free buffers 49 (min 19), ts 1937222/177401/0
Tx timeouts 0,0,1759820,0,0,1407845 last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 13800/13800
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c488
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b4
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 39.62, max wait times: 73.8ms/21.3ms
Codes per second: 1.46
Maximum length of RX/TX data transfers: 6916/1688

M122 B20

M122 B20
Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta4 (2021-09-27 14:41:33)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2632, free system stack 2768 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,58) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) ACCEL(notifyWait,0.0%,27) TMC(delaying,3.0%,57) MAIN(running,91.8%,346) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:11:53 ago, cause: VDD brownout
Last software reset data not available
Driver 0: pos 0, 718.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 28998, writes 12, 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 1/5, peak Rx sync delay 611, resyncs 0/0, no step interrupt scheduled
VIN: 25.4V
MCU temperature: min 25.6C, current 42.9C, max 42.9C
Ticks since heat task active 166, ADC conversions started 713409, completed 713409, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 171 ticks ago, loop time 0
CAN messages queued 14372, send timeouts 0, received 6473, 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 3, other errors 0

dc42

@heartleander81 thanks. What M955 command do you use to configure the accelerometer?

Heartleander81

@dc42

M955 P20.0 I10 R12

With the Duet Accelerometer is the Hz displayed

dc42

@heartleander81 thanks. What response do you get when you send M955 P20.0 without parameters?

When you've done that, please remove the R12 parameter from that command. I think it may be causing a problem.

Heartleander81

@dc42 the response ist M955 P20.0

mfs12

@Heartleander81 can you share the acceleroemter csv file with the new config (without R12 parameter)?

Heartleander81

@mfs12 from your is plugin I doun't find the file. In the Folder Accelerometer is only the csv files from manuelly test.

mfs12

@heartleander81, please run the manual test again and share the file.

Heartleander81

@mfs12 20_2021-10-08_12.32.09.csv

Heartleander81

ACC from duet

IS Plugin

Sorry for the Bad Picture Quality

mfs12

@heartleander81, @dc42,

The plugin behaves here correctly as the file reports a sample rate of zero. This is why only zeros are displayed. I am not sure why RRF reports a sample rate of zero despite recording all those samples.

From https://forum.duet3d.com/assets/uploads/files/1633689320062-20_2021-10-08_12.32.09.csv:

998,-0.031,-0.125,1.039
999,-0.031,-0.125,1.039
Rate 0, overflows 0