You would test it the same way as if you configured using /dev/ttyUSB0 for
example.
You just use /dev/weather instead of /dev/ttyUSB0.
There is nothing special about it really. I just use this method as I have
several usb devices on my server and I name them to reflect the application
I am
What is a good way to test the symlink rule to verify that it was created
correctly? There is the new file in /dev/weather but is there a more
complete way to test? thank you
On Tuesday, November 17, 2020 at 7:29:08 PM UTC-6 Greg from Oz wrote:
> I set my fineoffset rule to:
>
>
I set my fineoffset rule to:
SUBSYSTEM=="usb", ATTRS{idVendor}=="1941", ATTRS{idProduct}=="8021",
MODE="0666", GROUP="plugdev", SYMLINK+="weather"
That way it is always /dev/weather regardless of the ttyUsb it is attached
to.
ll /dev/weather
lrwxrwxrwx 1 root root 15 Nov 17 09:26
Are you sure? Depending on what permissions the usb port has, you may need
to use sudo to run lsof:
*sudo lsof /dev/ttyUSB0*
Come to think of it, you may have to do that with minicom, too.
Personally, I change the udev rule that governs permissions for usb devices
to give everyone access to the
Thanks everyone, I think I have a bad logger (6540).
On Tuesday, November 17, 2020 at 9:41:56 AM UTC-5 bgra...@umw.edu wrote:
> root@raspberrypi:/home/pi# ll /dev/ttyUSB0
> crw-rw 1 root dialout 188, 0 Nov 16 17:48 /dev/ttyUSB0
>
>
> root@raspberrypi:/home/pi# lsof /dev/ttyUSB0
> lsof:
root@raspberrypi:/home/pi# ll /dev/ttyUSB0
crw-rw 1 root dialout 188, 0 Nov 16 17:48 /dev/ttyUSB0
root@raspberrypi:/home/pi# lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
On Monday, November 16, 2020
If it were a permissions problem, it would have said so. Same if
modemmanager controlled the port. Still, it doesn't hurt to try lsof and
see if anything else is using the port.
*lsof /dev/ttyUSB0*
On Mon, Nov 16, 2020 at 5:36 PM Greg from Oz wrote:
> Is the user running this in the dialout
Is the user running this in the dialout group?
On Tuesday, 17 November 2020 at 12:30:14 UTC+11 tke...@gmail.com wrote:
> The only thing I can think of to try is to reseat the logger.
>
> Unless, you actually have the serial version of the VantagePro and are
> using a serial-to-usb converter.
The only thing I can think of to try is to reseat the logger.
Unless, you actually have the serial version of the VantagePro and are
using a serial-to-usb converter. They are notoriously flakey. If you have a
spare one, try that.
If none of that works, call Davis.
On Mon, Nov 16, 2020 at 5:04
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
OK, but did you hit 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 wrote:
>
> I don’t remember the minicom string but it was the one posted to test
> TEST.
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.
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 a few
types before trying to type TEST?
-tk
On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu wrote:
> I have a VP2 console that I am
from the log:
the USB/serial adapter seems okay and provides a port.
weewx has opened the port, written some data out, but received no data on read.
is the vp2 connected to the USB/serial adapter? (my DB9 plug sometimes comes
adrift so i screwed it in…)
> On 17 Nov 2020, at 9:55 am,
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
15 matches
Mail list logo
