42.0°E Türksat 5B

Thanks jaes

Here is my VERTICAL SCAN on 1.2m KATHREIN CAS 120... nothing here too.

FYI: Data toppic from this position in extanded range, here. Reports from strannik, here.

PS: I will re-name to "42.0°E Türksat 5B" soon.

private data

Quote from jaes

Question - - has anybody got any idea what the lnbf product for 13.75 - 14.5GHz is intended for use with ? .. ie: which satellite / data / tv / ? etc

To monitor the TX band, maybe? but I'd expect that to be a pro product like http://www.xmwinc.com/_download.php?…are%20available as mentioned by femi

I had a look at 42E yesterday using an SMW Q-PLL type R which has a poor NF (3dB @13.4 to 7dB @13.65) I could not see anything from 42E using the analyser in a narrow & wide bandwidths. The beacon on 13401 on 31E was at its normal level.

Those who have installed this Ku lnb extender try it with Strannik's app, IQmonitor; it would be a confirmation or a refutation of what Strannik has achieved.

I can't check the upper band because I haven't installed this type of lnb on the antenna.

Quote from satesco

Those who have installed this Ku lnb extender try it with Strannik's app, IQmonitor; it would be a confirmation or a refutation of what Strannik has achieved.

I can't check the upper band because I haven't installed this type of lnb on the antenna.

I am not in a position to use IQMonitor at the moment. However, it is possible to detect signals way below DVB threshold using the spectrum analyser and I saw nothing.

My understanding of the method used by strannik is that there would still be a strong response at the fundamental which is

10600+((13418-10600)/3) = 11539.3MHz.

There is a feed listed at 11540H on the east beam of Turksat 3A There are a few other feeds listed here around that frequency including one for BRT on 11548H 2960 5/6 which has similar parameters to the one mentioned by strannik. This will not be very strong in UK but will be at a high level further east. satesco Have you seen or can you see anything around that frequency?

Quote from s-band

...My understanding of the method used by strannik is that there would still be a strong response at the fundamental which is

10600+((13418-10600)/3) = 11539.3MHz.

There is a feed listed at 11540H on the east beam of Turksat 3A There are a few other feeds listed here around that frequency including one for BRT on 11548H 2960 5/6 which has similar parameters to the one mentioned by strannik. ...

Are you thinking that the frequency in upper Ku reported by strannik is not a true upper Ku frequency but it is a "ghost" or a "reflection" from the normal Ku East beam frequency of 11540MHz?

Quote from jaes

I have been monitoring this satellites reported upper Extended Ku capability for quite a while now from my location 17k North of the City of Nottingham UK with a dedicated 13.4 - 13.65GHz lnbf and a 1.2 mtr Gibertini antenna...

The group buy of custom L.O. upper Ku LNBF's we bought from China have L.O. of 11.8GHz with frequency range of 12,75GHz to 13,75GHz.

Are you using a different/modified LNB and not the Chinese one we bought?

...and mine is the right one from that picture...

Quote from moonbase

Are you thinking that the frequency in upper Ku reported by strannik is not a true upper Ku frequency but it is a "ghost" or a "reflection" from the normal Ku East beam frequency of 11540MHz?

Sort of. It's just terminology. The 3LO response at 2818MHz is technically the "unwanted" response that is being used by strannik. The card is actually tuned to 939.3MHz which is the main response which will be 20dB or more higher than the response at 2818MHz.

There's no reason that strannik's way could not be made to work. It needs a high pass or band pass filter between the card and the LNB to get rid of f_wanted/3 responses, including the excess noise from the lower part of the band. An IF amplifier after the filter might also be useful.

I am not sure that any of the standard LNBs (10.6GHz LO) will work very well above 13GHz though. The SMW single band 12.25-12.75 11.3LO that I use is quite good (<2.5dB NF after small tweak). However, I also tried an NJRC one of similar spec and that did not work above about 13.2GHz.

According to the pictures, when using a Chinese LNB, there is mutual interference in it (even though NIT is said to contain KU-ext frequencies)

Post

RE: 07.0°W Nilesat 301

LNB probably uses inverse mode for LOF

satellitescommunity.de/index.php?attachment/86171/

You should try on a satellite where there are only a few transponders in Hihg-Band.

Can you take a photo of the label from the LNB? Is it this one ?

but if you compare these pictures, it seems that the LNB is 9750/10600 and not 12800

EnoSat

December 5, 2022 at 7:46 PM

EnoSat:

Eher werden Märchen wahr, als Transponderdaten einer NIT. Die wenigen reellen befinden sich u.a. auf 19,2°E

Fairy tales come true sooner than transponder data from a NIT. The few real ones are located at 19.2°E, among others 

Weder auf 42°E, noch auf 30,9°E gibt von meinem Standort (1,8 m) ein verwertbares Signal.

Die manuell versuchten Feedreports zeigten keinerlei Anzeichen einer bestimmten Modulation.

Neither at 42°E nor at 30.9°E is there a usable signal from my location (1,8 m). 

The manually attempted feed reports showed no signs of any particular modulation.

Quote from femi

EnoSat:

Eher werden Märchen wahr, als Transponderdaten einer NIT. Die wenigen reellen befinden sich u.a. auf 19,2°E

Fairy tales come true sooner than transponder data from a NIT. The few real ones are located at 19.2°E, among others 

80 percent in Ku have the correct NIT (if entered)

13030-14030

13750-14500

vertical nothing lockable on my location...

Quote from femi

13750-14500

I think that this may be the image of:

12800 - 1622.5 = 11177.5 which, allowing for DRO error, is close to 11180

If you look at 11180H, is the parameter "Inv" showing as "On"? The image will be frequency inverted compared to the wanted signal.

If you look the picture, Inv showing as off.

But if you are right, I must ask why only this one transponder?

Quote from femi

If you look the picture, Inv showing as off.

I meant that if you look at what I think is the image, 11180H, using a standard LNB, and you see Inv is "on" for 11180H then it is likely that it actually is the image of the one you see on 14422. It's unlikely that there really is a signal there as that is not within the Turksat band.

Quote from femi

But if you are right, I must ask why only this one transponder?

Good question It may have something to do with the ratio of the 11180 signal at the image to the noise from the front end at the wanted frequency (14422). That noise should be quite high and may mask a lot of things. I note that 14422 is at a point where the overall noise is low which might be expected as it is at the top of the LNBs's range. If you look above 14422, do you see anything that matches the lower frequencies (below 11180)?

You do have some responses in your vertical plot. Checking 14071V, there is something at 11526V 2222 3/4 which is close to the predicted image of 11529. However, the parameters shown by IQ Monitor do not match but it is below lock.

Edit:

Looking at this, there are no signals until you get down to an IF of 1000MHz by which time the wanted band noise is high so the image ratio may be better. There are some above 1700MHz but they are off the Ext Ku scan.

Another thing is that there probably isn't anything to see above 13.65GHz apart from uplinks, some very tightly controlled beams from TDRSS and maybe some old Russian satellites. I did scan with a wide band LNA/feed some time ago and found nothing apart from local RADAR.