Email support issues here: firstname.lastname@example.org
PoG Technologies LLC
8442 W Pinnacle Peak Rd.
Peoria, AZ. 85383
April 12, 2015
Firmware Version 1.4 and earlier.
We currently have an ongoing issue where FW may not alarm when the filter is dirty. This is not an issue with the electronics but more of a use issue. We are finding a couple different scenarios and if your filter watch has not triggered and your filter looks dirty then it may be one of the following:
In all cases we promote then installation to be on a return vent because this is where we focus out testing.
- Low use seasons with the FAN ON is posing and issue. What occurs is that FW finds the FAN ON speed and expects that speed to go down. 10 days later, FW finds the system ON speed and waits another 10 days. As the season changes, FW is more likely to find the ON speed and reduction of that to 25% below the FAN ON speed will like never happen.
If you haven’t sent in your device for the power usage issues, we will update with the latest firmware and will likely have a fix for this. If you do not run you FAN ON mode then there is no need to consider this issue.
- Corner installations have been a little problematic. In some installations, the air speed in the corners actually goes UP as the filter gets clogged BUT never comes down before the filter is over-clogged.
Try a different location that enables FW to be closer to the center of the vent. After some testing has completed we may have an edge location that works better. Update firmware will like add an alarm if we detect a rise in airspeed after a set period.
Jan 31, 2015
Firmware Version 1.2 and earlier. (Firmware version is displayed after battery volts on power-up F1.x). If the version is not displayed, you have a very early version.
If your HVAC system is NOT running more than 4 or 5 hours in a 24 hour period, FW uses a considerable amount of battery power due to a software error. This error has been corrected in firmware version 1.4 and later.
- A user can turn FW off in the less critical months of non-peak usage seasons (HVAC is on LESS than 4 hours in a 24 hour period).
- A user can just change the batteries when they go LOW. This might occur in as little as 4 months under the right conditions.
- A user can send their unit(s) back for a firmware upgrade. Please use the address listed above.
Weird Buzzer Sounds
We are aware the the beeper might make a sound that has a little vibration in it OR seems intermittent.. Intermittent beepers are the biggest issue we deal with during testing. We have determined the cause is related to package design. When we hear a beeper that does not sound as expected, we manually ‘trim’ the package in 2 place and we make sure as to not over tighten the middle screw on the back housing. In most cases we have made the package modifications as a matter practice. If you end up returning your unit for firmware upgrades, we will make sure it has all the modifications (if needed).
Jan 1, 2015
Filterwatch uses less that 50uA (micro amps) of battery when it is in sleep nmode. However, the first time after any power cycle, the battery consumption apporoaches 200uA when in sleep mode. To make sure FW is using only 50uA, when in sleep mode, the followinng procedure must be followed:
- Turn ON FW with the power switch and wait until the unit sleeps in 10 seconds
- Wake the unit with either button and wait until the unit sleeps in 10 seconds.
Anytime the unit power is cycled, this must be followed or the unit will consume more battery power then we expect.
Here is some math:
AAA batteries have 1200000 uAh of power @ 50uAh of continuous usage, the batteries would last 1000 days (minus FW ON time). At 200uAh of continuous usage, the batteries would last 200 days (minus FW).
FW uses 15000uAh of battery power every 11 days. This equates to being able to check air flow 96 times a day for 80 days. During peak HVAC operatring season, we have found that it takes under 15 airflow checks to get a ‘valid’ airspeed that we use for processing.
“My FW is making a funny noise and my unit says LOBATT after 2 weeks”
When LOBATT is displayed on the LCD, a number should also be displayed. That number is the voltage left in the batteries. A battery check is performed on every wake-up of the device, if the voltage is less than 2V, LOBATT will occur and the batteries MUST BE CHANGED. Cycling power does nothing.
Low batteries cause all kinds of issues, especially with electronics that require a large inrush of power, LIKE THE BEEPER. We don’t even attempt to sound the beeper if the battery voltage is less than 1.9V. The device may initially sound a beep or 2 but power drops FAST at that point and generally, only the LED can be supported. The weird sound is a result of insufficient battery power.
AAA batteries can range from 860-1200 mAh of power when new. We don’t check the batteries initially supplied with the unit. We selected a USA manufacturer. There is a possibility that one of the batteries was ‘bad’.
With known good batteries and FW mode only use (not using the annemoeter), there is currently no known reason for the batteries to last oinly 2 weeks. We test (and have devices still in test that have been running for months) while setting the device in a box with no airflow. This will cause FW to run the fliter check 96 times after the first 3 days, and every 11th day after that.
USER CHECK: Follow power ON procedure above and install known good batteries. If the issue occurs again, contact us via email.