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.

Sign up for GitHub

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

Jump to bottom

MKS-Gen L V1.0 w/5 Fystech 2130 drivers for reference #28

Open
wbarber69 opened this issue Mar 18, 2018 · 41 comments
Open

MKS-Gen L V1.0 w/5 Fystech 2130 drivers for reference #28

wbarber69 opened this issue Mar 18, 2018 · 41 comments

Comments

@wbarber69
Copy link

gen-l_diagram
here is a rudimentary drawing of how im using my drivers on an MKS-Gen L V1.0 board. Just in case anyone else needs a refernce
@Budavaril
Copy link

Hi,
Why better to use those irregular pins (example servos pins) than using same standard pins (aux2-aux3)on any other ramps based boards?

@wbarber69
Copy link
Author

wbarber69 commented Mar 20, 2018 via email

@Budavaril
Copy link

Budavaril commented Mar 20, 2018 •
edited
Loading

That make sense. So may that's why I had a some trouble with my FLsun i3 during TMC2130 upgrade?
I using my board with "dual screen" .
One of the 3.2" touch screen has SD and WiFi built in, that's why I thought if I using for "second screen" just an (Anet Discount) 12864 what has no SD feature I should have no any those problems to changing my drivers to TMC2130.
But may yes .. Because I tried first using Marlin v1.1.8 and library TMC2130 v2.2.1 but that combo wasn't succesful. Motors just moved shortly with strong noise and I got few messages:
"00:00: X driver overtemperature warning! (0mA)"
"X driver error detected: short to ground (coil A)"
"Error:Printer halted. kill() called!"
I thing there is some bug and the "AUTOMATIC_CURRENT_CONTROL" (What called "MONITOR_DRIVER_STATUS" in v1.1.8) doesn't really worked and my motors got (uncontrolled) maximum current.
After I downgraded to Marlin 1.1.6 and TMC2130 2.0.0 looks everything working. But I still have to troubleshooting because I still loosing some steps on X and Y.
I thought that can be solving with some "current-speed-acceleration tune". But may there is a communication problem?

@wbarber69
Copy link
Author

wbarber69 commented Mar 20, 2018 via email

@wbarber69
Copy link
Author

wbarber69 commented Mar 20, 2018 via email

@wbarber69
Copy link
Author

wbarber69 commented Mar 20, 2018 via email

@teemuatlut
Copy link
Owner

Marlin v1.1.8 has an issue with setting the pin mode for CS too late and that causes problems with the configuration. The bugfix-1.1.x has this fixed.

Also it might be clearer to use "serial" to mean "USART" and not "Serial Peripheral Interface".

@wbarber69
Copy link
Author

is that correct though? every where its referenced that tmc2130 is connecting in spi mode. 2208's use a uart connection.

@Budavaril
Copy link

