Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #31541 > unrolled thread
| Started by | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| First post | 2023-01-17 07:24 -0800 |
| Last post | 2023-03-29 00:44 -0700 |
| Articles | 20 on this page of 155 — 18 participants |
Back to article view | Back to comp.arch.embedded
Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 07:24 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 11:31 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 12:19 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 13:07 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 13:29 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 14:04 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 14:47 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 15:32 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 15:44 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 16:04 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 17:32 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 20:02 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 20:24 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-17 20:56 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-17 22:30 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-18 00:37 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-18 04:43 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-18 14:19 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-18 23:15 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-19 12:21 -0800
Re: Boxed MCU with RS-232 Port Andrew Smallshaw <andrews@sdf.org> - 2023-01-18 12:15 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-18 04:55 -0800
Re: Boxed MCU with RS-232 Port Andrew Smallshaw <andrews@sdf.org> - 2023-01-18 13:22 +0000
Re: Boxed MCU with RS-232 Port Andrew Smallshaw <andrews@sdf.org> - 2023-01-18 13:28 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-18 06:20 -0800
Re: Boxed MCU with RS-232 Port David Brown <david.brown@hesbynett.no> - 2023-01-18 10:04 +0100
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-01-18 16:18 +0000
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-18 14:10 -0800
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-01-19 10:29 +0000
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-01-19 05:41 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-19 10:00 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-19 12:42 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-19 14:10 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-19 16:16 -0800
Re: Boxed MCU with RS-232 Port Grant Edwards <invalid@invalid.invalid> - 2023-01-19 16:07 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-19 10:13 -0800
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-01-19 14:51 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-19 10:06 -0800
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-01-20 13:03 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-20 06:28 -0800
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-01-20 19:14 -0800
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-01-20 20:41 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-01-21 05:05 -0700
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-01-21 10:53 +0000
Re: Boxed MCU with RS-232 Port Herbert Kleebauer <klee@unibwm.de> - 2023-01-20 19:17 +0100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-20 12:37 -0800
Re: Boxed MCU with RS-232 Port Dimiter_Popoff <dp@tgi-sci.com> - 2023-01-20 23:02 +0200
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-20 14:08 -0800
Re: Boxed MCU with RS-232 Port Dimiter_Popoff <dp@tgi-sci.com> - 2023-01-21 01:38 +0200
Re: Boxed MCU with RS-232 Port antispam@math.uni.wroc.pl - 2023-01-21 01:58 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-20 18:44 -0800
Re: Boxed MCU with RS-232 Port antispam@math.uni.wroc.pl - 2023-01-21 20:02 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-22 17:12 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-02-03 09:22 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-02-03 10:04 -0800
Re: Boxed MCU with RS-232 Port Dimiter_Popoff <dp@tgi-sci.com> - 2023-03-26 22:24 +0300
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 02:27 -0700
Re: Boxed MCU with RS-232 Port pozz <pozzugno@gmail.com> - 2023-01-20 08:54 +0100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-01-20 01:03 -0800
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-22 12:18 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-22 20:35 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-22 23:26 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-22 23:28 -0700
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-03-23 10:06 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 00:59 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-23 09:00 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 01:03 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-23 08:54 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 01:02 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 01:43 -0700
Re: Boxed MCU with RS-232 Port Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2023-03-24 12:44 +0100
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-03-24 14:20 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 08:08 -0700
Re: Boxed MCU with RS-232 Port Theo <theom+news@chiark.greenend.org.uk> - 2023-03-24 16:23 +0000
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 13:42 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 14:31 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 18:19 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 18:22 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 18:34 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 19:43 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 20:01 -0700
Re: Boxed MCU with RS-232 Port Paul Rubin <no.email@nospam.invalid> - 2023-03-24 21:18 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-24 15:35 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 18:21 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-24 19:21 -0700
Re: Boxed MCU with RS-232 Port George Neuner <gneuner2@comcast.net> - 2023-03-25 21:42 -0400
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-25 19:26 -0700
Re: Boxed MCU with RS-232 Port Jim Jackson <jj@franjam.org.uk> - 2023-03-26 18:27 +0000
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 13:23 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 13:32 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 13:52 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-26 19:30 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 20:31 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 07:04 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 09:21 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 09:56 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 13:08 -0700
Re: Boxed MCU with RS-232 Port Jim Jackson <jj@franjam.org.uk> - 2023-03-27 20:46 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:07 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:07 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 14:50 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:07 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:24 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:36 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:37 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:42 -0700
Re: Boxed MCU with RS-232 Port David Brown <david.brown@hesbynett.no> - 2023-03-27 11:03 +0200
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 07:11 -0700
Re: Boxed MCU with RS-232 Port Dimiter_Popoff <dp@tgi-sci.com> - 2023-03-27 17:47 +0300
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 08:05 -0700
Re: Boxed MCU with RS-232 Port Dimiter_Popoff <dp@tgi-sci.com> - 2023-03-27 19:09 +0300
Re: Boxed MCU with RS-232 Port David Brown <david.brown@hesbynett.no> - 2023-03-27 17:38 +0200
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-26 19:22 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-26 19:11 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 13:37 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-26 19:28 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 13:38 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:05 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:08 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:25 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:38 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 13:23 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-26 19:25 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-26 20:31 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 07:05 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 09:18 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 10:09 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 12:16 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 13:03 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 13:17 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 15:05 -0700
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-27 15:40 -0700
Re: Boxed MCU with RS-232 Port Clifford Heath <no.spam@please.net> - 2023-03-28 10:36 +1100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 17:59 -0700
Re: Boxed MCU with RS-232 Port Clifford Heath <no.spam@please.net> - 2023-03-28 12:58 +1100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 20:41 -0700
Re: Boxed MCU with RS-232 Port Clifford Heath <no.spam@please.net> - 2023-03-28 15:21 +1100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-28 08:37 -0700
Re: Boxed MCU with RS-232 Port Jim Jackson <jj@franjam.org.uk> - 2023-03-28 20:00 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-28 13:06 -0700
Re: Boxed MCU with RS-232 Port Clifford Heath <no.spam@please.net> - 2023-03-29 08:03 +1100
Re: Boxed MCU with RS-232 Port Don Y <blockedofcourse@foo.invalid> - 2023-03-28 00:11 -0700
Re: Boxed MCU with RS-232 Port "b...@gmx.com" <bl1@gmx.com> - 2023-03-27 16:17 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 18:12 -0700
Re: Boxed MCU with RS-232 Port Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2023-03-24 19:26 +0100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 08:03 -0700
Re: Boxed MCU with RS-232 Port Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2023-03-24 19:10 +0100
Re: Boxed MCU with RS-232 Port Herbert Kleebauer <klee@unibwm.de> - 2023-03-24 17:16 +0100
Re: Boxed MCU with RS-232 Port Herbert Kleebauer <klee@unibwm.de> - 2023-03-24 18:54 +0100
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-24 11:34 -0700
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-27 10:18 -0700
Re: Boxed MCU with RS-232 Port Uwe Bonnes <bon@hertz.ikp.physik.tu-darmstadt.de> - 2023-03-28 20:53 +0000
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-28 16:12 -0700
Re: Boxed MCU with RS-232 Port Niklas Holsti <niklas.holsti@tidorum.invalid> - 2023-03-29 09:06 +0300
Re: Boxed MCU with RS-232 Port Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-29 00:44 -0700
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 14:50 -0700 |
| Message-ID | <e5eb3680-693f-4650-aab2-6ed9ee36f33bn@googlegroups.com> |
| In reply to | #31739 |
On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: > On 3/27/2023 9:56 AM, Rick C wrote: > > On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: > >> On 3/27/2023 7:04 AM, Rick C wrote: > >>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: > >>>> On 3/26/2023 7:30 PM, Rick C wrote: > >>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: > >>>>>> On 3/26/2023 1:32 PM, Don Y wrote: > >>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: > >>>>>>>> I build these into connector shells that are designed to support a > >>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label > >>>>>>>> telling me the device that it is intended to normalize (e.g., I have > >>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function > >>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, > >>>>>>>> etc.) > >>>>>>> > >>>>>>> This is the APC widget mentioned: > >>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> > >>>>>> And this is the COTS *PC* that I use as a name server: > >>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> > >>>>>> > >>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT > >>>>>> network connection (it's just a name server, it doesn't need to > >>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), > >>>>>> wifi and USB. The four mounting holes visible are the VESA standard > >>>>>> (I have these mounted between my monitor and support arm) > >>>>>> > >>>>>> As an ISA PC, it will run damn near any OS intended for such > >>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted > >>>>>> AND TARGETED tools are available (I have a LFC monitor wired to > >>>>>> one of the serial ports to discipline my time service as that > >>>>>> was easier/cheaper to implement than any other solution!). > >>>>> > >>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. > >>>>> > >>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. > >>>>> > >>>>> Thanks, > >>>> To show that if you buy something (or, in my case, RESCUE something with > >>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how > >>>> a responsible design would pin the connectors. > >>>> > >>>> I rescued this item. I had no idea what sort of CPU was inside. > >>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would > >>>> be serial ports -- why? because the rest of the box LOOKED like > >>>> it was trying to be a PC, albeit in a very small form factor > >>>> and with a wonky power connector). Or, if the 8P8C was actually > >>>> a network port. Or, if the circular DIN was intended as a PS/2 > >>>> keyboard. Or, the DE15 as a video port. > >>>> > >>>> The markings by the connectors *suggested* these uses. And, it > >>>> seemed more likely than not... > >>>> > >>>> With *no* documentation, I opted to plug in a monitor (largely > >>>> confident that the resolution would be supported by this > >>>> "unknown" box) and keyboard and poke around the SETUP screen > >>>> (which I *also* assumed would be available... somehow). > >>>> > >>>> Why was I *not* surprised with that outcome? > >>>> > >>>> You've posted a link to a device selected from a vendor > >>>> that I'm unfamiliar with and, you infer, insufficiently > >>>> documented (hey, at least you KNOW who made/makes your > >>>> device! That's more than *I* had to go on!). > >>>> > >>>> Then, expect "us" to give you a definitive answer about > >>>> specifics related to that device. And, frown on those of > >>>> us that point this out to you as being "not helpful". > >>>> > >>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE > >>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, > >>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR > >>>> DIRECTIONS. I suspect more than a few people learned something > >>>> about the standard, here. And, the approach I have taken > >>>> to handle pinning differences (my "widgets"). > >>>> > >>>> Why aren't you talking to the vendor? Do you expect him/her > >>>> to be reading your posts, here? > >>>> > >>>> Buy something that appears to be a PC. It won't succeed > >>>> in that ubiquitous market if it differs radically from > >>>> other devices that also claim to be PCs. So, you can, > >>>> /with a high degree of confidence/, expect the connectors > >>>> to be pinned the way a PC would pin them. > >>>> > >>>> Or, buy from Joe's Garage Shop -- ask for Joe. > >>>> > >>>> THIS example is a testament to how I was able to make use > >>>> of a COMPLETELY undocumented device simply by making a > >>>> good assumption about the intent of the product and the > >>>> logical conclusions that flow from that assumption. The > >>>> only examination required was trying to deduce the > >>>> connections to the power connector and the associated > >>>> voltages (but, I had a pretty good feeling it wouldn't > >>>> be 7.293VDC or 28V or... again, because of the likely market) > >>> > >>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? > >> You still fail to see how this applies to "determining which > >> pin is the output". > >> > >> Wow, can a person get any denser? > > > > No, you can't. You completely fail to understand what is going on with this issue. > > > > > >> Hey, rick, I've got a box here. It's got a DB25 connector on it. > >> Is it for a printer? Serial port? SCSI interface? I'd post a photo > >> of it but the only distinguishable feature is the connector... > >> > >> Surely you should be able to answer this question! > > > > What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. > > > > > >> BTW, Joe is still waiting for your call... > > > > I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. > Wow, had you put this much effort into YOUR problem, you could have put > a SoC on a board and written the page of code it would take to suit your > problem. The BALANCE of the time, you could have ASSEMBLED the boards > into boxes! > > It's now 27 March. Your initial post was 17 January. A productive two months > for you, eh? Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. Thanks for your concern about the use of my time. -- Rick C. +-+-- Get 1,000 miles of free Supercharging +-+-- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-27 15:07 -0700 |
| Message-ID | <tvt42s$3dd67$1@dont-email.me> |
| In reply to | #31743 |
On 3/27/2023 2:50 PM, Rick C wrote: > On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: >> On 3/27/2023 9:56 AM, Rick C wrote: >>> On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: >>>> On 3/27/2023 7:04 AM, Rick C wrote: >>>>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: >>>>>> On 3/26/2023 7:30 PM, Rick C wrote: >>>>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: >>>>>>>> On 3/26/2023 1:32 PM, Don Y wrote: >>>>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: >>>>>>>>>> I build these into connector shells that are designed to support a >>>>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label >>>>>>>>>> telling me the device that it is intended to normalize (e.g., I have >>>>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function >>>>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, >>>>>>>>>> etc.) >>>>>>>>> >>>>>>>>> This is the APC widget mentioned: >>>>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> >>>>>>>> And this is the COTS *PC* that I use as a name server: >>>>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> >>>>>>>> >>>>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT >>>>>>>> network connection (it's just a name server, it doesn't need to >>>>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), >>>>>>>> wifi and USB. The four mounting holes visible are the VESA standard >>>>>>>> (I have these mounted between my monitor and support arm) >>>>>>>> >>>>>>>> As an ISA PC, it will run damn near any OS intended for such >>>>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted >>>>>>>> AND TARGETED tools are available (I have a LFC monitor wired to >>>>>>>> one of the serial ports to discipline my time service as that >>>>>>>> was easier/cheaper to implement than any other solution!). >>>>>>> >>>>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. >>>>>>> >>>>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. >>>>>>> >>>>>>> Thanks, >>>>>> To show that if you buy something (or, in my case, RESCUE something with >>>>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how >>>>>> a responsible design would pin the connectors. >>>>>> >>>>>> I rescued this item. I had no idea what sort of CPU was inside. >>>>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would >>>>>> be serial ports -- why? because the rest of the box LOOKED like >>>>>> it was trying to be a PC, albeit in a very small form factor >>>>>> and with a wonky power connector). Or, if the 8P8C was actually >>>>>> a network port. Or, if the circular DIN was intended as a PS/2 >>>>>> keyboard. Or, the DE15 as a video port. >>>>>> >>>>>> The markings by the connectors *suggested* these uses. And, it >>>>>> seemed more likely than not... >>>>>> >>>>>> With *no* documentation, I opted to plug in a monitor (largely >>>>>> confident that the resolution would be supported by this >>>>>> "unknown" box) and keyboard and poke around the SETUP screen >>>>>> (which I *also* assumed would be available... somehow). >>>>>> >>>>>> Why was I *not* surprised with that outcome? >>>>>> >>>>>> You've posted a link to a device selected from a vendor >>>>>> that I'm unfamiliar with and, you infer, insufficiently >>>>>> documented (hey, at least you KNOW who made/makes your >>>>>> device! That's more than *I* had to go on!). >>>>>> >>>>>> Then, expect "us" to give you a definitive answer about >>>>>> specifics related to that device. And, frown on those of >>>>>> us that point this out to you as being "not helpful". >>>>>> >>>>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE >>>>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, >>>>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR >>>>>> DIRECTIONS. I suspect more than a few people learned something >>>>>> about the standard, here. And, the approach I have taken >>>>>> to handle pinning differences (my "widgets"). >>>>>> >>>>>> Why aren't you talking to the vendor? Do you expect him/her >>>>>> to be reading your posts, here? >>>>>> >>>>>> Buy something that appears to be a PC. It won't succeed >>>>>> in that ubiquitous market if it differs radically from >>>>>> other devices that also claim to be PCs. So, you can, >>>>>> /with a high degree of confidence/, expect the connectors >>>>>> to be pinned the way a PC would pin them. >>>>>> >>>>>> Or, buy from Joe's Garage Shop -- ask for Joe. >>>>>> >>>>>> THIS example is a testament to how I was able to make use >>>>>> of a COMPLETELY undocumented device simply by making a >>>>>> good assumption about the intent of the product and the >>>>>> logical conclusions that flow from that assumption. The >>>>>> only examination required was trying to deduce the >>>>>> connections to the power connector and the associated >>>>>> voltages (but, I had a pretty good feeling it wouldn't >>>>>> be 7.293VDC or 28V or... again, because of the likely market) >>>>> >>>>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? >>>> You still fail to see how this applies to "determining which >>>> pin is the output". >>>> >>>> Wow, can a person get any denser? >>> >>> No, you can't. You completely fail to understand what is going on with this issue. >>> >>> >>>> Hey, rick, I've got a box here. It's got a DB25 connector on it. >>>> Is it for a printer? Serial port? SCSI interface? I'd post a photo >>>> of it but the only distinguishable feature is the connector... >>>> >>>> Surely you should be able to answer this question! >>> >>> What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. >>> >>> >>>> BTW, Joe is still waiting for your call... >>> >>> I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. >> Wow, had you put this much effort into YOUR problem, you could have put >> a SoC on a board and written the page of code it would take to suit your >> problem. The BALANCE of the time, you could have ASSEMBLED the boards >> into boxes! >> >> It's now 27 March. Your initial post was 17 January. A productive two months >> for you, eh? > > Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. "Multi-million dollar job". And you're dicking around with nickels and dimes? Buy 20 BRAND SPANKING NEW pc's and be done with it! Wow, what a great businessman -- not! > Thanks for your concern about the use of my time. I'd hate to see you waste it -- as you have, ours!
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 15:24 -0700 |
| Message-ID | <2a174119-0cf9-4382-be8f-65c180ed77aan@googlegroups.com> |
| In reply to | #31746 |
On Monday, March 27, 2023 at 6:07:29 PM UTC-4, Don Y wrote: > On 3/27/2023 2:50 PM, Rick C wrote: > > On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: > >> On 3/27/2023 9:56 AM, Rick C wrote: > >>> On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: > >>>> On 3/27/2023 7:04 AM, Rick C wrote: > >>>>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: > >>>>>> On 3/26/2023 7:30 PM, Rick C wrote: > >>>>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: > >>>>>>>> On 3/26/2023 1:32 PM, Don Y wrote: > >>>>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: > >>>>>>>>>> I build these into connector shells that are designed to support a > >>>>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label > >>>>>>>>>> telling me the device that it is intended to normalize (e.g., I have > >>>>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function > >>>>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, > >>>>>>>>>> etc.) > >>>>>>>>> > >>>>>>>>> This is the APC widget mentioned: > >>>>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> > >>>>>>>> And this is the COTS *PC* that I use as a name server: > >>>>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> > >>>>>>>> > >>>>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT > >>>>>>>> network connection (it's just a name server, it doesn't need to > >>>>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), > >>>>>>>> wifi and USB. The four mounting holes visible are the VESA standard > >>>>>>>> (I have these mounted between my monitor and support arm) > >>>>>>>> > >>>>>>>> As an ISA PC, it will run damn near any OS intended for such > >>>>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted > >>>>>>>> AND TARGETED tools are available (I have a LFC monitor wired to > >>>>>>>> one of the serial ports to discipline my time service as that > >>>>>>>> was easier/cheaper to implement than any other solution!). > >>>>>>> > >>>>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. > >>>>>>> > >>>>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. > >>>>>>> > >>>>>>> Thanks, > >>>>>> To show that if you buy something (or, in my case, RESCUE something with > >>>>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how > >>>>>> a responsible design would pin the connectors. > >>>>>> > >>>>>> I rescued this item. I had no idea what sort of CPU was inside. > >>>>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would > >>>>>> be serial ports -- why? because the rest of the box LOOKED like > >>>>>> it was trying to be a PC, albeit in a very small form factor > >>>>>> and with a wonky power connector). Or, if the 8P8C was actually > >>>>>> a network port. Or, if the circular DIN was intended as a PS/2 > >>>>>> keyboard. Or, the DE15 as a video port. > >>>>>> > >>>>>> The markings by the connectors *suggested* these uses. And, it > >>>>>> seemed more likely than not... > >>>>>> > >>>>>> With *no* documentation, I opted to plug in a monitor (largely > >>>>>> confident that the resolution would be supported by this > >>>>>> "unknown" box) and keyboard and poke around the SETUP screen > >>>>>> (which I *also* assumed would be available... somehow). > >>>>>> > >>>>>> Why was I *not* surprised with that outcome? > >>>>>> > >>>>>> You've posted a link to a device selected from a vendor > >>>>>> that I'm unfamiliar with and, you infer, insufficiently > >>>>>> documented (hey, at least you KNOW who made/makes your > >>>>>> device! That's more than *I* had to go on!). > >>>>>> > >>>>>> Then, expect "us" to give you a definitive answer about > >>>>>> specifics related to that device. And, frown on those of > >>>>>> us that point this out to you as being "not helpful". > >>>>>> > >>>>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE > >>>>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, > >>>>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR > >>>>>> DIRECTIONS. I suspect more than a few people learned something > >>>>>> about the standard, here. And, the approach I have taken > >>>>>> to handle pinning differences (my "widgets"). > >>>>>> > >>>>>> Why aren't you talking to the vendor? Do you expect him/her > >>>>>> to be reading your posts, here? > >>>>>> > >>>>>> Buy something that appears to be a PC. It won't succeed > >>>>>> in that ubiquitous market if it differs radically from > >>>>>> other devices that also claim to be PCs. So, you can, > >>>>>> /with a high degree of confidence/, expect the connectors > >>>>>> to be pinned the way a PC would pin them. > >>>>>> > >>>>>> Or, buy from Joe's Garage Shop -- ask for Joe. > >>>>>> > >>>>>> THIS example is a testament to how I was able to make use > >>>>>> of a COMPLETELY undocumented device simply by making a > >>>>>> good assumption about the intent of the product and the > >>>>>> logical conclusions that flow from that assumption. The > >>>>>> only examination required was trying to deduce the > >>>>>> connections to the power connector and the associated > >>>>>> voltages (but, I had a pretty good feeling it wouldn't > >>>>>> be 7.293VDC or 28V or... again, because of the likely market) > >>>>> > >>>>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? > >>>> You still fail to see how this applies to "determining which > >>>> pin is the output". > >>>> > >>>> Wow, can a person get any denser? > >>> > >>> No, you can't. You completely fail to understand what is going on with this issue. > >>> > >>> > >>>> Hey, rick, I've got a box here. It's got a DB25 connector on it. > >>>> Is it for a printer? Serial port? SCSI interface? I'd post a photo > >>>> of it but the only distinguishable feature is the connector... > >>>> > >>>> Surely you should be able to answer this question! > >>> > >>> What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. > >>> > >>> > >>>> BTW, Joe is still waiting for your call... > >>> > >>> I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. > >> Wow, had you put this much effort into YOUR problem, you could have put > >> a SoC on a board and written the page of code it would take to suit your > >> problem. The BALANCE of the time, you could have ASSEMBLED the boards > >> into boxes! > >> > >> It's now 27 March. Your initial post was 17 January. A productive two months > >> for you, eh? > > > > Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. > "Multi-million dollar job". And you're dicking around with nickels and > dimes? Buy 20 BRAND SPANKING NEW pc's and be done with it! You continue to not understand the application, yet you feel qualified to recommend solutions. Yes, you are very much the sort of consultant that gives the group as a whole, a bad name. > Wow, what a great businessman -- not! > > Thanks for your concern about the use of my time. > I'd hate to see you waste it -- as you have, ours! I can't waste your time. That is entirely up to you. I'm finding the rather entertaining. Nothing technical arising from the discussion with you, but at this point, it's exploring your compulsive responses to everything I post. -- Rick C. ++--- Get 1,000 miles of free Supercharging ++--- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-27 15:36 -0700 |
| Message-ID | <tvt5q8$3dmjr$1@dont-email.me> |
| In reply to | #31750 |
On 3/27/2023 3:24 PM, Rick C wrote: > On Monday, March 27, 2023 at 6:07:29 PM UTC-4, Don Y wrote: >> On 3/27/2023 2:50 PM, Rick C wrote: >>> On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: >>>> On 3/27/2023 9:56 AM, Rick C wrote: >>>>> On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: >>>>>> On 3/27/2023 7:04 AM, Rick C wrote: >>>>>>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: >>>>>>>> On 3/26/2023 7:30 PM, Rick C wrote: >>>>>>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: >>>>>>>>>> On 3/26/2023 1:32 PM, Don Y wrote: >>>>>>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: >>>>>>>>>>>> I build these into connector shells that are designed to support a >>>>>>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label >>>>>>>>>>>> telling me the device that it is intended to normalize (e.g., I have >>>>>>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function >>>>>>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, >>>>>>>>>>>> etc.) >>>>>>>>>>> >>>>>>>>>>> This is the APC widget mentioned: >>>>>>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> >>>>>>>>>> And this is the COTS *PC* that I use as a name server: >>>>>>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> >>>>>>>>>> >>>>>>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT >>>>>>>>>> network connection (it's just a name server, it doesn't need to >>>>>>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), >>>>>>>>>> wifi and USB. The four mounting holes visible are the VESA standard >>>>>>>>>> (I have these mounted between my monitor and support arm) >>>>>>>>>> >>>>>>>>>> As an ISA PC, it will run damn near any OS intended for such >>>>>>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted >>>>>>>>>> AND TARGETED tools are available (I have a LFC monitor wired to >>>>>>>>>> one of the serial ports to discipline my time service as that >>>>>>>>>> was easier/cheaper to implement than any other solution!). >>>>>>>>> >>>>>>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. >>>>>>>>> >>>>>>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>> To show that if you buy something (or, in my case, RESCUE something with >>>>>>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how >>>>>>>> a responsible design would pin the connectors. >>>>>>>> >>>>>>>> I rescued this item. I had no idea what sort of CPU was inside. >>>>>>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would >>>>>>>> be serial ports -- why? because the rest of the box LOOKED like >>>>>>>> it was trying to be a PC, albeit in a very small form factor >>>>>>>> and with a wonky power connector). Or, if the 8P8C was actually >>>>>>>> a network port. Or, if the circular DIN was intended as a PS/2 >>>>>>>> keyboard. Or, the DE15 as a video port. >>>>>>>> >>>>>>>> The markings by the connectors *suggested* these uses. And, it >>>>>>>> seemed more likely than not... >>>>>>>> >>>>>>>> With *no* documentation, I opted to plug in a monitor (largely >>>>>>>> confident that the resolution would be supported by this >>>>>>>> "unknown" box) and keyboard and poke around the SETUP screen >>>>>>>> (which I *also* assumed would be available... somehow). >>>>>>>> >>>>>>>> Why was I *not* surprised with that outcome? >>>>>>>> >>>>>>>> You've posted a link to a device selected from a vendor >>>>>>>> that I'm unfamiliar with and, you infer, insufficiently >>>>>>>> documented (hey, at least you KNOW who made/makes your >>>>>>>> device! That's more than *I* had to go on!). >>>>>>>> >>>>>>>> Then, expect "us" to give you a definitive answer about >>>>>>>> specifics related to that device. And, frown on those of >>>>>>>> us that point this out to you as being "not helpful". >>>>>>>> >>>>>>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE >>>>>>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, >>>>>>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR >>>>>>>> DIRECTIONS. I suspect more than a few people learned something >>>>>>>> about the standard, here. And, the approach I have taken >>>>>>>> to handle pinning differences (my "widgets"). >>>>>>>> >>>>>>>> Why aren't you talking to the vendor? Do you expect him/her >>>>>>>> to be reading your posts, here? >>>>>>>> >>>>>>>> Buy something that appears to be a PC. It won't succeed >>>>>>>> in that ubiquitous market if it differs radically from >>>>>>>> other devices that also claim to be PCs. So, you can, >>>>>>>> /with a high degree of confidence/, expect the connectors >>>>>>>> to be pinned the way a PC would pin them. >>>>>>>> >>>>>>>> Or, buy from Joe's Garage Shop -- ask for Joe. >>>>>>>> >>>>>>>> THIS example is a testament to how I was able to make use >>>>>>>> of a COMPLETELY undocumented device simply by making a >>>>>>>> good assumption about the intent of the product and the >>>>>>>> logical conclusions that flow from that assumption. The >>>>>>>> only examination required was trying to deduce the >>>>>>>> connections to the power connector and the associated >>>>>>>> voltages (but, I had a pretty good feeling it wouldn't >>>>>>>> be 7.293VDC or 28V or... again, because of the likely market) >>>>>>> >>>>>>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? >>>>>> You still fail to see how this applies to "determining which >>>>>> pin is the output". >>>>>> >>>>>> Wow, can a person get any denser? >>>>> >>>>> No, you can't. You completely fail to understand what is going on with this issue. >>>>> >>>>> >>>>>> Hey, rick, I've got a box here. It's got a DB25 connector on it. >>>>>> Is it for a printer? Serial port? SCSI interface? I'd post a photo >>>>>> of it but the only distinguishable feature is the connector... >>>>>> >>>>>> Surely you should be able to answer this question! >>>>> >>>>> What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. >>>>> >>>>> >>>>>> BTW, Joe is still waiting for your call... >>>>> >>>>> I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. >>>> Wow, had you put this much effort into YOUR problem, you could have put >>>> a SoC on a board and written the page of code it would take to suit your >>>> problem. The BALANCE of the time, you could have ASSEMBLED the boards >>>> into boxes! >>>> >>>> It's now 27 March. Your initial post was 17 January. A productive two months >>>> for you, eh? >>> >>> Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. >> "Multi-million dollar job". And you're dicking around with nickels and >> dimes? Buy 20 BRAND SPANKING NEW pc's and be done with it! > > You continue to not understand the application, yet you feel qualified to recommend solutions. Yes, you are very much the sort of consultant that gives the group as a whole, a bad name. > > >> Wow, what a great businessman -- not! >>> Thanks for your concern about the use of my time. >> I'd hate to see you waste it -- as you have, ours! > > I can't waste your time. That is entirely up to you. I'm finding the rather entertaining. Nothing technical arising from the discussion with you, but at this point, it's exploring your compulsive responses to everything I post. I'm enjoying showing others your silliness. I seem to be doing a pretty good job at it!
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 15:37 -0700 |
| Message-ID | <e84c1fb0-c0a6-4f01-a97b-75fa0413cff9n@googlegroups.com> |
| In reply to | #31752 |
On Monday, March 27, 2023 at 6:37:02 PM UTC-4, Don Y wrote: > On 3/27/2023 3:24 PM, Rick C wrote: > > On Monday, March 27, 2023 at 6:07:29 PM UTC-4, Don Y wrote: > >> On 3/27/2023 2:50 PM, Rick C wrote: > >>> On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: > >>>> On 3/27/2023 9:56 AM, Rick C wrote: > >>>>> On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: > >>>>>> On 3/27/2023 7:04 AM, Rick C wrote: > >>>>>>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: > >>>>>>>> On 3/26/2023 7:30 PM, Rick C wrote: > >>>>>>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: > >>>>>>>>>> On 3/26/2023 1:32 PM, Don Y wrote: > >>>>>>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: > >>>>>>>>>>>> I build these into connector shells that are designed to support a > >>>>>>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label > >>>>>>>>>>>> telling me the device that it is intended to normalize (e.g., I have > >>>>>>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function > >>>>>>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, > >>>>>>>>>>>> etc.) > >>>>>>>>>>> > >>>>>>>>>>> This is the APC widget mentioned: > >>>>>>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> > >>>>>>>>>> And this is the COTS *PC* that I use as a name server: > >>>>>>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> > >>>>>>>>>> > >>>>>>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT > >>>>>>>>>> network connection (it's just a name server, it doesn't need to > >>>>>>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), > >>>>>>>>>> wifi and USB. The four mounting holes visible are the VESA standard > >>>>>>>>>> (I have these mounted between my monitor and support arm) > >>>>>>>>>> > >>>>>>>>>> As an ISA PC, it will run damn near any OS intended for such > >>>>>>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted > >>>>>>>>>> AND TARGETED tools are available (I have a LFC monitor wired to > >>>>>>>>>> one of the serial ports to discipline my time service as that > >>>>>>>>>> was easier/cheaper to implement than any other solution!). > >>>>>>>>> > >>>>>>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. > >>>>>>>>> > >>>>>>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>> To show that if you buy something (or, in my case, RESCUE something with > >>>>>>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how > >>>>>>>> a responsible design would pin the connectors. > >>>>>>>> > >>>>>>>> I rescued this item. I had no idea what sort of CPU was inside. > >>>>>>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would > >>>>>>>> be serial ports -- why? because the rest of the box LOOKED like > >>>>>>>> it was trying to be a PC, albeit in a very small form factor > >>>>>>>> and with a wonky power connector). Or, if the 8P8C was actually > >>>>>>>> a network port. Or, if the circular DIN was intended as a PS/2 > >>>>>>>> keyboard. Or, the DE15 as a video port. > >>>>>>>> > >>>>>>>> The markings by the connectors *suggested* these uses. And, it > >>>>>>>> seemed more likely than not... > >>>>>>>> > >>>>>>>> With *no* documentation, I opted to plug in a monitor (largely > >>>>>>>> confident that the resolution would be supported by this > >>>>>>>> "unknown" box) and keyboard and poke around the SETUP screen > >>>>>>>> (which I *also* assumed would be available... somehow). > >>>>>>>> > >>>>>>>> Why was I *not* surprised with that outcome? > >>>>>>>> > >>>>>>>> You've posted a link to a device selected from a vendor > >>>>>>>> that I'm unfamiliar with and, you infer, insufficiently > >>>>>>>> documented (hey, at least you KNOW who made/makes your > >>>>>>>> device! That's more than *I* had to go on!). > >>>>>>>> > >>>>>>>> Then, expect "us" to give you a definitive answer about > >>>>>>>> specifics related to that device. And, frown on those of > >>>>>>>> us that point this out to you as being "not helpful". > >>>>>>>> > >>>>>>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE > >>>>>>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, > >>>>>>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR > >>>>>>>> DIRECTIONS. I suspect more than a few people learned something > >>>>>>>> about the standard, here. And, the approach I have taken > >>>>>>>> to handle pinning differences (my "widgets"). > >>>>>>>> > >>>>>>>> Why aren't you talking to the vendor? Do you expect him/her > >>>>>>>> to be reading your posts, here? > >>>>>>>> > >>>>>>>> Buy something that appears to be a PC. It won't succeed > >>>>>>>> in that ubiquitous market if it differs radically from > >>>>>>>> other devices that also claim to be PCs. So, you can, > >>>>>>>> /with a high degree of confidence/, expect the connectors > >>>>>>>> to be pinned the way a PC would pin them. > >>>>>>>> > >>>>>>>> Or, buy from Joe's Garage Shop -- ask for Joe. > >>>>>>>> > >>>>>>>> THIS example is a testament to how I was able to make use > >>>>>>>> of a COMPLETELY undocumented device simply by making a > >>>>>>>> good assumption about the intent of the product and the > >>>>>>>> logical conclusions that flow from that assumption. The > >>>>>>>> only examination required was trying to deduce the > >>>>>>>> connections to the power connector and the associated > >>>>>>>> voltages (but, I had a pretty good feeling it wouldn't > >>>>>>>> be 7.293VDC or 28V or... again, because of the likely market) > >>>>>>> > >>>>>>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? > >>>>>> You still fail to see how this applies to "determining which > >>>>>> pin is the output". > >>>>>> > >>>>>> Wow, can a person get any denser? > >>>>> > >>>>> No, you can't. You completely fail to understand what is going on with this issue. > >>>>> > >>>>> > >>>>>> Hey, rick, I've got a box here. It's got a DB25 connector on it. > >>>>>> Is it for a printer? Serial port? SCSI interface? I'd post a photo > >>>>>> of it but the only distinguishable feature is the connector... > >>>>>> > >>>>>> Surely you should be able to answer this question! > >>>>> > >>>>> What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. > >>>>> > >>>>> > >>>>>> BTW, Joe is still waiting for your call... > >>>>> > >>>>> I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. > >>>> Wow, had you put this much effort into YOUR problem, you could have put > >>>> a SoC on a board and written the page of code it would take to suit your > >>>> problem. The BALANCE of the time, you could have ASSEMBLED the boards > >>>> into boxes! > >>>> > >>>> It's now 27 March. Your initial post was 17 January. A productive two months > >>>> for you, eh? > >>> > >>> Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. > >> "Multi-million dollar job". And you're dicking around with nickels and > >> dimes? Buy 20 BRAND SPANKING NEW pc's and be done with it! > > > > You continue to not understand the application, yet you feel qualified to recommend solutions. Yes, you are very much the sort of consultant that gives the group as a whole, a bad name. > > > > > >> Wow, what a great businessman -- not! > >>> Thanks for your concern about the use of my time. > >> I'd hate to see you waste it -- as you have, ours! > > > > I can't waste your time. That is entirely up to you. I'm finding the rather entertaining. Nothing technical arising from the discussion with you, but at this point, it's exploring your compulsive responses to everything I post. > I'm enjoying showing others your silliness. I seem to be doing a pretty good > job at it! Yeah, you are good at your job I guess. Does it pay much? -- Rick C. ++--+ Get 1,000 miles of free Supercharging ++--+ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-27 15:42 -0700 |
| Message-ID | <tvt64e$3dmjr$4@dont-email.me> |
| In reply to | #31753 |
On 3/27/2023 3:37 PM, Rick C wrote: > On Monday, March 27, 2023 at 6:37:02 PM UTC-4, Don Y wrote: >> On 3/27/2023 3:24 PM, Rick C wrote: >>> On Monday, March 27, 2023 at 6:07:29 PM UTC-4, Don Y wrote: >>>> On 3/27/2023 2:50 PM, Rick C wrote: >>>>> On Monday, March 27, 2023 at 4:08:12 PM UTC-4, Don Y wrote: >>>>>> On 3/27/2023 9:56 AM, Rick C wrote: >>>>>>> On Monday, March 27, 2023 at 12:21:52 PM UTC-4, Don Y wrote: >>>>>>>> On 3/27/2023 7:04 AM, Rick C wrote: >>>>>>>>> On Sunday, March 26, 2023 at 11:31:18 PM UTC-4, Don Y wrote: >>>>>>>>>> On 3/26/2023 7:30 PM, Rick C wrote: >>>>>>>>>>> On Sunday, March 26, 2023 at 4:52:48 PM UTC-4, Don Y wrote: >>>>>>>>>>>> On 3/26/2023 1:32 PM, Don Y wrote: >>>>>>>>>>>>> On 3/26/2023 1:23 PM, Don Y wrote: >>>>>>>>>>>>>> I build these into connector shells that are designed to support a >>>>>>>>>>>>>> pair of back-to-back connectors (DB9 or 25) and then affix a label >>>>>>>>>>>>>> telling me the device that it is intended to normalize (e.g., I have >>>>>>>>>>>>>> one at my feet that "fixes" APC's UPS serial port) *or* the function >>>>>>>>>>>>>> it is intended to perform (gender change, NULL modem, NULL 'terminal'!, >>>>>>>>>>>>>> etc.) >>>>>>>>>>>>> >>>>>>>>>>>>> This is the APC widget mentioned: >>>>>>>>>>>>> <https://mega.nz/file/J35SBBob#FtQznCDovhBZHJdA5OspHdMo6_DiDMjQwtCqnh3Oa54> >>>>>>>>>>>> And this is the COTS *PC* that I use as a name server: >>>>>>>>>>>> <https://mega.nz/file/Fi4hEACJ#YgVZ5tdZBjTcwW76gXC2vdgv5M6u4lTpUDAwu53Z9n8> >>>>>>>>>>>> >>>>>>>>>>>> Note the *two* serial ports (DTE as the standard dictates), 100BaseT >>>>>>>>>>>> network connection (it's just a name server, it doesn't need to >>>>>>>>>>>> have high throughput), PS/2 keyboard and VGA (cuz it's a PC!), >>>>>>>>>>>> wifi and USB. The four mounting holes visible are the VESA standard >>>>>>>>>>>> (I have these mounted between my monitor and support arm) >>>>>>>>>>>> >>>>>>>>>>>> As an ISA PC, it will run damn near any OS intended for such >>>>>>>>>>>> a platform (I run NetBSD on this box). So, all of the PC hosted >>>>>>>>>>>> AND TARGETED tools are available (I have a LFC monitor wired to >>>>>>>>>>>> one of the serial ports to discipline my time service as that >>>>>>>>>>>> was easier/cheaper to implement than any other solution!). >>>>>>>>>>> >>>>>>>>>>> Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. >>>>>>>>>>> >>>>>>>>>>> Don, why are you here? Why are you posting in this thread? You have gone completely off topic. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>> To show that if you buy something (or, in my case, RESCUE something with >>>>>>>>>> *no* markings at all on it) for a KNOWN MARKET, then you can *infer* how >>>>>>>>>> a responsible design would pin the connectors. >>>>>>>>>> >>>>>>>>>> I rescued this item. I had no idea what sort of CPU was inside. >>>>>>>>>> Nor memory. Nor pinouts of the DB9's (which I *assumed* would >>>>>>>>>> be serial ports -- why? because the rest of the box LOOKED like >>>>>>>>>> it was trying to be a PC, albeit in a very small form factor >>>>>>>>>> and with a wonky power connector). Or, if the 8P8C was actually >>>>>>>>>> a network port. Or, if the circular DIN was intended as a PS/2 >>>>>>>>>> keyboard. Or, the DE15 as a video port. >>>>>>>>>> >>>>>>>>>> The markings by the connectors *suggested* these uses. And, it >>>>>>>>>> seemed more likely than not... >>>>>>>>>> >>>>>>>>>> With *no* documentation, I opted to plug in a monitor (largely >>>>>>>>>> confident that the resolution would be supported by this >>>>>>>>>> "unknown" box) and keyboard and poke around the SETUP screen >>>>>>>>>> (which I *also* assumed would be available... somehow). >>>>>>>>>> >>>>>>>>>> Why was I *not* surprised with that outcome? >>>>>>>>>> >>>>>>>>>> You've posted a link to a device selected from a vendor >>>>>>>>>> that I'm unfamiliar with and, you infer, insufficiently >>>>>>>>>> documented (hey, at least you KNOW who made/makes your >>>>>>>>>> device! That's more than *I* had to go on!). >>>>>>>>>> >>>>>>>>>> Then, expect "us" to give you a definitive answer about >>>>>>>>>> specifics related to that device. And, frown on those of >>>>>>>>>> us that point this out to you as being "not helpful". >>>>>>>>>> >>>>>>>>>> ALL ONE CAN TELL YOU ABOUT A RANDOM DEVICE THAT APPEARS TO HAVE >>>>>>>>>> SERIAL PORT(S) IS WHAT THE STANDARD SAYS ABOUT THOSE PORTS, >>>>>>>>>> THEIR GENDER AND THE SIGNALS ASSIGNED TO THE PINS AND THEIR >>>>>>>>>> DIRECTIONS. I suspect more than a few people learned something >>>>>>>>>> about the standard, here. And, the approach I have taken >>>>>>>>>> to handle pinning differences (my "widgets"). >>>>>>>>>> >>>>>>>>>> Why aren't you talking to the vendor? Do you expect him/her >>>>>>>>>> to be reading your posts, here? >>>>>>>>>> >>>>>>>>>> Buy something that appears to be a PC. It won't succeed >>>>>>>>>> in that ubiquitous market if it differs radically from >>>>>>>>>> other devices that also claim to be PCs. So, you can, >>>>>>>>>> /with a high degree of confidence/, expect the connectors >>>>>>>>>> to be pinned the way a PC would pin them. >>>>>>>>>> >>>>>>>>>> Or, buy from Joe's Garage Shop -- ask for Joe. >>>>>>>>>> >>>>>>>>>> THIS example is a testament to how I was able to make use >>>>>>>>>> of a COMPLETELY undocumented device simply by making a >>>>>>>>>> good assumption about the intent of the product and the >>>>>>>>>> logical conclusions that flow from that assumption. The >>>>>>>>>> only examination required was trying to deduce the >>>>>>>>>> connections to the power connector and the associated >>>>>>>>>> voltages (but, I had a pretty good feeling it wouldn't >>>>>>>>>> be 7.293VDC or 28V or... again, because of the likely market) >>>>>>>>> >>>>>>>>> You are off topic in this thread. Why not start your own thread, rather than polluting this one? >>>>>>>> You still fail to see how this applies to "determining which >>>>>>>> pin is the output". >>>>>>>> >>>>>>>> Wow, can a person get any denser? >>>>>>> >>>>>>> No, you can't. You completely fail to understand what is going on with this issue. >>>>>>> >>>>>>> >>>>>>>> Hey, rick, I've got a box here. It's got a DB25 connector on it. >>>>>>>> Is it for a printer? Serial port? SCSI interface? I'd post a photo >>>>>>>> of it but the only distinguishable feature is the connector... >>>>>>>> >>>>>>>> Surely you should be able to answer this question! >>>>>>> >>>>>>> What does YOUR box have to do with my project? You are projecting your imaginings, onto a conversation that is very different from what you are talking about. But that's typical of you. At least your last few posts have not been a complete dump of every stray thought that you encountered while writing the post. >>>>>>> >>>>>>> >>>>>>>> BTW, Joe is still waiting for your call... >>>>>>> >>>>>>> I'm sure he will wait a long time to come. He's probably waiting for you to stop posting off topic in this thread. >>>>>> Wow, had you put this much effort into YOUR problem, you could have put >>>>>> a SoC on a board and written the page of code it would take to suit your >>>>>> problem. The BALANCE of the time, you could have ASSEMBLED the boards >>>>>> into boxes! >>>>>> >>>>>> It's now 27 March. Your initial post was 17 January. A productive two months >>>>>> for you, eh? >>>>> >>>>> Some people think small. I'm currently negotiating a multi-million dollar job. This design is actually for my brother who needs a gadget and so far, has not been able to find anyone to help him. There are a few people who have contacted me here and one from another group. I expect one of them will turn out to be a good choice. >>>> "Multi-million dollar job". And you're dicking around with nickels and >>>> dimes? Buy 20 BRAND SPANKING NEW pc's and be done with it! >>> >>> You continue to not understand the application, yet you feel qualified to recommend solutions. Yes, you are very much the sort of consultant that gives the group as a whole, a bad name. >>> >>> >>>> Wow, what a great businessman -- not! >>>>> Thanks for your concern about the use of my time. >>>> I'd hate to see you waste it -- as you have, ours! >>> >>> I can't waste your time. That is entirely up to you. I'm finding the rather entertaining. Nothing technical arising from the discussion with you, but at this point, it's exploring your compulsive responses to everything I post. >> I'm enjoying showing others your silliness. I seem to be doing a pretty good >> job at it! > > Yeah, you are good at your job I guess. Does it pay much? Enough to have retired, comfortably, more than 10 years ago! How long you planning on slogging away at it?
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-03-27 11:03 +0200 |
| Message-ID | <tvrm44$352le$1@dont-email.me> |
| In reply to | #31717 |
On 27/03/2023 04:30, Rick C wrote: > Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. > > Don, why are you here? Why are you posting in this thread? You have gone completely off topic. > Rick, why are /you/ here? You have been on Usenet for decades, but still seem to struggle with the basics. A group like this is a discussion group. It is not your personal support channel. You do not have any rights to the group, or any rights to the thread. If Don wants to post here, he can post here. If he wants to ramble or rant (and he does like doing that - he has a lot of experience and likes to share), that's his right and his choice. Ignore his posts if you don't like them. You have spent this thread bullying and insulting people, pushing them into doing your work for free. When it looks like some here might be possible paid suppliers, you undermine and patronise them. When you come looking for help and advice, it's fair enough to disagree - but we can do without the sarcasm and belittlement of your responses. And if you want to killfile me for writing some hard truths, go ahead. But first you'll have to figure out how to use Usenet instead of blaming Google Groups for your own problems.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 07:11 -0700 |
| Message-ID | <dc36d935-9a75-4183-949d-fe7485d7b034n@googlegroups.com> |
| In reply to | #31723 |
On Monday, March 27, 2023 at 5:03:06 AM UTC-4, David Brown wrote: > On 27/03/2023 04:30, Rick C wrote: > > > Wow! He's gone from making overly verbose posts with far more description than needed, to making replies to himself, neither of which are needed. > > > > Don, why are you here? Why are you posting in this thread? You have gone completely off topic. > > > Rick, why are /you/ here? You have been on Usenet for decades, but > still seem to struggle with the basics. > > A group like this is a discussion group. It is not your personal > support channel. Correct, but it is not appropriate to hijack a thread. Doing that turns every group into s.e.d. > You do not have any rights to the group, or any rights > to the thread. If Don wants to post here, he can post here. If he > wants to ramble or rant (and he does like doing that - he has a lot of > experience and likes to share), that's his right and his choice. Ignore > his posts if you don't like them. Correct that I don't own the group or the thread. I'm simply pointing out that in contrast to convention and courteous behavior, Don is trashing this thread. > You have spent this thread bullying and insulting people, pushing them > into doing your work for free. When it looks like some here might be > possible paid suppliers, you undermine and patronise them. LOL! How on earth do you bully anyone in a newsgroup? You are just being silly now. > When you come looking for help and advice, it's fair enough to disagree > - but we can do without the sarcasm and belittlement of your responses. I'm pretty sure Don is the only person I've been anything but polite to. That's because Don has been anything but polite. Don's posts have been like walking up to a couple of strangers on the street, having a conversation, and inviting himself to join in with comments that have nothing to do with what they were discussing. Not acceptable there, not acceptable here. > And if you want to killfile me for writing some hard truths, go ahead. > But first you'll have to figure out how to use Usenet instead of blaming > Google Groups for your own problems. Sounds like you are the one with complaints that would make you want to kill file someone. Bye -- Rick C. -+++- Get 1,000 miles of free Supercharging -+++- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Dimiter_Popoff <dp@tgi-sci.com> |
|---|---|
| Date | 2023-03-27 17:47 +0300 |
| Message-ID | <tvsa9q$38qut$1@dont-email.me> |
| In reply to | #31727 |
On 3/27/2023 17:11, Rick C wrote: > On Monday, March 27, 2023 at 5:03:06 AM UTC-4, David Brown wrote: > .... > >> You do not have any rights to the group, or any rights >> to the thread. If Don wants to post here, he can post here. If he >> wants to ramble or rant (and he does like doing that - he has a lot of >> experience and likes to share), that's his right and his choice. Ignore >> his posts if you don't like them. > > Correct that I don't own the group or the thread. I'm simply pointing out that in contrast to convention and courteous behavior, Don is trashing this thread. Oh stop it Rick. Your initial question - about board availability - was valid, you must have googled, not found anything and asked here; so far so good. Then you started talking about signal polarities, RS-232 standards etc., things most people here have leaned how to deal with 30 or so years ago. It does not get much lamer than that. And now you complain you got too much detail or whatever, eventually you discovered that only a wintel PC is your off the shelf option etc. etc. lame stuff. It was obvious after the first 2-3 posts you would not find what you initially asked for as being mass produced, why all the whining now.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 08:05 -0700 |
| Message-ID | <7be2ae83-c251-4b0d-976c-b2fc9e63886fn@googlegroups.com> |
| In reply to | #31728 |
On Monday, March 27, 2023 at 10:47:28 AM UTC-4, Dimiter_Popoff wrote: > On 3/27/2023 17:11, Rick C wrote: > > On Monday, March 27, 2023 at 5:03:06 AM UTC-4, David Brown wrote: > > .... > > > >> You do not have any rights to the group, or any rights > >> to the thread. If Don wants to post here, he can post here. If he > >> wants to ramble or rant (and he does like doing that - he has a lot of > >> experience and likes to share), that's his right and his choice. Ignore > >> his posts if you don't like them. > > > > Correct that I don't own the group or the thread. I'm simply pointing out that in contrast to convention and courteous behavior, Don is trashing this thread. > Oh stop it Rick. No, YOU stop it! > Your initial question - about board availability - was > valid, you must have googled, not found anything and asked here; so > far so good. > Then you started talking about signal polarities, RS-232 standards etc., > things most people here have leaned how to deal with 30 or so years ago. > It does not get much lamer than that. > And now you complain you got too much detail or whatever, eventually > you discovered that only a wintel PC is your off the shelf option etc. > etc. lame stuff. > It was obvious after the first 2-3 posts you would not find what you > initially asked for as being mass produced, why all the whining now. Why do you feel you needed to post any of this? Why are you whining? -- Rick C. -++++ Get 1,000 miles of free Supercharging -++++ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Dimiter_Popoff <dp@tgi-sci.com> |
|---|---|
| Date | 2023-03-27 19:09 +0300 |
| Message-ID | <tvsf31$39je8$1@dont-email.me> |
| In reply to | #31729 |
On 3/27/2023 18:05, Rick C wrote: > On Monday, March 27, 2023 at 10:47:28 AM UTC-4, Dimiter_Popoff wrote: >> On 3/27/2023 17:11, Rick C wrote: >>> On Monday, March 27, 2023 at 5:03:06 AM UTC-4, David Brown wrote: >>> .... >>> >>>> You do not have any rights to the group, or any rights >>>> to the thread. If Don wants to post here, he can post here. If he >>>> wants to ramble or rant (and he does like doing that - he has a lot of >>>> experience and likes to share), that's his right and his choice. Ignore >>>> his posts if you don't like them. >>> >>> Correct that I don't own the group or the thread. I'm simply pointing out that in contrast to convention and courteous behavior, Don is trashing this thread. >> Oh stop it Rick. > > No, YOU stop it! > > >> Your initial question - about board availability - was >> valid, you must have googled, not found anything and asked here; so >> far so good. >> Then you started talking about signal polarities, RS-232 standards etc., >> things most people here have leaned how to deal with 30 or so years ago. >> It does not get much lamer than that. >> And now you complain you got too much detail or whatever, eventually >> you discovered that only a wintel PC is your off the shelf option etc. >> etc. lame stuff. >> It was obvious after the first 2-3 posts you would not find what you >> initially asked for as being mass produced, why all the whining now. > > Why do you feel you needed to post any of this? Why are you whining? > Because I do read the group and your lame whining is a bit excessive. Notice I kept silent before you got into abuse/whine mode. You have been a whiner ever since I know you on Usenet, decades by now. So I am not asking you to disappear, we are all different people, just to tone it down. You got *all* the answers to your questions here and you complain you got too much information. Either do the work you seem to be trying to do or just let it go, no more help for you here.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-03-27 17:38 +0200 |
| Message-ID | <tvsd99$39bb5$1@dont-email.me> |
| In reply to | #31727 |
On 27/03/2023 16:11, Rick C wrote: > On Monday, March 27, 2023 at 5:03:06 AM UTC-4, David Brown wrote: >> On 27/03/2023 04:30, Rick C wrote: >> >>> Wow! He's gone from making overly verbose posts with far more >>> description than needed, to making replies to himself, neither of >>> which are needed. >>> >>> Don, why are you here? Why are you posting in this thread? You >>> have gone completely off topic. >>> >> Rick, why are /you/ here? You have been on Usenet for decades, but >> still seem to struggle with the basics. >> >> A group like this is a discussion group. It is not your personal >> support channel. > > Correct, but it is not appropriate to hijack a thread. Doing that > turns every group into s.e.d. > I suspect you have been in s.e.d. too long, and other groups too little. (To be fair, there's not a lot of traffic in many of the technical groups.) You are a polite and respectful poster by s.e.d. standards, but not by the standards of groups that remain technical. > >> You do not have any rights to the group, or any rights to the >> thread. If Don wants to post here, he can post here. If he wants to >> ramble or rant (and he does like doing that - he has a lot of >> experience and likes to share), that's his right and his choice. >> Ignore his posts if you don't like them. > > Correct that I don't own the group or the thread. I'm simply > pointing out that in contrast to convention and courteous behavior, > Don is trashing this thread. > I was turned off from joining in this thread by /your/ posts. Don's are easy to ignore. His posts are often long and somewhat off-topic, and people often skip them - that's not news to him or to anyone else here. Read them if you are interested, skip them if you are not. > >> You have spent this thread bullying and insulting people, pushing >> them into doing your work for free. When it looks like some here >> might be possible paid suppliers, you undermine and patronise >> them. > > LOL! How on earth do you bully anyone in a newsgroup? You are just > being silly now. > Do you ever try reading the things you write? Perhaps trying to imagine how they might be viewed by others? Perhaps, like many bullies, you simply don't understand how you come across. Perhaps you really do view everyone else as though they are here to do your bidding and answer your questions. > >> When you come looking for help and advice, it's fair enough to >> disagree - but we can do without the sarcasm and belittlement of >> your responses. > > I'm pretty sure Don is the only person I've been anything but polite > to. That's because Don has been anything but polite. Don's posts > have been like walking up to a couple of strangers on the street, > having a conversation, and inviting himself to join in with comments > that have nothing to do with what they were discussing. Not > acceptable there, not acceptable here. > Again, I think you are unaware of how Usenet works. It's more like a coffee shop, or an office water cooler. Don's the old guy who always seems to be there, sitting in the same seat. He's part of the conversation whether he posts or not. Some people are interested in the war stories he tells, others not - and for many, we find some of the things he says interesting, and some things less so. He has helped out a great many people over the decades, and I hope and expect he will continue to do so. /You/ are the one who wandered in here looking for help, and then chastise people for not concentrating fully on /your/ problems, or failing to read your mind regarding the answers you expect. Don's posting behaviour is /entirely/ acceptable here. Yours is a lot more on the edge, which is why I am making these comments. The hope is that you will think a little about what you write, and moderate yourself - then we can get back to politer technical discussions and enjoy their wanderings, wherever they may lead. > >> And if you want to killfile me for writing some hard truths, go >> ahead. But first you'll have to figure out how to use Usenet >> instead of blaming Google Groups for your own problems. > > Sounds like you are the one with complaints that would make you want > to kill file someone. > > Bye >
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-26 19:22 -0700 |
| Message-ID | <a967ed6b-c03b-450c-84a1-d635594987a7n@googlegroups.com> |
| In reply to | #31709 |
On Sunday, March 26, 2023 at 4:25:49 PM UTC-4, Don Y wrote: > On 3/26/2023 11:27 AM, Jim Jackson wrote: > > Many years ago I often had to connect up gear with RS232 interfaces, and > > it was a pain, as there was often no manual for the gear or the manual > > was badly written and the author used the RS232 "standard" terms in a > > cavalier way. > Folks who haven't designed communications equipment where RS232 (in its > various bastardized forms) don't understand that commenting on a product > chosen (seemingly) at random from a producer of unknown character is > pure folly. Simply because the folks who design said pieces of > kit are operating often in ignorance -- trying to make a device that > mates with X instead of a device that conforms to a standard. And there is the problem. The RS-232 standard defines the interface between data terminal equipment and data communication equipment, at the data communication equipment interface. It says nothing about anything else. However, people use these voltages and so these level shifting devices, often along with the same type of connectors for many *other* applications. At that point, the RS-232 standard does not apply in a consistent way. So people are free to pick and choose the parts they want, and the parts they don't want. The RS-232 moniker is often used, when even the voltage levels are not the same. At that point, there is nothing RS-232 about it. People are just using the term as a synonym for an async serial port. -- Rick C. -+--- Get 1,000 miles of free Supercharging -+--- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-26 19:11 -0700 |
| Message-ID | <11b8ae5c-64d5-4693-bde8-11688f35c4e2n@googlegroups.com> |
| In reply to | #31706 |
On Sunday, March 26, 2023 at 2:27:14 PM UTC-4, Jim Jackson wrote: > On 2023-03-26, Rick C <gnuarm.del...@gmail.com> wrote: > > > > I often have this problem with people who don't actually understand > > how RS-232 is used. There are people who view the world through data > > sheets and specification standards. Then there's the real world, > > where you have to toss out some of that, and ask questions like, > > "Which pin is output and which pin is input?" If the person you are > > talking to gives you anything other than a pin number, you are talking > > to the wrong person. > Many years ago I often had to connect up gear with RS232 interfaces, and > it was a pain, as there was often no manual for the gear or the manual > was badly written and the author used the RS232 "standard" terms in a > cavalier way. > > So I used an RS232 breakout box to try and identify RXD and TXD, and > what the various pins did, and what had to be strapped to what to get > either end to speak! Oh happy days - NOT! > > Good luck with the project. Fortunately, this effort only uses TX and GND on one port and RX and GND on the other port. I don't care what the TX and RX pins are called, one is input, the other output and we just need to connect the input to the device that is sending the data and connect the output to the device that is receiving data. All this has already been worked out and a prototype was built. Unfortunately there is some problem that results in a hung unit from time to time. That developer doesn't have the time to mess with it, so we are looking elsewhere. But the pin assignments are not a problem, just people's perspective on the issue. -- Rick C. --+++ Get 1,000 miles of free Supercharging --+++ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-26 13:37 -0700 |
| Message-ID | <tvqael$2remq$5@dont-email.me> |
| In reply to | #31703 |
On 3/25/2023 7:26 PM, Rick C wrote: > Engineers design stuff. Technicians figure out how to make it work. And you apparently do neither. <frown>
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-26 19:28 -0700 |
| Message-ID | <9ed850b7-1212-4d9c-9790-da901fbe0bb2n@googlegroups.com> |
| In reply to | #31711 |
On Sunday, March 26, 2023 at 4:37:45 PM UTC-4, Don Y wrote: > On 3/25/2023 7:26 PM, Rick C wrote: > > Engineers design stuff. Technicians figure out how to make it work. > And you apparently do neither. <frown> You seem to have gone off the weird end. I wish GG had a kill file feature. At least you managed to post without overflowing everyone's input buffers. You seem to have a penchant for using 100 words, when 20 will do. Thanks for keeping this one brief. -- Rick C. -+-+-- Get 1,000 miles of free Supercharging -+-+-- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-27 13:38 -0700 |
| Message-ID | <tvsut5$3ccdv$1@dont-email.me> |
| In reply to | #31716 |
On 3/26/2023 7:28 PM, Rick C wrote: > On Sunday, March 26, 2023 at 4:37:45 PM UTC-4, Don Y wrote: >> On 3/25/2023 7:26 PM, Rick C wrote: >>> Engineers design stuff. Technicians figure out how to make it work. >> And you apparently do neither. <frown> > > You seem to have gone off the weird end. I wish GG had a kill file feature. At least you managed to post without overflowing everyone's input buffers. You seem to have a penchant for using 100 words, when 20 will do. Says a guy who spawned a 2.5 month long thread OVER A PINOUT! Wow! I wonder how long the thread will be about power supply voltages... > Thanks for keeping this one brief. >
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 15:05 -0700 |
| Message-ID | <57af4a97-e950-4680-aac3-f64b3f04a86an@googlegroups.com> |
| In reply to | #31741 |
On Monday, March 27, 2023 at 4:39:06 PM UTC-4, Don Y wrote: > On 3/26/2023 7:28 PM, Rick C wrote: > > On Sunday, March 26, 2023 at 4:37:45 PM UTC-4, Don Y wrote: > >> On 3/25/2023 7:26 PM, Rick C wrote: > >>> Engineers design stuff. Technicians figure out how to make it work. > >> And you apparently do neither. <frown> > > > > You seem to have gone off the weird end. I wish GG had a kill file feature. At least you managed to post without overflowing everyone's input buffers. You seem to have a penchant for using 100 words, when 20 will do. > Says a guy who spawned a 2.5 month long thread OVER A PINOUT! > > Wow! I wonder how long the thread will be about power supply voltages... What is the power supply voltage? -- Rick C. +-++- Get 1,000 miles of free Supercharging +-++- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-27 15:08 -0700 |
| Message-ID | <tvt45n$3dd67$3@dont-email.me> |
| In reply to | #31745 |
On 3/27/2023 3:05 PM, Rick C wrote: > On Monday, March 27, 2023 at 4:39:06 PM UTC-4, Don Y wrote: >> On 3/26/2023 7:28 PM, Rick C wrote: >>> On Sunday, March 26, 2023 at 4:37:45 PM UTC-4, Don Y wrote: >>>> On 3/25/2023 7:26 PM, Rick C wrote: >>>>> Engineers design stuff. Technicians figure out how to make it work. >>>> And you apparently do neither. <frown> >>> >>> You seem to have gone off the weird end. I wish GG had a kill file feature. At least you managed to post without overflowing everyone's input buffers. You seem to have a penchant for using 100 words, when 20 will do. >> Says a guy who spawned a 2.5 month long thread OVER A PINOUT! >> >> Wow! I wonder how long the thread will be about power supply voltages... > > What is the power supply voltage? Blue. No, maybe a light shade of violet.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 15:25 -0700 |
| Message-ID | <8fc65c7f-fecf-4cb2-b887-a93ffd776884n@googlegroups.com> |
| In reply to | #31749 |
On Monday, March 27, 2023 at 6:09:01 PM UTC-4, Don Y wrote: > On 3/27/2023 3:05 PM, Rick C wrote: > > On Monday, March 27, 2023 at 4:39:06 PM UTC-4, Don Y wrote: > >> On 3/26/2023 7:28 PM, Rick C wrote: > >>> On Sunday, March 26, 2023 at 4:37:45 PM UTC-4, Don Y wrote: > >>>> On 3/25/2023 7:26 PM, Rick C wrote: > >>>>> Engineers design stuff. Technicians figure out how to make it work. > >>>> And you apparently do neither. <frown> > >>> > >>> You seem to have gone off the weird end. I wish GG had a kill file feature. At least you managed to post without overflowing everyone's input buffers. You seem to have a penchant for using 100 words, when 20 will do. > >> Says a guy who spawned a 2.5 month long thread OVER A PINOUT! > >> > >> Wow! I wonder how long the thread will be about power supply voltages... > > > > What is the power supply voltage? > Blue. No, maybe a light shade of violet. Indeed. I think you are learning... rather slowly, but learning nonetheless. -- Rick C. ++--+ Get 1,000 miles of free Supercharging ++--+ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
Back to top | Article view | comp.arch.embedded
csiph-web