How to update a Volicon Probe when the over air frequency changes for ATSC/8VSB Channels

1. On the Desktop of the Central Server, right click Probe Manager and select "Run as Administrator". In the Probe Manager click on Volicon Media-Hub Management and answer yes when prompted to connect with the local MediaHub service.

2. Under Media-Hub #1, click on BdaNode and locate TunerFrequencyMHZ and Channel. If the values for the frequency is known, it can be updated and saved here and you can skip to step 4.

3. If it is necessary to discover the frequency/channel, this can be done by clicking on BdaNode Advanced Setup under Actions on the right of the Probe Manager window

- In the Tuner Frequency Scanner window that opens, select the desired Channel Range and on the right hand side under Actions click Start Frequency Scanning. The scanner will attempt to tune each channel for 15 seconds to check if it is valid. 

- Once the scan completes it will display a notification of the channels and tuner frequencies that were discovered. Click on the desired channel Frequency, right click it and select Apply Tuner Frequency and the BdaNode that needs to be changed. "To this BDA Node" can be used to apply the change to a different BdaNode.

- Click Ok on the confirmation message, "Please update the configuration in order to apply the new Tuner Frequency settings on the BDA Node device node."

- On the right hand side of the Probe Manager window, select "Update configuration on conne...". In the windows that appears with "Which Media-Hub instance(s) would you like to update the configuration." make sure that the option "All Media-Hub instance(s) are selected.

4. On the left hand pane of Probe Manger, select the HardDriveStoreNode associated with the BdaNode being updated, then on the right hand side under Actions, click on "HardDriveStoreNode Diagnos..." This will display the channels Inventory Report that can be used to confirm the correct Callsign and sub-channels

5. In the left hand pane of Probe Manager, under Observer Encoder, select the Encoder. Make sure the Encoder Settings tab at the top is highlighted. Under the category TS SOurce, find Program Name and click on the dropdown arrow at the right of the field. You should be able to select the channel for this encoder. Click on save at the bottom of the Probe Manager Window.

6. If the Encoders will not start after making these changes, it could be an issue with the configuration of the Audio feed. It will be necessary to click on the Encoder on the left hand side of Probe Manager, and then click on the Encoder Log tab at the top center. Messages similar to the following examples would indicate needing to update Audio settings for the encoder

-"Failed to find an unconnected output pin"
-" Failed to build the TS encoder graph:... Failed to find an output pin"
-"Faile to connect "AC3... to "input" ping of "ID: ..."

These settings can be modified under the "Encoder Settings" tab > "Audio settings" > "Audio streams device" > "Collection" > "..." 

7. If the Encoder is displaying a Yellow Box at the beginning of its name, this indicates it is in Recovery mode. Right click on it, select Start Encoder. This may display a window, "Activating ... while in recovery will terminate the watchdog. Keep the watchdog activated?" Click on "Yes".

8. Once the Encoder is started, confirm the channel is viewable in Observer Classic. If it is not, please do the following:

- In Observer versions 8 and 9, ensure the encoder is synced by clicking on the Gear icon in the top right of the browser > select Configuration>  make sure Encoders is selected on the left > Make sure the tab "Encoders" is selected at the top center > click on the "+" next to the Probe to display the individual encoders> hovering over the Encoder will display several buttons > click on the "S" to synchronize the Encoder > if the feed is still not viewable do the following:

- Run the Artisan Update utility on the Central Server to rebuild the services. In an Administrator Command prompt: "\Program Files\Volicon\observer\framework\php artisan update"

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.