2.4 DH Antenna installation

[John]

Yes
Both. Scanned at 2MHz steps. There were another 3 or 4 that could be manually tuned at reasonable SNR. Done at 15:00-18:00

Yes
Both. Scanned at 2MHz steps. There were another 3 or 4 that could be manually tuned at reasonable SNR. Done at 15:00-18:00

Just done LHC now and got 45TP's using 2MHz steps, got to go and pick the dragon up from work now ---will do RHC when i get back

 

[scopus]

Nothing in the instructions for these electrical connectors x3, presume there for the servo connection ?
View attachment 105666 View attachment 105667

Just the same as the ones we use at BT, grease filled IDC connectors. Insert the two wires and press the red area down with pliers.

 

[blademedia]

Just the same as the ones we use at BT, grease filled IDC connectors. Insert the two wires and press the red area down with pliers.

Thanks scopus, i need to disconnect it when swapping and changing lnb, will use a plug type.

 

[John]

Just done LHC now and got 45TP's using 2MHz steps, got to go and pick the dragon up from work now ---will do RHC when i get back

Just done LHC now and got 45TP's using 2MHz steps, got to go and pick the dragon up from work now ---will do RHC when i get back

Here's the scan for LHC that i did for comparison just before picking the dragon up ... It is a normal 3.6 to 4.2 GHz scan, no extended frequencies.
..................................................................................................................................................................................................................................................

 

[John]

.... and here's the RHC scan for 40.5°
.......................................................................................................................................................................................................................

 

[Channel Hopper]

Thanks G, what connection is needed to connect to them.

This should help. There was a similar thread on this forum dating back to the new millennium, but there were a number of post deletions two years ago that could not be recovered.

Polor Rotor control? - Ricks Satellite Wildfeed and Backhaul Forum

 

[blademedia]

This should help. There was a similar thread on this forum dating back to the new millennium, but there were a number of post deletions two years ago that could not be recovered.

Polor Rotor control? - Ricks Satellite Wildfeed and Backhaul Forum

Thanks but, my Question was to do with the connection below, the answer is I don't need anything, the connector below is a crimp connection for joining two/more wires

 

[s-band]

Thanks, John. I compared my results to yours. Mine, with Zinwell and AVC, are a dB or 2 lower. However, with Co-Rotor some TPs were a dB or so stronger than yours but only when the skew was optimised (a dB or so lower when not optimised). Do you get any improvement tweaking the skew per TP? Whilst I had the focus at phase centre on the feed, I did not have the scalar optimised.

Looking through my results, I was using blindscan 1 vs. your BS2. Below is a Crazyscan output from a BS2 scan using the Chaparral 17k LNB with the co-rotor (the set-up I had in 1990ish)

Oh, the cursed 22kHz bit me again. I spent ages trying to work out what was wrong with all the WR229 LNBs! EBSPro defaults to 22k on for C band grrr.

