public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] laptop desktop serial connection don't work on one direction
Date: Sat, 5 Nov 2011 10:17:22 +0000	[thread overview]
Message-ID: <201111051017.24591.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CAHNvW1L-rpzhwjjgvtNgGJvaazgSe36SC23ZD8UXuv-np_awUg@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 2051 bytes --]

On Saturday 05 Nov 2011 09:20:19 Kfir Lavi wrote:
> Hi all,
> I have a problem connecting my laptop to my server at home with a serial
> cable.
> I have cable end for /dev/ttyS0 and 2 cable ends for /dev/ttyUSB0.
> This lets me test the connection between all serial outputs.
> Desktop1-minicom <-> Desktop2-minicom
> works with all connections, i.e ttyUSB0 <-> ttyUSB0, or ttyS0 <-> ttyUSB0
> and viseversa.
> So when connecting 2 desktop computers everything works as expected.
> 
> The problem:
> When I connect my laptop to any of those desktops, I get just one way
> connection!
> If I swap the sides of the cable, the one way connection switch side.
> The laptop doesn't have ttyS0, so it have to be connected via ttyUSB0
> When I swap sides, it is just between two usb dongles.
> 
> The usb dongles are PL2303 both sides.
> Settings of minicom is 38400 8n1  Hardware Flow Control=OFF
> 
> Laptop setserial:
> setserial -a /dev/ttyUSB0
> /dev/ttyUSB0, Line 0, UART: 16654, Port: 0x0000, IRQ: 0
>         Baud_base: 460800, close_delay: 0, divisor: 0
>         closing_wait: infinte
>         Flags: spd_normal
> 
> Desktop1 setserial:
> setserial -a /dev/ttyS0
> /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
>         Baud_base: 115200, close_delay: 50, divisor: 0
>         closing_wait: 3000
>         Flags: spd_normal skip_test
> 
> setserial -a /dev/ttyUSB0
> /dev/ttyUSB0, Line 0, UART: 16654, Port: 0x0000, IRQ: 0
>         Baud_base: 460800, close_delay: 0, divisor: 0
>         closing_wait: infinte
>         Flags: spd_normal
> 
> I tried to add the skip_test but this seems to be not working.
> I'm not sure what to do next.
> 
> Any help will be appreciated,
> Thanks,
> Kfir

I think that you will need the pin mapping of a 'null modem' to be able to 
have bidirectional connectivity.

Have a look here:

http://en.wikipedia.org/wiki/Null_modem

I think I still have an RS-232 to D9 null modem adaptor somewhere in my bins 
of spares.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-11-05 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05  9:20 [gentoo-user] [OT] laptop desktop serial connection don't work on one direction Kfir Lavi
2011-11-05 10:17 ` Mick [this message]
2011-11-05 10:48   ` Kfir Lavi
2011-11-05 11:25     ` Kfir Lavi
2011-11-05 19:57   ` bill.longman
2011-11-06  9:03     ` Kfir Lavi
2011-11-06 13:27       ` Andrea Conti
2011-11-06 20:39         ` Kfir Lavi
2011-11-06 10:49     ` Maciej Grela
2011-11-05 12:30 ` bill.longman
2011-11-05 13:28   ` Kfir Lavi
2011-11-07  0:07 ` Jeremy McSpadden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201111051017.24591.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox