Jump to content

EFB not updating REXe weather


Recommended Posts

Clive,

 

On the screenshot I can see that the METAR code on the REX screen is different than the METAR code on the EFB screen. Just to be sure, did you press the "Refresh" button already?

 

The timestamp (Observation time UTC) is taken from the METAR code. If the METAR code contains 1020Z then EFB will show 1020Z regardless of any other timestamp in REXe.

 

Which folder did you reference in the DisplayUnit settings?

Link to comment
Share on other sites

Urs

 

Yes I have already pressed the 'refresh button' but no change in EFB

 

I am pointing DP to the MetarXML folder.

 

The metar code will be different as REXe has updated but EFB has not. even after I had pressed the 'refresh button'

Link to comment
Share on other sites

Here's my theory, for what it's worth :lol:

 

In the MetarXMl folder for today I had the following files:

20120630_00Z

20120630_02Z

_04Z

_10Z

_14Z

_16Z

_ 18Z

_20Z

 

EFB was looking into the latest file (_20Z) for the latest weather, which is 1020Z in that file. No matter how often you hit 'refresh' in EFB, nothing will change as that is the latest metar in that file.

 

What REXe does; I think it updates a previous file, in this case it was the _10Z file which held more current metar date than _20Z. Internally REXe know this and hence the weather is up to date, but you will see time differences in EFB as EFB thinks that _20Z is the latest file and so would I :)

 

How did I find this out. I deleted all the files in the MetarXML folder, then restarted REXe. When I looked in the MetarXML folder the new file was the _10Z file. Weather was up to date in REXe and when I restarted EFB and checked the weather, it was also correct.

 

Well, that's my thoughts on this. I think once REXe has downloaded 8 files for that Date it starts over writing them. REXe knows that hence the weather is always current. I think users will see this but only after 8 hours of use of a third party program that accesses REXe for weather. Otherwise if you use just FSX and REXe you will never notice anything is wrong.

 

So 8 files with 3 hrs of updated data per file per day.

 

I'm probably talking a load of rubbish as I'm no programmer.

 

 

Any thoughts on this?

 

 

Clive

Link to comment
Share on other sites

I've left REXe running

 

I now have the _12Z file downloaded. SO my theory is slight out :lol: Only in I think you get 12 files per 24hrs and these are over written.

 

Also if you use 'historical weather' in REXe it is from what you have in your MetarXML folder only. SO you can't get weather from two month ago if you haven't downloaded it. Like you can do in other weather programs.

 

Now there are two files, EFB is not updating.

 

EFB data from _10Z

EGNJ 301750Z 25012KT 9999 SCT030 18/09 Q1005

 

REXe Data from the _12Z

EGNJ 301650Z 21017KT 9999 SCT040 19/11 Q1004

 

EFB is not reading the _12Z data even if I restart the DP

 

 

Changed EFB to 'Online from NOAA

EGNJ 301820Z 25011KT 9999 SCT030 17/10 Q1005

Link to comment
Share on other sites

Her's the Data from the _10Z

 

EGNJ 301650Z 21017KT 9999 SCT040 19/11 Q1004

EGNJ

2012-06-30T16:50:00Z

53.57

-0.35

19.0

11.0

210

17

6.21

29.64567

VFR

METAR

31.0

 

 

Here's the Data from the _12Z

 

EGNJ 301750Z 25012KT 9999 SCT030 18/09 Q1005

EGNJ

2012-06-30T17:50:00Z

53.57

-0.35

18.0

9.0

250

12

6.21

29.675198

VFR

METAR

31.0

Link to comment
Share on other sites

Yep, it sure does overwrite the files. It's just over written the _12Z file. 'Refreshed' in EFB and it updated OK.

So, within the next 20 minutes REXe should download the _14z file with new data and the problems will start IF you already had downloaded the _14Z earlier in the day, as the current data will be written to this file and not the _20Z file and EFB will still be looking at the _20Z file, which has out of date weather data.

 

 

