Date: Wed, 25 Oct 2017 11:43:18 -0500 From: Kyle Evans <kevans91@ksu.edu> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: We do serial differently. Message-ID: <CACNAnaGf7yAP6Sc6coNhZVcZyw0OA1ZUvaOu=t3D-tfn4sXwcQ@mail.gmail.com> In-Reply-To: <CACpH0MdpucayKsWzPN86w9tJkydQhhz5eL8GLHfADE1C12kr3A@mail.gmail.com> References: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9%2BdUtp66%2BSSjVuyhpxA@mail.gmail.com> <CACNAnaEu0-mdO9HTgOX8BRF5_FMVsszQzan6RYKEsLzoMgDXjQ@mail.gmail.com> <CACpH0MdpucayKsWzPN86w9tJkydQhhz5eL8GLHfADE1C12kr3A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 25, 2017 at 11:34 AM, Zaphod Beeblebrox <zbeeble@gmail.com> wrote: > On Mon, Oct 23, 2017 at 9:45 AM, Kyle Evans <kevans91@ksu.edu> wrote: > >> Hi, >> >> Are you able to connect to it otherwise (w/ cu or friends) and issue, >> say, an M105 manually? >> > > yes. With CU I can connect, it resets, then I can issue an "M105<cr>" and > it parrots back some status. > Ok, cool, that's expected and sounds like Pronterface is doing something it shouldn't be. I'll poke at it a little bit more- last I checked, it didn't look like it was doing anything too crazy with pyserial and I've got a working OctoPrint (w/ pyserial) setup, so I know that works to some extent.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaGf7yAP6Sc6coNhZVcZyw0OA1ZUvaOu=t3D-tfn4sXwcQ>