Jump to content

Supera380

Members
  • Content count

    36
  • Joined

  • Last visited

  1. Supera380

    Alternates - enroute and destination?

    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
  2. Supera380

    Intermittent license access issues

    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
  3. Supera380

    Intermittent license access issues

    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
  4. 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
  5. 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
  6. 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
  7. Supera380

    Server cannot be reached

    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
  8. Update: Re-installed the full v1.6.8 package and everything is now running as expected. Regards Mark
  9. 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
  10. Supera380

    A few questions

    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
  11. Supera380

    Procedures

    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
  12. 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
  13. Supera380

    Remove Arrival

    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
  14. 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
  15. 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
×