Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About WereCatf

  • Title

Contact Methods

  • Discord
  • Steam
  • Origin
  • UPlay
  • Twitch.tv

Profile Information

  • Location
    Somewhere between kitchen, bed and my PC.
  • Gender
  • Interests
    PornHu...oh, wait.
  • Biography

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Single Status Update

See all updates by WereCatf

  1. Just compiled a custom firmware for my Prusa i3 MK2S - printer. The original firmware uses a baudrate of 115200 to communicate with Octoprint, which means large gcode-files take FRICKING FOREVER to transfer to the SD-card from Octoprint. I wanted to speed this up, so I went and set the baudrate to 921600 and compared the speed against the original one: original firmware takes 2 minutes 44 seconds with the gcode test-file and my custom firmware takes 2 minutes 11 seconds.


    Not exactly a huge win or anything and 2 minutes is still a lot, but..well, it did shave half a minute off, so I guess it's still an improvement.

    1. Show previous comments  1 more
    2. WereCatf


      @LeventBecause the printer is upstairs, I'm downstairs, and I don't want to do the upstairs-downstairs-upstairs-downstairs song-and-dance every time I want to upload a new print.

    3. Levent


      Is there are a reason why you aren't using octoprint to print? 

    4. WereCatf


      @LeventI find it's more reliable to upload the gcode to the SD-card. I've had multiple times the print go bad with Octoprint crashing or disconnecting or otherwise bugging mid-print, but if I use Octoprint to upload the code to the SD-card and just use Octoprint to monitor the printer and init the print, the printer will handle the actual printing from the card all on its own.