Changelog

ISSUE

During registration, if the instant email validation is used, the system would return an SQL error message.

ROOT CAUSE

Code that was not properly changed to reflect a previous transition of CDBS data to a different database.  

RESOLUTION

Modified the code to conform with the new internal CDBS database parameters.

On the HAAT Check, myLPFM now advises when an LPFM station is within 125 km of the Mexican border.  The message displays the various §73.807 rules that apply to LPFM stations in that area.

REC is currently experiencing issues with the server.  

eLMS real time is currently down.

Channel searches may be returning incorrect information.

Manual morning FCC database update in progress.

Revised ETU 1 PM ET.

This issue was resolved at about 2 PM ET.  

We have made some changes and fixes to myLPFM v3.

Zero latitude/longitude issue

Fixed a bug where some stations were coming up with a latitude and longitude of 0. 

Encroachment Report enhancement

On Encroachment Reports, there will now be a color band indicator to the left of each station entry.  These color bands are currently:

Added two new modules to myLPFM v3 (early release):

Translator Interference

Early access version 3 of myLPFM released today.  

Full information about this release can be found here:

https://recnet.com/node/3684

ISSUE

Received reports that the Advanced Coverage Map in FCCdata was not displaying contours. 

ROOT CAUSE

Issues with the REC interface with the FCC legacy height above average terrain (HAAT) calculator.

RESOLUTION

REC Networks has retried myLPFM version 2.  

REC is nearing completion of myLPFM version 3.  The new version will address the issues that myLPFM version 2 was experiencing.  The new version will be available to all existing licensed LPFM stations and will require a password for entry.  This will be the same password that is used for the REC Voluntary Public Inspection File system.  

Created a new website dedicated to show of interest forms for the Generation 3 LPFM Filing Window.

Developed URL https://lpfm.app

Site includes information pages on the LPFM service to introduce potential applicants to the service.

Public Notice handling issues

A very minor enhancement was installed today into FCC.today which, on most granted call sign requests (CSR), the new call sign will appear after the community name in the "Actions" section.

For example:  PODUNK XX (now KFWB) 

The new functionality covers only original call sign requests and basic call sign changes.  It does not yet support call sign swaps. 

Overview:

BACKGROUND

enac_lpfm (every nook and cranny) is a legacy (pre-eLMS) table that is used in several REC systems to store specific critical data elements in a single file instead of in a relational database (which is the basis for CDBS, LMS and eLMS).  This table is used mainly for FM channel searches, bulk reports and similar functionality where search speed is essential.  enac_lpfm is updated directly from the daily FCC LMS data load and does not use eLMS as a data source and therefore is authoratative for filings.

ISSUE

On Thursday, August 4, 2022.  REC has received a bad load from the FCC.  This will impact many tools throughout the REC universe.  Recovery attempt in progress.

REPORTED ISSUE

When the call sign in FCCdata is entered for an FM station, the information is not being retrieved. 

OBSERVATIONS

This is an issue that is happening mainly with new FM facilities that were authorized as a result of Auction 109 and the 2021 NCE Filing Window.