Hey everyone,Hope all is well. Just a quick question, is anyone else having issues fetching data for LLBG or using it as a destination? For some reason, LLBG does not seem to be reporting correctly for me...Right now it showsWind 000/0Vis 0 0 SMClouds NonePrecip NoneTemp 0C Dew 0CPressure 00.0 mb 00.00 inchesThis has happened the past few times I have tried to fly to LLBG so I am wondering if I am the only one.Weird,Thanks in advance,-PaulPrimary RigLiquid CooledAMD FX-57 @ 3 gigsAsus A8NSLI-Premium2 gigs Corsair XMS PC3500LL 2 3 2 6 1TXFX 7900 GTX 690/1750XFX 7800 GTX 515/135024 inch Widescreen LCDDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1khttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7800 GTX 515/1350 Raid-0http://forums.avsim.net/user_files/154870.jpg

Hi,Try after updating to B503.I just got a good fetch.Please let us know!Hope this helps,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Will do Jim, upgrading now,As always, thanks for the qick response,-Paul

Hmmm,Something still doesn't seem right. For some reason ASV is pulling LLBG from OJAM (Amman Jordan) and decoding it differently than the actual weather at LLBG...LLBG

Hi,I just got a bad fetch also. The current wx snapshot has an incomplete report so it looks for the closest station.Hope this helps,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Thanks Jim,I have been seeing this for some time now, probably 2-3 weeks but wanted to give it some time to see if it fixed itself before bothering you. Not sure what the root cause is. What happens when you are midflight sometimes is that you get "Destination Metar Unavailable" if you try to check your wxr enroute to determine a landing runway...Thanks for looking into it for me Jim, do you think anything can be done? Obviously LLBG is reporting :)Off topic, are you going to be at the convention in DC? This is my first one so I am excited to see who I am going to meet.Thanks again Jim, speak to you soon,-Paul

Hi Paul,It is reporting but the data is not real stable. Now it give a report from LLSD.No, we will not be in DC. I can't afford it, even from Michigan. And Detroit teachers are on strike so I am not sure about any bills right now.Hope this helps,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Hey Jim,Is there anyway to look into this? I am still getting the same results for LLBG and can not use it as a destination in my F/P as it will not be able to fetch destination weather....Any help would be appreciated.Thanks,-Paul

Hi Paul,I have informed Damian of this thread and told him what I know about the situation. The station data is good, but the weather is behind.We will see,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Hi,Two problems here. One is that LLBG is problematically sending NIL reports between every valid report. This confuses our server. This is the only station we've seen with this NIL behavior. At this time it looks like a temporary issue with their METAR transmissions, but if it persists for longer than 15 days we'll try and handle via our server code.Second problem is OJAM, which AS is properly selecting as the next closest valid station, but the METAR report for OJAM is invalid, causing a complete parse error. (Note that the winds elements are broken into two, instead of 00000KT it is 00000 KT). ASv6 should be able to recover from the parse error, and it is not in this case so we'll be looking to fix that. In the mean time, since OJAM reports are invalid, OJAM has been removed from the server fetch list. The next most valid station wx will thus be used and further problems with flight plans should be avoided. This pertains to any weather downloaded after 21:00Z today.In short, we'll be working on adding additional handling for this invalid data being sent out by these stations, but in the mean time things should continue to work now that OJAM has been removed.Best,

Jim and Damian,Absolutely stellar support as always. I am mid-flight right now so i cannot verify but I will try to do a route to LLBG tomorrow to double check.Thank you very much, amazing support...-Paulhttp://forums.avsim.net/user_files/156237.jpg

hey guys, just an update. Still no luck. I just tuned com 2 to 122.00 and got Dest * for the wxr report doing KEWR-LLBG. I would say this has been going on since the beginning of August now. Is there anything that can be done?Thanks in advance,-Paul

Hi Paul,I'm not getting that at the moment with current wx. Can you please e-mail me at damiancAThifisim.com including your .PLN file and asv6.ini file? I'll attempt to duplicate and follow up with you via e-mail to get this solved ASAP. Thanks!Best,