I am reading the udevrules wiki, made note of the results but don't know what to do with that info (yet). Also read below about modifying vantage rules in /home/weewx/util/udev/rules.d/vantage.rules and modifying the info in a non-existent ultimeter.rules (do I create it based upon the vantage one? Where do I put it, same place? ) THanks for clarifying this for me---- again, I do not know what changed which broke my Pi3 / ultimeter comms. ---Phil (MP)
On Tuesday, January 2, 2018 at 11:52:49 PM UTC-6, mwall wrote: > > On Wednesday, January 3, 2018 at 12:26:28 AM UTC-5, Terry Hock wrote: >> >> The Ultimeter is connected directly to the PI USB port, however, I do >> have a USB hub for keyboard and mouse on one of the other PI USB ports. >> I have also tried three different power supplies and get the same >> results, with one being a 7 amp power supply. >> The Pi is a: Raspberry Pi 2 Model B >> I am not plugging any USB devices into the unit, I just let it run. >> > > something is not playing nice with the usb on your pi, resulting in a usb > event that renumbers/reorders the usb devices. > > you don't notice it with the acurite hardware, because the weewx acurite > driver looks for, opens, reads, then closes the acurite usb device each > time it does a read (every 18 seconds). the acurite driver finds the > acurite hardware using product/vendor codes, so usb reset will go unnoticed. > > you *do* notice it with the usb-to-serial converter, because the weewx > ultimeter driver opens the connection once then keeps it open until weewx > quits. this is because the peet bros hardware can emit data as fast as > twice per second (way faster than acurite hardware!). so when a usb reset > happens, the connection weewx had to the ultimeter goes away, weewx retries > and fails 5 times, then quits. > > as a hack, use a udev rule so that weewx will always find your ultimeter > at /dev/ultimeter. see the util/udev/rules.d/vantage.rules file and adjust > the product/vendor codes to match your FTDI adapter. see the weewx wiki > for more details: > > https://github.com/weewx/weewx/wiki/udevrules > > or better yet, fix whatever is borking your usb. look for usb-related > events in the syslog just before the first ultimeter failures (before the > log entries you posted). > > m > -- 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.
