From: "Rick Bolen(gm)" <rickbolgm@gmail.com>
To: linux-serial@vger.kernel.org
Subject: using a RS232->RS485 adapter issues...
Date: Mon, 22 Apr 2013 14:19:04 -0400 [thread overview]
Message-ID: <51757F18.8070908@gmail.com> (raw)
Hello,
I'm perplexed in using a RS232C->RS485 dongle that worked perfectly on a
Debian Lenny box for years. Now that I'm migrating to Debian Wheezy,
albeit, different mobo (Intel mini-itx D2500CC) and serial card
(RocketPort), this dongle doesn't work as before.
The dongle sourced working power *from* the host serial port
(cannibalizing DTR, etc?). Using the RocketPort, I have to power the
dongle separately and create a simple data only pass-thru (TX\RX\GND, no
other connections) connection for this dongle to function.
So I don't know if there are voltage level differences on the DTR etc
that result in the failure to power the dongle from the serial port.
Also, having examined the serial port configs with stty between the two
machines, and making all the settings identical, I don't understand why
I have to create the data only pass-thru for communication to work. All
hw\sw flow controls are identical between the working machine and the
new machine... at least as far as stty reports.
1) What serial pin can reliably measure to determine voltage level for
the port (i.e. 12V, 5V, 3.3V)?
2) What else might be different between the working machine and the new
machine with respect to serial port config?
3) Is there an stty config that should effectively provide me with the
same "port config\functionality" that the data only pass-thru adapter
gives me (i.e., can I achieve in software config what I'm doing in
hardware)?
The working (and duplicated) stty config is:
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt
= ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 0; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl
-ixon -ixoff -iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
vt0 ff0
-isig -icanon -iexten -echo echoe echok -echonl -noflsh -xcase -tostop
-echoprt echoctl echoke
Or in stty form:
0:4:cbd:a30:3:1c:7f:15:4:0:0:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
Thanks,
Rick
next reply other threads:[~2013-04-22 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 18:19 Rick Bolen(gm) [this message]
2013-04-22 21:53 ` using a RS232->RS485 adapter issues Grant Edwards
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=51757F18.8070908@gmail.com \
--to=rickbolgm@gmail.com \
--cc=linux-serial@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).