Before replacing a flowmeter, resetting it can be a good way to check not only its status but help with inaccurate readings, lack of data, or reading delays
To reset a flowmeter
- Locate the keg that is causing the issue
- Run your hand along the line delivering the beer to the tap handle, locating the flowmeter
- There will be a black-and-white or black-and-red wire that will be plugged into a small white port/housing unit
- Remove the cord from the white port and dry it off, as condensation can cause it to trip.
To remove the unit, use a flathead screwdriver to pop the tab. It is important that the housing unit remains attached to the chip within the flowmeter. If it is removed, contact support.
- Locate the opposite end of the wire that is connected to the BevBox. Check its integrity.
- Replace the cord back into the white port/housing unit on the flowmeter
Once done, wait 5 minutes. You'll then want to conduct a mini pour test by pouring approximately 1-2 oz from the keg with the reset flowmeter. Review your findings and see if the issue has been resolved.
For the V4 BevBox, it is recommended to perform a Dot Test. If you notice that the dots are down, please refer to Dots Down Troubleshooting.
For the v5 BevBox, if the light to the flowmeter is still not on, proceed with the following:
- Locate the black and white wire for the flowmeter in question that is connected to the BevBox
- Remove the font panel on the BevBox to reveal the individual ports for each of the draft lines/flowmeter. This can be achieved by removing the two screws at the bottom of the BevBox
- Look for any wires that may have come out of the port. These can be re-inserted by pushing on the tab directly above the female connection and inserting the wire.
- Once all wires have been checked and the lights have come back on, put the cover back on the BevBox.
Should you need assistance or further guidance, contact support. It is important to complete these steps as it enables BeerBoard support to see if it is the port, flowmeter, or possibly a bad connection.