Close



Results 1 to 10 of 14

Hybrid View

  1. #1
    Quote Originally Posted by warkmal View Post
    Don't use cura to talk directly to the printer. The thing that doesn't read gcode directly is your printer. Makerbots and clones use x3g protocol. Use cura to do the slicing and then use gpx or RepG to convert the gcode to x3g for the SD card. You'll particularly need to get the start and and gcode to be correct for your printer.
    I understand x3g for the SD card. But i don't use an SD card (yet), I use a direct connection. Can't see the virtue in handing an extra bit of hardware from one machine to the other unless I needed to take the computer somewhere else. So does your comment still apply?

  2. #2
    Technician
    Join Date
    Feb 2015
    Posts
    91
    Quote Originally Posted by Joymaker View Post
    I understand x3g for the SD card. But i don't use an SD card (yet), I use a direct connection. Can't see the virtue in handing an extra bit of hardware from one machine to the other unless I needed to take the computer somewhere else. So does your comment still apply?
    Yes, still applies. The printer itself doesn't understand gcode directly over the wire or from an SD card. You can only use printer hosts that understand and send x3g protocol (ie not Cura).

    At higher speeds you'll get better results from the SD card because you'll avoid pauses due to serial communication interruption (even 10ms pauses are sufficient to cause a zit on your print). You can avoid passing it back and forth by using a FlashAir and putting things on the SD card wirelessly.

    That said, these days I mostly print from OctoPrint running on a Raspberry Pi connected to the printer via USB and upload gcode directly to that. But that's because I want to put as many hours on my plugin as possible for testing purposes.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •