Have you checked the wiki?
https://github.com/weewx/weewx/wiki/udevrules

also
https://github.com/weewx/weewx/wiki/Raspberry-Pi

weewx wiki is a mine of useful information!!



On Wednesday, 3 January 2018 07:26:28 UTC+2, 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.
>
> Here is some more syslog info:
> raspberrypi kernel: [92708.882124] ftdi_sio ttyUSB0: error from 
> flowcontrol urb
> raspberrypi kernel: [92708.882524] ftdi_sio ttyUSB0: FTDI USB Serial 
> Device converter now disconnected from ttyUSB0
>
> and
> raspberrypi weewx[471]: ultimeter: Failed attempt 4 of 5 to get readings: 
> device reports readiness to read but returned no data (device disconnected 
> or multiple access on port?)
> raspberrypi weewx[471]: ultimeter: Failed attempt 5 of 5 to get readings: 
> device reports readiness to read but returned no data (device disconnected 
> or multiple access on port?)
> raspberrypi kernel: [92723.109936] hid-generic 0003:24C0:0003.0006: 
> timeout initializing reports
> raspberrypi kernel: [92723.110373] input: Chaney Instrument as 
> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:24C0:0003.0006/input/input9
> raspberrypi kernel: [92723.110902] hid-generic 0003:24C0:0003.0006: 
> input,hidraw3: USB HID v1.11 Device [Chaney Instrument] on 
> usb-3f980000.usb-1.5/input0
> raspberrypi mtp-probe: checking bus 1, device 16: 
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
> raspberrypi mtp-probe: bus: 1, device: 16 was not an MTP device
> raspberrypi systemd-udevd[8509]: Process '/usr/sbin/th-cmd --socket 
> /var/run/thd.socket --passfd --udev' failed with exit code 1.
> raspberrypi weewx[471]: ultimeter: Max retries (5) exceeded for readings
> raspberrypi weewx[471]: engine: Shutting down StdReport thread
> raspberrypi weewx[471]: engine: Caught WeeWxIOError: Max retries (5) 
> exceeded for readings
> raspberrypi weewx[471]:     ****  Waiting 60 seconds then retrying...
> raspberrypi dhcpcd[543]: enxb827ebaba863: no IPv6 Routers available
> raspberrypi weewx[471]: engine: retrying...
> raspberrypi weewx[471]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> raspberrypi weewx[471]: engine: Loading station type Ultimeter 
> (weewx.drivers.ultimeter)
> raspberrypi weewx[471]: ultimeter: driver version is 0.18
> raspberrypi weewx[471]: ultimeter: using serial port /dev/ttyUSB0
> raspberrypi weewx[471]: import of driver failed: [Errno 2] could not open 
> port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' 
> (<class 'serial.serialutil.SerialException'>)
> raspberrypi weewx[471]: engine: Unable to load driver: [Errno 2] could not 
> open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'
> raspberrypi weewx[471]:     ****  Exiting...
>
> Can you provide more details for your suggestion of using udev rule, 
> thanks.
> On Tuesday, January 2, 2018 at 9:20:52 PM UTC-7, mwall wrote:
>>
>> On Tuesday, January 2, 2018 at 10:33:25 PM UTC-5, Terry Hock wrote:
>>>
>>> Hi,
>>>    I am trying to get the Peet Brothers Ultimeter 2100 working 
>>> *reliably*. The issues appears to be the serial-USB converter. The 
>>> system can run flawless for hours or at other times no more than 10 minutes 
>>> and then weewx stops updating. I have previously used an Accurite weather 
>>> station with no issues, so I am only changing the driver by using 
>>> wee_config.
>>>
>>
>> hi terry,
>>
>> it would help to see more of the log, in particular the messages that 
>> lead up to that 'no such file or directory' message.
>>
>> is the ultimeter connected directly to the pi, or via a hub?
>>
>> what kind of rpi is it?
>>
>> are you plugging/unplugging things into the rpi while the ultimeter is 
>> connected?
>>
>> whenever there is a usb reset, the usb-to-serial device may change, e.g., 
>> from /dev/ttyUSB0 to /dev/ttyUSB1.  it depends on what else is connected to 
>> the usb, and it depends on how flaky the usb hub is.  the usb 'hub' built 
>> in to first-generation rpi is not as reliable as rpi2 or rpi3.  the usb on 
>> all rpi is sensitive to the type of power supply you use to power the pi.
>>
>> next time you see that error message, do 'ls /dev/ttyUS*'.
>>
>> if this is, in fact, what i happening on your system, you can work around 
>> it by using a udev rule to change the device name to /dev/ultimeter, for 
>> example.  that will not fix the problem, but weewx will be able to recover 
>> without your intervention.
>>
>> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to