Yesterday on 10/16, I helped Alonzo G with the FBC lift station. A tech for the station had said that it was possibly bad cell signal causing issues, and sent instructions on how to resolve. Alonzo didn't send me the email, but he showed me. This is to document the changes made at Alonzo's request and to provide information for future times working with the station. You have to click update a few times to have settings take effect.
1. Wire in a laptop directly to the lift station modem into the lan 1 (or land & console, or lan & serial) port in the fenced in area past the cdl parking lot.
2. Set the IP settings as such on the laptop's ethernet port: IP 192.168.1.100, SN 255.255.255.0, GW 192.168.1.1.
3. Disable wifi adapter.
4. Type in 192.168.1.1 in a web browser's URL bar.
5. Login to the page that comes up as admin. The proper credentials hadn't been set by the company, so the login was admin for both the username and password. I changed the credentials according to the email that Alonzo had received. The new credentials are UN admin and PW Sensaphone01.
6. At the main dashboard click details button and underneath the Sim A column, you should see signal levels.
7. Compare the signal levels to the attached picture.
8. Once finished comparing and documenting, go to system and see if there is a firmware update using an option on the left and checking for updates. (When I looked, there was an update available to 8.3.0 from 8.1.3 so I updated it. Made a little improvement in the signal strength, which was already in the excellent range on two metrics and good/fair on another one prior to the update.)
They recommended moving the antenna at least 5 feet from the modem itself and any other electrical equipment. Alonzo is going to work on moving the antenna higher by a few feet, as it is currently right next to the electrical box.
Those are the instructions that they sent.
To document the changes: updated the password to the correct setting, updated the firmware to 8.3.0, set the modem to only look for signal from Verizon instead of looking at everything from AT&T/Tmobile and Verizon. According to Alonzo, only Verizon is used for the station and never AT&T/Tmobile.
It was set to automatically look for signals from each and the CPU % was maxed out and jumping from 100 to 27 to 84 to 53, etc. After getting Alonzo's verbal permission, I set the device to look only for Verizon. After setting the device as such, the modem was showing a cpu usage of around 20% after a few minutes of minor flucuations (15-23%).