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 4 of 8 — ← Prev page 1 2 3 [4] 5 6 7 8 Next page →
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-22 20:35 -0700 |
| Message-ID | <87cz50i1hx.fsf@nightsong.com> |
| In reply to | #31668 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > BTW, to those who contacted me about this and haven't heard back after > the initial exchange, I'm sorry. I got busy with my own work and lost > track of the emails. Of those who did reply, only one had a design in > a box, ready for software. But that is not yet working. You still want someone to do this custom? What is your budget and how many units do you want? Did you ever find out more about the requirements? I know a good who is good at this stuff. You are probably looking at $1000 or more of NRE, but spread across a few dozen units it might not be too bad, as the hardware itself should be quite cheap.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-22 23:26 -0700 |
| Message-ID | <40aa56ff-c2a7-48f3-99e0-8c50322b1187n@googlegroups.com> |
| In reply to | #31671 |
On Wednesday, March 22, 2023 at 11:35:18 PM UTC-4, Paul Rubin wrote:
> Rick C <gnuarm.del...@gmail.com> writes:
> > BTW, to those who contacted me about this and haven't heard back after
> > the initial exchange, I'm sorry. I got busy with my own work and lost
> > track of the emails. Of those who did reply, only one had a design in
> > a box, ready for software. But that is not yet working.
> You still want someone to do this custom? What is your budget and how
> many units do you want? Did you ever find out more about the
> requirements? I know a good who is good at this stuff. You are
> probably looking at $1000 or more of NRE, but spread across a few dozen
> units it might not be too bad, as the hardware itself should be quite cheap.
If you are talking about someone to build a board, no thanks. That is what I meant to say in the post, but I guess I glossed over that. I found a platform that is affordable, even if it is way overkill. A custom board design is not needed. Heck, a custom board design was never needed, except that RS-232 voltage levels are needed at the serial port I/Os. Otherwise, an Arduino of some variation, would be ideal.
I will just write the software myself with the $300 platform I guess. Being a PC type platform, running an OS, updating the software is just a matter of copying a file from an SD card or a USB memory stick. It could even be hooked up through the Ethernet port, although I'm not so familiar with that these days.
Years ago, I had a couple of desktop PCs running Win2k and from the info I found on the website World of Windows Networking, was able to connect them so the disk drives were available on either machine. I tried to do the same think a couple of years ago and it was much, much harder. Microsoft has made networking much more complex now.
I did manage to find my way through management speak and arrive at a very simple set of requirements. In fact, the problem with the guy we currently have working on the effort, is he added requirements of his own, that mess up the operation we intended. We might still use his solution, if he can get it to work for us. But he's in the UK and this is mucking up the debugging.
This device goes between a sensor, and an EDAS, which is just an industrial computer acting as an intermediary, collecting other data and sending it all on to other receivers of the data. A product update in the sensor (third party product) changed the data format. Before this new sensor was used, the translator was not needed. The translator makes the new sensor output compliant with the old sensor format which is expected downstream.
Serial formats are 9600, 8, N, 1. The input data is 1 line per second, output as soon as converted. A header is appended after each 20th input line. At these data rates, there will be no handshaking and no chance of any collisions.
New data format on incoming message example:
# 032023 174930 23.024 6.79 17.37 12.44
Terminated with /r/n
Old data format on output message example:
01/30/23 19:15:28 21.788 6.23 17.41 12.66
Terminated by /r/n
The modifications in the data are removing the "# " at the beginning and inserting '\' and ':' into the date and time fields.
Every 20 lines a header should be inserted and sent to the output. If something corrupts the line count, it's not a problem.
===========================================
Date Time Temp SpCond pH ODO
m/d/y hh:mm:ss C mS/cm mg/L
-------------------------------------------
*** 1-LOG last sample 2-LOG ON/OFF, 3-Clean optics ***
Anything received that isn't in the input format specified above, should be sent on to the output. No other data should be sent to the output, such as boot messages. The only error checking should be that the line does not overflow the internal translator buffers. A watchdog timer could be used to reset the unit, if the software is lost in the weeds. The goal here is not for any data error checking, or other optimizations. If the old sensor produced any crap data, it didn't muck up the works before, and it shouldn't be a problem now, so just send it on.
I don't know for certain that the input data format is always the same length, so this should not be assumed. I would say an 80 character max length is a safe assumption. The /r/n should be the line delimiter. If garbage is received on the input before a message, it will prevent detection of the start of the message, which is fine. As soon as the next /r/n is received, it will be back in alignment. That's all that matters.
If I had more free time, I would have this done by now. lol
--
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-22 23:28 -0700 |
| Message-ID | <ed374404-5e4f-4283-898e-d8930a9b0923n@googlegroups.com> |
| In reply to | #31672 |
On Thursday, March 23, 2023 at 2:26:40 AM UTC-4, Rick C wrote: > On Wednesday, March 22, 2023 at 11:35:18 PM UTC-4, Paul Rubin wrote: > > Rick C <gnuarm.del...@gmail.com> writes: > > > BTW, to those who contacted me about this and haven't heard back after > > > the initial exchange, I'm sorry. I got busy with my own work and lost > > > track of the emails. Of those who did reply, only one had a design in > > > a box, ready for software. But that is not yet working. > > You still want someone to do this custom? What is your budget and how > > many units do you want? Did you ever find out more about the > > requirements? I know a good who is good at this stuff. You are > > probably looking at $1000 or more of NRE, but spread across a few dozen > > units it might not be too bad, as the hardware itself should be quite cheap. > If you are talking about someone to build a board, no thanks. That is what I meant to say in the post, but I guess I glossed over that. I found a platform that is affordable, even if it is way overkill. A custom board design is not needed. Heck, a custom board design was never needed, except that RS-232 voltage levels are needed at the serial port I/Os. Otherwise, an Arduino of some variation, would be ideal. > > I will just write the software myself with the $300 platform I guess. Being a PC type platform, running an OS, updating the software is just a matter of copying a file from an SD card or a USB memory stick. It could even be hooked up through the Ethernet port, although I'm not so familiar with that these days. > > Years ago, I had a couple of desktop PCs running Win2k and from the info I found on the website World of Windows Networking, was able to connect them so the disk drives were available on either machine. I tried to do the same think a couple of years ago and it was much, much harder. Microsoft has made networking much more complex now. > > I did manage to find my way through management speak and arrive at a very simple set of requirements. In fact, the problem with the guy we currently have working on the effort, is he added requirements of his own, that mess up the operation we intended. We might still use his solution, if he can get it to work for us. But he's in the UK and this is mucking up the debugging. > > This device goes between a sensor, and an EDAS, which is just an industrial computer acting as an intermediary, collecting other data and sending it all on to other receivers of the data. A product update in the sensor (third party product) changed the data format. Before this new sensor was used, the translator was not needed. The translator makes the new sensor output compliant with the old sensor format which is expected downstream. > > Serial formats are 9600, 8, N, 1. The input data is 1 line per second, output as soon as converted. A header is appended after each 20th input line. At these data rates, there will be no handshaking and no chance of any collisions. > > New data format on incoming message example: > # 032023 174930 23.024 6.79 17.37 12.44 > Terminated with /r/n > > Old data format on output message example: > 01/30/23 19:15:28 21.788 6.23 17.41 12.66 > Terminated by /r/n > > The modifications in the data are removing the "# " at the beginning and inserting '\' and ':' into the date and time fields. > > Every 20 lines a header should be inserted and sent to the output. If something corrupts the line count, it's not a problem. > > =========================================== > Date Time Temp SpCond pH ODO > m/d/y hh:mm:ss C mS/cm mg/L > ------------------------------------------- > *** 1-LOG last sample 2-LOG ON/OFF, 3-Clean optics *** > > Anything received that isn't in the input format specified above, should be sent on to the output. No other data should be sent to the output, such as boot messages. The only error checking should be that the line does not overflow the internal translator buffers. A watchdog timer could be used to reset the unit, if the software is lost in the weeds. The goal here is not for any data error checking, or other optimizations. If the old sensor produced any crap data, it didn't muck up the works before, and it shouldn't be a problem now, so just send it on. > > I don't know for certain that the input data format is always the same length, so this should not be assumed. I would say an 80 character max length is a safe assumption. The /r/n should be the line delimiter. If garbage is received on the input before a message, it will prevent detection of the start of the message, which is fine. As soon as the next /r/n is received, it will be back in alignment. That's all that matters. > > If I had more free time, I would have this done by now. lol The number of units required is initially 20, and probably another 20 in a few months. After that, not sure. -- Rick C. ++-- Get 1,000 miles of free Supercharging ++-- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2023-03-23 10:06 +0000 |
| Message-ID | <kJc*RKWbz@news.chiark.greenend.org.uk> |
| In reply to | #31673 |
Rick C <gnuarm.deletethisbit@gmail.com> wrote: > The number of units required is initially 20, and probably another 20 in a > few months. After that, not sure. We've been here before, but there are many many 'mini PCs' (often Celeron or similar low power CPU) coming out of China that have multiple RS232 ports. There doesn't seem to be much special about this one. If such a 'mini PC' is within your spec (you were talking about microcontrollers originally), it's just a case of finding a distributor who meets your requirements. Easiest is to just go on Aliexpress [1] and buy them, but if that's not your thing then I'm sure there is a US/wherever importer. If you're going to need many years worth of supply that's a bit trickier, since they tend to update the product lines every time Intel releases a new chip. Theo [1] https://www.aliexpress.com/w/wholesale-mini-pc-rs232.html
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 00:59 -0700 |
| Message-ID | <7f84b3be-354b-4198-9eea-c6b207b152e3n@googlegroups.com> |
| In reply to | #31674 |
On Thursday, March 23, 2023 at 6:06:46 AM UTC-4, Theo wrote: > Rick C <gnuarm.del...@gmail.com> wrote: > > The number of units required is initially 20, and probably another 20 in a > > few months. After that, not sure. > We've been here before, but there are many many 'mini PCs' (often Celeron or > similar low power CPU) coming out of China that have multiple RS232 ports. > There doesn't seem to be much special about this one. Yes, but initially I was looking for something more like an Arduino in a box. That never materialized. The solution we are looking at now, is a custom design someone did for another project, that suits our needs, but since the production quantities are low, the unit price is a bit steep, even if manageable. > If such a 'mini PC' is within your spec (you were talking about > microcontrollers originally), it's just a case of finding a distributor who > meets your requirements. Easiest is to just go on Aliexpress [1] and buy > them, but if that's not your thing then I'm sure there is a US/wherever > importer. LOL! Aliexpress is literally the last place I would go for commercial gear. > If you're going to need many years worth of supply that's a bit trickier, > since they tend to update the product lines every time Intel releases a new > chip. > > Theo > > [1] https://www.aliexpress.com/w/wholesale-mini-pc-rs232.html Useless, since you may not be able to buy the same unit even six months from now. But thanks for the suggestion. I'm presently talking to Aaeon who has some affordable units. -- Rick C. ++-+ Get 1,000 miles of free Supercharging ++-+ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-23 09:00 -0700 |
| Message-ID | <874jqbihk9.fsf@nightsong.com> |
| In reply to | #31673 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > The number of units required is initially 20, and probably another 20 > in a few months. After that, not sure. You are really willing to spend $300 per box in that quantity? So $6000 or $12000 depending? This sounds very doable. Where is the deployment site geographically?
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 01:03 -0700 |
| Message-ID | <0e7232b0-2f7d-4894-afcf-4e37deb4c777n@googlegroups.com> |
| In reply to | #31676 |
On Thursday, March 23, 2023 at 12:00:35 PM UTC-4, Paul Rubin wrote: > Rick C <gnuarm.del...@gmail.com> writes: > > The number of units required is initially 20, and probably another 20 > > in a few months. After that, not sure. > You are really willing to spend $300 per box in that quantity? So $6000 > or $12000 depending? This sounds very doable. > > Where is the deployment site geographically? Multiple. Some are in the DC area. -- Rick C. ++++ Get 1,000 miles of free Supercharging ++++ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-23 08:54 -0700 |
| Message-ID | <878rfnihti.fsf@nightsong.com> |
| In reply to | #31672 |
Rick C <gnuarm.deletethisbit@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, pick some enclosure out of a catalog, put the stuff together, get the code running on the board and test everything, etc. Then send the assembled unit to the actual deployment site for in situ testing before making more units. There is always some stuff going wrong or consuming time in any process like that. Thus there will be some NRE.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 01:02 -0700 |
| Message-ID | <579cd7b3-b5ae-41ef-acd1-1f57eacd11c4n@googlegroups.com> |
| In reply to | #31675 |
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. Don't know why, but half of them tend to hang, even if after days. Not acceptable. > pick some enclosure > out of a catalog, put the stuff together, get the code running on the > board and test everything, etc. Then send the assembled unit to the > actual deployment site for in situ testing before making more units. Sounds great. Do you have a proposal? > There is always some stuff going wrong or consuming time in any process > like that. Thus there will be some NRE. Yeah, I'll just do the software myself. The cost difference between the Arduino and a minature PC is so small, it's more than made up in the savings of not having to do any of the stuff you mentioned other than write software. -- Rick C. +++- Get 1,000 miles of free Supercharging +++- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-24 01:43 -0700 |
| Message-ID | <87zg82h73y.fsf@nightsong.com> |
| In reply to | #31678 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > That's one of the problems. Boards like Arduinos do not have RS-232 > support. I thought I had located one and posted a link here. I'll look again. > Sounds great. Do you have a proposal? I'm open to this but I'm probably not the best person for it, since I'm mostly a software guy. Do you have a timeframe? I can also check with other people I know who might be interested, and will refer them to you by email if they are.
[toc] | [prev] | [next] | [standalone]
| From | Hans-Bernhard Bröker <HBBroeker@t-online.de> |
|---|---|
| Date | 2023-03-24 12:44 +0100 |
| Message-ID | <k85gpoFdvftU4@mid.dfncis.de> |
| In reply to | #31678 |
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?
[toc] | [prev] | [next] | [standalone]
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2023-03-24 14:20 +0000 |
| Message-ID | <kJc*RX2bz@news.chiark.greenend.org.uk> |
| In reply to | #31681 |
Hans-Bernhard Bröker <HBBroeker@t-online.de> 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? 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. It's not the design that's the problem, it's the manufacturing. Although for quantity 20 at these kind of price points, I might be tempted to build something using dev boards, eg: https://www.dfrobot.com/product-1030.html and maybe a bit of 3D printing for an enclosure. For two of those boards you might need to hand-patch one to use different pins, but it's not hard and could be done. If the customer is willing to pay $300 a unit it might be worth Rick's (or somebody else's) time to do it. I'll be happy to take that contract, email address works :-) Theo
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 08:08 -0700 |
| Message-ID | <dd4c443b-69fe-4c40-95e4-45dce5ab0e83n@googlegroups.com> |
| In reply to | #31682 |
On Friday, March 24, 2023 at 10:20:37 AM UTC-4, Theo wrote: > Hans-Bernhard Bröker <HBBr...@t-online.de> 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? > 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. > > It's not the design that's the problem, it's the manufacturing. > > Although for quantity 20 at these kind of price points, I might be tempted > to build something using dev boards, eg: > https://www.dfrobot.com/product-1030.html > and maybe a bit of 3D printing for an enclosure. For two of those boards > you might need to hand-patch one to use different pins, but it's not hard > and could be done. This device is exactly what makes this difficult. Which pin on the DB9 is the data output? > If the customer is willing to pay $300 a unit it might be worth Rick's (or > somebody else's) time to do it. I'll be happy to take that contract, email > address works :-) You will need to post an email address. GG doesn't provide the email. Just HBBr...@t-online.de -- Rick C. ----+ Get 1,000 miles of free Supercharging ----+ Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2023-03-24 16:23 +0000 |
| Message-ID | <lJc*Lo3bz@news.chiark.greenend.org.uk> |
| In reply to | #31684 |
Rick C <gnuarm.deletethisbit@gmail.com> wrote: > On Friday, March 24, 2023 at 10:20:37 AM UTC-4, Theo wrote: > > This device is exactly what makes this difficult. Which pin on the DB9 is the data output? TXD (output of MAX2323ESE) is pin 2, RXD (input of MAX2323ESE) is pin 3. ie would connect to a PC via a straight-through cable, not a null modem. > > If the customer is willing to pay $300 a unit it might be worth Rick's (or > > somebody else's) time to do it. I'll be happy to take that contract, email > > address works :-) > > You will need to post an email address. GG doesn't provide the email. Just HBBr...@t-online.de My email is on the bottom of http://www.markettos.org.uk/ (I am in the UK, if that makes a difference) Theo
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-24 13:42 -0700 |
| Message-ID | <87tty9hoe2.fsf@nightsong.com> |
| In reply to | #31684 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > This device is exactly what makes this difficult. Which pin on the > DB9 is the data output? The pinout is given here: https://wiki.dfrobot.com/RS232_Shield How do you feel about using that board, with an Arduino? Digikey stocks it, if that helps: https://www.digikey.com/en/products/detail/dfrobot/DFR0258/6588574 How do you feel about recycling the enclosure from one of those port selector switches discussed a while back? Here is a Lilygo board which has an ESP32-C3 MCU and RS232 among other things, for $17.98: https://www.lilygo.cc/products/t-rsc3 It is shipped from China so maybe doesn't fulfill requirements because of that, but it at least shows that such a product exists. Article about it with an Aliexpress redirect link (it is also sold through there): https://www.cnx-software.com/2023/01/20/lilygo-t-rsc3-esp32-c3-board-features-isolated-rs232-rs485-interfaces-5-to-24v-dc-input/ Direct Aliexpress https://www.aliexpress.com/item/1005005136988162.html Here is an Olimex MSP430 board with RS232 for around $32: https://www.olimex.com/Products/MSP430/Starter/MSP430-5438-STK/ It is available at Mouser, though they only have 9 in stock right now: https://www.mouser.com/ProductDetail/Olimex-Ltd/MSP430-5438STK?qs=BoUPAr39LHyy3j%2FN0eUzfQ%3D%3D It is also on Digikey's site, but out of stock there. There are more Olimex boards with RS232 that I didn't look up. You mentioned that you didn't want to use an external FTDI cable on a USB port. What about having an FTDI dongle inside the box, installed so that its DB9 connector is panel mounted? https://ftdichip.com/products/usb-com232-plus1/ https://ftdichip.com/products/db9-usb-f/ TTL to RS232 (?): https://www.sparkfun.com/products/449 Similar: https://www.waveshare.com/wiki/RS232_Board Regarding the locations: are any in the western US?
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 14:31 -0700 |
| Message-ID | <8f169598-33e2-435a-a55a-b2716853084an@googlegroups.com> |
| In reply to | #31691 |
On Friday, March 24, 2023 at 4:42:55 PM UTC-4, Paul Rubin wrote: > Rick C <gnuarm.del...@gmail.com> writes: > > This device is exactly what makes this difficult. Which pin on the > > DB9 is the data output? > The pinout is given here: https://wiki.dfrobot.com/RS232_Shield You didn't answer the question. Which pin is the data output and which is the data input? > How do you feel about using that board, with an Arduino? Digikey stocks > it, if that helps: > > https://www.digikey.com/en/products/detail/dfrobot/DFR0258/6588574 Are you going to make the cable required? > How do you feel about recycling the enclosure from one of those port > selector switches discussed a while back? Recycling is not a problem, as long as there is no branding on the box. > Here is a Lilygo board which has an ESP32-C3 MCU and RS232 among > other things, for $17.98: https://www.lilygo.cc/products/t-rsc3 > > It is shipped from China so maybe doesn't fulfill requirements because > of that, but it at least shows that such a product exists. > > Article about it with an Aliexpress redirect link (it is also sold > through there): > > https://www.cnx-software.com/2023/01/20/lilygo-t-rsc3-esp32-c3-board-features-isolated-rs232-rs485-interfaces-5-to-24v-dc-input/ > > Direct Aliexpress > > https://www.aliexpress.com/item/1005005136988162.html > > Here is an Olimex MSP430 board with RS232 for around $32: > > https://www.olimex.com/Products/MSP430/Starter/MSP430-5438-STK/ > > It is available at Mouser, though they only have 9 in stock right now: > > https://www.mouser.com/ProductDetail/Olimex-Ltd/MSP430-5438STK?qs=BoUPAr39LHyy3j%2FN0eUzfQ%3D%3D > > It is also on Digikey's site, but out of stock there. > > There are more Olimex boards with RS232 that I didn't look up. > > You mentioned that you didn't want to use an external FTDI cable on a > USB port. What about having an FTDI dongle inside the box, installed so > that its DB9 connector is panel mounted? > > https://ftdichip.com/products/usb-com232-plus1/ > https://ftdichip.com/products/db9-usb-f/ Are you going to write the USB stack to run on the simple CPUs you have linked to? > TTL to RS232 (?): https://www.sparkfun.com/products/449 > Similar: https://www.waveshare.com/wiki/RS232_Board I don't know why you are showing all these devices. > Regarding the locations: are any in the western US? I don't know. Why does this matter? You won't be visiting the customer's site. You seem to be thrashing around in looking at every little board that might or might not do the job, rather than finding one that will. The single port boards you've identified have the DB9 connector, but you don't indicate how you will split this into the two connectors required for the job. Do you understand the requirements? -- Rick C. ---+- Get 1,000 miles of free Supercharging ---+- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-24 18:19 -0700 |
| Message-ID | <87pm8xhbk9.fsf@nightsong.com> |
| In reply to | #31692 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > You didn't answer the question. Which pin is the data output and > which is the data input? The transmit pin (TXD, pin 2 in that table) is the output and the receive pin (RXD, pin 3) is the input. Since it is a female connector, by the standard, the box is considered data communications equipment (DCE), rather than data terminal equipment (DTR). If it was DTR, the two pins would be switched around. Is that what you are asking? In any case, one always has to test to be sure. >> https://www.digikey.com/en/products/detail/dfrobot/DFR0258/6588574 > Are you going to make the cable required? A splitter cable? I thought I posted a url to order those from. > Recycling is not a problem, as long as there is no branding on the box. There could be a label with your own branding, strategically placed to cover up any existing branding, if that works for you. > Are you going to write the USB stack to run on the simple CPUs you > have linked to? It exists already on some of them. I wouldn't write a new one. >> TTL to RS232 (?): https://www.sparkfun.com/products/449 >> Similar: https://www.waveshare.com/wiki/RS232_Board > I don't know why you are showing all these devices. There are tons of cpus with built in UARTs > I don't know. Why does this matter? You won't be visiting the > customer's site. Somebody at some point might have to do that. I hope not, but the saying is, hope for the best and plan for the worst. Frankly the first thing I would try is taking one of your homebrew boxes that is known to be failing, swapping out the homemade level shifter PCB with one of the ones linked above, and seeing if that works. Or at least, use a scope to check the voltages coming out of the homemade PCB. > You seem to be thrashing around in looking at every little board that > might or might not do the job, rather than finding one that will. It is a two step process: 1) identify possible candidates; 2) pick one. Posting links to those boards is in part a demonstration that such boards exist. > The single port boards you've identified have the DB9 connector, but > you don't indicate how you will split this into the two connectors > required for the job. Do you understand the requirements? I believe so. There are premade splitter cables that separate pins 2 and 3 from a DB9 into two more DB9's, or such a thing can be made, or (preferable) one can use a CPU with two serial ports (or USB split into two ports). The splitter cable can be inside the box since IIRC you don't want it flopping around on the outside. Then the two DB9's would be on the rear panel.
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-24 18:22 -0700 |
| Message-ID | <87lejlhbfl.fsf@nightsong.com> |
| In reply to | #31694 |
Paul Rubin <no.email@nospam.invalid> writes: > (DCE), rather than data terminal equipment (DTR). If it was DTR, the > two pins would be switched around. Sorry I meant DTE, not DTR. DTR is one of the signal pins. I believe I got the assignments right for DCE but maybe not. Anyway there are only two possibilities, and it's very easy to get stuff switched around someplace, so one always has to check.
[toc] | [prev] | [next] | [standalone]
| From | Rick C <gnuarm.deletethisbit@gmail.com> |
|---|---|
| Date | 2023-03-24 18:34 -0700 |
| Message-ID | <5e4f37f7-b566-4922-bc10-da207ec3701cn@googlegroups.com> |
| In reply to | #31694 |
On Friday, March 24, 2023 at 9:19:59 PM UTC-4, Paul Rubin wrote: > Rick C <gnuarm.del...@gmail.com> writes: > > You didn't answer the question. Which pin is the data output and > > which is the data input? > The transmit pin (TXD, pin 2 in that table) is the output and the > receive pin (RXD, pin 3) is the input. Since it is a female connector, > by the standard, the box is considered data communications equipment > (DCE), rather than data terminal equipment (DTR). If it was DTR, the > two pins would be switched around. Is that what you are asking? In any > case, one always has to test to be sure. You are providing links to hardware. I'm asking you which pin is data out and which pin is data in? This is a very simple question, no? > >> https://www.digikey.com/en/products/detail/dfrobot/DFR0258/6588574 > > Are you going to make the cable required? > A splitter cable? I thought I posted a url to order those from. Do you know if that splitter will work for this application? I don't see the link. How many messages back, or how many days/weeks ago was that? You posted a lot of links in the message I replied to. > > Recycling is not a problem, as long as there is no branding on the box. > There could be a label with your own branding, strategically placed to > cover up any existing branding, if that works for you. > > Are you going to write the USB stack to run on the simple CPUs you > > have linked to? > It exists already on some of them. I wouldn't write a new one. Can't use a USB dongle if there's no USB software. > >> TTL to RS232 (?): https://www.sparkfun.com/products/449 > >> Similar: https://www.waveshare.com/wiki/RS232_Board > > I don't know why you are showing all these devices. > There are tons of cpus with built in UARTs Having a UART is not sufficient. The interface needs to be a DB9 male, RS-232 voltage levels. One connector for the input data, and one connector for the output data. > > I don't know. Why does this matter? You won't be visiting the > > customer's site. > Somebody at some point might have to do that. I hope not, but the > saying is, hope for the best and plan for the worst. That is far outside your concern. > Frankly the first thing I would try is taking one of your homebrew boxes > that is known to be failing, swapping out the homemade level shifter PCB > with one of the ones linked above, and seeing if that works. Or at > least, use a scope to check the voltages coming out of the homemade PCB. > > You seem to be thrashing around in looking at every little board that > > might or might not do the job, rather than finding one that will. > It is a two step process: 1) identify possible candidates; 2) pick one. Have you picked one yet? > Posting links to those boards is in part a demonstration that such > boards exist. I've never needed convincing that these boards exist. > > The single port boards you've identified have the DB9 connector, but > > you don't indicate how you will split this into the two connectors > > required for the job. Do you understand the requirements? > I believe so. There are premade splitter cables that separate pins 2 > and 3 from a DB9 into two more DB9's, or such a thing can be made, or > (preferable) one can use a CPU with two serial ports (or USB split into > two ports). The splitter cable can be inside the box since IIRC you > don't want it flopping around on the outside. Then the two DB9's would > be on the rear panel. Does the splitter cable run a signal to pins 2 and 3 on both cables? I've yet to find one that connects to pin 2 on one connector and pin 3 on the other connector, leaving the other pins 2 and 3 unconnected. I think you will find the splitter cable will need to be a custom design. It's probably easier to just use a CPU without a DB9 and build a cable to run from the header to the two DB9s on the box. But then you will need a CPU card with RS232 level shifters. This is why I don't want to do the design. It's messy and far too much work for something so simple. -- Rick C. --+-- Get 1,000 miles of free Supercharging --+-- Tesla referral code - https://ts.la/richard11209
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2023-03-24 19:43 -0700 |
| Message-ID | <87h6u9h7o2.fsf@nightsong.com> |
| In reply to | #31697 |
Rick C <gnuarm.deletethisbit@gmail.com> writes: > You are providing links to hardware. I'm asking you which pin is data > out and which pin is data in? This is a very simple question, no? Didn't I answer? I wrote: >> The transmit pin (TXD, pin 2 in that table) is the output and the >> receive pin (RXD, pin 3) is the input. Pin 2 = data out, pin 3 = data in. Is something missing from that answer? There is a possibility that it is wrong and that the two are switched, but that would show up immediately during testing. >> A splitter cable? I thought I posted a url to order those from. > Do you know if that splitter will work for this application? It sounded to me like it should, but part of the task is to put the stuff together and test it. Anyway I think it is better to use a board with two uarts. I checked, and the Arduino Leonardo has two, so it sounds like that is a suitable board if you want to use the Arduino approach. > Can't use a USB dongle if there's no USB software. The USB software is present in the boards that have USB host ports. >> >> TTL to RS232 (?): https://www.sparkfun.com/products/449 >> >> Similar: https://www.waveshare.com/wiki/RS232_Board >> > I don't know why you are showing all these devices. >> There are tons of cpus with built in UARTs > > Having a UART is not sufficient. The interface needs to be a DB9 > male, RS-232 voltage levels. One connector for the input data, and > one connector for the output data. Right, that is the purpose of those boards that I linked. To convert TTL levels to RS232 levels. You connect the UART to the level converter board. That is pretty much the same thing that you already did with the homemade MAX232(?) PCB, thus the idea of swapping in this other board and seeing if it works where your existing one doesn't. > That is far outside your concern. I am glad to hear this. So what happens if I ship you boxes that I've tested on my bench and that supply the right voltages as shown on a scope, but only half of them work at the customer site, like with your boards? Who is responsible? > Have you picked one yet? The Leonardo looks good to me but obviously I would want to test an evaluation unit before settling on it. > Does the splitter cable run a signal to pins 2 and 3 on both cables? > I've yet to find one that connects to pin 2 on one connector and pin 3 > on the other connector, leaving the other pins 2 and 3 unconnected. I would have to check that. However, disconnecting pin 2 or 3 can in a cable like that can be done with a wire cutter. > I think you will find the splitter cable will need to be a custom > design. It's probably easier to just use a CPU without a DB9 and > build a cable to run from the header to the two DB9s on the box. But > then you will need a CPU card with RS232 level shifters. The suggestion further up is to use that level shifter card. > This is why I don't want to do the design. It's messy and far too > much work for something so simple. Yes, that's why nobody else wanted to do it either until you mentioned a figure of $300 per box. That is enough to cover the necessary amount of derping around that always afflicts a project like this. You've done a lot more hardware stuff than I have, so I shouldn't be the one who has to explain that.
[toc] | [prev] | [next] | [standalone]
Page 4 of 8 — ← Prev page 1 2 3 [4] 5 6 7 8 Next page →
Back to top | Article view | comp.arch.embedded
csiph-web