Jump to content

Supera380

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by Supera380

  1. Hi, Appreciate the answer and clarification. Sorry for the dumb question but the approach plate as depicted in EFB threw me. For me it was not immediately obvious the bold number in the table was the runway number especially when the runway number is given at the top of the approach plate window and having the MDA and RVR values in the same box is not the typical convention. Nonetheless I will read the manual in more detail. I found and read the relevant section regarding the minima and so I will have a go at customizing the values as you suggested. Thanks
  2. Hello, I am using the trial version of EFB v2 with P3Dv3.4 and using the default, included 1802 cycle. I have the PMDG 747-400 loaded which is a Cat D aircraft. When I create a flight plan from ENGM to LOWW and select a RNAV (LNAV/VNAV) 34 approach for LOWW, I see the Approach plate shown at the bottom of the screen. Info displayed for this approach within EFB looks odd as the DA is shown to be 34ft. I am not sure this is correct. It should be 834ft according to Austro Controls charts. See attached for the EFB display and the Austro Control chart from Feb 2017. Note: If I look at the corresponding ILS 34 approach it also shows 34ft also as the DA within EFB while Austro Control shows the same approach to be 804ft. Field elevation of this runway is 584ft. So is the approach data within 1802 cycle incorrect or is this an EFB related problem with showing incorrect DA/DHs? Can someone confirm my observations for this airport/runway? Regards LO_AD_2_LOWW_24-6-9-4_en.pdf
  3. Hi Jonas, Thx for the pointer. Yes you are correct. My ENGM Configurator tool was missing when I installed the scenery for some reason so I had overlooked it and the option to turn static aircraft on was enabled. I have turned this off and the actual view was in snych with EFB. Thanks for that. Regards Mark
  4. Hello, I am seeing similar problems of only seeing limited AI traffic displayed on the client with sim generated traffic in P3Dv4.3. At Oslo (ENGM, Aerosoft) I have 3 aircraft sitting at the same terminal within 300m of my user aircraft positioned at Gate 49 (AI occupying Gates 38, 39 & 42) but the Client does not depict these aircraft at all. On the Traffic Monitor, only 2 aircraft are listed that are on the ground but they are positioned at another terminal farther away from my aircraft. Strange! I have not changed the default settings of -5000-5000 within EFB v2 for the AI altitude limits. I am hoping the bug found and subsequent fix by Urs will resolve this. Regards Mark
  5. Hi Oskar, I understand your point and thanks for explaining the rationale for this not being in v2. The counter argument is that we are working with the simulator, so for those of us practicing normal and abnormal procedures/ops, diversion planning is part of that learning curve. When Simbrief is able to generate alternates etc it would be nice to have that carried through to EFB. I for one was using this feature in v1. If it could be re-considered at a future point in time that would be great. Regards Mark
  6. Hi Mike Hotel, all Glad I am not the only one in the same boat! I have to say its quite frustrating with trying to evaluate v2 when there's these issues with the demo licenses. So far having installed v2 I have spent approx 1hr over the entire weekend where I got it work. The demo expiry time is counting down and I am limited to being able to evaluate EFB v2 only at the weekends. Urs- Is there something that can be done here? It's likely that v1 users wanting to try out v2 will be frustrated the same as I am and to be honest jumping in and buying the software because the demo license doesn't work is not the right way to go about this. If this is the only route to get v2 working (buying a full v2 license) , could you please consider a higher discount for those that are existing v1 users to make this more attractive. Without this and any other help available to fix the Port 13 issues , I am probably going to stick with v1. Regards Mark
  7. Hi, Yes I have read that, but I would like to try the demo for more time before I decide to purchase or not. If the demo mode is problematic then this somewhat limits the flexibility of having a demo version in the first place. I am still trying to "find my feet" with v2. Right now I am unable to update the database, update the AIRAC etc. Regards Mark
  8. Hi, I have been experimenting with creating a flight plan and so far so good. v2 really looks good. The Airport layout is much improved as well. You actually get to see the closed runways now! One small thing is I have not been able to figure out (yet) where to define the alternates for a given route which were available in v1. I had a look in a couple of the manuals including the FlightPlan one and no information appears on how to set these. Is this feature available in v2 and if so where can I find it? Many thx Mark
  9. Hi, I am running the demo version of v2 and the latest updates installed and am still experiencing issues with the license being found and not found. Local Port 13 is configured to be open as an Outbound rule in Windows Defender and on occasions I see the EFB Server start up without any warnings but on other occasions it has a problem finding the license.Windows Firewall has also been turned off completely but same issue. Secondly, I also see that I can not start the DbBuilder even though I am prompted that the FS configuration files have changed when starting up the EFB Server. This just runs in an endless loop between DBBuilder and Server where the license can not be detected by the DBBuilder and points back to restarting the Server. In the Licenses folder there is a .dlsc file present. I was able to access the DBBuilder the first time as part of the installation but since then not able to access. Any ideas why this would be intermittent? Example with no warning. 2018-07-08 11:14:51.675 Debug : ========== AivlaSoft.Efb.Server 2.0.52.0 started ========== 2018-07-08 11:14:51.784 Debug : CPU = Intel64 Family 6 Model 158 Stepping 10, GenuineIntel, No of proc. = 12 2018-07-08 11:14:51.784 Debug : OS = Microsoft Windows 10 Pro 2018-07-08 11:14:51.784 Debug : OS language = en-US, Language settings = en-US 2018-07-08 11:14:51.784 Debug : Process is 64bit 2018-07-08 11:14:51.800 Debug : Settings loaded from: C:\Users\User\Documents\AivlaSoft\EFB2\Server\Settings\serverSettings.txt 2018-07-08 11:14:51.800 Debug : Verify license ... 2018-07-08 11:14:54.471 Debug : Trial version running, trial will end in 25 days. 2018-07-08 11:14:56.260 Debug : AutoUpdateInterval = 1 2018-07-08 11:14:56.739 Debug : Database selected = P3Dv4.NG-1802/R1 2018-07-08 11:14:56.749 Debug : Looking for already running simulator ... 2018-07-08 11:14:56.749 Debug : Simulator is not yet running 2018-07-08 11:14:56.749 Debug : Loading database ... 2018-07-08 11:14:59.308 Debug : Database loaded 2018-07-08 11:14:59.323 Debug : Global settings loaded from: C:\Users\User\Documents\AivlaSoft\EFB2\Server\Settings\globalSettings.txt 2018-07-08 11:14:59.542 Debug : Flight plan backup loaded (EDDF to LOWW) 2018-07-08 11:14:59.542 Debug : Backups loaded 2018-07-08 11:14:59.542 Debug : Starting weather (Real world) ... 2018-07-08 11:14:59.542 Debug : Weather (Real world) started 2018-07-08 11:14:59.557 Debug : Services started 2018-07-08 11:14:59.557 Debug : Organized tracks disabled because AIRAC cycle is outdated 2018-07-08 11:14:59.557 Debug : TCP controller started, waiting for clients ... 2018-07-08 11:14:59.557 Debug : A/C is on ground (Init) 2018-07-08 11:15:06.353 Debug : Closing ... 2018-07-08 11:15:06.353 Debug : Begin disconnect FSUIPC 2018-07-08 11:15:06.353 Debug : FSUIPC successfully disconnected 2018-07-08 11:15:06.353 Debug : Stopping weather (Real world) ... 2018-07-08 11:15:06.353 Debug : Weather (Real world) stopped 2018-07-08 11:15:06.353 Debug : Services stopped 2018-07-08 11:15:06.384 Debug : Server settings saved to: C:\Users\User\Documents\AivlaSoft\EFB2\Server\Settings\serverSettings.txt 2018-07-08 11:15:06.384 Debug : ========== Terminated ========== Example with warning 2018-07-08 11:17:39.100 Debug : ========== AivlaSoft.Efb.Server 2.0.52.0 started ========== 2018-07-08 11:17:39.193 Debug : CPU = Intel64 Family 6 Model 158 Stepping 10, GenuineIntel, No of proc. = 12 2018-07-08 11:17:39.194 Debug : OS = Microsoft Windows 10 Pro 2018-07-08 11:17:39.194 Debug : OS language = en-US, Language settings = en-US 2018-07-08 11:17:39.194 Debug : Process is 64bit 2018-07-08 11:17:39.217 Debug : Settings loaded from: C:\Users\User\Documents\AivlaSoft\EFB2\Server\Settings\serverSettings.txt 2018-07-08 11:17:39.219 Debug : Verify license ... 2018-07-08 11:17:42.723 Warning : Neither trial nor licensed: Trying to verify demo license but could not reach any time server on the internet.Please make sure that your computer is connected to the internet and the firewall is properly configured to allow reaching any time server on the internet (TCP port 13 must be open for outgoing traffic). 2018-07-08 11:20:07.560 Debug : AutoUpdateInterval = 1 2018-07-08 11:20:08.276 Debug : Database selected = P3Dv4.NG-1802/R1 2018-07-08 11:20:08.288 Debug : Looking for already running simulator ... 2018-07-08 11:20:08.290 Debug : Running simulator process found, type is 'Prepar3D'. Getting file version ... 2018-07-08 11:20:08.292 Debug : ... file version is 4.3.29.25520 2018-07-08 11:20:08.294 Debug : Loading database ... 2018-07-08 11:20:10.921 Debug : Database loaded 2018-07-08 11:20:10.930 Debug : Global settings loaded from: C:\Users\User\Documents\AivlaSoft\EFB2\Server\Settings\globalSettings.txt 2018-07-08 11:20:11.121 Debug : Flight plan backup loaded (EDDF to LOWW) 2018-07-08 11:20:11.122 Debug : Backups loaded 2018-07-08 11:20:11.125 Debug : Starting weather (Real world) ... 2018-07-08 11:20:11.126 Debug : Weather (Real world) started 2018-07-08 11:20:11.126 Debug : Services started 2018-07-08 11:20:11.128 Debug : Organized tracks disabled because AIRAC cycle is outdated 2018-07-08 11:20:11.130 Debug : TCP controller started, waiting for clients ... 2018-07-08 11:20:11.132 Debug : A/C is on ground (Init) 2018-07-08 11:20:11.341 Debug : FSUIPC successfully connected 2018-07-08 11:20:11.569 Debug : Simulator type = P3Dv4 (FSUIPC 12, 43) 2018-07-08 11:20:56.128 Debug : New client 127.0.0.1 accepted 2018-07-08 11:20:56.250 Debug : Client (127.0.0.1) registered, version = 2.0.70.0 2018-07-08 11:21:00.906 Debug : Profile received: B747-400 2018-07-08 11:21:02.954 Debug : FPL sent to 127.0.0.1 on request 2018-07-08 11:21:03.182 Debug : Sent weather on request to 127.0.0.1 2018-07-08 11:21:17.138 Debug : Flight plan backup removed 2018-07-08 11:21:17.322 Debug : GPS flight plan successfully removed 2018-07-08 11:22:40.871 Debug : Closing ... 2018-07-08 11:22:41.373 Debug : Begin disconnect FSUIPC 2018-07-08 11:22:42.224 Debug : FSUIPC successfully disconnected 2018-07-08 11:22:42.227 Debug : Stopping weather (Real world) ... 2018-07-08 11:22:42.228 Debug : Weather (Real world) stopped 2018-07-08 11:22:42.230 Debug : Services stopped Regards Mark
  10. Just to confirm this is likely to be a FSUIPC issue. Had the same issue. EFB Client was not connecting so started out at LSZH as the default location each time. In my case the P3D dll.xml contained no FSUIPC entry (for the unregistered version) even though FSUIPC and the Install log showed the installation was complete without errors. Once the entry is present in this file , you will see the EFB Server run its startup routine/log and will see FSUIPC running via this message "FSUIPC successfully connected". Also check in P3D that FSUIPC appears in the Add-on Menu. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC5.dll</Path> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_connect_64.dll</Path> </Launch.Addon> </SimBase.Document> Regards Mark
  11. Sorry you are not having much luck. I ran into similar problems. I can only pass my findings along to you which helped solve some of the issues. Re connection issues, I found that Port 13 had to be configured as an Outbound rule within Windows Defender. I also found out it is easy to misconfigure the port. If you access the Outbound rule you created for this open port, select Properties and then go to the Protocols and Ports tab, you want to make sure "13" is set to a Local Port. Mine was set to the Remote port when I set up the rule initially and this gave me the connection failure. As for your other AV program, it depends upon which one you use and it's appropriate settings for the port. Maybe you could share which AV program you have so someone else can comment? You could also try disabling your AV completely and just try with configuring Windows Defender to open Port 13. Basically simplify the set up. Hope this helps a little?? Regards Mark
  12. Update: Re-installed the full v1.6.8 package and everything is now running as expected. Regards Mark
  13. Hello Urs, Just to let you know I have run into the same problem in updating from v1.6.6 to v1.6.8 using the update package. Update package was successfully installed according to Add/Remove Programs. However when clicking the Data Provider nothing happens. Same for the DU. Checked the log files and nothing is recorded at all in terms of DP or DU starting. Am now attempting an EFB uninstall and re-install of the full package. Regards Mark
  14. Hi Ken, I will attempt to answer some of your questions...answers in red below. 1) Are the ILS frequencies shown for the various airports ... this is critical or your looking for charts. Yes. If you're not seeing the glide slope and ILS info for example, go to the Approach segment view. There's a toolbar with a few navigational icons. Select the icon showing a 3x3 grid with a tick mark. This is a "visibility" button. From there you will see you can enable Comm frequencies, the Briefing strip and Profile view with GS to show up. Alternatively , if you click on the Approach segment view, you should see your arrivals airport in the main menu (it's context sensitive depending which segment of the flight your are in). From here click this button and select "Airport Information". Selecting the Landing Aids tab will give you ILS frequencies and more for all runways.Section7 of the manual explains all the info available 2) Does the "moving map" require a kick start by clicking the Ctrl+Shift+M or does it need to be configured somewhere. Should not need this. Again the icons bar includes one that activates the map-. Essentially it synchs the position of the plan within FSX to your position on the EFB map. The icon you are looking for is one with an aircraft inside it. It may be greyed out if you do not have an active connection between EFB and FSX.Section7 of the manual explains all the info available. 3) I'm a little confused about how to get Active Sky's data working in EFB ... what are we looking for and where. Pass. 4) On the wish list I would like to see "VRoute" included ... it seldom fails to find a current route for even the "small town" flights like CYKA to CYVR but it's not a big deal to paste them in. Best left to Travis or Urs to consider this. 5) CYKA now has an ILS ...(WestJet) wouldn't bring their 737's in without it ... but how do I set that new ILS up in EFB ... or can it even be done? The old existing FSX NDB is a pain If the real world airport now has an ILS approach, you'll need to purchase or subscribe to Navigraph or equivalent service to download the latest FMS data (so called AIRAC cycle) and import into EFB. Having said that, there may still be problems if the airport scenery in FSX has not been updated with this info as well, so you would likely suffer a mismatch issue. Regards Mark
  15. Chris, Are you talking about where the flight plans are saved in a specific folder or something else. Please provide more details and we can try and help you out. Mark
  16. Hi Joe, I think your problem may relate to a mismatch of runways found in your EFB navdata versus what is in FSX (either default airport or airport add-on). You should be getting warnings in the Dataprovider information log. Many times, these mismatches can be resolved by creating-modifying a file called runways.txt. Info on how to edit this file and resolve some of the issues can be found in Chapter 4 of the manual. Without knowing the exact warning you're getting hard to say what the final answer is. Hope this points you in the right direction. Regards, Mark
  17. Hi Chris, You should be able to do this by going back to Route menu then clicking the Modify button. You will see your flight plan split into the different segments. Select the Arrivals tab radio button and this will display details of the waypoints. Delete the arrivals segment using the button marked "Remove STAR". Note: This will remove the entire segment. With the current version of EFB specific waypoints can not be deleted individually from the departure, arrival and approach segments. This will come in v2 I believe. More info can be found in Section 5 of the manual. Hope that helps. Regards Mark
  18. Hi, I have noticed that there's a warning message indicating "ICAO code validation EDDB2 , length > 4" in the Scenery update error log. I can see why this warning is given because of an invalid 5 character airport code, but where do I try and look to fix this in my airport? I have Aerosoft's Berlin Brandenburg installed. Can you tell me what EFB is actually indexing and then I can go fix it at the actual airport it? thx Mark
  19. Hi Urs, All Just wanted to also add some additional info here as I ran into the same problem today. I am running a networked config and had been able to run the Display Unit from my Win 8 laptop in the past , but today the DP would not connect. No errors. Just the indication the DP was trying to connect but would not. One interesting point was I still have the DU installed on my target flightsim PC and this worked fine. Anyway after checking a few things on the config on the DU PC, I decided to go back into the Windows Firewall on the DU (Display Unit) PC and turn it completely off which resulted in a connection straight away. Since I had set this PC up with the distributed EFB back in March and had already configured the Firewall settings already, I took another look. Originally I had seen 4 inbound rules for the EFB DP listed of which I had both Private rules set to "allowed" but the Public rules "blocked"(My flightsim PC is typically not connected to the Internet) . By changing the Public EFB rules to "allowed" solved the issue. Not sure why the original firewall settings initially worked and then failed, but I am back in action with enabling all inbound rules for EFB. I hope this is of some use to others that may have this issue. Best regards Mark
  20. Hi Urs, Thx for the reply and update. Yes, you are correct. My mistake. Not the path for the .EXE files but the location of the top level folder above the Nav Data and SIDSTARS folders as indicated in that dialog window. This is what I had to set for both Flightsims in order to exit that window without errors. Thx for clarifying that. Thx Mark
  21. Hi Urs, Travis, Thx for the v1.5 update. Much appreciated. I'd like to report a possible minor defect that I spotted once the update was done. Not sure if anyone else had this issue? Update installed fine but when I started the Data Provider for the first time, it took me to some new dialog windows to confirm the Flight Sim program I had installed (I selected the FSX radio button) and also the main paths for the corresponding .EXE for those programs. However I could not get out of the dialog windows until both FSX and P3D paths had been identified. It provided a warning error and kept requesting that I fill in the P3D path. Since I do not have P3D installed, I had to specify the same main FSX path for P3D before I could complete the screens and exit. Did anyone else see this with only their FSX installation? Regards Mark
  22. Many thanks Urs for the info and updates. Much appreciated. We'll be definitely looking forward to v2.0 when it comes. If you would like any assistance in testing the airport layout functions in the future, please let me know. I would be glad to help you out, if needed. Regards Mark
  23. Hi Urs, Chris I would like to bring this observation back to the table because I am seeing similar things with missing taxiway labels as well. Urs was kind enough to show in the last post my freeware EDDF airport design where L20 and L21 correctly appear, but I see the same thing with other taxiways even after double-checking that the taxiways are correctly labeled in the AFCAD. I have attached a couple of images for EDDF. One for EFB and the other the AFCAD in ADE. A good example is the intersection of L17 and M30 circled in red with L17 missing. There are other examples also circled in blue in the AFCAD for reference where the same issue is observed. One thing that I noticed that may be causing EFB issues is that many of these taxiways adjoin a runway that have an apron link running across the runway, but I am not entirely convinced of that. Many developers add apron links (as opposed to taxi links) mid runway to allow taxiing AI aircraft to cross. Urs, if you would like we can further tweak my Frankfurt AFCAD to see if we can identify what's causing the taxiway labeling issue either in the AFCAD or in EFB?? I can certainly understand that taxiways where they are very short in length or those that do not have a taxiway designator in the AFCAD would not appear in EFB. Also one other observation and that is EFB does not appear to be able to depict closed runways. When EFB sees one of these, it basically ignores it. Not a big deal in that you're not supposed to use them anyway for taxiing, but it doesn't depict the airport layout 100%. Is there a way this could be fixed in a future EFB update? This is a minor issue in my opinion. I have circled a couple of examples of this in pink. And last a question: :When using the taxiway guidance feature within EFB, and there's a taxiway discontinuity reported, is it possible one of the reasons is that in order to get to the final destination you need to cross a runway? Is EFB able to "navigate" taxiways that cross intermediate runways in order to give the complete taxi route from a gate to the assigned departure runway? This last one may constitute a separate post. :Let me know if you would like to make this a separate post? Let me know if you have any further thoughts on any of this? Regards Mark
  24. Ronald, Just following up on this, it was not exactly clear if these charts you spoke about were enroute or sectional charts as opposed to aerodrome charts. One of the things you could do is to view those recently purchased charts within EFB via the Library function. If you need to refer to them at any time, just go to the Modules/Library function and add them in here. You can create a folder structure to keep various charts, procedures etc organized. To add the content simply go to your My Documents/Aivlasoft/EFB/User Data/Library folder and create a sub-folder for your charts there, then simply copy the chart files into this folder. Not sure if this is what you were trying to do?? I hope this helps. Regards Mark
  25. Thx URs. Thought I had missed something in the EFB set up. Not a problem. Looking forward to version 2! Cheers Mark
×
×
  • Create New...