[SATTYPE]
1=0380
2=
[DVB]
0=46
1=3627,H,2787,35,8PSK
2=3641,H,2787,35,8PSK
3=3645,H,2533,34,QPSK
4=3652,H,3998,56,QPSK
5=3667,H,3749,34,8PSK
6=3672,H,3749,34,8PSK
7=3682,H,3029,78,QPSK
8=3695,H,2962,34,NBC_QPSK
9=3723,H,13300,56,8PSK
10=3736,H,7398,78,QPSK
11=3763,H,29990,56,8PSK
12=3803,H,27490,78,QPSK
13=3843,H,29990,89,8PSK
14=3866,H,2221,78,QPSK
15=3870,H,3749,56,8PSK
16=3875,H,3702,34,QPSK
17=3887,H,3659,34,8PSK
18=3891,H,2998,56,8PSK
19=3907,H,2387,56,8PSK
20=3910,H,2455,34,8PSK
21=3915,H,5828,23,8PSK
22=3923,H,6998,34,8PSK
23=3935,H,8877,34,QPSK
24=3980,H,21595,34,8PSK
25=3999,H,3749,34,8PSK
26=4004,H,3579,56,NBC_QPSK
27=4012,H,9827,34,8PSK
28=4025,H,12830,34,8PSK
29=4038,H,1480,34,32APSK
30=4043,H,1836,34,8PSK
31=4054,H,7498,35,8PSK
32=4066,H,12000,89,8PSK
33=4079,H,3749,34,8PSK
34=4086,H,4441,35,8PSK
35=4094,H,4343,34,8PSK
36=4104,H,4698,35,8PSK
37=4111,H,3749,34,8PSK
38=4121,H,2399,23,8PSK
39=4125,H,4249,34,8PSK
40=4132,H,2479,34,QPSK
41=4137,H,4398,34,QPSK
42=4144,H,2570,78,QPSK
43=4161,H,7498,23,NBC_QPSK
44=4172,H,5598,56,NBC_QPSK
45=4183,H,4998,34,8PSK
46=4194,H,5615,12,NBC_QPSK
[SATTYPE]
1=0380
2=
[DVB]
0=40
1=3629,V,2169,34,QPSK
2=3636,V,605,?
3=3641,V,2665,34,QPSK
4=3648,V,6665,34,QPSK
5=3667,V,2221,56,QPSK
6=3684,V,3749,34,8PSK
7=3694,V,5178,34,QPSK
8=3699,V,2199,34,QPSK
9=3723,V,29990,56,8PSK
10=3763,V,29990,56,8PSK
11=3803,V,29990,56,8PSK
12=3830,V,6141,78,QPSK
13=3835,V,2082,34,8PSK
14=3846,V,9598,45,NBC_QPSK
15=3854,V,2169,34,QPSK
16=3858,V,4798,34,8PSK
17=3883,V,26650,56,QPSK
18=3920,V,19995,35,NBC_QPSK
19=3938,V,4699,23,QPSK
20=3960,V,1258,78,QPSK
21=3972,V,1999,56,8PSK
22=3987,V,8644,34,QPSK
23=4010,V,9237,34,8PSK
24=4021,V,3199,34,8PSK
25=4028,V,7998,34,8PSK
26=4040,V,4439,78,QPSK
27=4046,V,5898,56,8PSK
28=4054,V,5898,23,QPSK
29=4065,V,12500,34,8PSK
30=4087,V,1679,56,NBC_QPSK
31=4094,V,4343,34,8PSK
32=4100,V,6110,34,QPSK
33=4119,V,2959,34,QPSK
34=4130,V,3843,78,QPSK
35=4136,V,1049,56,8PSK
36=4139,V,4165,23,8PSK
37=4151,V,3279,56,QPSK
38=4168,V,18390,23,8PSK
39=4187,V,11500,34,QPSK
40=4196,V,2959,56,QPSK

 

[moonbase]

...Oh, the cursed 22kHz bit me again. I spent ages trying to work out what was wrong with all the WR229 LNBs! EBSPro defaults to 22k on for C band...

@s-band

Would you please be able to explain in a little more detail the 22khz issue with the WR229 flange LNB's on C Band with EBS Pro and is it global to all versions of EBS Pro and all WR229 flange LNB's?

Thx

 

[s-band]

@s-band

Would you please be able to explain in a little more detail the 22khz issue with the WR229 flange LNB's on C Band with EBS Pro and is it global to all versions of EBS Pro and all WR229 flange LNB's?

Thx

The 22kHz tone is not filtered out on any of the WR229 LNBs that I have. See here for more detail Norsat 3220 C band LNB Warning
It's nothing to do with the flange, it is just that the LNBFs must have better supply filtering.
The default setting for EBSPro C band LNBs is to switch the 22k on. I checked and it does it on V14 & V16. Crazyscan does the same but the 22k check box is more obvious when selecting LNB type.

 

[moonbase]

The 22kHz tone is not filtered out on any of the WR229 LNBs that I have. See here for more detail Norsat 3220 C band LNB Warning
It's nothing to do with the flange, it is just that the LNBFs must have better supply filtering.
The default setting for EBSPro C band LNBs is to switch the 22k on. I checked and it does it on V14 & V16. Crazyscan does the same but the 22k check box is more obvious when selecting LNB type.

Thank you for the quick reply and explanation.

Rgds

 

[John]

Thanks, John. I compared my results to yours. Mine, with Zinwell and AVC, are a dB or 2 lower. However, with Co-Rotor some TPs were a dB or so stronger than yours but only when the skew was optimised (a dB or so lower when not optimised). Do you get any improvement tweaking the skew per TP? Whilst I had the focus at phase centre on the feed, I did not have the scalar optimised.

Looking through my results, I was using blindscan 1 vs. your BS2. Below is a Crazyscan output from a BS2 scan using the Chaparral 17k LNB with the co-rotor (the set-up I had in 1990ish)

Oh, the cursed 22kHz bit me again. I spent ages trying to work out what was wrong with all the WR229 LNBs! EBSPro defaults to 22k on for C band grrr.

