For those following on from me.....the two power packs - 1 feeding the Rpi 
3 and the other feeding the USB hub has made a tremendous difference.....no 
problems shown in the log, no time problems, no voltage problems....it just 
flows and operates really well. I wish I had known this from the start it 
would have saved me so much grief!

On Tuesday, 29 January 2019 15:27:46 UTC+13, monmul wrote:
>
> Yes it was, apologies to those I doubted!
>
> On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote:
>>
>> Congratulations! Looks like it was a power supply problem.
>>
>> USB power supplies fail. I had one that would show +5V under no load, but 
>> it would sag to near nothing with just a modest load.
>>
>> On Mon, Jan 28, 2019 at 5:26 PM monmul <[email protected]> wrote:
>>
>>> It is working again!.....This time I used both official power 
>>> units...one to power the Pi and one to power the hub.....
>>>
>>> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:
>>>>
>>>> Then you definitely have a connectivity problem!
>>>>
>>>> -tk
>>>>
>>>> On Mon, Jan 28, 2019 at 4:32 PM monmul <[email protected]> wrote:
>>>>
>>>>> Welcome to minicom 2.7
>>>>>
>>>>> OPTIONS: I18n 
>>>>> Compiled on Apr 22 2017, 09:14:19.
>>>>> Port /dev/ttyUSB0, 13:15:39
>>>>>
>>>>> Press CTRL-A Z for help on special keys
>>>>>
>>>>> Even after lots or <enter>s nothing happens on TEST
>>>>>
>>>>> Similarly for screen.......
>>>>>
>>>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>>>>>>
>>>>>> The "establishing connectivity" instructions don't mention it, but be 
>>>>>> sure to hit <enter> a few times before typing TEST.
>>>>>>
>>>>>> On Mon, Jan 28, 2019 at 4:11 PM monmul <[email protected]> wrote:
>>>>>>
>>>>>>> Tried both screen and minicom.....no TEST echo back....so must be 
>>>>>>> hardware....but totally flummoxed as all hardware (apart from Rpi) has 
>>>>>>> been 
>>>>>>> replaced.....have another pi on order....but in the meantime I guess I 
>>>>>>> will 
>>>>>>> go back to scratch and start all over again....at least it has worked 
>>>>>>> before with this set up....maybe something has become corrupted!
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>>>>>>>>
>>>>>>>> Try to communicate directly with the Envoy, without going through 
>>>>>>>> WeeWX. For how to do this, see the section *Establishing 
>>>>>>>> connectivity 
>>>>>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in 
>>>>>>>> the User's Guide. If you are unable to do that, then this is 
>>>>>>>> definitely a 
>>>>>>>> hardware problem.
>>>>>>>>
>>>>>>>> -tk
>>>>>>>>
>>>>>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin <[email protected]> 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks, but no I don't ....I use VNC.
>>>>>>>>>
>>>>>>>>> On Tue, Jan 29, 2019 at 11:35 AM <[email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in 
>>>>>>>>>> touch screen) attached that is running off the same power supply as 
>>>>>>>>>> the Pi? 
>>>>>>>>>> I had a setup like that which used a splitter to power both the 
>>>>>>>>>> monitor and 
>>>>>>>>>> Pi from one power pack. My setup kept complaining of undervolting 
>>>>>>>>>> until I 
>>>>>>>>>> removed the splitter and plugged the monitor and pi each into their 
>>>>>>>>>> own 
>>>>>>>>>> power supply.
>>>>>>>>>>
>>>>>>>>>> phil
>>>>>>>>>>
>>>>>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>>>>>>>>>>
>>>>>>>>>>> I have replaced the power unit, taken it off the power strip an 
>>>>>>>>>>> plugged both it and the Vanatage into the mains. I have replaced 
>>>>>>>>>>> the 
>>>>>>>>>>> powered hub (official RPi one...with another official RPi one) 
>>>>>>>>>>> ...and here 
>>>>>>>>>>> is what I am getting.......very dispirited! I have another Davis 
>>>>>>>>>>> Weather 
>>>>>>>>>>> Envoy which I will soon substitute for the one I am currently 
>>>>>>>>>>> using.....but 
>>>>>>>>>>> nothing seems to make a difference and the Envoy just will not wake 
>>>>>>>>>>> up!
>>>>>>>>>>>
>>>>>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>>>>>>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
>>>>>>>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>>>>>>>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: 
>>>>>>>>>>> SPrintConnMgr: Failed to add printer: 
>>>>>>>>>>> server-error-service-unavailable
>>>>>>>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
>>>>>>>>>>> available
>>>>>>>>>>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake 
>>>>>>>>>>> up console
>>>>>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
>>>>>>>>>>> Unable to wake up Vantage console (<class 'weewx.WakeupError'>)
>>>>>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
>>>>>>>>>>> driver: Unable to wake up Vantage console
>>>>>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]:     ****  Exiting...
>>>>>>>>>>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.239.8.22
>>>>>>>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 202.46.185.18
>>>>>>>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 203.99.128.48
>>>>>>>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.106.66.123
>>>>>>>>>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.242.68.69
>>>>>>>>>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.106.65.219
>>>>>>>>>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.242.70.5
>>>>>>>>>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 122.252.188.99
>>>>>>>>>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 130.217.226.51
>>>>>>>>>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 103.242.68.68
>>>>>>>>>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 203.99.128.34
>>>>>>>>>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 202.46.177.18
>>>>>>>>>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 2407:f100:0:4::3
>>>>>>>>>>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server 
>>>>>>>>>>> 202.46.178.18
>>>>>>>>>>> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
>>>>>>>>>>> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
>>>>>>>>>>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 
>>>>>>>>>>> 9h 28min 39.184756s random time.
>>>>>>>>>>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: 
>>>>>>>>>>> Adding 27min 17.961005s random time.
>>>>>>>>>>> Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && 
>>>>>>>>>>> run-parts --report /etc/cron.hourly)
>>>>>>>>>>> Jan 29 09:22:29 raspberrypi kernel: [  368.155297] 
>>>>>>>>>>> rpi_firmware_get_throttled: 2 callbacks suppressed
>>>>>>>>>>> Jan 29 09:22:29 raspberrypi kernel: [  368.155304] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:22:33 raspberrypi kernel: [  372.315315] 
>>>>>>>>>>> rpi_firmware_get_throttled: 2 callbacks suppressed
>>>>>>>>>>> Jan 29 09:22:33 raspberrypi kernel: [  372.315322] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:24:27 raspberrypi kernel: [  486.716533] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:24:34 raspberrypi kernel: [  492.956607] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:26:28 raspberrypi kernel: [  607.357755] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:26:32 raspberrypi kernel: [  611.517793] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:26:45 raspberrypi ntpd[467]: 203.99.128.34 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:30:13 raspberrypi ntpd[467]: 103.239.8.22 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:30:45 raspberrypi ntpd[467]: 203.99.128.48 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:31:18 raspberrypi ntpd[467]: 122.252.188.99 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:31:23 raspberrypi systemd[1]: Starting Cleanup of 
>>>>>>>>>>> Temporary Directories...
>>>>>>>>>>> Jan 29 09:31:23 raspberrypi systemd[1]: Started Cleanup of 
>>>>>>>>>>> Temporary Directories.
>>>>>>>>>>> Jan 29 09:32:22 raspberrypi ntpd[467]: 130.217.226.51 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:32:59 raspberrypi kernel: [  998.401865] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:33:03 raspberrypi kernel: [ 1002.561870] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:33:05 raspberrypi kernel: [ 1004.643095] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:33:12 raspberrypi kernel: [ 1010.882010] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:33:22 raspberrypi kernel: [ 1021.282184] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:33:34 raspberrypi kernel: [ 1033.762240] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:34:42 raspberrypi ntpd[467]: 103.106.66.123 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:35:16 raspberrypi ntpd[467]: 103.106.65.219 local addr 
>>>>>>>>>>> 10.1.1.7 -> <null>
>>>>>>>>>>> Jan 29 09:38:17 raspberrypi kernel: [ 1316.645409] 
>>>>>>>>>>> rpi_firmware_get_throttled: 12 callbacks suppressed
>>>>>>>>>>> Jan 29 09:38:17 raspberrypi kernel: [ 1316.645416] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:38:26 raspberrypi kernel: [ 1324.965452] 
>>>>>>>>>>> rpi_firmware_get_throttled: 12 callbacks suppressed
>>>>>>>>>>> Jan 29 09:38:26 raspberrypi kernel: [ 1324.965457] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:38:28 raspberrypi kernel: [ 1327.045547] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:38:32 raspberrypi kernel: [ 1331.205544] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>> Jan 29 09:38:36 raspberrypi kernel: [ 1335.365722] Under-voltage 
>>>>>>>>>>> detected! (0x00050005)
>>>>>>>>>>> Jan 29 09:38:55 raspberrypi kernel: [ 1354.085857] Voltage 
>>>>>>>>>>> normalised (0x00000000)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tuesday, 29 January 2019 08:51:01 UTC+13, vince wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> On Monday, January 28, 2019 at 11:34:08 AM UTC-8, monmul wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I do have a spare official power supply, so I will swap out 
>>>>>>>>>>>>> that and test. ... I have a Pi3B+ on the way
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Reminder, the pi3b+ need 'more' power and runs a little hotter 
>>>>>>>>>>>> than the others, so definitely be certain you have a quality power 
>>>>>>>>>>>> supply.
>>>>>>>>>>>>
>>>>>>>>>>>> I have had great luck with 
>>>>>>>>>>>> https://www.amazon.com/CanaKit-Raspberry-Power-Supply-Listed/dp/B07BC6WH7V
>>>>>>>>>>>>  
>>>>>>>>>>>> just as one example.  Also like the nice on/off switch dongle that 
>>>>>>>>>>>> came 
>>>>>>>>>>>> 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 [email protected].
>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>>> 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].
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>> -- 
>>>>>>> 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].
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>> -- 
>>>>> 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].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> -- 
>>> 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].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to