Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.electronics.design > #454503

Re: ACbrrr monitoring

Show all headers | View raw

On 3/31/2017 3:33 PM, Lasse Langwadt Christensen wrote:
> Den lørdag den 1. april 2017 kl. 00.08.19 UTC+2 skrev Neon John:
>> On Thu, 30 Mar 2017 14:31:35 -0700, Don Y
>> <blockedofcourse@foo.invalid> wrote:
>>
>> As an engineer who has operated an industrial/commercial refrigeration
>> business on the side for most of his career,  I'll take a shot.
>>
>>> 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?
>>
>> I have no idea what "ACbrrr" is but I'll guess that you're speaking of
>> the HVAC on a modern car.
>
> I believe Don is talking about HVAC for a house

Exactly.  There are heating related issues, as well -- but I think
I've got them covered (i.e., if intake temperature and output temperature
are the same, you're not getting any heat!  Is blower turning?  Is the
blower *motor* consuming power?  Is natural gas flowing?  etc.)

Here, what tends to happen is folks turn on their ACbrrr in preparation for
the cooling season (which typically begins in April; February, *this* year)
and "discover" that it doesn't work.  That discovery usually comes in the
form of "its not cooling"; rarely in terms of "the compressor isn't running".

It would be nice to be able to give some advance warning as to when and
whether PM is required (few folks have their ACbrrr "serviced" each year as
it is usually not needed -- just clean the condenser coils and make sure
the air filters in the blower have been changed, recently).

Knowing when the compressor is starting to see extra wear (as a result of
bad refrigerant levels *or* just plain wear-and-tear) and likely to fail.
Or, when efficiency is falling (few people keep track of how *much*
their ACbrrr runs; even fewer can correlate this with environmental
factors that would possibly account for the increased use) as a result
of a dirty evaporator coil or blocked vent; etc.

I.e., instead of an "open loop" PM practice, let the device assist the user
in *closing* that loop -- to save money (unnecessary service calls, reduced
energy efficiency) and increase comfort.

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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