Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-13 Thread vince 
On Sunday, December 13, 2020 at 12:46:22 AM UTC-8 kiwigander wrote:

> So it's back to /dev/ttyUSB0 via the converter, which is working as well 
> on the XCY as on the old Dell.  
>
>
There's a point in time where the value of your time exceeds the value of 
the adventure of figuring out why the serial port for your unusual os (on 
your unusual hardware) isn't as trivial as most setups.  Sounds like you 
could have bought a new computer with the time-value of battling this one.

Glad to hear the serial-to-usb adaptor worked.  Just stick with it.


-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1095eaa6-3b82-4443-90e5-d2a93818986bn%40googlegroups.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-13 Thread kiwigander 
I spoke (wrote) too soon.
Weewx *seemed* to be working on the XCY through /dev/ttyS1 after 
modemmanager was purged, but it stopped working.  It looks as if it was 
still struggling with CRC check errors.  I thought the fault might have 
been (re-)triggered by an update to some Mint system files and applications 
(although none seemed likely), but reverting to the previous configuration 
and rebooting did not help.  So it's back to /dev/ttyUSB0 via the 
converter, which is working as well on the XCY as on the old Dell.  

On Sunday, December 13, 2020 at 2:34:40 PM UTC+13 peterq...@gmail.com wrote:

> copy the database file from the old machine to the new one.
>
> On Sat, Dec 12, 2020 at 5:24 PM kiwigander  wrote:
>
>> And for the final test before giving up on the XCY mini-PC, I ran *sudo 
>> apt purge modemmanager*
>>
>> and now weewx is working through /dev/ttyS1 on the XCY mini-PC.  
>>
>> Some corollary of Murphy's Law says that if a problem is going to be 
>> solved, it will be solved by a simple manoeuvre that you ran out of time to 
>> try.
>>
>> Thank you Tom & colleagues!
>>
>> Now one more thing:
>>
>> The new server's database starts just a few minutes ago.  The old 
>> server's database goes back quite a few years.  How do I merge the previous 
>> data onto the new server?
>>
>> On Sunday, December 13, 2020 at 12:35:49 PM UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> 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  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 tke...@gmail.com 
> 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  
>> 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 tke...@gmail.com 
>>> 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  
 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 differen

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-12 Thread p q 
copy the database file from the old machine to the new one.

On Sat, Dec 12, 2020 at 5:24 PM kiwigander  wrote:

> And for the final test before giving up on the XCY mini-PC, I ran *sudo
> apt purge modemmanager*
>
> and now weewx is working through /dev/ttyS1 on the XCY mini-PC.
>
> Some corollary of Murphy's Law says that if a problem is going to be
> solved, it will be solved by a simple manoeuvre that you ran out of time to
> try.
>
> Thank you Tom & colleagues!
>
> Now one more thing:
>
> The new server's database starts just a few minutes ago.  The old server's
> database goes back quite a few years.  How do I merge the previous data
> onto the new server?
>
> On Sunday, December 13, 2020 at 12:35:49 PM UTC+13 tke...@gmail.com wrote:
>
>> 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  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 tke...@gmail.com
 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 
> 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 tke...@gmail.com
>> 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  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
>
>>>

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-12 Thread kiwigander 
And for the final test before giving up on the XCY mini-PC, I ran *sudo apt 
purge modemmanager*

and now weewx is working through /dev/ttyS1 on the XCY mini-PC.  

Some corollary of Murphy's Law says that if a problem is going to be 
solved, it will be solved by a simple manoeuvre that you ran out of time to 
try.

Thank you Tom & colleagues!

Now one more thing:

The new server's database starts just a few minutes ago.  The old server's 
database goes back quite a few years.  How do I merge the previous data 
onto the new server?

On Sunday, December 13, 2020 at 12:35:49 PM UTC+13 tke...@gmail.com wrote:

> 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  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 tke...@gmail.com 
>>> 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  
 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 tke...@gmail.com 
> 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  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 fro

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-12 Thread Tom Keffer 
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  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 tke...@gmail.com
>> 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 
>>> 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 tke...@gmail.com
 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  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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
>> 
>> .
>>
> --
 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 weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-12-12 Thread kiwigander 
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 tke...@gmail.com 
> 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  
>> 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 tke...@gmail.com 
>>> 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  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 weewx-user+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
>  
> 
> .
>
 -- 
>>> 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 weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because y

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-27 Thread kiwigander 
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 tke...@gmail.com 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  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 tke...@gmail.com 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  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 weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
  
 
 .

