lalee

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • August 31, 2013 at 8:57 pm in reply to: TinyG + Raspberry Pi #4443
    lalee
    Member

    I’ve not had experience with OctoPrint, so I can’t comment on that specifically. The requirements list for running it kind of turned me off.

    I’ve had tough luck with Raspberry Pi. The linux usb driver (dwc_otg) is some of the shoddiest funk I’ve ever had the displeasure of fixing. Try running a HD webcam off the USB port, and the USB driver falls apart at the seams. It also doesn’t help that the RPi folks refuse to acknowledge there’s a problem, even though they’ve hired a guy to specifically work on that code since January. *Sigh*, hopefully it gets better soon.

    At the moment, I’m knee-deep into enhancing the TinyG firmware to operate a ShapeOko/TinyG based 3D printer – at least something usable enough to print up the parts I need for my next machine. ‘Wish TinyG was MIT-licensed to continue forward with it on the next machine build, but can understand the desire to restrict commercial use. I’ll have to go clean-room for the next machine’s hardware/firmware combo.

    Anyway, while glossing over the TinyG firmware code, I noticed the serial buffers are on the small side at only 256 bytes. After recompiling with each direction’s buffer bumped up to 1K, I seem to be getting reliable results at 115K on my v6.

    August 19, 2013 at 6:10 pm in reply to: TinyG + Raspberry Pi #4415
    lalee
    Member

    When using Minicom, the easiest way to check that communications is working is to press Ctrl-X (“reset TinyG”), and possibly Ctrl-M and Ctrl-J to force a carriage-return and linefeed.

    You should be able to get a response.

    While Minicom is not an “official” method, I have found it to be usable enough to do ASCII uploads of GCode files with a few setting tweaks.

    I have a writeup on my blog along with my thoughts on what may be a root-cause in the TinyG firmware preventing ASCII uploads via Minicom or even a “cat [filename] > /dev/ttyUSB0” from working.

    In a nutshell, disabling echo, status verbosity, and text verbosity should keep the line free for TinyG to transmit flow-control characters unimpeded. If you want extra reliability, drop the baud rate to 38400.

    • This reply was modified 11 years, 4 months ago by lalee. Reason: blog link got eaten by wp?
  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)