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 | 15 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 8 of 8 — ← Prev page 1 2 3 4 5 6 7 [8]
| From | Clifford Heath <no.spam@please.net> |
|---|---|
| Date | 2023-03-29 08:03 +1100 |
| Message-ID | <1750b119fcdef6e7$11$1053351$1aa14cb9@news.thecubenet.com> |
| In reply to | #31766 |
On 29/03/23 02:37, Rick C wrote: > On Tuesday, March 28, 2023 at 12:22:01 AM UTC-4, Clifford Heath wrote: >> On 28/03/23 14:41, Rick C wrote: >>> On Monday, March 27, 2023 at 9:58:27 PM UTC-4, Clifford Heath wrote: >>>> On 28/03/23 11:59, Rick C wrote: >>>>> On Monday, March 27, 2023 at 7:36:33 PM UTC-4, Clifford Heath wrote: >>>>>> On 28/03/23 09:40, Don Y wrote: >>>>>>> On 3/27/2023 3:05 PM, Rick C wrote: >>>>>>>> On Monday, March 27, 2023 at 4:17:29 PM UTC-4, Don Y wrote: >>>>>>>>> On 3/27/2023 1:03 PM, Rick C wrote: >>>>>>>>>>>>>>>> I was playing the game, where questions are asked, until the >>>>>>>>>>>>>>>> other person sees the absurdity of >>>>>>>>> -------^^^^^^^^^^^^^^^^^^^^^^^\ >>>>>>>>> >>>>>>>>> Ah, so you're not an engineer. Not a technician. Comedian?? >>>>>>>>>> what they were saying. You still haven't figured that out. >>>>>>>>>>> I gave the only answer that anyone COULD give to your silly question. >>>>>>>>>>> Were you hoping someone here was USING the exact same board AND had >>>>>>>>>>> explored that issue in enough detail to yield a pin number? Instead >>>>>>>>>>> of just "Gee, I dunno. It worked WHEN I PLUGGED IN THE CABLE!" >>>>>>>>>> >>>>>>>>>> You still don't get it. In the post you replied to, there was a >>>>>>>>>> board referenced. It even gave the same general info YOU provided in >>>>>>>>>> response, about TXD, RXD, DTE and DCE. BUT IT DIDN'T SAY DIDDLY >>>>>>>>>> ABOUT WHICH PIN WAS INPUT AND WHICH WAS OUTPUT! >>>>>>>>> And my answer fits that dfescription. >>>>>>>>> >>>>>>>>> Here, Master Rick. Please, in clear English sentences of no more than >>>>>>>>> 3 syllables, explain what you want from us. And, WHY YOU EXPECT >>>>>>>>> SOMEONE HERE >>>>>>>>> to have that information. >>>>>>>> >>>>>>>> I don't expect anything from you, and so far, you have not disappointed. >>>>>>>> >>>>>>>>> Do you think one of us designed the board? >>>>>>>> >>>>>>>> What board? The one with insufficient information? No, but you still >>>>>>>> fail to understand that I never expected an answer to the question. >>>>>>>> It was a question that would have led any intelligent person to the >>>>>>>> realization that the question could not be answered, which was the >>>>>>>> point I was trying to make to the person who posted the link to the >>>>>>>> board. But, in your usual way, you jumped in to fix what YOU thought >>>>>>>> was the problem, while you knew no more than anyone else. >>>>>>> >>>>>>> Ah, so now we know -- you're just here to waste our time. >>>>>>> I'm so glad you admitted that! I'm sure people will keep >>>>>>> that in mind as they consider whether or not to answer >>>>>>> future questions that you pose! >>>>>> I long ago gave up trying to answer Ricky, though my resolve sometimes >>>>>> stumbles. He has a kind of willful incomprehension that prevents him >>>>>> from receiving input, either on technical subjects or about his own >>>>>> incapacities... even the excellent and succinct feedback from David >>>>>> Brown. I suspect it's a flavour of autism. >>>>>> >>>>>> Rick, no need to answer. I'm not talking to you, but about you. >>>>> >>>>> Oh, dear god. Another one who can't understand, no matter how carefully I explain it. >>>> I have precisely zero interest in your question or the foregoing >>>> discussion, which I haven't read and do not wish to understand. >>>> >>>> I'm only commenting on some of the various personality defects on display. >>> >>> Which completely changes because you don't understand the issues being discussed. >>> >>> I'm happy to receive input. But I also expect to be able to give feedback when people don't understand what is being discussed. >>> >>> Interestingly, no one has provided any feedback at all, on the technical issues I've pointed out. Only that I'm wrong. DCE/DTE is what it's all about and that my personality is defective. If they don't listen to what I'm saying, they can't possibly understand the issues. >>> >> It is *your behaviour* that has made it impossible for anyone to answer >> you to your satisfaction. Nothing else. RS232 signals bored me over two >> decades ago, when I last had to worry about how things should be. We >> encountered equipment that was made with every possible combination of >> errors, and we all just figured it out and got on with our lives, in >> exactly the way you seem unable to. > > Still misunderstanding the conversation It's not possible to misunderstand something I haven't read. I just came late to observe the interpersonal argy-bargy your feisty incompetence *always* creates. Seriously mate, take a long hard took at yourself. This is not about RS-232 (which has always been badly designed, implemented, documented, and misunderstood - a fact we've all known for decades). It's about you.
[toc] | [prev] | [next] | [standalone]
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Date | 2023-03-28 00:11 -0700 |
| Message-ID | <tvu3ug$3l036$1@dont-email.me> |
| In reply to | #31758 |
On 3/27/2023 4:36 PM, Clifford Heath wrote: > On 28/03/23 09:40, Don Y wrote: >> Ah, so now we know -- you're just here to waste our time. >> I'm so glad you admitted that! I'm sure people will keep >> that in mind as they consider whether or not to answer >> future questions that you pose! > > I long ago gave up trying to answer Ricky, though my resolve sometimes > stumbles. He has a kind of willful incomprehension that prevents him from > receiving input, either on technical subjects or about his own incapacities... > even the excellent and succinct feedback from David Brown. I suspect it's a > flavour of autism. > > Rick, no need to answer. I'm not talking to you, but about you. He's far too busy to answer -- working on those million dollar deals (yet nickel and diming people for free engineering services!). Gotta wonder what answering these posts is costing him in terms of lost opportunities! Probably another million dollar deal -- or two! (sigh) Some people are just slow learners. Imagine all the trouble he's gonna have when he advances from RS232 to HDLC/SDLC to Token Ring to Ethernet! And, I shudder to think how he'll make the emotional adjustment to *wireless*!
[toc] | [prev] | [next] | [standalone]
| From | "b...@gmx.com" <bl1@gmx.com> |
|---|---|
| Date | 2023-03-27 16:17 -0700 |
| Message-ID | <418ec5d7-8d8d-4b70-91cf-3613ec74a435n@googlegroups.com> |
| In reply to | #31744 |
On Tuesday, March 28, 2023 at 0:05:07 UTC+2, Rick C wrote: > On Monday, March 27, 2023 at 4:17:29 PM UTC-4, Don Y wrote: [snip] > Which is exactly the point. YOU can't answer the question, because there is not adequate information. It has been all this time that you've been spouting about DCE/DTE and convention this and all manner of formality, which is of ZERO value, because the board is not documented as to whether it's DTE or DCE wired! Don't want to disturb your argument, but: If it has a male connector, it's most likely DTE wired, if it has a female one, it's most likely DCE wired. There's a ~3% chance that this guess is wrong, but whoever designs comms equipment has heard about RS-232, DCEs and DTEs, and tries to get things straight... [snip]
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 18:12 -0700 |
| Message-ID | <2f598b30-013d-4251-aef7-a4c6333ef3f3n@googlegroups.com> |
| In reply to | #31757 |
On Monday, March 27, 2023 at 7:17:47 PM UTC-4, b...@gmx.com wrote: > On Tuesday, March 28, 2023 at 0:05:07 UTC+2, Rick C wrote: > > On Monday, March 27, 2023 at 4:17:29 PM UTC-4, Don Y wrote: > [snip] > > Which is exactly the point. YOU can't answer the question, because there is not adequate information. It has been all this time that you've been spouting about DCE/DTE and convention this and all manner of formality, which is of ZERO value, because the board is not documented as to whether it's DTE or DCE wired! > Don't want to disturb your argument, but: > > If it has a male connector, it's most likely DTE wired, if it has a female one, it's most likely DCE wired. > There's a ~3% chance that this guess is wrong, but whoever designs comms equipment has heard about RS-232, DCEs and DTEs, and tries to get things straight... I'm curious, how did you arrive at the 3% figure? I've read that 78.4% of all statistics are made up. In my experience, there is little correlation of connector gender and pin configuration. You are making the same mistake that Don has been making all along... *assumptions*. Nothing I'm talking about is comms equipment. That was one of my first comments about the issue, that RS-232 defines the connectors at ONE POINT in a comms system, the connectors and pin out of the DTE and DCE ON the DCE unit. It says nothing about what connectors are on the other end of the cable (or their pin out) and it says nothing about how devices are connected when they are not DCE/DTE. *This* is why RS-232 is a mess as a general purpose interconnect. That's why using the terms TXD and RXD tell you nothing about the direction of the signals. Most of the time, there is no DTE or DCE. So the connectors are not actually the part of the spec that is used. What is used, is the voltage levels, and possibly the connector, but with no guidance to indicate if TXD is input or output, because there's no DCE or DTE. That's why I always look for an indication of input and output, rather than focusing on the parts of the RS-232 standard that are likely not being used. That was my point, when I kept asking which was input and which was output. It took Don several exchanges to figure out that he could not say, and I'm not sure if, even now, he understands that was why I was asking. I don't need the answer, because I'm not using that board. I was trying to make it obvious, that it was not documented, and so could not be found from the info available, regardless of all the DCE/DTE hoolah. -- Rick C. ++-++ Get 1,000 miles of free Supercharging ++-++ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Hans-Bernhard Bröker <HBBroeker@t-online.de> |
|---|---|
| Date | 2023-03-24 19:26 +0100 |
| Message-ID | <k868b1FdvfuU2@mid.dfncis.de> |
| In reply to | #31682 |
Am 24.03.2023 um 15:20 schrieb Theo: > The problem is that commercial microcontroller boards like Arduinos tend to > have TTL level serial ports (or USB ones). If you want a box holding one of > those with some RS232 ports, you need to make a PCB with a MAX232 and a DB9, > and an enclosure to match. Rick was trying to find a box with all that > already done for him and drew a blank. Of course he did. Finding that kind of box off-the-shelf was a very long shot, IMHO. Industrialized versions of the Raspberry Pi might have come close, but they're more likely to offer RS485 or 422, insead of 232.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 08:03 -0700 |
| Message-ID | <9119030a-9d22-4df4-852c-ecfee2e5cf1an@googlegroups.com> |
| In reply to | #31681 |
On Friday, March 24, 2023 at 7:45:03 AM UTC-4, Hans-Bernhard Bröker wrote: > Am 24.03.2023 um 09:02 schrieb Rick C: > > On Thursday, March 23, 2023 at 11:54:54 AM UTC-4, Paul Rubin wrote: > >> Rick C <gnuarm.del...@gmail.com> writes: > >>> If you are talking about someone to build a board, no thanks. > >> No, building a board would be crazy unless you're making 1000s of them. > >> Pick an Arduino or similar board with RS232 support, > > > > That's one of the problems. Boards like Arduinos do not have RS-232 support. They have serial ports, but that's what was tried initially, with a home brew RS-232 level shifter added on a perf board. > Color me puzzled. Why on earth would anyone home-brew an RS232 level > shifter, particularly for a project that could clearly afford using > ready-made ICs like MAX232 instead? That's what they used. I simply meant it was not a commercial product on a PCB. Half the units have some problem. Did you think I meant they designed their own level shifter chip? -- Rick C. ----- Get 1,000 miles of free Supercharging ----- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Hans-Bernhard Bröker <HBBroeker@t-online.de> |
|---|---|
| Date | 2023-03-24 19:10 +0100 |
| Message-ID | <k867deFdvfuU1@mid.dfncis.de> |
| In reply to | #31683 |
Am 24.03.2023 um 16:03 schrieb Rick C: > On Friday, March 24, 2023 at 7:45:03 AM UTC-4, Hans-Bernhard Bröker > wrote: >> Am 24.03.2023 um 09:02 schrieb Rick C: >>> That's one of the problems. Boards like Arduinos do not have >>> RS-232 support. They have serial ports, but that's what was tried >>> initially, with a home brew RS-232 level shifter added on a perf >>> board. >> Color me puzzled. Why on earth would anyone home-brew an RS232 >> level shifter, particularly for a project that could clearly afford >> using ready-made ICs like MAX232 instead? > > That's what they used. I simply meant it was not a commercial > product on a PCB. Half the units have some problem. > > Did you think I meant they designed their own level shifter chip? You said you home-brewed the level shifter. How else was anybody to interpret that?
[toc] | [prev] | [next] | [standalone]
| From | Herbert Kleebauer <klee@unibwm.de> |
|---|---|
| Date | 2023-03-24 17:16 +0100 |
| Message-ID | <tvkie8$1o1oq$1@dont-email.me> |
| In reply to | #31668 |
On 22.03.2023 20:18, Rick C wrote: > I was skimming the web for this again and I think I found something from Aaeon. Not sure why I didn't find this before. Maybe I did, but at that time was really looking for something with a simple CPU, rather than something to run a full OS. Beggars and choosers... > > https://eshop.aaeon.com/ultra-slim-box-pc-boxer-6405.html > > This one is $366, which is more than I'd like, but beggars... It is cheaper than the tailored unit a guy is working on for us. A sample unit doesn't work right and debugging across an ocean is not working very well. I could have this up and running in a day or something, as long as it comes with Linux installed. A lot of power consumption for such a task! An Atmel board would only consume about 0.4 W, for example something like that: https://www.ledato.de/product_info.php?products_id=33 https://www.ledato.de/product_info.php?products_id=35 The price is crazy, but there should be similar devices for only 1/5 of this price.
[toc] | [prev] | [next] | [standalone]
| From | Herbert Kleebauer <klee@unibwm.de> |
|---|---|
| Date | 2023-03-24 18:54 +0100 |
| Message-ID | <tvko4t$1p0h5$1@dont-email.me> |
| In reply to | #31685 |
On 24.03.2023 17:16, Herbert Kleebauer wrote: > https://www.ledato.de/product_info.php?products_id=33 > https://www.ledato.de/product_info.php?products_id=35 The same company (ledato.de, taskit.de) has also an ARM board with Ubuntu and 2 (or 3) RS232 ports which is cheaper: https://www.taskit.de/produkte/flex-iot/ https://youtu.be/Fsr8F6B7j0s
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 11:34 -0700 |
| Message-ID | <8e338f10-94f5-4dea-b122-250a3ae097a8n@googlegroups.com> |
| In reply to | #31685 |
On Friday, March 24, 2023 at 12:17:17 PM UTC-4, Herbert Kleebauer wrote: > On 22.03.2023 20:18, Rick C wrote: > > > I was skimming the web for this again and I think I found something from Aaeon. Not sure why I didn't find this before. Maybe I did, but at that time was really looking for something with a simple CPU, rather than something to run a full OS. Beggars and choosers... > > > > https://eshop.aaeon.com/ultra-slim-box-pc-boxer-6405.html > > > > This one is $366, which is more than I'd like, but beggars... It is cheaper than the tailored unit a guy is working on for us. A sample unit doesn't work right and debugging across an ocean is not working very well. I could have this up and running in a day or something, as long as it comes > with Linux installed. > A lot of power consumption for such a task! An Atmel board > would only consume about 0.4 W, for example something like > that: > > https://www.ledato.de/product_info.php?products_id=33 > https://www.ledato.de/product_info.php?products_id=35 > > The price is crazy, but there should be similar > devices for only 1/5 of this price. There should be many things in this world.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-27 10:18 -0700 |
| Message-ID | <bd037c18-b30e-4705-a4b7-4f8b052c29f8n@googlegroups.com> |
| In reply to | #31541 |
On Tuesday, January 17, 2023 at 11:24:33 AM UTC-4, Rick C wrote: > The unit only really needs one serial port, but it is more convenient to have two connectors, so I guess it needs to ports. One port will only receive and the other only transmit, no handshaking. > > The function is pretty simple. A sensor sends a line of about 50 chars, at 9,600 bps, once per second. This box counts 20 lines and adds a header. So nothing fancy is required of the MCU. There are parameters set when starting operation. > > The main thing I'm having trouble finding, is this needs to be in a box as a unit, not a board and a box to be assembled. Google hasn't been much help returning all sorts of things that aren't useful. > > Anyone know of such a box? The programming might be contracted out, if you are interested. There's a prototype using an Arduino nano, but some of them are flaky and it would not hurt to start over from scratch. In case anyone is interested, I think I've found a good board level solution. Arduino Mega coupled to this board to provide RS-232. https://leemangeophysical.com/product/rs-232-arduino-mega-xbee-data-shield/ It has no DB9 connectors, which is good, allowing them to be mounted in the case. Now I just need to procure a case. If I have to, I suppose I can design that myself and get a few made. Anyone knowledgeable in designing small cases? I'd love to have this be a turn-key purchase. -- Rick C. +--+- Get 1,000 miles of free Supercharging +--+- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Uwe Bonnes <bon@hertz.ikp.physik.tu-darmstadt.de> |
|---|---|
| Date | 2023-03-28 20:53 +0000 |
| Message-ID | <k8h2eoFcln3U1@mid.individual.net> |
| In reply to | #31541 |
Rick C <gnuarm.deletethisbit@gmail.com> wrote: > The unit only really needs one serial port, but it is more convenient to have two connectors, so I guess it needs to ports. One port will only receive and the other only transmit, no handshaking. > > The function is pretty simple. A sensor sends a line of about 50 chars, at 9,600 bps, once per second. This box counts 20 lines and adds a header. So nothing fancy is required of the MCU. There are parameters set when starting operation. > > The main thing I'm having trouble finding, is this needs to be in a box as a unit, not a board and a box to be assembled. Google hasn't been much help returning all sorts of things that aren't useful. > > Anyone know of such a box? The programming might be contracted out, if you are interested. There's a prototype using an Arduino nano, but some of them are flaky and it would not hurt to start over from scratch. > The boxes sell refurbed at 49 Euro https://www.itsco.de/thin-client-lenovo-thinkcentre-m625q-amd-7th-gen-e2-9000e-2x-1-5ghz.html and have "2x seriell RS-232 Tiny" -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-28 16:12 -0700 |
| Message-ID | <008d6173-e4a5-4250-9f9e-0b4ae53bf995n@googlegroups.com> |
| In reply to | #31770 |
On Tuesday, March 28, 2023 at 4:53:51 PM UTC-4, Uwe Bonnes wrote: > Rick C <gnuarm.del...@gmail.com> wrote: > > The unit only really needs one serial port, but it is more convenient to have two connectors, so I guess it needs to ports. One port will only receive and the other only transmit, no handshaking. > > > > The function is pretty simple. A sensor sends a line of about 50 chars, at 9,600 bps, once per second. This box counts 20 lines and adds a header. So nothing fancy is required of the MCU. There are parameters set when starting operation. > > > > The main thing I'm having trouble finding, is this needs to be in a box as a unit, not a board and a box to be assembled. Google hasn't been much help returning all sorts of things that aren't useful. > > > > Anyone know of such a box? The programming might be contracted out, if you are interested. There's a prototype using an Arduino nano, but some of them are flaky and it would not hurt to start over from scratch. > > > > The boxes sell refurbed at 49 Euro > https://www.itsco.de/thin-client-lenovo-thinkcentre-m625q-amd-7th-gen-e2-9000e-2x-1-5ghz.html > and have "2x seriell RS-232 Tiny" Thank you for the link. I can't find a way to use English on the site. itsco.com brings up an english version of the site, but it doesn't seem to include any equipment sales. Maybe it's not the same company? I see companies selling these on Ebay. Do you know if they will boot up and operate with no keyboard, mouse or video connected? I would run these on Linux and they would have to boot stand alone. -- Rick C. +++++ Get 1,000 miles of free Supercharging +++++ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Niklas Holsti <niklas.holsti@tidorum.invalid> |
|---|---|
| Date | 2023-03-29 09:06 +0300 |
| Message-ID | <k8i2rvFadprU1@mid.individual.net> |
| In reply to | #31773 |
On 2023-03-29 2:12, Rick C wrote: > On Tuesday, March 28, 2023 at 4:53:51 PM UTC-4, Uwe Bonnes wrote: >> Rick C <gnuarm.del...@gmail.com> wrote: >>> The unit only really needs one serial port, but it is more >>> convenient to have two connectors, so I guess it needs to ports. >>> One port will only receive and the other only transmit, no >>> handshaking. >>> >>> The function is pretty simple. A sensor sends a line of about 50 >>> chars, at 9,600 bps, once per second. This box counts 20 lines >>> and adds a header. So nothing fancy is required of the MCU. There >>> are parameters set when starting operation. >>> >>> The main thing I'm having trouble finding, is this needs to be in >>> a box as a unit, not a board and a box to be assembled. Google >>> hasn't been much help returning all sorts of things that aren't >>> useful. >>> >>> Anyone know of such a box? The programming might be contracted >>> out, if you are interested. There's a prototype using an Arduino >>> nano, but some of them are flaky and it would not hurt to start >>> over from scratch. >>> >> >> The boxes sell refurbed at 49 Euro >> https://www.itsco.de/thin-client-lenovo-thinkcentre-m625q-amd-7th-gen-e2-9000e-2x-1-5ghz.html >> >> >> and have "2x seriell RS-232 Tiny" > > Thank you for the link. I can't find a way to use English on the > site. itsco.com brings up an english version of the site, but it > doesn't seem to include any equipment sales. Maybe it's not the same > company? > > I see companies selling these on Ebay. Do you know if they will boot > up and operate with no keyboard, mouse or video connected? I would > run these on Linux and they would have to boot stand alone. One of the customer reviews on the site says "Das Ganze wird am LAN ohne Monitor, Tastatur und Maus betrieben" = "All of it runs on LAN without video, keyboard and mouse", under Debian 11. I would assume that also means it can boot up in that configuration, but the review does not say that explicitly.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-29 00:44 -0700 |
| Message-ID | <6764ec41-7ad0-4fd3-ba87-7261ac7f7692n@googlegroups.com> |
| In reply to | #31777 |
On Wednesday, March 29, 2023 at 2:07:03 AM UTC-4, Niklas Holsti wrote: > On 2023-03-29 2:12, Rick C wrote: > > On Tuesday, March 28, 2023 at 4:53:51 PM UTC-4, Uwe Bonnes wrote: > >> Rick C <gnuarm.del...@gmail.com> wrote: > >>> The unit only really needs one serial port, but it is more > >>> convenient to have two connectors, so I guess it needs to ports. > >>> One port will only receive and the other only transmit, no > >>> handshaking. > >>> > >>> The function is pretty simple. A sensor sends a line of about 50 > >>> chars, at 9,600 bps, once per second. This box counts 20 lines > >>> and adds a header. So nothing fancy is required of the MCU. There > >>> are parameters set when starting operation. > >>> > >>> The main thing I'm having trouble finding, is this needs to be in > >>> a box as a unit, not a board and a box to be assembled. Google > >>> hasn't been much help returning all sorts of things that aren't > >>> useful. > >>> > >>> Anyone know of such a box? The programming might be contracted > >>> out, if you are interested. There's a prototype using an Arduino > >>> nano, but some of them are flaky and it would not hurt to start > >>> over from scratch. > >>> > >> > >> The boxes sell refurbed at 49 Euro > >> https://www.itsco.de/thin-client-lenovo-thinkcentre-m625q-amd-7th-gen-e2-9000e-2x-1-5ghz.html > >> > >> > >> and have "2x seriell RS-232 Tiny" > > > > Thank you for the link. I can't find a way to use English on the > > site. itsco.com brings up an english version of the site, but it > > doesn't seem to include any equipment sales. Maybe it's not the same > > company? > > > > I see companies selling these on Ebay. Do you know if they will boot > > up and operate with no keyboard, mouse or video connected? I would > > run these on Linux and they would have to boot stand alone. > One of the customer reviews on the site says "Das Ganze wird am LAN ohne > Monitor, Tastatur und Maus betrieben" = "All of it runs on LAN without > video, keyboard and mouse", under Debian 11. I would assume that also > means it can boot up in that configuration, but the review does not say > that explicitly. Thanks again. I will consider these. I found them on Ebay and other sites at similar prices. It seems there are variants with different I/O, including no serial ports. So, I'll have to be careful to check that. I still prefer a system with no OS and low power. So the Arduino or rPi Pico is my preferred option at the moment. But those need cases. I guess the vast majority of such small units are sold for amateur use, where a case is not important. I believe they sell a version of the rPi for commercial use with have some level of assurance of continuing supply. I might want to look at that harder, but again, there's not as much support for operation without an OS. I took a look at the Forth tools available for the AVR. Other than Forth Inc. the supply is very limited. The ARM, of course, has wide support. But this program is so simple, it could be written in any language, without concern. I'm just much more familiar with Forth these days. -- Rick C. - Get 1,000 miles of free Supercharging - Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [standalone]
Page 8 of 8 — ← Prev page 1 2 3 4 5 6 7 [8]
Back to top | Article view | comp.arch.embedded
csiph-web