Incorporated the RDS (Radio Data Service) Program Identification (PI) Code database operated by NAB-PILOT. This database will be updated daily (during the morning load) with all assigned PI codes including the one-off codes for 3-letter call FM stations and FM translators therefore allowing these facilities to now be displayed.
ISSUE
With the newly implemented RadioDNS functionality, stations owned by Beasley are returning warning messages and no RadioDNS information.
ROOT CAUSE
The SI file for the Beasley stations does not include any services, only a service provider. The system expects to see services in the SI file.
FCCdata now supports RadioDNS. RadioDNS is an open source system that provides metadata and logos for radio stations intended to be used with connected cars and other compatible devices. For clients using RadioDNS, such as FCCdata, this involves having to make domain name server (DNS) calls to retrieve an XML file which includes the station's basic information as well as links to logo graphics.
Every morning at 02:30 RECOT (same time as Mountain Standard/Arizona time), REC conducts a full download and update of the FCC's CDBS and LMS raw data and runs various programs to support the data. Some of these programs are memory intensive and can cause the system to substantially slow down during those update periods. This issue is further frustrated when other automated operations, such as eLMS updates take place during the program run, especially on days when the FCC grants renewal applications.
Earlier this year, we noticed that the REC interface to FCC Electronic Documents (recnet.com/edocs) stopped working. This service was connected to an FCC operated API. That FCC API failed. We allowed some time for the FCC to fix the issue, they never did. It appears that they discontinued the API.
A fix was put into place where when an EDOCS item is selected in the REC system, it will now redirect to the FCC's public page that provides information similar to what we were delivering through this page.
As an initial matter, the launch of v3.1 was delayed due to a wait for the Federal Emergency Management Agency to approve REC's application to access the IPAWS-OPEN production environment. During this wait time, more features were added from the development roadmap that were not supposed to go until a later version.
REC has made a major dot release for myLPFM.
Version 3.1 will include the following:
REC has suspended all new user registrations on the Voluntary Public Inspection File (VPIF) system.
All station administration functions for VPIF will be transitioned to the myLPFM Station Management System.
LPFM stations currently using VPIF can continue to use the system as they normally have at this time.
LPFM stations not on VPIF are encouraged to go to mylpfm.com and apply for a free password there.
The @DelmarvaEAS Twitter account has in the past, operated as a public service of REC. It originally was driven based on the emails received from REC's DASDEC. The service was discontinued in mid-2021.
Using the new REC OPEN/IPAWS interface, we have restored the Twitter service to include EAS and non-EAS (National Weather Service) data.
The Twitter page can be found at:
https://twitter.com/delmarvaEAS
REC Networks had previously signed a Memorandum of Understanding with the Federal Emergency Management Agency for access to the IPAWS All Hazards database. This is what is used for EAS, National Weather Service alerts (SAME) that do not go over EAS.
REC has built an interface that will poll the IPAWS All Hazards system once per minute and add the data to our database.
With this data in our datastore, this will permit REC to offer various database products through our entire line of services as well as introduce new services for broadcast users.
With today's release, we now include a Channel Reject Report on all channel search report results. The Channel Reject Report was previously in myLPFM v2.
Users wishing to view a Channel Reject Report can make a channel search (either at the same or different location). A link to the Channel Reject Report will appear after the display of available channels.
The Channel Reject Report will show all 100 FM channels and if a channel is short-spaced, it will show:
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.
Fixed a bug where some stations were coming up with a latitude and longitude of 0.
On Encroachment Reports, there will now be a color band indicator to the left of each station entry. These color bands are currently:
Please show your support by using the Ko-Fi link at the bottom of the page. Thank you for supporting REC's efforts!
