Duet Tool board V1.2 installed. "Accelerator not found" error.

Mr_Phelps

I had a LIS3DH installed before an that worked fine.
If I query with M955 the machine returns with 121:0 with orientation 10.
If I query with M122 B121 it comes back yes with status 00

I am running a Duet 3 6HC with a Tool board V1.2 using the Duet web interface to run the printer.
Printer is a VCore 500.

What am I doing wrong?

dc42

@mr_phelps what command did you send that provokes the error message?

Mr_Phelps

@dc42 When I use the Input Shaper plugin to try to generate a motion profile it returns with the "Accelerometer not found" pop-up.

dc42

@mr_phelps I've just re-tested the input shaping plugin on my machine. I the the "No accelerometer found" message if I try to record a motion profile without selecting a tool first. When I select the tool that uses the tool board that has the accelerometer, it doesn't give that message and it allows me to set the motion parameters. We will look into why this happens.

Mr_Phelps

@dc42 Ah, I will try that as soon as the current print finishes. Should be in 4 hours or so. In a time crunch to get work parts out.

Thanks for your time!

Mr_Phelps

@mr_phelps Just to be clear, how do select a tool? I can't mess with the menu at the moment. I don't want to risk the 16 hour print.

Mr_Phelps

@mr_phelps Poked at it a little between prints. I can get data from the M956 command. So the machine can talk to the accelerometer. But there is no option to select a tool when I try to use the plugin. As soon as I select "Record Motion Profile" it dumps me out with the not found error.

dc42

@mr_phelps try selecting a tool before you try to record a new motion profile. You can do this either by clicking on the tool in DWC or by sending a T command, for example T0 to select tool 0.

Mr_Phelps

@dc42 I will try that once the current print finishes. When you say clicking on the tool in DWC, do you mean "Tool 0" in the Tools and Extra window?

dc42

@mr_phelps said in Duet Tool board V1.2 installed. "Accelerator not found" error.:

@dc42 I will try that once the current print finishes. When you say clicking on the tool in DWC, do you mean "Tool 0" in the Tools and Extra window?

Yes.

chrishamm

@mr_phelps Can you confirm that you have v3.4.1 installed on both boards? I just tried to reproduce it and I got a glitch with 3.4.1 on 6HC and 3.3 on the TOOL1LC resulting in no accelerometer showing up until I hit E-STOP. Once I upgraded the tool board to 3.4.1, the problem disappeared.

Mr_Phelps

@chrishamm The current part will finish in a few hours. Once that is done I can try your request. DWC is 3.4.0.
I'm still not great at upgrading, so that might take a little bit once I get back from work.

Mr_Phelps

@mr_phelps Tried to upgrade to 3.4.1 but it still shows as 3.4.0 and still getting the Accelerometer not found issue.

Was trying to use the Machine specific tab and went through several tries. Downloaded both versions of the upgrade that I could find (Master and SD) but same results each time. Had to set it aside as the next print needs to start. ~24 hour print and these have to be done before the end of the week. (Though that only gets one set out when I need two. Second set will have to ship to France next week.)

Phaedrux

Are you running standalone or with a Pi?

If standalone, updating is as simple as uploading a zip file.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1/Duet2and3Firmware-3.4.1.zip

Upload that as is to the system tab in DWC. That should prompt to update everything.

If you're using an Pi. You'll need to send sudo apt update and sudo apt upgrade from the terminal on the pi.

Mr_Phelps

@phaedrux Running two printers of my Surface (other printer is a Prusa Mk 2.5S that I changed to Duet 5 Mini board.)
So I shut everything down. Power cycled the Surface. Open DWC and grabbed the file you linked (thanks for that) and ran the upgrade. This time it worked. Not sure if for some reason the web browser was the thing not letting the upgrade finish.

But now, with latest firmware, the plugin sees the accelerometer and it actually ran the routine.

So I think we are good to go. Thanks for all the help!