>>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4e8e3c23-b016-40e6-b1db-19dbcff76aa7n%40googlegroups.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-27 Thread Tom Keffer 
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  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 tke...@gmail.com 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  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 weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA5zJ6CqEhNT%2BDjP8S8h2xBGr-o2P9CvSrJycqaQzFRNg%40mail.gmail.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-27 Thread Cameron D 
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 tke...@gmail.com 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  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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/95f8e263-0d64-46de-bf3e-e6089756f45an%40googlegroups.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-27 Thread Tom Keffer 
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  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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zED0avzG%2Bjhcgxw7iaSooFYukHj85HN%3DFKAZoiHs0SYtwg%40mail.gmail.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-26 Thread kiwigander 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d7e49691-043f-4f6c-a998-dd91c3eaa34an%40googlegroups.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-26 Thread vince 


> 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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/51fd7550-4f45-4831-967b-049f72e08b93n%40googlegroups.com.

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-26 Thread kiwigander 
Thank you.  No joy with ttyS1 either (and yes, I did change the setting in 
weewx.conf!).

Still using ttyS1, I tried 

*stty sane -F /dev/ttyS1*

but it's still not working.

Restarting the daemon, then

*sudo service weewx* status yields (repeatedly, the block of messages 
doesn't alter) the following:

● weewx.service - LSB: weewx weather system
 Loaded: loaded (/etc/init.d/weewx; generated)
 Active: active (running) since Fri 2020-11-27 15:14:37 NZDT; 5s ago
   Docs: man:systemd-sysv-generator(8)
Process: 2864 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
  Tasks: 1 (limit: 9244)
 Memory: 10.0M
 CGroup: /system.slice/weewx.service
 └─2882 /usr/bin/python3 /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] DEBUG weewx.drivers.vantage: 
Retry #0 failed
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] DEBUG weewx.drivers.vantage: 
Gentle wake up of console successful
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] ERROR weewx.drivers.vantage: 
No  received from console
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #0: 'No  received from Van>
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] ERROR weewx.drivers.vantage: 
No  received from console
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #1: 'No  received from Van>
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] DEBUG weewx.drivers.vantage: 
Hardware type is 16
Nov 27 15:14:41 XCY weewxd[2882]: weewx[2882] ERROR weewx.drivers.vantage: 
No  received from console
Nov 27 15:14:42 XCY weewxd[2882]: weewx[2882] DEBUG weewx.drivers.vantage: 
Retry #0 failed
Nov 27 15:14:42 XCY weewxd[2882]: weewx[2882] DEBUG weewx.drivers.vantage: 
Rude wake up of console successful
~
~
~
lines 1-20/20 (END)

And *sudo cat /proc/tty/driver/serial *yielded a similar result to the 
previous: the tx:, rx:, fe: and brk: values incremented until

serinfo:1.0 driver revision:
0: uart:16550A port:03F8 irq:4 tx:0 rx:0 DSR|CD|RI
1: uart:16550A port:02F8 irq:3 tx:1123 rx:1654 fe:95 brk:108 DSR|CD|RI
2: uart:unknown port:03E8 irq:4
3: uart:unknown port:02E8 irq:3
4: uart:unknown port: irq:0

and then they stopped incrementing, as if the daemon gave up trying to 
connect.

I rebooted again and looked at /var/log/syslog again, *grep*-ing for weewx, 
and got (sorry for the length here):

Nov 27 15:52:22 XCY weewx[738] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 27 15:52:26 XCY weewx[738] DEBUG weewx.drivers.vantage: 
Get_data_with_crc16; try #1 failed: Expected to read 3 chars; got 0 instead
Nov 27 15:52:26 XCY weewx[738] DEBUG weewx.drivers.vantage: Timeout in 
get_data_with_crc16
Nov 27 15:52:26 XCY weewx[738] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 27 15:52:26 XCY weewx[738] ERROR weewx.drivers.vantage: No  
received from console
Nov 27 15:52:26 XCY weewx[738] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 27 15:52:26 XCY weewx[738] ERROR weewx.drivers.vantage: No  
received from console
Nov 27 15:52:26 XCY weewx[738] DEBUG weewx.drivers.vantage: Rude wake up of 
console successful
Nov 27 15:52:30 XCY weewx[738] DEBUG weewx.drivers.vantage: 
Get_data_with_crc16; try #1 failed: Expected to read 3 chars; got 0 instead
Nov 27 15:52:30 XCY weewx[738] DEBUG weewx.drivers.vantage: Timeout in 
get_data_with_crc16
Nov 27 15:52:30 XCY weewx[738] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 27 15:52:38 XCY weewx[738] DEBUG weewx.drivers.vantage: Retry #0 failed
Nov 27 15:52:38 XCY weewx[738] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 27 15:52:38 XCY weewx[738] DEBUG weewx.drivers.vantage: ISS ID is 1
Nov 27 15:52:38 XCY weewx[738] ERROR weewx.engine: Import of driver failed: 
Unknown hardware type 0 ()
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine:   Traceback 
(most recent call last):
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 109, in setupStation
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 39, in loader
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine:   return 
VantageService(engine, config_dict)
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 1898, in __init__
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Nov 27 15:52:38 XCY weewx[738] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 516, in __init__
Nov 27 15:52:38 XCY

