I would suggest to use something more lightweight than a RaspberryPi, 
something like an ESP8266, if it is just for collecting the data and 
transfer it to a place you can handle it.
Oscar Barlow schrieb am Mittwoch, 10. Februar 2021 um 18:44:50 UTC+1:

> A simpler approach.  Thanks!
>
> On Tuesday, February 9, 2021 at 2:53:28 PM UTC-7 Andy wrote:
>
>> Just add a field in the database and adapt this persons code to put your 
>> well reading in the db
>>
>> https://gitlab.com/wjcarpenter/bme280wx/-/blob/master/bin/user/bme280wx.py
>>
>> On Tuesday, February 9, 2021 at 10:32:17 AM UTC-8 Oscar Barlow wrote:
>>
>>> I am about to purchase an Eno Scientific Well Watch 760. It has an RS232 
>>> and USB interface and I thought about using weewx to collect that data, 
>>> store it in a data base and produce charts. I would have a pi 3 mounted in 
>>> existing metal electrical cabinet by the well head. It would be connected 
>>> to the device and use WiFi to connect to network.
>>>
>>>
>>> There isn’t a lot of data to store. Time stamp and water level. The 
>>> unit’s current settings could be stored with the record. The big issue I 
>>> see is that the log interval could change. I may want to log every minute 
>>> from 7AM to 10PM and once an hour during off hours. 
>>>
>>>
>>> A couple of questions. 
>>>
>>> 1. Am I nuts? Yes is an acceptable answer. I may be trying to plow a 
>>> field with a sports car.
>>>
>>> 2. I’d need to write a driver and a service. Anything else?
>>>
>>> 3. Suggestions or a different another approach?
>>>
>>>
>>> Sill in the design phase. Waiting to confirm with my well guy he can 
>>> install the 760 and electrical for my pi.
>>>
>>>
>>> Thanks,
>>>
>>> Oscar
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/29d5edae-42e4-4829-9b02-8ad88b6cf821n%40googlegroups.com.

Reply via email to