Groups > sci.electronics.design > #454286

Re: ACbrrr monitoring

From	Don Y <blockedofcourse@foo.invalid>
Newsgroups	sci.electronics.design
Subject	Re: ACbrrr monitoring
Date	2017-03-30 15:02 -0700
Organization	A noiseless patient Spider
Message-ID	<objv4u$i9c$1@dont-email.me> (permalink)
References	<objtac$dmj$1@dont-email.me> <d1bf7f85-d09c-475c-b08a-5b8f39b3309e@googlegroups.com>

Show all headers | View raw

On 3/30/2017 2:49 PM, Lasse Langwadt Christensen wrote:
> Den torsdag den 30. marts 2017 kl. 23.31.47 UTC+2 skrev Don Y:
>> What can I learn (in absolute and relative terms) from monitoring
>> the temperature and pressure in high and low side coolant lines
>> to the ACbrr's evaporator coil?
>>
>> E.g., obviously, they can tell me of compressor failures/losses
>> in the extreme case.  And, for "constant" environmental conditions
>> can give me an idea as to how the system is degrading, over time.
>>
>> But, is there anything beyond a "check engine light" that
>> could be gleaned from that instrumentation?
>
> you can draw the PH diagram and get all sorts of info
>
> https://www.ohio.edu/mechanical/thermo/Intro/Chapt.1_6/Chapter4c.html

Thanks, I'll dig through that.

> somewhere I have a program I made for a guy that does refrigration systems
> that could plot the cycle on a PH diagram for various refrigerants in realtime given the pressures and temperatures

But how would the user -- or, an AI acting on his behalf -- interpret
this information to provide "meaningful" information to the user:
- "Your compressor is about to fail"
- "Your refrigerant is low"
- "You are expecting more performance from your system than it can deliver"
- "Clean your evaporator/condenser coils"
etc.

Thread

ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-30 14:31 -0700
  Re: ACbrrr monitoring Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-03-30 14:49 -0700
    Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-30 15:02 -0700
      Re: ACbrrr monitoring Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-03-30 15:16 -0700
        Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-30 15:45 -0700
  Re: ACbrrr monitoring Neon John <no@never.com> - 2017-03-31 18:08 -0400
    Re: ACbrrr monitoring Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-03-31 15:33 -0700
      Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-31 15:53 -0700
        Re: ACbrrr monitoring Neon John <no@never.com> - 2017-03-31 20:36 -0400
          Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-31 19:22 -0700
            Re: ACbrrr monitoring Neon John <no@never.com> - 2017-04-01 12:18 -0400
              Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-04-01 11:17 -0700
                Re: ACbrrr monitoring Neon John <no@never.com> - 2017-04-02 12:26 -0400
                Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-04-02 14:42 -0700
    Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-31 16:06 -0700
      Re: ACbrrr monitoring Neon John <no@never.com> - 2017-03-31 20:53 -0400
        Re: ACbrrr monitoring Don Y <blockedofcourse@foo.invalid> - 2017-03-31 19:38 -0700
          Re: ACbrrr monitoring krw@notreal.com - 2017-03-31 23:11 -0400

csiph-web