• 5 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle

  • I started using OpenTracks a couple years ago and ditched runtastic (i keep calling that, it’s been adidas running for ages) when I discovered it made my runs public, with gps data and all, for the social features of their app. OpenTracks is FOSS, I got it from fdroid, the data stays on your phone, you do what you want with it. And most importantly it only tracks your activity, just that, no social media crap.

    Then again if you don’t want to track your runs just don’t, I personally do it because I like to see my progression and to keep notes to myself on how/what/when i eat/sleep/etc effects my runs and stuff like that












  • Hello, I suggested heat creep in your last post, which didn’t end up being the issue. I don’t remember if anyone suggested it, but have you tried checking the bowden assembly, on the motor side? Whether the stepper works, or the gears wore down (I’m pointing towards this), or there are clogs somewhere in the mechanism, even some dust that accumulated where it shouldn’t had. Or did you change settings like the current limit on the steppers? If that’s controlled with a potentiometer on the main board, maybe it got turned down for some reason (if so, I’d try to understand why’s that). I don’t know how Klipper handles motor drivers where current limits are controlled in software, I know that Marlin has a dedicated submenu in the Configuration>Advanced Configuration. If you reflashed the firmware, maybe the settings where in the eeprom and did not get transfered over or got overwritten in the flashing process.

    I remembered that on a couple different printers I had the same problem as you, and it came down to damaged/untightened nozzles (which you excluded already) or wore down gears or, on the printer I’m working on right now, too low current limits which made the stepper skip steps somewhat randomly








  • Also depending on the architecture on the computer, this might be the only possible solution. I have a samsung m2020 series printer connected to a Pi to share it on the local network. Samsung Unified Driver does not work on armhf as it is only compiled for x86/x64, but splix can be compiled on armhf and it actually supports my printer