Just to prove that I shut down EFB totally and replace the _20Z file back into the metarXML folder. Remember that the _14Z file has later data than the _20Z file.

 

Restarted EFB and it read the _20Z file so now if I was flying the weather that EFB is reporting is now 10 hours old and hence the yellow warning triangle.

Also be aware that the weather depicted in FSX will ALWAYS be current.

 

The time stamp of the _20Z file is 1135hrs

The time stamp of the NEW _12Z file is 1959hrs

 

Is the way forward to get EFB to 'read' the date and time of the each file in the MetarXML folder and use the latest one regardless of the 'file name'?

 

How I would love to be a program Tester ;)

 

 

Over to you URS

Link to comment
Share on other sites

Just got the NEW _14Z data file downloaded time stamp of 2057hrs

 

Therefore I think you get 10 files in 24hrs, each one being overwritten once.

 

If you don't 'fly' more than 10hrs in 24 I think you would not notice that there is a problem either and if the 10hrs+ of flying (long Haul) goes into another day you would also not notice the issue.

Then again if you didn't use EFB or perhaps FSCaptain(nudges Travis :D ), then you would never find out these 'small issues :roll:

 

@Travis......would this be the same issue in FSC perhaps?

 

Then again; all that I've written here maybe totally wrong :cry:

Link to comment
Share on other sites

Thanks for that info Andy,

 

Here's the time stamps on the files from REXe

 

10Z 1820hrs

12Z 1959hrs

14Z 2057hrs

16Z 2157hrs

18Z 2257hrs

 

I think the 20Z file will be about 2357hrs ;)

 

Remember this is the rewrite of these files in the same day. SO as an example the 14Z file has held data for 1057hrs and 2057hrs (approx ;) ) today

 

So for EFB to give the correct weather it would have to 'read' each file twice in 24hrs at the right time.

 

Again, that's just my humble opinion. I'm sure others here will know much more about this than me.

Link to comment
Share on other sites

Just to confirm again that each Z file holds two sets of data

 

20Z time stamped at 1135hrs AND 2345hrs the same day :shock:

 

 

That's me now on this subject.

 

The only 'easy' way is to purge the metarXML folder manually of the correct Z files at the correct time, then EFB will give the correct weather data every time.

 

that's what I will do, the manual way I think. Saves the grief

 

 

good night all

Link to comment
Share on other sites

Yes, I got an answer from the lead developer (sorry for not posting earlier) who said that the files will never be overwritten. He also confirmed that if EFB does a sort (ascending) of the files in that directory, the last file will then always contain the latest METAR data.

 

I guess, there is nothing to change in EFB :?

Link to comment
Share on other sites

I can tell you the file EFB reads its the 22Z file which is the incorrect file. I know because I've just loaded EFB to test it.

 

EGNJ 081050Z 36010KT 8000 3000S RA SCT004 BKN011 BKN015 15/15 Q1006

EGNJ

2012-07-08T10:50:00Z

53.57

-0.35

15.0

15.0

360

10

4.97

29.704725

RA

MVFR

METAR

31.0

 

 

It Should have read the 04Z file as this file has the latest data:

 

EGNJ 081350Z 35009KT 9999 SCT016 SCT029 17/14 Q1006

EGNJ

2012-07-08T13:50:00Z

53.57

-0.35

17.0

14.0

350

9

6.21

29.704725

VFR

METAR

31.0

 

 

So, what do you think the issue is? IS it EFB reading the incorrect file OR is REXe over writing files OR something else?

 

If EFB could sort the files by 'created date and time' and then look at the latest; regardless of the file name then the issue would be solved

Link to comment
Share on other sites

Hi Clive,

 

I can see from your screenshot that the file "... 04z" has a newer timestamp than the file "... 22z", so I'm confused too. I just wrote to the REX developer again, hoping that he can advise on how to proceed.

Link to comment
Share on other sites

×
×
  • Create New...