[weewx-user] Re: Acurite 01536 (Costco) pressure sensor
Note from the datasheet that it measures both pressure and temperature, and has correction constants built in, but correction must be applied externally. On Sunday, January 22, 2017 at 10:55:11 PM UTC-8, David Morgan wrote: > > I have been able to photograph and read the sensor in my unit. Here is a > photo. The black IC next to it has a different part of a photo pasted over > it so you can see the chip labeling. > > This may be the proper design PDF for the sensor: > http://www.mouser.com/ds/2/418/MS5637-02BA03-768293.pdf > > > > http://www.mouser.com/ProductDetail/Measurement-Specialties/MS563702BA03-50/?qs=ZSTLft15nNCFYZwlCm%2FnTA%3D%3D > > > -- 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.
[weewx-user] Acurite 01536 (Costco) pressure sensor
I have been able to photograph and read the sensor in my unit. Here is a photo. The black IC next to it has a different part of a photo pasted over it so you can see the chip labeling. This may be the proper design PDF for the sensor: http://www.mouser.com/ds/2/418/MS5637-02BA03-768293.pdf http://www.mouser.com/ProductDetail/Measurement-Specialties/MS563702BA03-50/?qs=ZSTLft15nNCFYZwlCm%2FnTA%3D%3D -- 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.
[weewx-user] Re: Acurite 01536 (Costco)
On Wednesday, January 18, 2017 at 4:24:16 PM UTC-8, David Morgan wrote: > > >> I also got a Costco Acurite 01536-RX for Christmas. > . I am curious if anyone knows yet what sensors are used. I have > resisted peeking so far, but that may change. > I have been looking I photos I took of the main board. I now see that it uses a 24C512 EEPROM. Right next to it appears to be the barometric pressure sensor. Photo is not good enough to read the part number. Also, I believe the humidity and temp sensors are on long leads, and stick out to where they are close to the air opening in the upper left side of the unit as you look at it from the front. -- 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.
[weewx-user] Re: Acurite 01536 (Costco)
On Wednesday, January 18, 2017 at 4:24:16 PM UTC-8, David Morgan wrote:
>
>
>>
> The barometric pressure is way wrong on the console, and there is some
> disagreement between the console and the WeeWx display. I am curious if
> anyone knows yet what sensors are used. I have resisted peeking so far,
> but that may change.
>
I did take the console apart last night to see what parts were used. I
found the ICs were covered over with a hard black coating so you cannot
identify what is there. I did not find anything that looked like pressure
sensor. I did find what is probably the temp sensor.
I am finding that with my laptop, connecting to the console is not
consistent. Once connected, it seems to do OK. I am not a programmer, so
understanding the python code is not so easy for me. Makes it hard to
understand just where things are not working. Wireshark is showing the
system is having trouble initiating the transfer of data from the console
to the host, even though it has already read the initialization data from
the console. Below is a dump from wireshark.
Frame 595, the host issues a USB SET INTERFACE Request
Frame 596, the console responds, USB SET INTERFACE Response :: URB
status: Protocol error (-EPROTO) (-71)
Frame 597, the host issues a USBHID GET_REPORT Request
Frame 598, the console responds, USBHID GET_REPORT Response :: URB
status: Success (0) Console responded with 10 data bytes.
All following messages were successful. So why did it just start working?
And why was the data request successful when the set interface request
failed? Is it not necessary for the USB interface to be set before a
USBHID request? Who sent the USB request? Was it Python or the linux
kernel? These are things I have not figured out.
595 690.183528 host 5.14.0USB
64 SET INTERFACE Request
Frame 595: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on
interface 0
USB URB
[Source: host]
[Destination: 5.14.0]
URB id: 0x88011c951300
*URB type: URB_SUBMIT ('S')*
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x00, Direction: OUT
Device: 14
URB bus id: 5
Device setup request: relevant (0)
Data: present (0)
URB sec: 1484814928
URB usec: 977890
URB status: Operation now in progress (-EINPROGRESS) (-115)
URB length [bytes]: 0
Data length [bytes]: 0
[Response in: 596]
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x
Number of ISO descriptors: 0
URB setup
00 13 95 1c 01 88 ff ff *53* 02 00 0e 05 00 00 00 *S*...
Submit
0010 50 7a 80 58 00 00 00 00 e2 eb 0e 00 8d ff ff ff Pz.X
0020 00 00 00 00 00 00 00 00 01 0b 00 00 00 00 00 00
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
596 690.187517 5.14.0host USB
64 SET INTERFACE Response
Frame 596: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on
interface 0
USB URB
* [Source: 5.14.0]*
*[Destination: host]*
URB id: 0x88011c951300
URB type: URB_COMPLETE ('C')
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x00, Direction: OUT
Device: 14
URB bus id: 5
Device setup request: not relevant ('-')
Data: not present ('>')
URB sec: 1484814928
URB usec: 981879
* URB status: Protocol error (-EPROTO) (-71)*
URB length [bytes]: 0
Data length [bytes]: 0
[Request in: 595]
[*Time from request: 0.003989000 seconds*]
Unused Setup Header
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x
Number of ISO descriptors: 0
00 13 95 1c 01 88 ff ff 43 02 00 *0e 05 00* 2d 3e C.->
From 14 05, the console bus address
0010 50 7a 80 58 00 00 00 00 77 fb 0e 00 *b9 ff ff ff* Pz.Xw...
Bold means protocol error
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
597 690.187738 host 5.14.0USBHID
64 GET_REPORT Request
Frame 597: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on
interface 0
USB URB
*[Source: host]*
*[Destination: 5.14.0]*
URB id: 0x88011c951300
*URB type: URB_SUBMIT ('S')*
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x80, Direction: IN
Device: 14
URB bus id: 5
Device setup request: relevant (0)
Data: not present ('<')
URB sec: 1484814928
URB usec: 982100
URB status: Operation now in progress (-EINPROGRESS) (-115)
URB length [bytes]: 10
Data length [bytes]: 0
[Response in: 598]
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x0200
Num
[weewx-user] Re: Acurite 01536 (Costco)
> > > I also got a Costco Acurite 01536-RX for Christmas. Delayed a couple of weeks in setting it up. I tried weewx first on my Toshiba L355, not successful. But I was not successful at first, probably my error. I think I tried installing with the deb package and from the Mint repository both. I did get to the input screen a couple of times, was not sure what to use for the model number as it is not listed as supported. Decided to try it on my wifes laptop, a Lenovo, running Mint 17.x or 18. It worked just fine. Came back to my computer, finally got it running. Don't know why, it seems to have a hard time getting started. I plan to do more looking at that. I modified acurite.py a little for debugging. After getting it running, I found I can use Wireshark to look at the serial interface (after enabling a kernel module), would have been nice to know that earlier. The barometric pressure is way wrong on the console, and there is some disagreement between the console and the WeeWx display. I am curious if anyone knows yet what sensors are used. I have resisted peeking so far, but that may change. I will admit to being older, and getting confused about what I entered where in getting this going. But it has been fun, and interesting poking through the Python code to add a couple of debugging outputs to the log file. -- 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.