[SATTYPE]
1=0380
2=
[DVB]
0=46
1=3627,H,2787,35,8PSK
2=3641,H,2787,35,8PSK
3=3645,H,2533,34,QPSK
4=3652,H,3998,56,QPSK
5=3667,H,3749,34,8PSK
6=3672,H,3749,34,8PSK
7=3682,H,3029,78,QPSK
8=3695,H,2962,34,NBC_QPSK
9=3723,H,13300,56,8PSK
10=3736,H,7398,78,QPSK
11=3763,H,29990,56,8PSK
12=3803,H,27490,78,QPSK
13=3843,H,29990,89,8PSK
14=3866,H,2221,78,QPSK
15=3870,H,3749,56,8PSK
16=3875,H,3702,34,QPSK
17=3887,H,3659,34,8PSK
18=3891,H,2998,56,8PSK
19=3907,H,2387,56,8PSK
20=3910,H,2455,34,8PSK
21=3915,H,5828,23,8PSK
22=3923,H,6998,34,8PSK
23=3935,H,8877,34,QPSK
24=3980,H,21595,34,8PSK
25=3999,H,3749,34,8PSK
26=4004,H,3579,56,NBC_QPSK
27=4012,H,9827,34,8PSK
28=4025,H,12830,34,8PSK
29=4038,H,1480,34,32APSK
30=4043,H,1836,34,8PSK
31=4054,H,7498,35,8PSK
32=4066,H,12000,89,8PSK
33=4079,H,3749,34,8PSK
34=4086,H,4441,35,8PSK
35=4094,H,4343,34,8PSK
36=4104,H,4698,35,8PSK
37=4111,H,3749,34,8PSK
38=4121,H,2399,23,8PSK
39=4125,H,4249,34,8PSK
40=4132,H,2479,34,QPSK
41=4137,H,4398,34,QPSK
42=4144,H,2570,78,QPSK
43=4161,H,7498,23,NBC_QPSK
44=4172,H,5598,56,NBC_QPSK
45=4183,H,4998,34,8PSK
46=4194,H,5615,12,NBC_QPSK
[SATTYPE]
1=0380
2=
[DVB]
0=40
1=3629,V,2169,34,QPSK
2=3636,V,605,?
3=3641,V,2665,34,QPSK
4=3648,V,6665,34,QPSK
5=3667,V,2221,56,QPSK
6=3684,V,3749,34,8PSK
7=3694,V,5178,34,QPSK
8=3699,V,2199,34,QPSK
9=3723,V,29990,56,8PSK
10=3763,V,29990,56,8PSK
11=3803,V,29990,56,8PSK
12=3830,V,6141,78,QPSK
13=3835,V,2082,34,8PSK
14=3846,V,9598,45,NBC_QPSK
15=3854,V,2169,34,QPSK
16=3858,V,4798,34,8PSK
17=3883,V,26650,56,QPSK
18=3920,V,19995,35,NBC_QPSK
19=3938,V,4699,23,QPSK
20=3960,V,1258,78,QPSK
21=3972,V,1999,56,8PSK
22=3987,V,8644,34,QPSK
23=4010,V,9237,34,8PSK
24=4021,V,3199,34,8PSK
25=4028,V,7998,34,8PSK
26=4040,V,4439,78,QPSK
27=4046,V,5898,56,8PSK
28=4054,V,5898,23,QPSK
29=4065,V,12500,34,8PSK
30=4087,V,1679,56,NBC_QPSK
31=4094,V,4343,34,8PSK
32=4100,V,6110,34,QPSK
33=4119,V,2959,34,QPSK
34=4130,V,3843,78,QPSK
35=4136,V,1049,56,8PSK
36=4139,V,4165,23,8PSK
37=4151,V,3279,56,QPSK
38=4168,V,18390,23,8PSK
39=4187,V,11500,34,QPSK
40=4196,V,2959,56,QPSK

Interesting G, i just changed to BS1 @ 2MHz steps and the Tp count was lower. Went back to BS2 and the count went up by two Tp's --- all in the space of three mins or so.
I set up my Cband scans to "Custom" which enables me to scan without the 22k.
I'll just try a scan with 22k running and also different supply volts to this 8000RI and see if i spot anything happening.

 

[John]

Interesting G, i just changed to BS1 @ 2MHz steps and the Tp count was lower. Went back to BS2 and the count went up by two Tp's --- all in the space of three mins or so.
I set up my Cband scans to "Custom" which enables me to scan without the 22k.
I'll just try a scan with 22k running and also different supply volts to this 8000RI and see if i spot anything happening.

@s-band ..... using my 6983 card same as yours, just tried a few combinations for 22k on or off, or 13/18 volt supplies and it made no difference to the 8000RI's performance .
I'll just transfer the feed across to the other pc with the 6903 card in it and see what the difference is from the 6983.

 

[John]

@s-band ..... using my 6983 card same as yours, just tried a few combinations for 22k on or off, or 13/18 volt supplies and it made no difference to the 8000RI's performance .
I'll just transfer the feed across to the other pc with the 6903 card in it and see what the difference is from the 6983.

