Small milestone - we passed 300,000 pageviews on the forum today (16th Sept)! 😁 P.S if you are not aware we're running a competition in the facebook group. Head over here to enter, if you haven't already! Ends Sun 22nd Sept!

JGAURORA JGMaker Magic Promotion

NEW Budget 3D Printer: JGMaker Magic
The best deal at the moment is from Gearbest, who are running a flash sale for just $179!
Amazon USA also is offering an $30 instant discount coupon on the JGAurora Magic - a great option for those who want it even faster!


[6th Jun 19] The LATEST JGAurora A5S is already for sale under $400 - use coupon GBA5S11 for a further $15 off!
Print quality is better than A5 out of the box, and it only takes 10 minutes to assemble.
Click here to check out this deal!

Anyone able to print with a pi/octoprint setup?

Hi all.  Was curious if anyone has successfully been able to print using a raspberry pi and octopi setup?  Have a pi3+ connected to the printer via the serial printer port.  I can control everything on the printer remotely except getting it to print.  It makes it a second into the print and then stalls.  Looks like poor/insufficient data transfer rate(why the A5s uses an outdated serial port is beyond me) causing it to stall.  Any recommendations on fixing the issue or am I stuck printing via an sd card?


  • Samuel PinchesSamuel Pinches Posts: 2,060Administrator
    A few things to check:
    - which slicer are you using? if you’re using Cura, the default A5S profile is setup to automatically turn on Mesh Bed Levelling. Normally this is fine, and the A5S will just continue normally even if it’s not setup. However, if no mesh is setup it logs this to the console as an error. In octopi there is an option to disconnect on errors... so you can guess what happens next! If you are not using mesh bed levelling, remove the “M420 S1” command from pronterface.
  • Samuel PinchesSamuel Pinches Posts: 2,060Administrator
    If that’s not it, try printing via octopi, but upload the file to the SD card on the printer and try print from there.

    also, try printing via pronterface, and see if the same problem occurs.
  • chainbreaker2012chainbreaker2012 Posts: 30Member
    Had this exact same issue using Cura 4.1 had to roll back to cura 4.0 that fixed my issue
  • Samuel PinchesSamuel Pinches Posts: 2,060Administrator
    Cura 4.2 may fix that as there is a known bug in 4.1.
  • charnjitsainicharnjitsaini Posts: 2Member
    Yes, I am using Raspberry pi 4 (2gb) with Cura 4.2.1 & marlin custom firmware on a5s 2.0D & it is working fine.
    Thanked by 1Samuel Pinches
  • Samuel PinchesSamuel Pinches Posts: 2,060Administrator
    Excellent, thank you for the feedback @charnjitsaini ! :smiley:
Sign In or Register to comment.