Social Feed
In another thread, I posted that while using my Diamond 9000 trying to see Ciel-2, which is low on my horizon through the trees, that it looked like something shorted out. It was during a rainstorm, and it's possible that somehow I got water into either the Invacom lnbf or my 4x1 diseqC switch, but I'm just guessing there, because I immediately connected another receiver, and it was seeing the signal I HAD been looking at.
But anyway, I played around with my Twinhan receiver for a while, and for a while was getting some signals, but not good results, then finally switched to my old Fortec Ultra, which "seemed" to be working. Then I decided to try to switch back to the Diamond, however it wouldn't come up. It would come up on OTA channels, but when I'd try to bring it up on a sat channel, I'd get an error which said something like "LNB FAULT" or something. Disconnected the COAX, and it comes up without the error. Connect the coax to my Ultra, and slave the Diamond through a DC block, and the Diamond works fine, and plays the channels.
So I thought that perhaps the coax to the dish was shorted out enough to cause it to draw too much current, so I started doing some current measurements, however I'm not sure how to interpret them.
C-band LNB from Drake..... didn't even register on mA meter. (this lnb works fine).
Coax to SG2100-->diseqC switch--> 4 different lnbfs over 150 mA (motor not moving)
4 ports of an old partially functional Invacom.... each port in 60-80 mA range.
4 ports on the Invacom I'm using.... 1 port near zero (wasn't using that one), the other ports in 50-100 mA range.
Anyway, I'm not sure how much current these lnbfs, motors and diseqC switches are supposed to draw. Does the 150 mA total seem excessive? Should the motor and DiseqC switches be drawing in the 70-80 mA range when not running.
It seemed strange that my C-band lnbf wouldn't even register, but the Invacom was drawing 50-100 mA. Is that normal? I guess that an LNBF has a bit of extra electronics for switching polarity, whereas the C-band lnb doesn't, but it doesn't seem like it should be that much of a difference.
Actually, my feeling is that none of these currents should be enough to kick the Diamond into the lnb fault error, as I think the motor will draw more than I'm measuring when it's running, so I'm fearing that my Diamond might have become crippled, and no longer be able to control the dish/lnbfs. I guess I'll have to just use it slaved from now on. :-(
I did notice one thing. When testing to see if the Diamond would kick out when connected to my OLD Invacom (not on the dish, and not through the motor/switch), the Diamond didn't kick into fault then, but it was interesting that since I wasn't locking a transponder, the receiver kept trying to send out DiseqC commands to the switch/motor. At the time, I was on a vertical transponder, ie 13V. Each couple seconds, it would switch back to 18V, and send out DiseqC commands, then switch back to 13V, looking for a lock. It never stopped doing this. If I switched into Dish Setting mode, it would stay on whatever polarity/setting I put it on. I think this is normal behavior, as I've seen the continual sending of DiseqC signals before on 2 other receivers, but I never noticed that it switches up to 18V before sending out the DiseqC commands. I guess that makes sense.
Anyway, I'm *HOPING* that if we ever get some dry weather here that maybe the system will dry out and the Diamond will come back to life, but I'm starting to think that I killed it, or at least made it only operational when slaved.
But anyway, I played around with my Twinhan receiver for a while, and for a while was getting some signals, but not good results, then finally switched to my old Fortec Ultra, which "seemed" to be working. Then I decided to try to switch back to the Diamond, however it wouldn't come up. It would come up on OTA channels, but when I'd try to bring it up on a sat channel, I'd get an error which said something like "LNB FAULT" or something. Disconnected the COAX, and it comes up without the error. Connect the coax to my Ultra, and slave the Diamond through a DC block, and the Diamond works fine, and plays the channels.
So I thought that perhaps the coax to the dish was shorted out enough to cause it to draw too much current, so I started doing some current measurements, however I'm not sure how to interpret them.
C-band LNB from Drake..... didn't even register on mA meter. (this lnb works fine).
Coax to SG2100-->diseqC switch--> 4 different lnbfs over 150 mA (motor not moving)
4 ports of an old partially functional Invacom.... each port in 60-80 mA range.
4 ports on the Invacom I'm using.... 1 port near zero (wasn't using that one), the other ports in 50-100 mA range.
Anyway, I'm not sure how much current these lnbfs, motors and diseqC switches are supposed to draw. Does the 150 mA total seem excessive? Should the motor and DiseqC switches be drawing in the 70-80 mA range when not running.
It seemed strange that my C-band lnbf wouldn't even register, but the Invacom was drawing 50-100 mA. Is that normal? I guess that an LNBF has a bit of extra electronics for switching polarity, whereas the C-band lnb doesn't, but it doesn't seem like it should be that much of a difference.
Actually, my feeling is that none of these currents should be enough to kick the Diamond into the lnb fault error, as I think the motor will draw more than I'm measuring when it's running, so I'm fearing that my Diamond might have become crippled, and no longer be able to control the dish/lnbfs. I guess I'll have to just use it slaved from now on. :-(
I did notice one thing. When testing to see if the Diamond would kick out when connected to my OLD Invacom (not on the dish, and not through the motor/switch), the Diamond didn't kick into fault then, but it was interesting that since I wasn't locking a transponder, the receiver kept trying to send out DiseqC commands to the switch/motor. At the time, I was on a vertical transponder, ie 13V. Each couple seconds, it would switch back to 18V, and send out DiseqC commands, then switch back to 13V, looking for a lock. It never stopped doing this. If I switched into Dish Setting mode, it would stay on whatever polarity/setting I put it on. I think this is normal behavior, as I've seen the continual sending of DiseqC signals before on 2 other receivers, but I never noticed that it switches up to 18V before sending out the DiseqC commands. I guess that makes sense.
Anyway, I'm *HOPING* that if we ever get some dry weather here that maybe the system will dry out and the Diamond will come back to life, but I'm starting to think that I killed it, or at least made it only operational when slaved.
5 Replies
·
1506 views
I'm not sure how the Diamond reacts, but I have accidentally hot swapped cables without issue and shorted cables with poor cable fittings over the years. Most receivers reboot in cycles when shorting occurs.
I know with mine that without the coax connected to screen just says something like no signal. I've had it powered a few times while playing around with channel list while disconnected from the dishes.
Any chance a channel list data is corrupted? I know with the Diamond the channel editor shows a lot more detail than the screen does.
I know with mine that without the coax connected to screen just says something like no signal. I've had it powered a few times while playing around with channel list while disconnected from the dishes.
Any chance a channel list data is corrupted? I know with the Diamond the channel editor shows a lot more detail than the screen does.
I'm not sure how the Diamond reacts, but I have accidentally hot swapped cables without issue and shorted cables with poor cable fittings over the years. Most receivers reboot in cycles when shorting occurs.
I know with mine that without the coax connected to screen just says something like no signal. I've had it powered a few times while playing around with channel list while disconnected from the dishes.
Any chance a channel list data is corrupted? I know with the Diamond the channel editor shows a lot more detail than the screen does.
Re channel list, yeah, I guess that's a possibility. I had used the editor about 6 times yesterday, changing names of channels, and adding new channels.
When this occurred, I had just been sitting on a transponder for more than a half hour, while using 2 receivers, one that was connected via the DC-blocked passthru, and another that was connected via a DC=blocked "T". I think I lost signal on the Diamond after I connected a receiver on the "T". I decided that I should check that "T" to make sure it still only passed power on 1 leg, but I can't quite figure it out. The "T" doesn't show continuity between either legs. I thought that perhaps it was a diode thing whereby it needed a minimum voltage before it conducted, so I hooked it up to LNBF power. Still no continuity. I guess that it must require some current to flow before it conducts??? Strange. I think I'm going back to regular direct connect "T"s with a DC block on one leg, instead of this power passing "T".
EDIT: Had the power reversed when I tested with 18V. The "T" was good. Although I had THOUGHT that it wasn't one of those diode type "T"s, but I guess it was.
Update:
I was about to hook up the Channel Master sat meter that has V/mA/22KHz indicators, and watch while I boot up the diamond to see if the voltage drops, and/or current changes prior to going into LNB Fault mode.
Well the good news is that for some unknown reason, perhaps leaving it off all night long, or perhaps that it's no longer raining, and the sun is shining, and my switch and lnbf might have dried out... ....
the darn thing works this morning.
The bad news is that the 2nd sat I turned it to, to check was one which had some nice hidden (manual PID) channels. They were there yesterday, but today they're gone.
Well, you win some and lose some. I think I may do some waterproofing around that LNBF today. I used to keep it in a plastic bag, but the bag fell off. I guess I'll put a new one on.
I was about to hook up the Channel Master sat meter that has V/mA/22KHz indicators, and watch while I boot up the diamond to see if the voltage drops, and/or current changes prior to going into LNB Fault mode.
Well the good news is that for some unknown reason, perhaps leaving it off all night long, or perhaps that it's no longer raining, and the sun is shining, and my switch and lnbf might have dried out... ....
the darn thing works this morning.
The bad news is that the 2nd sat I turned it to, to check was one which had some nice hidden (manual PID) channels. They were there yesterday, but today they're gone.
Well, you win some and lose some. I think I may do some waterproofing around that LNBF today. I used to keep it in a plastic bag, but the bag fell off. I guess I'll put a new one on.
Supporting Founder
Really excited for this season with Kentucky having a new coach and some really exciting recruits. Probably won't last long, but here's hoping this season is great.
145 Replies
·
1548 views
Nah, you just don't understand how ignore works, which is why you made your own NFL thread thinking there wasn't one
Anyone else watch this show? Any guesses as to what was in the box Gibbs gave to Abby that was on her desk? It look liked it was glowing.
I also heard that someone was leaving the show at the end of this season. Any guesses as to who thats going to be?
I also heard that someone was leaving the show at the end of this season. Any guesses as to who thats going to be?
2135 Replies
·
214793 views
Tony as the director.
Would you rather have LaRoche ???Tony as the director.
No. Bring in someone new.
Tony is not serious enough for me. Parker is too close to the team and Tim is too young to take over IMO.
I don't think Tim and Tony are that far apart in Age ...No. Bring in someone new.
Remember what Tony said to Tim when they first got back together ...
Tony said: I am the New Tony, Tim .... (something to that effect)
Tony has changed, he's been running his Security Business ... I'm sure he has grown up.
Give it time ... your judging the New Tony from the old Tony.
It sounds like Tim won't be around the Team much longer either.
Staff member
HERE TO HELP YOU!
Cutting Edge
Sometimes a thread gets so many posts in it that is can cause issues for the server so that why today we introduce The Song Name Game Part 3!
So let the game continue!
The last song was added by Bobby who posted...
One Meat Ball - Andrews Sisters
CONTINUE ON AND HAVE FUN! WELCOME HOME TO SATELLITEGUYS.US!
Here are the original rules for the game as posted by WebbyDude back in 2006. http://www.satelliteguys.us/threads/68645-Song-Name-Game
Just name a song title and the band who performed it. The next person does the same thing, but needs to list a song title or band name which includes a word from the previous entry. Pick songs from any genre.
Example:
Long Live Rock and Roll -- Rainbow
Rainbow in the Dark -- Dio
Another example:
Ride the Lightning -- Metallica
Lightning Strikes -- Ozzy Osbourne
Get it?
An additional note: we all know that song titles, sometimes, use profane words. Because this is a family friendly website it is advised that you clean up that title up a bit. This is accomplished by using something like sh!t instead of the real word. Thanks....
So let the game continue!
The last song was added by Bobby who posted...
One Meat Ball - Andrews Sisters
CONTINUE ON AND HAVE FUN! WELCOME HOME TO SATELLITEGUYS.US!
Here are the original rules for the game as posted by WebbyDude back in 2006. http://www.satelliteguys.us/threads/68645-Song-Name-Game
Just name a song title and the band who performed it. The next person does the same thing, but needs to list a song title or band name which includes a word from the previous entry. Pick songs from any genre.
Example:
Long Live Rock and Roll -- Rainbow
Rainbow in the Dark -- Dio
Another example:
Ride the Lightning -- Metallica
Lightning Strikes -- Ozzy Osbourne
Get it?
An additional note: we all know that song titles, sometimes, use profane words. Because this is a family friendly website it is advised that you clean up that title up a bit. This is accomplished by using something like sh!t instead of the real word. Thanks....
68513 Replies
·
2671750 views
Lon.TV
Time for another AWESOME video from Lon Seidman of LON.TV!
View: https://www.youtube.com/watch?v=XBnhKwMxIhs
Direct YouTube Link - Local AI Coding from Scratch: A Practical Beginner's Guide
The Official LON.TV Website
Lon on Facebook
View: https://www.youtube.com/watch?v=XBnhKwMxIhs
Direct YouTube Link - Local AI Coding from Scratch: A Practical Beginner's Guide
The Official LON.TV Website
Lon on Facebook
0 Replies
·
4 views
Staff member
Pub Member / Supporter
Please post your remote make/model here and any details of your issue. We are looking to collect as many examples as possible. I may reach out to you for your receiver number, but please do not post it here.
If you've already reported this to me, please repost it here so I can track all instances in one thread.
Thanks!
Brittany
If you've already reported this to me, please repost it here so I can track all instances in one thread.
Thanks!
Brittany
23 Replies
·
704 views
I was having similar issues last night while watching and recording the NLCS game on 148. When I tried resuming the game at one point the screen went blank and I couldn't get my H3 to respond to any remote commands. Eventually the Hopper went to a HD channel but still no remote response. After a while the Hopper went into a re-boot cycle. This happened at least 3 times. I was using an IR universal remote only.
A little frustrating to have the game broken up like that but at least the Brewers won
Yea, I've only been a CIO for the last 30 years!
Trust me, when something important breaks, they get to own it!
This started a couple months ago. I have 2 H3s on one network, both with 2 EHD identical 3 TB seperately powered so all recordings are accessible by all 4k & J4s (8 of them).
On one H3 (not the main one that controls the MOCA network), after it reboots, it doesn't recognize it has two EHDs plugged into it. Rebooting the EHD by their power source doesn't fix it. Resetting the network doesn't. Software h3 reset doesn't fix it. Rebooting MOCA h3 doesn't fix it but so far, after 3+ cold boots (unplug pwr to H3 with unrecognized EHDs), it finally it figures out they are plugged into it. BUT.... Then when you open a program it only partially shows series and episodes, but instead of showing recordings, it only shows upcoming airings. HELP!!!!
On one H3 (not the main one that controls the MOCA network), after it reboots, it doesn't recognize it has two EHDs plugged into it. Rebooting the EHD by their power source doesn't fix it. Resetting the network doesn't. Software h3 reset doesn't fix it. Rebooting MOCA h3 doesn't fix it but so far, after 3+ cold boots (unplug pwr to H3 with unrecognized EHDs), it finally it figures out they are plugged into it. BUT.... Then when you open a program it only partially shows series and episodes, but instead of showing recordings, it only shows upcoming airings. HELP!!!!
21 Replies
·
270 views
Thanks JohnGalt1234 - That's interesting. I wonder are the Boot Strap versions different between a Hopper 3 only and a Hopper 3 with Hopper Plus setup as I have the later. I guess when charlesrshell is able to since he has both setups, he can do the test. Unless the bootstrap version is tied to when the specific Hopper 3 is manufactured, in my case, mines is from February 2016 when it was installed.
At least Google Search AI is saying the bootstrap version will never change and unique to each Hopper 3.
This is probably why different people seem to either have the issue or they don't because the bootstrap code could also be tied to the hardware revision and
components other than the internal HD.
At least Google Search AI is saying the bootstrap version will never change and unique to each Hopper 3.
This is probably why different people seem to either have the issue or they don't because the bootstrap code could also be tied to the hardware revision and
components other than the internal HD.
JohnGalt1234 - So you basically have 2 Hopper 3's. The CasinoH3 is the one that is Hopper 3 only while Master Bedroom is a Hopper 3 with Hopper Plus setup.
Master Bedroom uses Android TV (ATV) software so the DISH part is actually a app and will behave differently as you can probably tell the Guide's are different on the Master Bedroom which will resemble the same guide used on other ATV devices such as the Joey 4 and Wireless Joey 4. If I am correct, the CasinoH3 is the one with the problem since you did say the one dated 09/05/2026 is the naughty one while 08/15/2026 named Master Bedroom is the nice one. Usually I would expect the CasinoH3 to be the one without the problem because it's Hopper 3 only and Master Bedroom would be the one with problems because it has the Hopper Plus involved. That is why they behave differently because CasinoH3 is running the native Hopper 3 software while Master Bedroom is running the Android TV software and also it runs a app called DISH known as package com.dish.atv.launcher, the version for mines is P15403 2026100917 so it's probably the same version as the Hopper Plus software version with the date of October 9, 2026, not sure what the 17 means except maybe revision 17?
This explains it better than I can. Sorry, had to take all the ads out.
Master Bedroom uses Android TV (ATV) software so the DISH part is actually a app and will behave differently as you can probably tell the Guide's are different on the Master Bedroom which will resemble the same guide used on other ATV devices such as the Joey 4 and Wireless Joey 4. If I am correct, the CasinoH3 is the one with the problem since you did say the one dated 09/05/2026 is the naughty one while 08/15/2026 named Master Bedroom is the nice one. Usually I would expect the CasinoH3 to be the one without the problem because it's Hopper 3 only and Master Bedroom would be the one with problems because it has the Hopper Plus involved. That is why they behave differently because CasinoH3 is running the native Hopper 3 software while Master Bedroom is running the Android TV software and also it runs a app called DISH known as package com.dish.atv.launcher, the version for mines is P15403 2026100917 so it's probably the same version as the Hopper Plus software version with the date of October 9, 2026, not sure what the 17 means except maybe revision 17?
This explains it better than I can. Sorry, had to take all the ads out.
Staff member
HERE TO HELP YOU!
Anyone making their own breakfast sausage? I've recently been trying different recipes, found some I like, some I've modified...
42 Replies
·
3609 views
TWiT Tech Podcast Network
Time for another AWESOME video from the TWIT Network!
View: https://www.youtube.com/watch?v=ewCzxcofBUw
Direct YouTube Link - Untitled Linux Show 275
TWIT's Website
TWIT Live Feed
View: https://www.youtube.com/watch?v=ewCzxcofBUw
Direct YouTube Link - Untitled Linux Show 275
TWIT's Website
TWIT Live Feed
0 Replies
·
8 views
Supporting Founder
Lifetime Supporter
No idea what improvements might be involved.
12 Replies
·
573 views
Two bugs out and three new bugs in.
Yep. Just got a call from a customer who said her DVR buttons stopped working. Told her about the new software and had her reboot her H3, problem solved.Two bugs out and three new bugs in.
TWiT Tech Podcast Network
Time for another AWESOME video from the TWIT Network!
View: https://www.youtube.com/shorts/E-QczD5oEh4
Direct YouTube Link - AI vs. Coders & Mathematicians: The Great Disruption #shorts
TWIT's Website
TWIT Live Feed
View: https://www.youtube.com/shorts/E-QczD5oEh4
Direct YouTube Link - AI vs. Coders & Mathematicians: The Great Disruption #shorts
TWIT's Website
TWIT Live Feed
0 Replies
·
11 views