Results 1 to 10 of 32
Thread: azbox and SG2100 dont mix??
- 03-22-2010 09:10 PM #1
azbox and SG2100 dont mix??
ADVERTS 1
I asked a couple folks if their azbox worked with a motor properly (as in it would actually keep a location) and they said it was bang on.
So tonight I tried to hook up the azbox elite with a SG2100 and was not happy
Locked 93W (true south) and selected Diseqc 1.2 and "save"...I did not do auto and selected my own position (1) and scanned in channels. Went to 91W and got that locked in. Saved it as 2 and scanned in channels. Now selected Azteca 7 (on 93W) and it said "moving to 93.1W in 20 sec" and counted down to 0....
no signal on screen
it did not save the right spot. Was off big time. Looked like it went to about 94 or so...Tried again. Saved 93, 91 & 72W. But here is when I noticed we have issues. I saved 72W and scanned in the NBC Satops mux.
1st channel shows 82 quality
selected second channel and the yellow bar didnt go as far....checked and quality was down to 62. So the receiver moves the motor on the same transponder....ugh!
So I went back to the Coolsat for now. Anybody using a azbox elite and a motor properly?Winegard 76cm dish, SG2100 motor, Sadoun dual KU LNB..... Directv Slimline SWM 3 LNB.... GeoSatPro 36" dish with Sadoun dual KU LNB... Coolsat 5000 on motorized.... Manhattan RS1933....Directv HR34 (yes the 5 tuner monster) GeoSatPro 200 to aim dishes.... few receivers not set up yet
Two 6 foot Fortec dish with GeoSatPro dual C-Band LNB "ghetto moved" to various C-Band satellites
- 03-22-2010 09:10 PM # ADS
Register Today & This Ad Goes Away! Circuit advertisement- Join Date
- Always
- Location
- Advertising world
- Posts
- Many
- 03-22-2010 10:18 PM #2
Yes, I have a sg6000. I found that USALS works perfectly.
Diseqc 1.2 on the other hand is buggy. I found that auto save works best. And do not 'reset' a setting. It will shuffle the remaining settings.
Also, after hitting 'save' you must menu over and hit 'go to position' or the motor will go amuck.
That being said, I have no issues using it with my Gbox. I can assign locations and 'bump' the motor with no problems. I still have to hit 'go to position' for the save to take though."I tried that once"
- 03-22-2010 10:32 PM #3
- Join Date
- Nov 17th, 2003
- Location
- Now Living In the Last House on the Left
- Posts
- 75,782 Thread Starter
Proud Staff MemberThats what I've notice that Diseqc 1.2 is buggy
I think I'll keep it as is for nowWinegard 76cm dish, SG2100 motor, Sadoun dual KU LNB..... Directv Slimline SWM 3 LNB.... GeoSatPro 36" dish with Sadoun dual KU LNB... Coolsat 5000 on motorized.... Manhattan RS1933....Directv HR34 (yes the 5 tuner monster) GeoSatPro 200 to aim dishes.... few receivers not set up yet
Two 6 foot Fortec dish with GeoSatPro dual C-Band LNB "ghetto moved" to various C-Band satellites
- 03-23-2010 03:48 AM #4
Ice (Tony),
Try to use USALS with the AZBox. Don't use DiSEqC 1.2.
I believe that both should work fine, but because of the screwy programming, it is difficult to keep the DiSEqC settings organized properly. With DiSEqC 1.2 motor positioning, you have to set each satellite up individually and I don't know how well the AZBox likes it.
I use USALS for EVERY satellite, except 30.0°W via my AZBox and it works great this way. 30.0°W I have to set with DiSEqC 1.2 because of my location coordinates and the limitations of USALS beyond a specific degree east or west.
Tony, I know that you have the Elite model and I have the Premium model AZBox, but I am sure that this difference has nothing to do with this problem. The differences are the power supply and HDD location and the option of the WiFi.
When you and I discussed this in a PM, I assured you that the motor control using USALS was SPOT ON. I adhere to that as it is still working so well for me today and it has been that good ever since I set it up.
I feel bad because it isn't working the same for you after I told you that it would work so well. I have had two different AZBoxes and they both worked perfectly in regards to satellite location. I don't understand why your AZBox Elite would not follow the arc just the same. They are the same machines, with a few different bells and whistles here and there, but the guts are the same.
If you have not been using USALS satellite location, try it instead of using DiSEqC 1.2 locating. I am noit sure that this is going to be helpful if something else is wrong, but I founjd that the AZBox doesn't like you to mess around with the satellite list. Every time I go there to play, it screws around with my other sat positions. I tried to forwarn you about this in my last PM, but I wasn't sure of how DiSEqC 1.2 functioned with more than one sat.
I really feel bad that your motor control isn't what I told you it should be, but I don't have any problems (other than what I stated about the corruption of the list) so I don't know what the error could be.
I cannot see the difference between the AZBox Elite and the Premium causing this. I have swapped so many different receivers with the same dish antenna and they have all worked spot on (except for the SonicView 360).
Tony, there must be something else that you and I are missing in this as I am sure that it isn't the AZBox itself. It cannot be, unless your AZBox is messed up, and I don't believe that.
We should discuss this further and come up with an answer so that others don't have to be surprised by this problem. We should get to the bottom of this. If you want, PM me for further discussion.
GordyLast edited by AcWxRadar; 03-23-2010 at 03:54 AM.
There ain't no Sundays west of Omaha. Clyde "Fats" Potter, "The Cowboys"
- 03-23-2010 06:18 AM #5
I use the AZ with SG2100 (USALS), SG6000 (USALS), and GBox (Diseqc 1.2) All work fine....except saving Diseqc 1.2 positions. I had numerous problems that change with Firmware updates.
For Diseqc 1.2, I use the GBox's remote to Find / Tweak and Save positions, and just used the MAZ Editor to enter the Position Numbers for the AZ. Not that easy with SG2100, but you could write down the Position Numbers from the Coolsat and enter them in to the AZBox's channel list via an Editor.10' Unimesh w/ DMX741, GBox 3000, AZBox Elite, SatHawk PVR800 with Motorized Prime Focus 36" Backup.
Diamond 9000, Motorized 80cm BJU Dish.
- 03-23-2010 07:05 PM #6
I have similar problem with Diseqc 1.2, but is working OK on USALS. If I remeber well, last FW working OK with Diseqc 1.2 was 0.9.2880. After that, strange things start happening.... Position was not saved, Sat/Channel list got corrupted, Sat position was changing etc...
There is lot of complains on AZbox forum about Diseqc 1.2
- 03-23-2010 08:17 PM #7
The AZBox Elite using DiSEqC 1.2 still drives me nuts. With all the firmware upgrades, it seems like they would of had ample opportunity to correct this major issue.
- 03-26-2010 02:00 PM #8
I haven't tried USALs in a long time but it was ridiculous 8 months ago.
I have an elite with a digiwave sg2100. I'm still using my coolsat 6100 to run the motor. Running the elite in slave mode sucks. 1/2 the transponders wont work until I go back into the coolsat and tune to a missing tp
I remember reading on this site that blindscan and motor control wasn't big on the azbox priority list. They were saying the IP TV was the main focus and no real changes were on the horizon.I prefer sat locations vs. spacecraft names
coolsat 6100 cyberhome AC3 converter
azbox elite, digiwave .85M w/qph031, sg2100
http://folding.extremeoverclocking.c...tKT7A&t=186785
- 03-26-2010 02:45 PM #9
Lak7,
I have been using my AZBox Premium with the SG2100 and the PowerTech DG-280B and DG-380 motors and have witnessed NO problems and no errors.
I have all satellites that I can receive set up to use USALS except one, 30.0°W. My longitude is 96.4°W and my latitude is 41.6°W and no matter what receiver or motor I use, the USALS system will not drive the motor beyond a certain degree. 37.6°W is good, but 30.0°W is a no go with USALS. So, somewhere between there USALS ceases to function for me and I have to switch to DiSEC 1.2 and position the dish step by step until I find the sat and then SAVE/STORE the motor position manually.
Otherwise, my use of USALS is spot on and so convenient that I told Tony in a PM that he would be pleased with the AZBox motor positioning. I feel bad that it doesn't work well for him, but I wonder if it doesn't have a relation with messing with the list of sats in the AZBox.
I have fought this ever since day one when I received my AZBox. If the list of sats and their positions are accurate, you regret editing them, as the list almost always becomnes corrupt and the table of memorized sat positions within the AZBox loses its mind. If I add a new satellite to the list, one or two other sat positions are comprimized during the process.
I have tried everything I can think of to prevent this, but just when I think I have resolved the conflict or problem, it screws me up again.
I have a back-up of my "good sat list" that I can rely upon so that I can reload everything easily and start over. But, that is not how this should work. Problems like this should not arise in the first place. I used the AZBox web site (OpenSat's bug report site) to complain about this issue a few times. Although, I don't see them addressing the issue yet. Maybe someday they will.
I will continue using my AZBox with USALS and adding new sats to my list, or deleting retired ones as I wish. I will just have to remember the littlke tricks that are necessary to keep my list clean and just woirk around the problems until they fix it permanently. A pain, I know, but not too awful.
RADARThere ain't no Sundays west of Omaha. Clyde "Fats" Potter, "The Cowboys"
- 03-26-2010 04:28 PM #10
I think we discussed this sat list thing before. My Azbox CAME with a corrupted sat list, and the only way I could get it uncorrupted was to make a basic list with that .xml file method. After that I only make changes (except for sat names) via the remote, not the editor.
Anyway, unless they have changed the default sat list, I think that you MUST mess with the sat list, but you MUST make sure you get rid of what was there originally, not just delete and add via the remote, because with MY Azbox, it wouldn't let me delete the corrupted data.
I'm curious about you saying that you post to OpenSat's bug report site. I went to that page, and got the template for the bug reports, but there was no way I could find to actually post on that page. I had to go to their SUGGESTION page, and post there. I see that other people have done the same thing. But they eventually remove the posts there and move them to archives and the posts don't seem to get any attention.
Looking at their bug report page, I don't see any of the common bugs we all know the Azbox has, so I'm confused about whether they are actually getting the info or not. Or (more likely), I'm just missing something when navigating that site.

LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks