From owner-freebsd-questions Wed Oct 18 18:46:22 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id AAA4837B479 for ; Wed, 18 Oct 2000 18:46:15 -0700 (PDT) Received: (qmail 24793 invoked by uid 100); 19 Oct 2000 01:46:14 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14830.21093.897235.687784@guru.mired.org> Date: Wed, 18 Oct 2000 20:46:13 -0500 (CDT) To: Chris Aitken Cc: questions@freebsd.org Subject: Re: Commandline Access to a Serial Port In-Reply-To: <5.0.0.25.0.20001019123412.023dfac8@mail.ideal.net.au> References: <3302859@toto.iv> <5.0.0.25.0.20001019123412.023dfac8@mail.ideal.net.au> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Aitken writes: > At 08:27 PM 18/10/2000, you wrote: > >Chris Aitken writes: > > > Does anyone have any suggestions as to a tool I can use on my FreeBSD 3.4 > > > Stable box that can allow me to communicate with my Serial Port ? > >Are you looking for tip and/or cu? If the man pages tell you that's > >wrong, provide more details about what you want to do. > I have been playing with cu, which seems to be a possibility, but after a > few misc commands, cu seems to have stopped working, and I cant seem to get > it back to how it was. > > I ran > cu -l /dev/cuaa0 -s 9600 > > which allowed me to connect to the serial port, issue it an AT command it > received an OK back. But when I tried the needed command, it came back as > error (which when issued through minicom still works perfectly). > > Then after a couple of playing around with ~| and other things, its all > screwed up, and now it wont respond after it connects to the port. Sounds like you found the right tool set. You might try tip instead, though there's no real reason to expect it to be better. You also need to make that parity, word length, and stop bits are all correct. That's a bit easier with tip than cu, as you can store tip configuration in /etc/remote.