Re: [weewx-user] Re: Can't get weewx working on a new server

2020-11-26 Thread Tom Keffer 
Lots of good information here. I wish all users were as diligent.

The results of stty show some small differences from mine. For example, you
have -iexten (the dash means negation), while I have iexten, which means
mine enables non-POSIX special characters and yours doesn't. That could
matter. Most of the others have to do with echoing characters and
translating CR/LF, etc. Some of them could also matter.

Try setting it to "sane" values. This will basically force your values to
mine.

*stty sane -F /dev/ttyS0*


Then try again. That's all I can think of.

-tk

On Thu, Nov 26, 2020 at 5:10 PM kiwigander  wrote:

> The new machine is an XCY (that's the brand; bought on AliExpress) fanless
> mini-PC, Celeron N4100 CPU, 8 GB RAM, 128 GB SSD, 2x gigabit Ethernet, 2x
> RS232, 4x USB (looks like USB 2.0).  Video is temporarily via HDMI (once
> the server is set up, that will be disconnected); internet is via Ethernet
> (unit has Wi-Fi built in but I have switched it off in Network Manager);
> Apple keyboard is plugged into a USB port and Logitech M570 trackball
> communicates through Logi Unifying Receiver plugged into Apple keyboard
> (again, once the server is set up, the keyboard will be disconnected).
>
> New OS is Linux Mint 20.  Output of uname -a is as follows:
>
> Linux XCY 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020
> x86_64 x86_64 x86_64 GNU/Linux
>
> Output of lsusb is as follows:
>
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 001 Device 003: ID 05ac:024f Apple, Inc. Keyboard Hub
> Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Output of stty -a -F /dev/ttyS0 is as follows:
>
> speed 19200 baud; rows 0; columns 0; line = 0;
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
> eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt =
> ^R;
> werase = ^W; lnext = ^V; discard = ^O; min = 0; time = 0;
> -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
> -ixoff
> -iuclc -ixany -imaxbel -iutf8
> -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
> vt0 ff0
> -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
> -echoprt
> -echoctl -echoke -flusho -extproc
>
> Output of sudo cat /proc/tty/driver/serial (truncated after line 4 as
> lines 4 through 31 are identical) is as follows:
>
> serinfo:1.0 driver revision:
> 0: uart:16550A port:03F8 irq:4 tx:610 rx:1151 fe:45 brk:33 DSR|CD|RI
> 1: uart:16550A port:02F8 irq:3 tx:0 rx:0 DSR|CD|RI
> 2: uart:unknown port:03E8 irq:4
> 3: uart:unknown port:02E8 irq:3
> 4: uart:unknown port: irq:0
>
> The output of that command is just a snapshot.  The first time I repeated
> it, the tx:, rx: and fe: values did increment (635, 1166, 46, 45) so
> something was trying to communicate through ttyS0.  Now they seem to be
> static.
>
> If human memory is correct, COM1=ttyS0=irq4 and COM2=ttyS1=irq3 since
> forever, so the serial ports don't seem to be non-standard.
>
> I've looped the serial cable through a ferrite sleeve; no difference.
>
> Output of sudo tail -f /var/log/syslog on a fresh cold boot is as follows:
>
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: 
> Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: File
> "/home/weewx/bin/weewx/drivers/vantage.py", line 515, in __init__
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: 
> self._setup()
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: File
> "/home/weewx/bin/weewx/drivers/vantage.py", line 1330, in _setup
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: 
> self.altitude  = self._getEEPROM_value(0x0F, " Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: File
> "/home/weewx/bin/weewx/drivers/vantage.py", line 1398, in _getEEPROM_value
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine:   raise
> weewx.RetriesExceeded("While getting EEPROM data value at address 0x%X" %
> offset)
> Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: 
> weewx.RetriesExceeded: While getting EEPROM data value at address 0xF
> Nov 27 11:40:52 XCY weewx[759] CRITICAL __main__: Unable to load driver:
> While getting EEPROM data value at address 0xF
> Nov 27 11:40:52 XCY weewx[759] CRITICAL __main__:   Exiting...
>
> (everything after that seems to involve the NTP daemon)
>
> Now (after a lunch break) I've run sudo service weewx status and got the
> following:
>
> Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine:
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine:
> File "/home/w