Sounds like our analysis was spot on. At least you know what the problem is now!
On Sat, Dec 12, 2020 at 2:55 PM kiwigander <[email protected]> wrote: > Progress report: > I've got a Unitek BF-810Y USB<=>RS232 converter. Plugged it in to the old > Dell; it was recognised as a pl2303 converter on ttyUSB0. Changed the > relevant line in weewx.conf, restarted the daemon and we're in business. > I'll have a last go at the RS232 ports on the XCY mini PC but I'm not > optimistic about that unit. > > On Saturday, November 28, 2020 at 1:23:28 PM UTC+13 kiwigander wrote: > >> Thanks again for the advice and suggestions. >> >> I've used *stty* to see how the ever-reliable RS232 port is configured >> on the old server and will try setting the new one to mimic it. >> >> I'll try purging modemmanager from the new server. >> >> Assuming, though, that the problem is defective hardware, the new server >> ought to be returnable but I'd have to send it back to the PRC. I wonder >> whether the serial comms module is replaceable -- that might be more >> cost-effective than sending the unit back. I'll try a USB<=>RS232 >> converter anyway. >> >> I'll be offline for a couple of weeks but will report back. >> >> On Saturday, November 28, 2020 at 3:02:00 AM UTC+13 [email protected] >> wrote: >> >>> Good point. I've had problems with modemmanager doing this. >>> >>> >>> *sudo apt purge modemmanager* >>> >>> >>> >>> On Fri, Nov 27, 2020 at 5:57 AM Cameron D <[email protected]> >>> wrote: >>> >>>> Have you checked that there is not any form of getty running on the >>>> port - they wait for logins and will steal some of the input characters. >>>> >>>> That's rather old school - I don't know how systemd does it. >>>> >>>> >>>> On Friday, 27 November 2020 at 11:00:27 pm UTC+10 [email protected] >>>> wrote: >>>> >>>>> I think we can say with some confidence that there is something wrong >>>>> with the UART chip on your new computer. Can you take it back? >>>>> >>>>> Alternatively, as Vince says, a serial-to-usb converter. They seem to >>>>> be more reliable these days. >>>>> >>>>> -tk >>>>> >>>>> On Thu, Nov 26, 2020 at 8:47 PM kiwigander <[email protected]> wrote: >>>>> >>>>>> Ta. The prevalent RS232<=>USB chipset around these parts seems to be >>>>>> an FTDI. I'll look around. >>>>>> >>>>>> On Friday, November 27, 2020 at 4:19:32 PM UTC+13 vince wrote: >>>>>> >>>>>>> I was hoping to avoid USB<=>RS232 converters, as I understood they >>>>>>>> were problematic (in the past) and would add another >>>>>>>> thing-to-go-wrong. I >>>>>>>> have one other old device to monitor and it too has only an RS232 >>>>>>>> interface. Thought I'd be clever and get a low power box with two >>>>>>>> RS232 >>>>>>>> ports. >>>>>>>> >>>>>>> >>>>>>> FWIW, i've been running a VP2 with serial datalogger and a >>>>>>> serial2usb dongle for something like 10 years now. I started with a >>>>>>> Shuttle mini-pc that had serial ports and switched to a little arm box >>>>>>> that >>>>>>> just has USB. Never had an issue with the serial2usb from day one. >>>>>>> Works >>>>>>> great. >>>>>>> >>>>>>> You basically just want to make sure you get the right chipset in >>>>>>> the adaptor. Anything with the PL2303 definitely works. Both mine have >>>>>>> that chipset, and they were picked up years apart from different >>>>>>> suppliers, >>>>>>> so they used to be pretty much what you always got. I haven't looked in >>>>>>> years to know if that's still the case. >>>>>>> >>>>>>> I'm running on a Seagate Dockstar (a 128MB RAM version of the >>>>>>> original PogoPlug) with a Seagate laptop drive plugged in, and you can >>>>>>> see >>>>>>> the serial adaptor available in the lsusb output below. >>>>>>> >>>>>>> root@debian:~# lsusb >>>>>>> Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port >>>>>>> HUB >>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>>>> Bus 001 Device 003: ID 0bc2:2120 Seagate RSS LLC >>>>>>> Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 >>>>>>> Serial Port >>>>>>> >>>>>>> >>>>>> -- >>>>>> >>>>> You received this message because you are subscribed to the Google >>>>>> Groups "weewx-user" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "weewx-user" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/f1192f7e-f6f8-4221-bc5f-79da5a697868n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/f1192f7e-f6f8-4221-bc5f-79da5a697868n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBAHKQ8YCVeM6E-5rhpt7MXp0fOL4uaqqk8bFFf%2B_XTWg%40mail.gmail.com.
