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.
Boxed MCU with RS-232 Port
Started by ●January 17, 2023
Reply by ●March 27, 20232023-03-27
Reply by ●March 27, 20232023-03-27
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. Whatever... -- Rick C. ++-+- Get 1,000 miles of free Supercharging ++-+- Tesla referral code - https://ts.la/richard11209
Reply by ●March 27, 20232023-03-27
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
Reply by ●March 27, 20232023-03-27
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.
Reply by ●March 28, 20232023-03-28
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. -- Rick C. +++-- Get 1,000 miles of free Supercharging +++-- Tesla referral code - https://ts.la/richard11209
Reply by ●March 28, 20232023-03-28
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.
Reply by ●March 28, 20232023-03-28
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*!
Reply by ●March 28, 20232023-03-28
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. I wasn't asking for help with the RS-232 signals. Never was. I was trying to make a point that the RS-232 interface circuit did not document the I/O well enough to know which was input and which was output. Even though I've explained this several times now, some people aren't getting it. -- Rick C. +++-+ Get 1,000 miles of free Supercharging +++-+ Tesla referral code - https://ts.la/richard11209
Reply by ●March 28, 20232023-03-28
On 2023-03-28, Rick C <gnuarm.deletethisbit@gmail.com> wrote:> On Tuesday, March 28, 2023 at 12:22:01???AM UTC-4, Clifford Heath wrote: >> > 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. I wasn't asking for help > with the RS-232 signals. Never was. I was trying to make a point > that the RS-232 interface circuit did not document the I/O well enough > to know which was input and which was output. > > Even though I've explained this several times now, some people aren't > getting it.Maybe you didn't explain it well enough. Or maybe you attempted sarcasm/irony/innuendo/whatever and it failed :-) You wouldn't know would you :-)
Reply by ●March 28, 20232023-03-28
On Tuesday, March 28, 2023 at 4:00:54 PM UTC-4, Jim Jackson wrote:> On 2023-03-28, Rick C <gnuarm.del...@gmail.com> wrote: > > On Tuesday, March 28, 2023 at 12:22:01???AM UTC-4, Clifford Heath wrote: > >> > 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. I wasn't asking for help > > with the RS-232 signals. Never was. I was trying to make a point > > that the RS-232 interface circuit did not document the I/O well enough > > to know which was input and which was output. > > > > Even though I've explained this several times now, some people aren't > > getting it. > Maybe you didn't explain it well enough. Or maybe you attempted > sarcasm/irony/innuendo/whatever and it failed :-) > You wouldn't know would you :-)Obviously it was not explained clearly enough. But sometimes, the audience is simply not able to understand a message, no matter how well explained. It is interesting that some people are so wrapped around the axle, that they can't stop replying to this thread, even when they have to address me in the third person. -- Rick C. ++++- Get 1,000 miles of free Supercharging ++++- Tesla referral code - https://ts.la/richard11209
