Yes, I did hit enter many times. Since dmesg said that the usb had attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had connected. I’m at a loss because everything was working... Thanks.
On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com wrote: > OK, but did you hit <enter> a few times before typing "TEST"? If so, you > have a connectivity problem, not a WeeWX problem. > > But, you probably already knew that! > > -tk > > On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu <bgra...@umw.edu> wrote: > >> >> I don’t remember the minicom string but it was the one posted to test >> TEST. When I opened minicom it just sat there no echo on TEST or VER. No >> reply. Several reboots no results. /dev/ttyUSB0 is there but does not >> respond. Dmesg Seems to have found it. >> I checked all plugs and connections. Removed batteries from console to >> reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc >> running from the ISS so I know that’s working and sending data. The rpi is >> setup as a second console which was running weather34. Thanks Tom and >> Graham (you helped me in the days of wview). >> Bob >> Main setup: grattans.org/wx >> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com wrote: >> >>> When you say you "tried listening to the console with minicom but got >>> no data" what do you mean? >>> >>> In particular, did you set the baudrate? And, did you type <enter> a few >>> types before trying to type TEST? >>> >>> -tk >>> >>> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu <bgra...@umw.edu> wrote: >>> >>>> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx >>>> is latest using setup.py. This RPI was running weewx (jessie) with no >>>> problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok >>>> and >>>> I actually moved the old one over to be sure. >>>> I tried listening to the console with minicom but got no data. I >>>> swapped out the RS232/USB converter but got the same problem. Not sure >>>> what I have done wrong, other than trying to fix something that wasn't >>>> broken... >>>> >>>> Attached file of some debug info. >>>> >>>> Thanks for any suggestions. >>>> >>>> Bob >>>> >>>> -- >>>> >>> 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/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%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 weewx-user+...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8afb9f09-184c-4244-ab5a-1590174ab7c0n%40googlegroups.com.
