Input Shaping Plugin dont display collected motion profiles data
-
i have an Accelerometer LIS2DW12 connected and its oriented and working fine. i am able to collect Data and i can view the data in the default accelerometer folder on Duet 6XD controller but when i got to motion analysis tab it does not display anything. Even if i select none, apply and rerun the data collection again . it finishes without errors but does not display.
i am running Duet3D RRF 3.6.0-beta-4 on the Duet3D 6XD Controller
On my Config i have the following
M955 P0 C"spi.cs2+spi.cs1" ; LIS2DW12 Accelerometer -- All wires connected to temp DB connector on Duet3D 6XD, no temperature daughterboard. M593 P"ei3" F46 ; ; To Collect accelerometer samples and save them to .csv file : default folder 0:/sys/accelerometer. Comment out when not collecting Accelerometer data M956 P0 S2000 A0 ; Note: A0 = Activate immediately, A1 = Activate before start of next move, A2= Activate before start of deceleration segment of next move
-
@developeralgo222 Are you using M956 in
config.g
? That doesn't look right. Can you please upgrade to 3.6.0-rc.1 and check if the problem persists? -
is M956 supposed to be in config.g or not ?
-
@developeralgo222 No, I don't think so, M956 is sent by the Input Shaping plugin. You only need to configure the accelerometer using M955 in config.g.
-
@chrishamm
i have upgraded to 3.6.0-rc1 and removed the M956 command from config.g file and rebooted the Duet3D 6XD but the problem persists . No display of collected accelerometer data -
@developeralgo222 Can you rename the "accelerometer" directory in the System directory to "accelerometer2", record a new motion profile, and check if that fixes it? Or can you open the browser dev tools and check the JS console for potential errors?
-
@chrishamm Yes !!! that fixed it. Is this some bug in DWC ?
-
@developeralgo222 It sounds like a bug, hence my question for the JS console output. Alternatively, can you ZIP the contents of
/sys/accelerometer2
and provide it? Then I may be able to reproduce and fix it here. -
@chrishamm
Sorry @chrishamm , unfortunately i deleted it before seeing this message. My mistake, i should have kept it. Sorry for that