On Sat, Jan 8, 2022 at 02:14 AM, Philip Robinson wrote:

Yes, i did restart the tellicast clients 

Philip,

I GIVE UP: You simply tell us the TelliCast client is broken as it is unable to log on D:.
Go on with your own "next step" of deleting all TelliCast stuff on C:. But don't blame
me if things don't work as expected anymore: "Wer nicht hören will muss fühlen!"

Regards,
Ernst

On Sat, Jan 8, 2022 at 01:39 AM, Philip Robinson wrote:

I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\

Philip,

after you make changes in the client.ini you have to restart the client. At least you say now "you are sure you TRIED". But if you actually DID the change and restarted the client and it still does not log on D: (whether with or whitout the ">>"), then you are telling us BS again ...

Ernst

On Sat, Jan 8, 2022 at 01:39 AM, Philip Robinson wrote:

I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\

Philip,

after you make changes in the client.ini you have to restart the client. At least you say now "you are sure you TRIED". But if you actually DID the change and restarted the client and it still does not log on D: (whether with or whitout the ">>"), then you are telling us BS again ...

Ernst

Ernst/Thorsten

My running clients are all on Drive D: and all my target paths point there ( as i tried unfailing to explain). I should therefore not need any of those C: EUMETCast clients, folders  etc etc now that I have all my EUMETCast running clients , folders etc are on DRIVE D: 

However I was getting the strange part that my logs were being directed  to my C:drive Logs folder.

I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\

Of course if that works i will do the same for the bas and hvs-2 log paths

I will try later

thanks

Philip

------ Original Message ------

From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>

To: MSG-1@groups.io

Sent: 08/01/2022 08:29:35

Subject: Re: [MSG-1] FY-3D

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:

My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.

Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Virus-free. www.avg.com

Ernst/Thorsten

My running clients are all on Drive D: and all my target paths point there ( as i tried unfailing to explain). I should therefore not need any of those C: EUMETCast clients, folders  etc etc now that I have all my EUMETCast running clients , folders etc are on DRIVE D: 

However I was getting the strange part that my logs were being directed  to my C:drive Logs folder.

I am sure i had tried changing the target path as that would make sense log_file=>>D:\EUMETCast\logs\recv_hvs-1.log.but it did not work. But may be that I omitted the 2 forward arrows before the D:\

Of course if that works i will do the same for the bas and hvs-2 log paths

I will try later

thanks

Philip

------ Original Message ------

From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...>

To: MSG-1@groups.io

Sent: 08/01/2022 08:29:35

Subject: Re: [MSG-1] FY-3D

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:

My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.

Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Virus-free. www.avg.com

On Fri, Jan 7, 2022 at 11:12 AM, Philip Robinson wrote:

My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.

Philip,

it seems you still don't know whether your clients are on drive C: or drive D: as you installed them on both drives (that's what you said).
If what Thorsten just posted works for you, then the running client is probably started on C:. In this case your next job will complete your mess ...
Be careful.

Ernst

Hi all

I now have FY-3d data files   the .hdf files are now being received  in my E1H-RDS2 folder

Well what happened?

I know i am going to get a told you so from Ernst.

The problem has occurred because a few years ago i set up all the EUMETCAST stuff on my C:drive. Something must have happened at some stage that i then installed again the whole EUMETCast stuff on my D: drive ( the same computer, but it was not an external drive). So therefore i had 2 duplicated lots of EUMETCAST on my computer.

I only use the D:Drive for my satellite reception and filing work

I then checked again my cast-client_hvs-1.ini folder and the  license_file  path and the channels_file path were pointed to the C:Drive. I altered those paths so they were now pointed to my D:drive

Just doing that alteration made a difference to the hvs_1 log and now when i check the log I am only receive hvs-1 data ( no BAS data in there now) and that includes receiving  the E1H-RDS-2 and E1H-RDS-1 data

I am not  totally sure why doing that has corrected everything  but the lesson to be learnt to newcomers to this hobby( and this is why i am trying to explain whats happened)  is ensure with EUMETCast setting up  that all the folders ...configs etc etc  must go on the same drive. 

I still have  data yet in EUMETCastview, i thought i would have now, but at least i know i have the .hdf data files received and  are now piling in to my computer. I can work it out from there I hope

My next job will to be delete all my  EUMETCast folders on my C:Drive so I do not get in such a mess. Also let OPS know that I am all sorted now. Then to sort out getting my FY3D data in to EUMETCastview.

Ernst

You know your stuff and i am very grateful that you put up with my questions, and you are always there to willingly help others as well

Ernst, David, Graham and Christian

thanks for your help

Philip

------ Original Message ------

From: "Philip Robinson" <philip6060@...>

To: "MSG-1@groups.io" <MSG-1@groups.io>

Sent: 07/01/2022 11:25:45

Subject: Re: [MSG-1] FY-3D

Ernst

I know I need to tidy up the data section that  I receive.

And as far as the mixture of bas and hvs-1 channels in the hvs-1 logfile I don’t understand why that’s happening. I seem to have set up the tellicasts correctly and I do receive bas files  in one of  MSG DataManagerand, hvs-1 files in the other MSGDataManager.

I am awaiting a reply from Debbie who is checking that the EARS services have been permitted

Regards

Philip

 

Sent from Mail for Windows

 

From: Ernst Lobsiger via groups.io
Sent: 07 January 2022 11:17
To: MSG-1@groups.io
Subject: Re: [MSG-1] FY-3D

 

Philip,

this is your home work:

1) You must find out why you have this mixture of channels in the hvs-1 log file. There must be something wrong !!!
2) In your own interest in EOP you should only tick data that you know you can and will process (IASI, ASCAT ???).

Ernst

 

Virus-free. www.avg.com

Ernst

I know I need to tidy up the data section that  I receive.

And as far as the mixture of bas and hvs-1 channels in the hvs-1 logfile I don’t understand why that’s happening. I seem to have set up the tellicasts correctly and I do receive bas files  in one of  MSG DataManagerand, hvs-1 files in the other MSGDataManager.

I am awaiting a reply from Debbie who is checking that the EARS services have been permitted

Regards

Philip

 

Sent from Mail for Windows

 

From: Ernst Lobsiger via groups.io
Sent: 07 January 2022 11:17
To: MSG-1@groups.io
Subject: Re: [MSG-1] FY-3D

 

Philip,

this is your home work:

1) You must find out why you have this mixture of channels in the hvs-1 log file. There must be something wrong !!!
2) In your own interest in EOP you should only tick data that you know you can and will process (IASI, ASCAT ???).

Ernst

 

Philip,

it seems indeed you have ticked what you need. The problem of EOP is that it's hard to find, what you have to tick if you compare with the EUMETCast channels and PID lists. And the EOP output and confirmation (mails ?) also differs consirerably if you tick additional thing. Unless there is some accidentally set PID filter in your receiver chain blocking you, it's about time to ask OPS for help.

Regards,
Ernst

Philip,

way down this thread (#32530) I posted what you have to tick in EOP. It seems you have ticked about everything you cannot use but I must assume you have not ticked EARS-MERSI under this tab:

Regional Data Services
RDS-EARS
EARS-ATOVS
EARS-AVHRR
EARS-ASCAT

Ernst