Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

X axis dancing #25

Open
Sekai1942 opened this issue Oct 23, 2020 · 13 comments
Open

X axis dancing #25

Sekai1942 opened this issue Oct 23, 2020 · 13 comments

Comments

@Sekai1942
Copy link

Hi. i just installed s42b on my diy printer and did the calibration and it works but the x axis when i try to move it it just goes back and forward really fast.I think the whole asamble is to large in weight and it overshouts when moving then try to compensate then it overshouts in reverse and that becames a loop.
I try to lower the accelaration but the same thing.
The Y axis does the same but not every time (as shown in video).
And when i turn off the motors in the interface below, the y axis i can move it but the x axis the motor stays energized but there is no compensation meaning the board is not active for close-loop.
Any ideea how to solve this?
https://drive.google.com/file/d/1P0TRuBtJh8re5k-FxD4gFDRKnzX-ddsW/view?usp=sharing

@Quas7
Copy link

Quas7 commented Oct 23, 2020

Did you calibrate without load (belt detached)? That would be my first shot as imprecise calibration kills the PID loop quite easy.

If the calibration is fine without load I would check for the PID settings of the S42B as they likely need tuning for heavy loads. Can be done either via serial control (see the manual) or via flashing the firmware directly (my prefered way).
Oszillation should be either too much I or P or to little D. Instead of I=10 a few use I=2 or even I=1. Just reduce I until you get no oszillation. If this is not possible, reduce P as well.

I am not sure, how far Jan is already for his fork to get PID tuning more user friendly: https://github.com/swanepoeljan/TrueStep

Maybe you check the other issues in this repo as well as there are some tunings required for Marlin 2.0.x as well.

@Sekai1942
Copy link
Author

You are right. i calibrated without load.I calibrated the y axis with load and it looks ok now but the x axis i have no way to reach out to the buttons. i will have to serial control it.
thanks.

@Sekai1942
Copy link
Author

btw how to upload the firmware?

@Quas7
Copy link

Quas7 commented Oct 25, 2020

for the flashing of the FW you will need an stlink dongle (clone). More details are here:

#3 (comment)

@Sekai1942
Copy link
Author

Sekai1942 commented Oct 28, 2020

for the flashing of the FW you will need an stlink dongle (clone). More details are here:

#3 (comment)

Thx for the replay. I order the dongle about a month ago for different project.
The current problem i have is i cannot modify the pid from serial.
It gives me a response back but when i try to change the parameter, it gives back crc sum error.
What i am doing wrong?

@Quas7
Copy link

Quas7 commented Oct 28, 2020

@Sekai1942 I never used the serial interface and always flashed my changes directly. So, I can not help much on this one but there are other issues discussing on this here, I think.

@swanepoeljan
Copy link

@Sekai1942 Did you see this document. It explains how to calculate the checksum.

@Sekai1942
Copy link
Author

yes i found out how to modify the parameters.

@swanepoeljan
Copy link

In the meantime I have added support for the original firmware in my terminal program which you could also use for changing the PID gains.

@robtheminnie
Copy link

Does this firmware also work with the s42b V2.0 or is it only suitable for the V1.0?

@swanepoeljan
Copy link

Since V2.0 uses the STM32F103 and probably also use a different pin out it will most likely not work. As for the terminal program, I am not sure, if they kept their protocol the same it could probably work.

@robtheminnie
Copy link

@swanepoeljan, thanks for the info. I commented in another issue, #32 , about having the same problem. The user fixed the issue by updating to your firmware fork. However, as I have V2.0 boards, this isn't possible. Are you familiar with the #32, and behaving indicated, with vertical lines and ringing. I'm assuming it's incorrect PID gains. Any thoughts?

@swanepoeljan
Copy link

Haven't seen that post, glad to hear it worked for him. I would also try playing with the gains to see if it helps, maybe he can share his printer model and gains that worked for him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants