Modem problems

Chris Osburn/CO149 seatcp@wetnet.net
Thu, 17 Oct 2002 21:28:57 -0700


Did you have it set to 7 bits, even parity before?  I usually do 8/none.
Might not be wrong, but it is unusual. :-)  Also, see if hitting ctrl-C
three times will wake it up.

Chris Osburn
KD7DVD


On Thu, Oct 17, 2002 at 08:44:07PM -0700, K. David Prince wrote:
> Well, it's back to the drawing board.  I had this thing working, but for
> some reason I lost it.  Here's the setup:
> 
> Debian laptop, AEA PK-96, Maxon radio.  I got a new address <44.24.123.9>,
> so I stopped the setup I had been using for testing purposes
> <44.24.123.249>.  But, for some reason, after I reconfigured for the new
> address, I couldn't reconnect to the modem.  Here's what I have on
> /dev/ttyS0:
> 
> acs:~# setserial -a /dev/ttyS0
> /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
>         Baud_base: 9600, close_delay: 50, divisor: 0
>         closing_wait: 3000
>         Flags: spd_normal skip_test
> 
> Using minicom, I have the following:
> 
> A -    Serial Device      : /dev/ttyS0                                x
> B - Lockfile Location     : /var/lock
> C -   Callin Program      :
> D -  Callout Program      :
> E -    Bps/Par/Bits       : 9600 7E1
> F - Hardware Flow Control : No
> G - Software Flow Control : Yes
> 
> I reset the modem, so DCD/CON/STA/MAIL/POWER leds are on, XMT off.  But,
> with the above settings, hitting the asterisk doesn't bring up the "cmd:"
> line.  Turning the modem on with minicom up toggles the "online" message:
> 
>  CTRL-A Z for help |  9600 7E1 | NOR | Minicom 1.83.1 | VT102 | Online 00:00
> 
> So, it seems the cable is working.  But, just to check I did use another
> serial cable with no luck.
> 
> What am I missing here?  The weird thing is that a few days ago I had this
> puppy working just fine.
> 
> Any hints would be helpful.
> 
> Dave
> WB0RAZ
> 
> _______________________________________________
> Seatcp mailing list
> Seatcp@wetnet.net
> http://wetnet.net/mailman/listinfo/seatcp