Philip,

I also just noticed that the entry I posted further down

# FY-3D, MERSI-2 (EARS)
[channel]
name=E1H-RDS-2
target_directory=/opt/E1H-RDS-2

might not be enoug in your case. It assumes some special general settings in the cast-client_hvs-1.ini file.

Can you post the non working entry you made for channel E1H-RDS-2 and an entry of a channel that works for you?
Have you made the entry for E1H-RDS-2 at the very bottom (again this bottom!)  AFTER  a * default channels entry?
In the latter case you will find your files in the default directory. You almost NEVER need a default directory anyway!

Regards,
Ernst

Philip,

there is more than that. In your cast-client_hvs-1.ini you indicate a tmp_directory that most probably points to C: where your client lives.
In your cast-client-channels_hvs-1.ini you use tmp_directories on D: (they must be on the same drive as your received data, D: is OK!)

Then in cast-client-channels_hvs-1.ini you also have an entry

[channel]
name =E2H-TPG-1
receive_buffer_size=8000000
target_directory=D:\EUMETCast\received\hvs-1\E2H-TPG-1
tmp_directory=D:\EUMETCast\tmp\hvs-1

which clearly sounds like a channel of hvs-2.

Regards,
Ernst

P.S. In cast-client_hvs-1.ini (that you should not publish with your user name and key!) you also have an entry

allow_execute=1

That's the first thing I normally stop. Most Windows users will have it, as they don't read manuals though ...

Philip,

the way you work this will never fly! You have again posted twice your secret login name and key. YES twice because your cast-client-channels_hvs-1.ini is in fact the same as cast-client_hvs-1.ini.
The log file you publish has entries from HVS-1 as well as Basic Service like DWDSAT and Channel_1 . NO idea how you manage to do that (your basic client seems to log to the hvs-1 log file).

Then of course it's EARS  that has not always files like Meteosat-11. But there is also timeliness (this is not direct readout). My last FY-3D file came in 17:12 UTC.


Ernst

Philip,

the way you work this will never fly! You have again posted twice your secret login name and key. YES twice because your cast-client-channels_hvs-1.ini is in fact the same as cast-client_hvs-1.ini.
The log file you publish has entries from HVS-1 as well as Basic Service like DWDSAT and Channel_1 . NO idea how you manage to do that (your basic client seems to log to the hvs-1 log file).

Then of course it's EARS  that has not always files like Meteosat-11. But there is also timeliness (this is not direct readout). My last FY-3D file came in 17:12 UTC.


Ernst

Hi

I have attached the ini. files i meant to attach earlier. (with no login name and key, temporary deleted for this attachment)

I still have no data from E1H-RDS-2

Is there anyone out there using just windows10 and receiving data succesfully from FY3D, and using those files  in EUMETCastview

I would love to know there settings

If not I may have to give up the idea of using FY3D in  EUMETCastview

I don`t normally give up, but i have run out of ideas

regards

Philip

use philip6060@....If you would you like to send  a private message 

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

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

To: MSG-1@groups.io

Sent: 06/01/2022 17:49:34

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

Philip,

the way you work this will never fly! You have again posted twice your secret login name and key. YES twice because your cast-client-channels_hvs-1.ini is in fact the same as cast-client_hvs-1.ini.
The log file you publish has entries from HVS-1 as well as Basic Service like DWDSAT and Channel_1 . NO idea how you manage to do that (your basic client seems to log to the hvs-1 log file).

Then of course it's EARS  that has not always files like Meteosat-11. But there is also timeliness (this is not direct readout). My last FY-3D file came in 17:12 UTC.


Ernst

Virus-free. www.avg.com

Yes, and clearly there are others. No point in using Eumetcastview until you are getting the relevant hdf files in your folder. Then you add that directory to the viewer selector. 

Cheers

James

On 6 Jan 2022, at 22:56, Philip Robinson <philip6060@...> wrote:



Hi

I have attached the ini. files i meant to attach earlier. (with no login name and key, temporary deleted for this attachment)

I still have no data from E1H-RDS-2

Is there anyone out there using just windows10 and receiving data succesfully from FY3D, and using those files  in EUMETCastview

I would love to know there settings

If not I may have to give up the idea of using FY3D in  EUMETCastview

I don`t normally give up, but i have run out of ideas

regards

Philip

use philip6060@....If you would you like to send  a private message 

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

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

To: MSG-1@groups.io

Sent: 06/01/2022 17:49:34

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

Philip,

the way you work this will never fly! You have again posted twice your secret login name and key. YES twice because your cast-client-channels_hvs-1.ini is in fact the same as cast-client_hvs-1.ini.
The log file you publish has entries from HVS-1 as well as Basic Service like DWDSAT and Channel_1 . NO idea how you manage to do that (your basic client seems to log to the hvs-1 log file).

Then of course it's EARS  that has not always files like Meteosat-11. But there is also timeliness (this is not direct readout). My last FY-3D file came in 17:12 UTC.


Ernst

Virus-free. www.avg.com

Ernst

Here they are attached

Many thanks for your help.

I have hardly touched the system configurations for well over a year because i have been receiving lots of data ok for Davids applications. I just thought i would see how good the FY-3D data is and thats where i have now come unstuck.

regards

It must be a tellicast configuration.. but ????

Philip

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

From: "James Brown" <satellite@...>

To: MSG-1@groups.io

Sent: 07/01/2022 08:45:02

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

Yes, and clearly there are others. No point in using Eumetcastview until you are getting the relevant hdf files in your folder. Then you add that directory to the viewer selector. 

Cheers

James

On 6 Jan 2022, at 22:56, Philip Robinson <philip6060@...> wrote:



Hi

I have attached the ini. files i meant to attach earlier. (with no login name and key, temporary deleted for this attachment)

I still have no data from E1H-RDS-2

Is there anyone out there using just windows10 and receiving data succesfully from FY3D, and using those files  in EUMETCastview

I would love to know there settings

If not I may have to give up the idea of using FY3D in  EUMETCastview

I don`t normally give up, but i have run out of ideas

regards

Philip

use philip6060@....If you would you like to send  a private message 

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

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

To: MSG-1@groups.io

Sent: 06/01/2022 17:49:34

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

Philip,

the way you work this will never fly! You have again posted twice your secret login name and key. YES twice because your cast-client-channels_hvs-1.ini is in fact the same as cast-client_hvs-1.ini.
The log file you publish has entries from HVS-1 as well as Basic Service like DWDSAT and Channel_1 . NO idea how you manage to do that (your basic client seems to log to the hvs-1 log file).

Then of course it's EARS  that has not always files like Meteosat-11. But there is also timeliness (this is not direct readout). My last FY-3D file came in 17:12 UTC.


Ernst

Virus-free. www.avg.com

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