|
Re: Gibertini OP 125L
Ernst Lobsiger
Mads, Below my Triax TD 110 elevation rod. You can turn it with a http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment1.jpg http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment2.jpg http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment3.jpg Sorry Arne for the deep links :-) but Google knows them anyway ...
|
|
|
|
Re: Gibertini OP 125L
Mads Kristoffersen
Hi Ernst
Can you post a image of your special elevation rod? My system is out of business for the moment but maybe I have a chance putting it into service and I would love to have a better elevation-option on my Triax (TD-110). Regards Mads
|
|
|
|
Re: Gibertini OP 125L
Ernst Lobsiger
John,
The photo is attached to my first post of this topic :-). Bear in mind that the pole must be 55mm in diameter (minimum) but should rather be 75mm (optimum for the clamp and high wind loads). The antenna must be attached on top of the pole. If you mount it in front of a longer pole you will be very limited in elevation. I have not yet fine tuned my OP 125L antenna. Far too hot for antenna pointing experiments these days ... Regards, Ernst
|
|
|
|
Re: Gibertini OP 125L
geojohnt@...
Hello Ernst,
Sorry to hear about your problems - and more so that you are having them with a Gibertini dish.
I am hoping to upgrade my system this autumn and would have gone for a 1.25 m Gibertini dish instead of my 1 m dish 'standard dish.'
Somehow, Gibertinin dishes have the reputation of having the highest gain of 'same size dishes.'
I wonder if you could please send a photo of the dish/az/el pole fixing arrangement to my personal email address?
The 1 m (I think) Gibertini dish that EUMETSAT used for their EUMETCast Conference some years ago had a simple but robust looking mounting arrangement.
Best wishes,
John.
+++++++++++++++++++++
In a message dated 30/07/2018 20:07:24 GMT Standard Time, ernst.lobsiger@... writes:
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Ernst Lobsiger
David and Hugo I'am just back up and running with my new antenna. There seems quite some change The channel configuration file is sorted by IP and does not correspond to https://www.eumetsat.int/website/home/News/DAT_3942692.html I noticed PID 511 is gone on BAS T1 (probably long ago) but on the other hand There is a new EUMETCast CD image from today August 2nd 2018 on ftp.eumetsat.int. I'll install the new 2.14.4 client and see what I find out ... Cheers,
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
I've tried the 2.14.4 Windows client simply by replacing the .exe and .lic files, and seen no difference.
There are two new parameters: delay_channel_leave_time= will keep the multicast channel joined, needed only for multicast on WAN network, i.e. EUMETCast Terrestrial receive_buffer_size= sets the kernel receive buffer (in MB) for the specified channel, helps mitigate slow IO performance of the computer or high load conditions but they aren't documented in the program's Web Help, and the buffer had been set to 8000000 for all EUMETSAT channels. This leaves open the questions (a) is it bytes or megabytes (!), and (b) what is a reasonable value to use. I'd like to use 600+ MB for the HVS data but, as you hint, in a 32-bit system that might be a little limiting (if three Sentinel full-resolution files are sent at once). I have an outstanding query with EUMETSAT about this. Do you have these new per-channel parameters in Linux? In the Web help? Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
*Topic: *Planned data delay for Metop-A and Metop-B
I don't know whether this affects EUMETCast as well. Could just be US.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ *Topic: *Planned data delay for Metop-A and Metop-B *Date/TimeMessage Issued: *August 2, 2018, 1340Z *Satellite(s) Involved: *Metop-A, Metop-B *Instrument(s) Involved:*All Instruments *Product(s) Involved/Affected: *All products *Date/Time(UTC) of Initial Implementation:*August 2, 2018, 1300Z *Date/Time(UTC) of Expected End: *August 2, 2018, 2000Z *Details/Specifics of Change:*There will be an ongoing intrusive test to the D3 Line affecting Jason data which shares the same line as Metop from Svalbard and McMurdo to ESPC. Expect a data delay for Metop-A (M02) and Metop-B (M01) of approximately 7 hours. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Ernst Lobsiger
Hugo,
If you just receive TC there is *NO* reason to use amd64Bit. Until one year back I only used 32Bit Linux (kernel 4.9.0-3-i686-pae to use my 8GB of memory) on TC receivers. Some distros begin to slowly turn down the 32Bit support but Debian testing "buster" appearently is and will still be available as 32Bit software. I use amd64Bit because my receivers also run SNAP 4.0 to process Sentinel OLCI EFR images on the fly. So it was mostly curiosity on my side and I wanted to test the TBS-drivers under amd64Bit too. My multiarch receivers prooved surprisingly stable. Of course EUMETSAT should provide a full amd64Bit suite for TelliCast. The TC client could certainly benefit from the much better memory handling. But that's something EUMETSAT promised when they prepared to change to DVB-S2 years ago. So I do not expect that we get rid of the stone aged pcscd and etokend stuff anytime soon .. Cheers, Ernst
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Hugo
Ernst,
Because all the Tellicast software is 32bit , is there any reason why I should use a 64bit OS ? My receiving PC is only for receiving Eumetcast. grts, Hugo
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Hugo
Hello Ernst and Christian,
Thanks for the quick reply ... Yes it must be something with the 32bit USB subsystem. My OS before the crash was Debian 8 and I I didn't have any problems installing Tellicast. This time I choose Ubuntu 18.04. I'am going to read your 'how to' and will report back if I'am able to get it to work. I can always reinstall Debian on my system. I always wondered why Eumetcast must be encrypted. Every member of Europe is paying for it via taxes, and the 60 euro is only the cost of the dongle....Probably because it's Europe... And another thing, the Tellicast software should be open source ! :) Kind regards, Hugo
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Ernst Lobsiger
Hugo
The 32-Bit USB subsystem might be the problem: Have you resolved all the missing dependencies? Is pcscd and etokend running? Have you edited the etoken rules? I have not yet installed the latest TC client. Here is what I use for Debian and Devuan ... Cheers Ernst
|
|
|
|
Re: Tellicast client version 2.14.4 for Linux
Christian Peters
Hugo,
toggle quoted messageShow quoted text
I changed to 2.14.4-2 without any problems on Debian 9 stretch. You should ask Ernst for his installation documentation on 64 bit systems, maybe there are some useful hints what goes wrong. I think the EKU software/libs which seems to be still 32 bit code could make the trouble. Regards, Christian Am 01.08.18 um 23:59 schrieb Hugo:
Hello,
|
|
|
|
Tellicast client version 2.14.4 for Linux
Hugo
Hello,
A few days ago I had a hard drive crash on my tellicast receiving station. So I had to install a new OS ( Ubuntu 18.04.1 LTS) and the Tellicast software. I decided to use the latest version from the Eumetsat ftp site : version 2.14.4. However, I have problems with this version. I don't have anything in host_key_4. It should be something like host_key_4 = ****-****-****-**** (Aladdin EToken PRO) This means that I get a lot of 'missing key' in the log file. I do receive the channels SAF-Europe, SAF-Global, SAF-Africa and SAF-Americas. These channels are probably not encrypted and so I can receive them. Does anyone have any ideas ? grts, Hugo
|
|
|
|
Re: EUMETCastView on GNU/Linux
@lumyk
Hi Ernst,
Thanks for nice description. It was easy to follow your instructions and everything went completely smoothly. At the first sight EUMETCastView 1.4.0 runs quickly and without any visible problem - globe shows constantly ~60 paintGL calls/s. Built and launched on my main computer (with plenty of memory): $ cat /etc/lsb-release | grep DESC ; uname -a; lscpu | grep "Model name"; glxinfo | grep OpenGL | head -3 DISTRIB_DESCRIPTION="Linux Mint 18.3 Sylvia" Linux mentos 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Model name: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 970/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 384.130
|
|
|
|
R: [MSG-1] Tbs 6903 addtap.bat
Stefano Mina
Yes, good evening John. I was able to find the missing script that creates two second distinct receive network card. the script was found in a post blog of msg1 groups compiled by David. Run as administrator the program works, Tomorrow I want to test the program SR-text.exe to test the single RF entry.
Da: MSG-1@groups.io <MSG-1@groups.io> Per conto di seggins2000 via Groups.Io
Did you run addtap.bat as administrator? Regards John
From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of Stefano Mina via Groups.Io
Sent: 31 July 2018 11:39 To: MSG-1@groups.io Subject: [MSG-1] Tbs 6903 addtap.bat
Good morning, I installed the 6903 tbs, but I can not find the command file to install the second tap card. Inside the file bdadataex 1.1.4.9 does not exist.I only managed to start the dual commands to have two BDAdataex configuration instances, but on the second instance it lacks MPE-Filter option, and the second card does not appear in the network
|
|
|
|
Re: Gibertini OP 125L
Ernst,
toggle quoted messageShow quoted text
I feel sorry that you have so much trouble with the dish. But I am happy that you are up and running now. Actually my TP1 SNR is up to 15.4 dB during chilly night hours. Fine tuning is a challenge. I was sure to have the optimum. But sun - sat - collinearty told me that I was 0.4 degrees west. Tightening the eastwards screws of the pole mount a little to turn the dish a tininess east gave me +0.3 dB SNR. Thorsten
On Mon, Jul 30, 2018 at 09:07 PM, Ernst Lobsiger wrote:
|
|
|
|
Re: Tbs 6903 addtap.bat
seggins2000
Did you run addtap.bat as administrator? Regards John
From: MSG-1@groups.io <MSG-1@groups.io> On Behalf Of Stefano Mina via Groups.Io
Sent: 31 July 2018 11:39 To: MSG-1@groups.io Subject: [MSG-1] Tbs 6903 addtap.bat
Good morning, I installed the 6903 tbs, but I can not find the command file to install the second tap card. Inside the file bdadataex 1.1.4.9 does not exist.I only managed to start the dual commands to have two BDAdataex configuration instances, but on the second instance it lacks MPE-Filter option, and the second card does not appear in the network
|
|
|
|
R: [MSG-1] Tbs 6903 addtap.bat
Stefano Mina
Fixed the problem by myself with the following script retrieved in a David Taylor post on Msg1 groups
Da: MSG-1@groups.io <MSG-1@groups.io> Per conto di Stefano Mina via Groups.Io
Good morning, I installed the 6903 tbs, but I can not find the command file to install the second tap card. Inside the file bdadataex 1.14.9 does not exist.I only managed to start the dual commands to have two BDAdataex configuration instances, but on the second instance it lacks MPE-Filter option, and the second card does not appear in the network
|
|
|
|
Tbs 6903 addtap.bat
Stefano Mina
Good morning, I installed the 6903 tbs, but I can not find the command file to install the second tap card. Inside the file bdadataex 1.1.4.9 does not exist.I only managed to start the dual commands to have two BDAdataex configuration instances, but on the second instance it lacks MPE-Filter option, and the second card does not appear in the network
|
|
|
|
GOES 17 ABI Problem.
Douglas Deans
NOAA have published an update on efforts to resolve the cooling issue with GOES 17 ABI instrument.
Please see :- https://www.nesdis.noaa.gov/content/experts-moving-closer-resolving-troubles-noaas-goes-17-abi My interpretation is that it is not fixable but that a number of clever workarounds will limit the losses. VIS channels are of course unaffected. Regards. Douglas.
|
|
|
