Re: serial port question

From: paul beard <paulbeard_at_gmail.com>
Date: Fri, 06 Oct 2023 04:42:23 UTC
This has all been great…got me on the right track. I am not getting a
response from the device but now I know it's not me. Hoping the developers
can fill in the gaps there.

On Thu, Oct 5, 2023 at 9:11 PM Edward Sanford Sutton, III <
mirror176@hotmail.com> wrote:

> On 10/5/23 17:28, paul beard wrote:
> > Not strictly FreeBSD-based but adjacent, surely…
> >
> > I have a 3D printer that has a serial port connection through USB but
> > it's not working through the various apps that obscure the details in
> > the name of "convenience." You know what I mean. I like convenience as
> > much as anyone but sometimes I just have to get on with it. Does anyone
> > have experience in communicating with really simple machines over a
> > serial connection? It's not always easy to ID the serial device but
> > that's a separate problem. Allegedly I can communicate up to 115k but
> > I'll settle for a lot less to send simple commands like M502 or M500.
>
>    If memory serves, multiple device permissions may be needed for the
> one device node to work. I had the following rules in a /etc/devfs.rules
> entry (which involves a header+/etc/rc.conf entry fi I recall). Likely
> only the first two mattered but I don't remember now.
> add path 'cuaU*' mode 0777 group operator
> add path 'ttyU*' mode 0777 group operator
> add path 'usb/*' mode 0660 group operator
>
>    Other posts are also correct about some software not searching
> through port labels when they vary from Linux. Most of my effort was put
> toward keeping a Makerbot Thing-O-Matic working off and on over the
> years but that kept me mostly just playing with replicatorg due to its
> incompatibilities with other software that I someday need to setup a
> workflow to migrate to. reprap software I had started to get basic
> control from but recall manually patching its list of checked and
> available ports when I did it years ago.
>
>    It isn't recommended but I have been known to either test software as
> root, or change many more permissions than I need to figure out how to
> get things working.
>
>    If you say what printer/software you are working with, others may be
> able to chime in with more specifics.
>
>

-- 
Paul Beard / www.paulbeard.org/