Topics created by TheIndianDude

I figured out the issue. The cables I was using were crap. Replaced them with a higher quality cable (I bought these from amazon: https://www.amazon.com/dp/B07GD2PHX9?ref=ppx_yo2ov_dt_b_product_details&th=1) and it's working without issues with default sampling rate, resolution, and SPI clock frequency:

M955 P0
Accelerometer 0 type LIS3DH with orientation 50 samples at 1344Hz with 10-bit resolution, SPI frequency 2000000

@phaedrux It does seem like an Ethernet controller problem. The SD card from the problem board works just fine on my spare Duet 2 Ethernet.

I tried resoldering the ethernet module pins to the board, but to no avail. When the board is first powered through USB, the module lights up. When I issue an M552 S0 to turn off networking, the module lights go out. When I enter M552 S1 to enable the network, the lights don't come back on. At this point I can't be certain if it's the main board or the ethernet module. Guess I'm going to have to switch it back to WiFi to confirm.

I will use my spare board in the meantime.

Thanks!

@theindiandude
No, move.axes[2] refers to the axis, not the drivers.
I have two Z axis drives.
If you send

echo move.axes[2].letter

from the console it will confirm.

@theindiandude Look at M18 and M84 which you can do to disable one motor/axis. Put this command in a trigger macro (e.g. trigger2.g) and save that macro to the /sys folder. Then in your M581 use T2 instead of T0 and that will call the macro "trigger2.g" which will in turn run M18 Z (or whatever command(s) you decide to use).

I followed your advice and I am now getting consistent readings within 0.005mm which is well within the margin of error for the probe. The key was the probing speed and the dive height (Set to 5mm/s and set to 5mm). Once I slowed the probe down and also didn't raise the Z height above 5 mm, the readings were consistent.

Thanks for the advice!

@SupraGuy Hmmm....I do have HTP Stove paint...🤔

@TheIndianDude

Glad to hear you got it all sorted.

Frederick

Ok, so I received my new Duet 2 Ethernet board today and the first thing I did was flashed firmware 3.2.2 on it. It is working without a glitch so far (fingers crossed). I guess the ethernet module on the other board was bad. I have ordered a replacement for it, so hopefully that fixes my problem.