I tried using the bugfix-1.1.x (not enabled the SW serial yet)and steppers are working looks well, but if I start a print (from pc or from the touchscreen's SD-USB) the bed and hotend doesn't heating up, just start immediately moving the head looks printing.
Any idea what I missed?

@wbarber69
Copy link
Author

wbarber69 commented Mar 22, 2018 via email

@Budavaril
Copy link

Budavaril commented Mar 22, 2018 •
edited
Loading

Thanks your quick response.
So it was strange. I uploaded previous 1.1.6 version what was working before, but got same problem.
I removed the USB cable, restarted the printer after start printing from SD card normally (first 1.1.6 and after bugfix1.1.x too).
I connected my laptop again, but same problem came back.
Restarted printer and laptop, after working everithing.
So was something problem with the laptop USB but example firmware upload was working.
I don't understand, but most important this part have fixed.
I still loos steps, I don't know what I should changing first.. The cables to same lenght (no chain) or change pins and activate SW serial? Finally I want to do both, but I'm courious which one cose in my configuration at the moment.

@wbarber69
Copy link
Author

images of the changes ive made to my step sticks to try to ensure better cooling.
Ive added heatsinks directly to the chip on the bottom an bent the spi header to facilitate better airflow when the dupont connector is inserted. I am using some arduino stack headers i got in a multipack to raise the chips up off the board.
img_1209
img_1210
img_1211

@wbarber69
Copy link
Author

And with everything put back together. I may clip those stack headers down in the future. Currently Ive re-enabled stepper interpolation and am running my current at 650 650 650 700 700. Im printing a nice medium sized part with a lot of circular patterns so I can see if i get any more layer shifting. so far it is nice and quiet and running pretty smooth. only time will tell.

img_1212

@wbarber69
Copy link
Author

wbarber69 commented Mar 23, 2018 via email

@wbarber69
Copy link
Author

I had my first successful print with stealthchop and interpolated stepping. Still some fine tuning to do on my slicer side of things but I printed for 5 hours straight at 60mm/s with 30% fast honeycomb infill on a part that is all curved outer perimeters with a separate thin but tall tower and not a single layer shift can be seen. So I can definitely say that cooling is the first step to a successful install. I also noticed that my motors are not getting near as hot as they were even when I was working with plain old 16th stepping.

@Budavaril
Copy link

20180323_172638
I still try all adviced upgrade, but not better.
I tried cooling with a 5015 blower fan from chip side, other 2pcs 40mm from "cable side) but result is same.
Another intresting, the lose steps coming on same points,most of the times between two layers.
Difference between the results, this effect sometimes just on X or on Y, sometimes on both axis coming.
Happening always when accelerating in travel (non printing) and motor(s) give "scratchy" noise.
I can do same if "playing" with the motors, I mean controlling manually by laptop (usb) or from any own (display) controller, if moving 10mm steps fast after each other. No matter, same direction or change direction. About every 10-15 movment give that noise and after of course able to go over the end points because lost the correct home position.
Can I adjust "jerk" or "acceleration" in config.h or if TMC2130 used there is another way?

@wbarber69
Copy link
Author

wbarber69 commented Mar 23, 2018 via email

@Budavaril
Copy link

Ok, I have 5pcs brand new "old type" driver and those heatshinks doesn't fitted yet, so I can using them instantly on the chips. Let's try..
I just don't understand, if overheating happening, why I can't see that in the log?
I guess any of this error message should be show there same than I got this message with official 1.1.8 which is doesn't adjust the current and after 10mm movement sent message "00:00: X driver overtemperature warning! (0mA)"
Anyway my 12V -> 24V step up converter and the timer modul are alredy on the way for that upgrade. May that will be solving? Until of course I can try to adjust my 12V PSU..
I still courious, how working instantly on the "old" Ramps boards (example in Thomas Sanladerer's video) without extra cooling and why we have this problem on MKS GEN L? What's the difference?

@wbarber69
Copy link
Author

wbarber69 commented Mar 23, 2018 via email

@wbarber69
Copy link
Author

wbarber69 commented Mar 23, 2018 via email

@Budavaril
Copy link

Budavaril commented Mar 23, 2018 •
edited
Loading

I haven't got that "overtemp" error message after changed that 1.1.8, not with my chained wire and not now with "parallel" cables. Not on 1.1.6 and not on bugfix 1.1.x.

Now cooled 2side by heatshinks. Uppers blowed 2pcs 40mm fans. Unders (on chip) blowed with 5015.
Voltage 13.9V (that's the maximum)
in firmware:
#define DEFAULT_MAX_ACCELERATION { 100, 100, 50, 10000 }
#define DEFAULT_ACCELERATION 100 // X, Y, Z and E acceleration for printing moves
#define DEFAULT_RETRACT_ACCELERATION 100 // E acceleration for retracts
#define DEFAULT_TRAVEL_ACCELERATION 100 // X, Y, Z acceleration for travel (non printing) moves
velocity on screen:
Vmax X:100
Vmax Y: 100
Vmax Z: 2
Vmax E: 25

Result:
20180323_203030

At the moment finished my all ideas..

@teemuatlut
Copy link
Owner

teemuatlut commented Mar 23, 2018 •
edited
Loading

To clear up a few things
TMC2208 uses Serial
TMC2130 uses SPI

There is no communication from the motherboard to the driver after the initial boot time, unless you have MONITOR_DRIVER_STATUS enabled.
It doesn't matter if you use SW SPI or HW SPI. The only difference is pins used and HW SPI is faster.
It shouldn't matter if the MOSI/MISO/SCK wires are from one driver to another or all starting from the same point. Electrically this is the same.

"Scratchy" noises from the motor indicate a mechanical problem. Check your motion system.

An acceleration of 100 would be excessively low. Max velocity of 500 would be excessively high.

Please post your M503 and M122 output if you're seeing skipped steps.

@wbarber69
Copy link
Author

wbarber69 commented Mar 23, 2018 via email

@Budavaril
Copy link

Thanks all of that, now I understanding better how works.
First my outputs:
M503:
11:14:37.492 : echo: G21 ; Units in mm
11:14:37.493 : echo: M149 C ; Units in Celsius
11:14:37.495 : echo:Filament settings: Disabled
11:14:37.496 : echo: M200 D1.75
11:14:37.496 : echo: M200 D0
11:14:37.497 : echo:Steps per unit:
11:14:37.499 : echo: M92 X100.00 Y100.00 Z400.00 E150.00
11:14:37.501 : echo:Maximum feedrates (units/s):
11:14:37.503 : echo: M203 X100.00 Y100.00 Z2.00 E25.00
11:14:37.504 : echo:Maximum Acceleration (units/s2):
11:14:37.506 : echo: M201 X9000 Y9000 Z50 E10000
11:14:37.510 : echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
11:14:37.511 : echo: M204 P3000.00 R3000.00 T3000.00
11:14:37.516 : echo:Advanced: S<min_feedrate> T<min_travel_feedrate> B<min_segment_time_us> X<max_xy_jerk> Z<max_z_jerk> E<max_e_jerk>
11:14:37.518 : echo: M205 S0.00 T0.00 B20000 X10.00 Y10.00 Z0.30 E5.00
11:14:37.519 : echo:Home offset:
11:14:37.520 : echo: M206 X0.00 Y0.00 Z0.00
11:14:37.522 : echo:Auto Bed Leveling:
11:14:37.522 : echo: M420 S0
11:14:37.523 : echo:Material heatup parameters:
11:14:37.524 : echo: M145 S0 H180 B50 F0
11:14:37.526 : echo: M145 S1 H240 B60 F0
11:14:37.526 : echo:PID settings:
11:14:37.527 : echo: M301 P22.20 I1.08 D114.00
11:14:37.528 : echo:Z-Probe Offset (mm):
11:14:37.530 : echo: M851 Z-0.50
11:14:37.531 : echo:Stepper driver current:
11:14:37.533 : echo: M906 X 800 Y 800 Z 800 E0 800 E1 800

and M122:
11:17:04.013 : X Y Z E0 E1
11:17:04.015 : Enabled false false false false false
11:17:04.016 : Set current 800 800 800 800 800
11:17:04.021 : RMS current 795 795 795 795 795
11:17:04.027 : MAX current 1121 1121 1121 1121 1121
11:17:04.029 : Run current 25/31 25/31 25/31 25/31 25/31
11:17:04.031 : Hold current 12/31 12/31 12/31 12/31 12/31
11:17:04.034 : CS actual 12/31 12/31 12/31 12/31 12/31
11:17:04.040 : PWM scale 2 2 2 2 2
11:17:04.043 : vsense 1=.18 1=.18 1=.18 1=.18 1=.18
11:17:04.047 : stealthChop true true true true true
11:17:04.051 : msteps 16 16 16 16 16
11:17:04.055 : tstep 1048575 1048575 1048575 1048575 1048575
11:17:04.056 : pwm
11:17:04.056 : threshold 0 0 0 0 0
11:17:04.060 : [mm/s] - - - - -
11:17:04.062 : OT prewarn false false false false false
11:17:04.062 : OT prewarn has
11:17:04.067 : been triggered false false false false false
11:17:04.071 : off time 5 5 5 5 5
11:17:04.071 : blank time 24 24 24 24 24
11:17:04.076 : hysteresis
11:17:04.076 : -end 2 2 2 2 2
11:17:04.079 : -start 3 3 3 3 3
11:17:04.080 : Stallguard thrs 0 0 0 0 0
11:17:04.080 : DRVSTATUS X Y Z E0 E1
11:17:04.087 : stallguard
11:17:04.087 : sg_result 0 0 0 0 0
11:17:04.093 : fsactive
11:17:04.093 : stst X X X X X
11:17:04.102 : olb
11:17:04.102 : ola
11:17:04.102 : s2gb
11:17:04.111 : s2ga
11:17:04.111 : otpw
11:17:04.111 : ot
11:17:04.113 : Driver registers: X = 0x80:0C:00:00
11:17:04.115 : Y = 0x80:0C:00:00
11:17:04.117 : Z = 0x80:0C:00:00
11:17:04.117 : E0 = 0x80:0C:00:00
11:17:04.119 : E1 = 0x80:0C:00:00

@teemuatlut
Copy link
Owner

See M201.

@Budavaril
Copy link

Wow.. No output.. Possible??

@teemuatlut
Copy link
Owner

In your M503 output you just posted.
You're using acceleration values of 9000.

@Budavaril
Copy link

That was the original and last time just set everything back to original.
But was same (bad) result if I adjusted like I posted yesterday:
#define DEFAULT_MAX_ACCELERATION { 100, 100, 50, 10000 }
#define DEFAULT_ACCELERATION 100 // X, Y, Z and E acceleration for printing moves
#define DEFAULT_RETRACT_ACCELERATION 100 // E acceleration for retracts
#define DEFAULT_TRAVEL_ACCELERATION 100 // X, Y, Z acceleration for travel (non printing) moves
velocity on screen:
Vmax X:100
Vmax Y: 100
Vmax Z: 2
Vmax E: 25

@teemuatlut
Copy link
Owner

M503 shows your current settings.
The set default values in configuration.h are overriden by the values stored in EEPROM.

@Budavaril
Copy link

Budavaril commented Mar 24, 2018 •
edited
Loading

Oh yeah... I think that was the key..
Now I set all this value to 100 on the smart controller , and printer became like old man. So that's why I couldnt realise any change about the movements any time... I tried to set all that values to 10 and had no any visible effect..
So good news because I have my original board "untached" (Just in case I ordered another same board to do all my experiments not on my original working board.) I can connect and read the original values after this "slow-motion" printing..

@teemuatlut
Copy link
Owner

Just send M201 X1000 Y1000 or use the LCD to update the values on an on going print.

@Budavaril
Copy link

Ok. that's cool. Now became "younger" and to be honest movements more similar how was with the old drivers.. Printing nearly finish and no any skipped steps until now. :)

@wbarber69
Copy link
Author

Sorry, I realize I had acceleration and velocity settings backwards earlier when I made the recommendation. Lots of settings and numbers to keep up with. This mornings tests are going well. I have doubled all my values for speed and acceleration and so far (fingers crossed) no layer skipping. Hopefully this trend will remain and I can get back to decent printing speeds. My first test at 60mm/s with slow settings was successful but outer perimeters were kinda not where I wanted them, but at 40mm/s we’re almost perfect.

@wbarber69
Copy link
Author

so it seems that acceleration is kind of flexible, as it doesnt seem to make as much of an impact as velocity does. im stable at or below 150-175. but i have tried accelerations of up to 1000 I havent gotten around to testing any higher values yet. my first test was with x and y at 250 with acceleration of 1000. I was also using a high jerk setting of 30. i had failures at the first sign of tighter shorter movements. so when my base feature was finished and only wall type features were being printed almost every other layer was problematic. stopped and went back to original velocities but increased acceleration had no problems. so ive begun to tune velocity only.

@Budavaril
Copy link

Budavaril commented Mar 24, 2018 •
edited
Loading

First I'd like to say big thanks about the helps.

I think good idea to sum and share my experiences:
The solution(s) in my case:

  • TMC2130 necessary different (reduced) acceleration settings compared with A4988 or Marlin's default values.
    (I don't know yet, but may it will coming back somewhere in printing speed or quality?)
    I also learned: "The set default values in configuration.h are overriden by the values stored in EEPROM."
    if I want setting "Marlin values", should do "Restore failsafe" and "Store settings" Or M502, M500?

I think I understand "How working?"

  • When powered and starting on SPI initialising the drivers. (set the mode, current. etc.)
  • after if MONITOR_DRIVER_STATUS and TMC_DEBUG active on SPI just "watching" and "responding" if happen any definied error.
  • during the printing still DIR and STEP pins in use to sending the commands from board to drivers.

My conclusions:

  • if MONITOR_DRIVER_STATUS and TMC_DEBUG active and TMC2130 loosing steps without error message(s) in the LOG, that can't cause any faulty or non faulty SPI communication, because the steps commands stil coming on another pins (same as using the original A4988 or any another driver), and no any communication happening on SPI.

  • Cables (harnes) no sensitive about "chain" or "parallel", if drivers are initialised successfuly mean "working" (checking M122)
    My harness:
    20180311_171110

Actually now modified a bit because of the SW SPI, but still looks this.
Compared with my "parallel prototype" :
20180324_170855

3- I'm not sure, but please let me know if I'm wrong... I think using SW SPI or HW SPI that matter just if using SD slot on the smart controllers, because in this circuit have no interference between the SD slot and TMC2130 driver modules. (?)

My personal experience about my TMC2130 temperature:
The drivers after firmware changed from Marlin 1.1.8 to "bugfix 1.1.x" have no problem with overtemperature anymore.
I just tried my last print (45min 60mm/s) without any fan on the drivers and the heatshinks just was warm but absolutely not hot. I haven't got any overtemp message or killed printing.
(I still will cooling them using a silent fan, but I wanted to test)
The final results:
20180324_185910

My next step is activating sensorless home function and if receiving my step-up booster + timer modules I'll upgrade for 24V. Hopefully will working with less troubleshooting..

@Budavaril
Copy link

I received the parts for 24V (12V/24Vstep-up converter and timer modul), but I'm not sure about the delayed method. First powered the MKS GEN L 12V and after the drivers "VM" 24V or first the 24V after the board 12V?

@teemuatlut
Copy link
Owner

If you can decide, apply the 24V first.

@teemuatlut teemuatlut mentioned this issue Jun 28, 2018
Closed
@qavro
Copy link

qavro commented Apr 5, 2019

Hello. Somehow i think you might be my savior, so i apologize in advance.
I have an Ender 3. After i have tunned the mechanical part next to "God" mode ( i am really advanced in CNC precision machines) i am ready to move on the brain. I have bought MKS GEN L board with regular A4988 drivers. I intend to change the drivers but that is another story, the board simply came with these. I have configured and installed the Marlin 1.1.9 (fixed) with no issues. But here comes my problem. I really want to keep my Ender 3 display. No biggie, simply works with the board after i swap the ribbon cable around. But i really really need and SD card. So, i bought the MKS SLOT V1.1. Can you please help me to understand how can i connect it to the board and/if is there anything else i should edit in my configuration file?

BIG thanks to you or anybody willing to give me a hand here.

@teemuatlut
Copy link
Owner

You likely won't find the help you're looking for at this page.
I suggest you try places like the Facebook groups for Marlin or Ender3 or Creality printers. Or the Reprap forums or the Toms3D forum. It's very likely that someone is already running the setup you want.

@qavro
Copy link

qavro commented Apr 21, 2019

Thank you. i wrote here because of the thread topic. Now i am running MKS Gen-L + TMC2130 +SDcard. Installing the sd card module was not that hard actually :)

@wbarber69
Copy link
Author

wbarber69 commented Apr 21, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wbarber69 @teemuatlut @Budavaril @qavro