Posts made by Alex_ZHANG

@dc42 used a faster sd card, turned mesh off. works. Thanks.
Before

After

Thanks for the advice.

@dc42 said in Accelerometer overflow and input shaping doing (almost) nothing:

reduce the number of samples you are collecting.

Do you mean reducing M955 S parameter or do you mean reducing moving distance when recording movement?
During the past few days I found reducing moving distance helps. I changed 80->250 (which is default value set by the plugin) to 140->180 and overflow issue goes away.
If the distance matters, do you have a recommended moving distance?

@dc42 said in Accelerometer overflow and input shaping doing (almost) nothing:

This can happen if you have configured segmentation in M669, or if you have mesh bed compensation in effect and the mesh is fairly fine. So try turning off segmentation (if you have enabled it) and mesh bed compensation.

M669 is relatively new to me (because M667 is removed in 3.5) so I didn't mess with the S parameter.
I don't remember using bed compensation, but I'll check when I get home.

I'm using 10k acceleration when recording movements, assuming that would amplify vibration altitude for easier data interpretation. And I usually print with 4k acceleration to reduce vibration. I suppose I'm doing it right?

@dc42 BTW, if it's convenient for you, could you have a look on my other post about accelerometer? I have a data overflow issue, and input shaper dose (alomost) nothing on long distance move.

Link here. https://forum.duet3d.com/topic/35189

Thanks.

@dc42 Aha, so that's what the 32s3.bin is for.

I'll use ESP07s. At the same price, what a fool I am to order ESP07 just for the same form factor

Thanks.

@droftarts yes, that might be the issue. ESP12 has 4MB and ESP07 has only 1MB spi flash. I'll order and try EPS07s with 4MB flash.
But I believe there are duet2 WiFi boards with stock ESP07 out there? Wouldn't that be a problem? I remember seeing someone ordered some from Roland.

And this happens every time I restart the board, not just the first time I upgrade.

Hi.
I have 2 Duet2WiFi, both running RRF 3.5.0 RC3.
Today I switched one of the board's wifi chip to esp07 with external antenna for better reception.

Interestingly, it starts to forget remembered networks on restart.
connecting via usb, sent m552 s0, m587 and m552 s1, it connects, but once i power off and on again, everything is lost.
I downgraded wifi server to 1.27, everything works fine.
Upgraded to 2.1, Alzheimer again.

I have extra esp12s esp12f and esp07 lying around, cross checked them with the two Duet2WiFi boards I have to eliminate soldering issue.
this only happens in esp07+wifi server2.1b6.

@Alex_ZHANG
Forgot to mention: It's a corexy machine with about 350mm bed. A BLV MGN Cube to be exact.
and here is my config.g if that helps.
config.g

@Alex_ZHANG said in Accelerometer overflow and input shaping doing (almost) nothing:

Good morning/afternoon/evening.
I'm running 3.5.0-rc.3 on Duet2 Wifi. Using LIS3DH, trying to do input shaping.

Good morning/afternoon/evening.
I'm running 3.5.0-rc.3 on Duet2 Wifi. Using LIS3DH, trying to do input shaping.
First problem: In all my input shaping motion profiles, the plugin says "The selected motion profile contains overflows. It may not be accurate."
Is that something I should worry about? What shall I do about it or should I just ignore that?

Second thing:
With each algorithm applied, when recording motion again, the graph shows almost no difference.
Well.... peak reduced from 0.0056 to 0.0039 at best, and the curve surely varies a little bit here and there.
I'm not quite sure what I'm doing wrong maybe? or is it just the best it can do?

Following are motion profiles under different algorithms.

MZV

ZVD

ZVDD

ZVDDD

EI2

EI3

@yetanotherusername
i just stripped them out, used five pairs of them with the foil shield grounded. A dedicated pair with shield is used on cs pin, another on int pin. others for the rest pins.

@yetanotherusername
cable problem. duet can see the accelerometer, but when recording data, you get too much interference, so accelerometer stopped transmitting. I've been through this. if you open the csv files manually, you will see a line: failed to collect data.

you need proper shileded wiring on cs and int pin, just like those in hdmi or usb3

@Alex_ZHANG said in Accelerometer question, because no data is recorded:

@yetanotherusername
same problem on my duet2wifi running 3.5rc, duet detects accelerometer fine, but DWC freezes when recording data, had to click the gray background or cancel.

What's different in my case is that i got the recorded file(in csv format) but when i open it, it says: failed to record data...

Switched to hdmi cable with shield grounded, problem solved

@yetanotherusername
same problem on my duet2wifi running 3.5rc, duet detects accelerometer fine, but DWC freezes when recording data, had to click the gray background or cancel.

What's different in my case is that i got the recorded file(in csv format) but when i open it, it says: failed to record data...