Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #28598
| From | Les Cargill <lcargill99@comcast.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Serial Port Emulation |
| Date | 2019-03-04 17:44 -0600 |
| Organization | A noiseless patient Spider |
| Message-ID | <q5kcv5$67n$1@dont-email.me> (permalink) |
| References | (7 earlier) <slrn3uboq6oaj4.r5h.andrews@sdf.lonestar.org> <q4sbal$sre$1@dont-email.me> <v3i37e57qvoghiqp27ki59vb0dj5g0hm16@4ax.com> <q57n0n$n4$1@dont-email.me> <q583bd$mas$1@dont-email.me> |
David Brown wrote: > On 28/02/2019 05:15, Les Cargill wrote: >> Robert Wessel wrote: >>> On Sat, 23 Feb 2019 14:48:40 -0600, Les Cargill >>> <lcargill99@comcast.com> wrote: >>> >>>> Andrew Smallshaw wrote: >>>>> On 2019-02-18, David Brown <david.brown@hesbynett.no> wrote: >>>>>> >>>>>> RS-232 is short distance too (though a bit longer than TTL) - for long >>>>>> distances you use RS-485 or RS-422. RS-232 is a legacy standard - >>>>>> there >>>>>> is plenty of old stuff the still has it, but it would be a strange >>>>>> choice for anything new. >>>>> >>>>> I'm genuinely interested to hear people thoughts on this. Personally >>>>> if I anticipate a true long life interfacing requirement - 20, 30, >>>>> 40 years - RS232 is my preferred option, ideally (if appropriate >>>>> to the use case) with a command line on it. >>>> <snip> >>>>> >>>>> I don't pretend to have answers in the general case, just interested >>>>> in what peoples thoughts are. >>>>> >>>> >>>> Anything you can do with RS323 you can do with Ethernet. There are >>>> pathological size/weight/power cases where Ethernet doesn't fit but >>>> if it does... >>> >>> >>> Ethernet does have a couple of annoying configuration issues, and >>> requires either a custom client on an attached PC, or requires enough >>> software to implement TCP and a TELNET or HTTP server (and TCP/IP >>> brings a couple of annoying configuration issues as well). >>> >> >> There exist things like RasPi boards which can have FTDI USB >> RS232 ports attached. So really? You should be able to use DynDNS and >> DHCP and that's about all the config you need. With the RasPi's I have >> seen, it's even 802.11 - just carry an AP and you're in. >> >> You can do all the fiddly bits once, and offsite. >> >> Generally, I'll have a custom TCP server running on the Pi, which >> provides the option of encoding any twiddly parts about the device on >> the other end of the FTDI device, within the Pi. > > I don't know what kind of systems you work with, but to me a Pi is > convenient for testing and developing, but is out of the question for > most delivered systems. The same goes for jumbled mixups with dynamic > DNS - fine for test setups, not for deployment. > All I can say is that a Pi makes a fine terminal server. Whether it's appropriate for deployed systems is up to you. I'd much rather use a Pi for field debugging rather than be tied to a serial cable's length from the DUT. >> >>> And, of course, as soon as you do have an Ethernet connection, >>> anything non-TCP/IP is ruled out because the customer and marketing >>> will immediately want to be able to do (whatever) from across the >>> campus, and then inevitably further than that. And then you have >>> security issues. >>> >> >> Almost everything has Ethernet now. > > Almost every microcontroller does /not/ have Ethernet. Almost every > electronics board made does /not/ have Ethernet. > Then you have to do something else, and it'll probably have to be a fully supported, costed and tracked set of circuit packs along with the associated soft deliverables. And it'll rot like beef in the summer sun as soon as the budget gets cut. Underspeccing the I/O capability of a target made a lot more sense 30 years ago than it does now. >> >>> Definitely the way to go if you can, but there are enough hurdles that >>> you can find yourself longing for async RS-232 and a terminal >>> emulator. >>> >> >> Oh, not so much :) Well, sometimes :) >> > -- Les Cargill
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-17 02:08 -0800
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-17 13:42 +0100
Re: Serial Port Emulation Chris <xxx.syseng.yyy@gfsys.co.uk> - 2019-02-17 15:49 +0000
Re: Serial Port Emulation Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2019-02-17 18:54 +0200
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-17 21:16 +0100
Re: Serial Port Emulation Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2019-02-18 10:38 +0200
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-18 10:49 +0100
Re: Serial Port Emulation Richard Damon <Richard@Damon-Family.org> - 2019-02-18 07:25 -0500
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-18 14:31 +0100
Re: Serial Port Emulation Andrew Smallshaw <andrews@sdf.org> - 2019-02-19 16:10 +0000
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-19 09:12 -0800
Re: Serial Port Emulation upsidedown@downunder.com - 2019-02-19 19:58 +0200
Re: Serial Port Emulation Grant Edwards <invalid@invalid.invalid> - 2019-02-19 18:22 +0000
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-19 22:50 +0100
Re: Serial Port Emulation Grant Edwards <invalid@invalid.invalid> - 2019-02-19 22:23 +0000
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-20 08:53 +0100
Re: Serial Port Emulation upsidedown@downunder.com - 2019-02-20 10:17 +0200
Re: Serial Port Emulation Theo <theom+news@chiark.greenend.org.uk> - 2019-02-19 22:35 +0000
Re: Serial Port Emulation upsidedown@downunder.com - 2019-02-20 01:36 +0200
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-19 19:40 -0800
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-20 09:00 +0100
Re: Serial Port Emulation upsidedown@downunder.com - 2019-02-19 19:16 +0200
Re: Serial Port Emulation Theo <theom+news@chiark.greenend.org.uk> - 2019-02-19 22:28 +0000
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-20 10:32 +0100
Re: Serial Port Emulation Robert Wessel <robertwessel2@yahoo.com> - 2019-02-19 18:44 -0600
Re: Serial Port Emulation Les Cargill <lcargill99@comcast.com> - 2019-02-23 14:48 -0600
Re: Serial Port Emulation Robert Wessel <robertwessel2@yahoo.com> - 2019-02-23 16:34 -0600
Re: Serial Port Emulation Les Cargill <lcargill99@comcast.com> - 2019-02-27 22:15 -0600
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-02-28 08:41 +0100
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-28 15:07 -0800
Re: Serial Port Emulation David Brown <david.brown@hesbynett.no> - 2019-03-01 10:04 +0100
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-03-01 13:09 -0800
Re: Serial Port Emulation Les Cargill <lcargill99@comcast.com> - 2019-03-04 17:58 -0600
Re: Serial Port Emulation Paul Rubin <no.email@nospam.invalid> - 2019-03-01 02:25 -0800
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-03-01 13:16 -0800
Re: Serial Port Emulation Paul Rubin <no.email@nospam.invalid> - 2019-03-01 16:45 -0800
Re: Serial Port Emulation Les Cargill <lcargill99@comcast.com> - 2019-03-04 17:44 -0600
Re: Serial Port Emulation Richard Damon <Richard@Damon-Family.org> - 2019-02-23 19:37 -0500
Re: Serial Port Emulation Les Cargill <lcargill99@comcast.com> - 2019-02-27 22:17 -0600
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-18 06:28 -0800
Re: Serial Port Emulation Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2019-02-18 22:33 +0100
Re: Serial Port Emulation "A.P.Richelieu" <aprichelieu@gmail.com> - 2019-02-17 21:06 +0100
Re: Serial Port Emulation raimond.dragomir@gmail.com - 2019-02-17 21:56 -0800
Re: Serial Port Emulation gnuarm.deletethisbit@gmail.com - 2019-02-17 22:37 -0800
Re: Serial Port Emulation "Mat Nieuwenhoven" <mnieuw@zap.a2000.nl> - 2019-02-18 12:34 +0100
csiph-web