Thanks ...
What about "103(s)?"
Sent from my LG-H932 using Tapatalk
Your wanting to check a Spot beam?Thanks ...
What about "103(s)?"
Sent from my LG-H932 using Tapatalk
That was on 99(s)Your wanting to check a Spot beam?
I thought he did that the other day ... I think I saw 100's on 2 transponders.
Oh, gotcha ...That was on 99(s)
Technically from local spotbeam tps. 2 and 3 on 99(s) from T14. However SW2 was recently bought back into service to provide a single spotbeam on 99(s) tp. 6 to deliver some nationals for PR onlyOh, gotcha ...
Which Sat do your Locals come from ?
Ok, got it now ...It's awaiting for aproval
https://www.satelliteguys.us/xen/attachments/20181009_160516_hdr-jpg.135298/
And this confirm PR setup
Receiver H25/100 using SL5 Lnbf
Are you sure it's not on 101 tp31, we use to get all even to on 101, but almost none on the odd tp's, that why we could not get an HD receiver loading, without a 10 or 12ft to see tp31Thanks, looks like a normal firmware version for the H25 so probably identical firmware to the US. My guess is that the card being activated in Puerto Rico causes it to do a few things differently, like looking for the 110 satellite at startup instead of 101 like in CONUS, and that "completed satellite setup for Puerto Rico" message.
I did some testing on one of my H20s (which has the old SD GUI so it is easier to see what is happening) and found that if I disconnect both even and odd 99/101 inputs from the dish and restart the receiver it will show "searching for satellite signal" forever. If I connect the odd it will find the signal but sit at 0% for the initial download forever. So apparently whatever it is looking for is only available on 101's even transponders (could be transponder 32, where the SWM guide channel is located for us)
My guess is that when Directv is ready to cut Puerto Rico over to using the 101 satellite in preparation for shutting down 110, we will see at least transponder 32 offloaded from T9S to T15 - maybe all 10 non-spotbeam transponders. Then they will show up on your satellite screen for 101, and 110 will probably show 0s soon after. No idea when this will happen, could be next week or could be a few months from now.
Are you sure it's not on 101 tp31, we use to get all even to on 101, but almost none on the odd tp's, that why we could not get an HD receiver loading, without a 10 or 12ft to see tp31
It was legacy, was years ago about 2011-2012, maybe things have changeWere you using SWM or legacy mode? When I experimented a couple days ago I couldn't get the H20 to load when it only saw 101's odd transponders, it had to see 101's even transponders to properly start up. Maybe the newer HD receivers act differently - the H20's last firmware update was in Sept. 2013 so Directv might have moved a few things around but without a firmware update it doesn't know where to look. I wonder what would happen if I put it in legacy mode
For me the most interesting thing I found during that experiment was if I had the 99/101 odds disconnected and 99/101 evens connected so it started up and the progress bar showed the percentage of loading, if I disconnected the 99/101 evens - leaving only 103 evens/odds remaining - the loading progress continued uninterrupted. It only needed 101 at startup to get some minimal bit of data - probably a current map of what's where which is a good way to handle receivers that might have been in storage for years and not had a firmware update, or for which firmware updates have stopped like the H20.
It was legacy, was years ago about 2011-2012, maybe things have change