Nah, the 6983 card has the edge over the 6903.

 

[John]

@s-band said --- >>Do you get any improvement tweaking the skew per TP?<<
If i'm doing a complete band scan of RHC let's say, i pick a frequency around mid band and using the analyser with peak hold selected, fine tune AZ / EL / Skew for best C/N with that freq selected and press go for a scan of the whole band. If i was just interested in a certain frequency i would set a tight span on the analyser of around 50MHz, depending on the bandwidth of the observed signal and tune the dish for max C/N or least interference from a neighboring sat. Iv'e found that one skew dosn't fit all lol.

 

[s-band]

Interesting G, i just changed to BS1 @ 2MHz steps and the Tp count was lower. Went back to BS2 and the count went up by two Tp's --- all in the space of three mins or so.
I set up my Cband scans to "Custom" which enables me to scan without the 22k.
I'll just try a scan with 22k running and also different supply volts to this 8000RI and see if i spot anything happening.

When things are close to threshold or close spaced there is some randomness in the detections. I find that no 2 sequential scans are the same most of the time.

@s-band ..... using my 6983 card same as yours, just tried a few combinations for 22k on or off, or 13/18 volt supplies and it made no difference to the 8000RI's performance .
I'll just transfer the feed across to the other pc with the 6903 card in it and see what the difference is from the 6983.

I didn't try switching voltage to see if it cleaned it up. The 22k problem was the same on a 6903 for me but I have not done a comparison of detection between the 2 cards.

@s-band said --- >>Do you get any improvement tweaking the skew per TP?<<
If i'm doing a complete band scan of RHC let's say, i pick a frequency around mid band and using the analyser with peak hold selected, fine tune AZ / EL / Skew for best C/N with that freq selected and press go for a scan of the whole band. If i was just interested in a certain frequency i would set a tight span on the analyser of around 50MHz, depending on the bandwidth of the observed signal and tune the dish for max C/N or least interference from a neighboring sat. Iv'e found that one skew dosn't fit all lol.

Thanks, as I thought. The physical length needed for 90 degrees electrical alters with frequency so the opposite polarity nulling will alter with relatively small frequency changes.

 

[John]

>> I find that no 2 sequential scans are the same most of the time.<<

Totally agree G.

Is there a particular difficult frequency on 40.5° W that we can do a quick comparison on ?

 

[Channel Hopper]

Thanks but, my Question was to do with the connection below, the answer is I don't need anything, the connector below is a crimp connection for joining two/more wires

They come with every mechanical polariser I've ever installed (some are twins, some triples).

The link was to provide a circuit design if you don't have a receiver with fine stepper control, and wish to build your own from Arduino/Pi gubbins.

 

[s-band]

CH, I like the controller linked from your post: N0QBH Free to Air Satellite PIC Projects I can't work out what the pulse range is though as my co-rotor needs 0.3ms to 2.5ms to cover the full range.

Totally agree G.

Is there a particular difficult frequency on 40.5° W that we can do a quick comparison on ?

I'm not sure we can use just one frequency unless it is a beacon but we need a different sat. as 40.5 is slant linear polarised. 2 of my scans using the Z +AVC, done 4 hours apart, had a couple of dB differences on some TPs. When I compared Ku LNBs I took the average of all TPs. Perhaps that's the way to do it. Given that the skew has to be optimised a few times, it would be a real pain to do! It doesn't matter if the total number of TPs are different as long as there are a lot of them. We also need to do it at the same time.

I went through my figures again and I'm questioning my earlier summary. Just staring at figures is not an ideal way to compare results! Another reason to try to distill all results into a couple of numbers. The Zinwell + AVC actually has the edge except on a couple of frequencies where it was a couple of dB below the rotor. It must have been those I looked at. For some reason, the corotor is bad (-4-5 dB ) at 3627L and generally at the bottom of the band (left) with all LNBs is worse. Right is ok and the noise figures of all LNBs are better at that end of the band, so I think it's a feed thing. Maybe I set the skew wrong for left.

Generally your results were +0.5dB to 1dB higher than my best with a couple of exceptions where mine were 2dB over yours. We can't be sure what's happening at the other end of all TPs and measuring down to sub-dB is questionable.

Going back to your thread, BM, it would be interesting to compare your rotor with an LNBF on a linear satellite.

 

[blademedia]

The link was to provide a circuit design if you don't have a receiver with fine stepper control, and wish to build your own from Arduino/Pi gubbins.

Thanks , I wondered why it had nothing to do with the connector question, I'm waiting delivery of a controller.