Thread: Attention: VOOMers in San Diego, LA, or Phoenix DMAs

have you experienced the problem of successfully scanning an OTA channel that is then unreceivable?

Please answer this post. Thanks.

Sean, I'm not sure I understand the question? I can scan extra channels like WB or Fox that don't actually come in but I thought this was an antenna issue. Please explain further. Thanks, MJB

This is a very specific problem that VOOM and Motorola are currently trying to chase down:

If there is a channel, which was not in the OTA map originally, that you were able to add to the map by doing channel scan, but after that you are not able to receive it.

If you have this problem and live in one of the areas mentioned in the subject, please reply in this thread. VOOM needs your help!

I'll do the channel scan tonight as I really didn't pay attention to the OTA that much before.

I have several channels that scan, but then a black screen is displayed when I try to tune them. I just hide them in the channel list. I will analyze it this evening and see if I have what you are describing.

I have that problem (or a very similar one,) but I live in the Albany, NY market.

Sean- I've told you about this atleast 3 times, still haven't heard anything about it. All Voomers I've encountered in this market have the same problem with the same channel.

17-3 (rf34) was originally "mis-mapped" by voom to 17-2 (The PSIP data is for 17-3)... So when channel scan came through in version 6.2 I had aquired 17-3... the program guide displayed 17-1, 17-2 (not an actual channel, but had the PG info for 17-3) and 17-3 with "No Data." A few days later VOOM updated the PG for my market because PG info was now on 17-3, 17-2 was gone. In the same DMA push I got mapping data for a yet to be operating 10-1. 17-3 has not come in on the VOOM STB since the morning of the mapping update, which was months ago at this point. 17-1 (on the same rf34) comes in fine. It figures 17-3 is the HD channel and 17-1 is the SD.

For those who have already reported the above problem: if possible, please provide a link to your previous posting, so it would be easier for VOOM/Moto engineers to find it. Thanks!

Originally Posted by Sean Mota

have you experienced the problem of successfully scanning an OTA channel that is then unreceivable?

Please answer this post. Thanks.

Sean, I have scanned channels with the Moto Voom receiver and have not been able to watch. However, I have a Samsung HD box for Direct. I received all the channels I scan i.e. those which I can scan on VOOM and not watch.

Let me know how I can help.

Ken
kfried@cox.net

Okay, I disconnected my antenna and then scanned for OTA channels. It found 0 channels and I saved the results. I rebooted the STB and then hooked up the antenna and stepped through the channels. The attached spreadsheet shows the results. I then rescanned the channels and found 34 channels which I okayed and then tried out. A few of the channels don't agree with the "mapped" channels as far as name. I have channel 13-1 "mapped" but it doesn't scan although it tunes in fine. I also have 3 other channels "mapped" but they don't scan and there is no signal.

I hope the attachment can help you debug whatever it is that you are looking for.


Attached Spreadsheet