Board index FlightGear Development Aircraft Cockpit development

FG1000 ready for integration into aircraft

Discussion about creating 2d and 3d cockpits.

FG1000 ready for integration into aircraft

Postby stuart » Thu Jun 21, 2018 1:48 pm

Hi All,

The http://wiki.flightgear.org/FG1000 is now in a state where it can be usefully integrated into aircraft as a glass cockpit.

As with everything, there's always further development to do, but most of the PFD and MFD function is complete and it would greatly benefit from being included in some aircraft. Plus it allows you to modernize your cockpit for the 21st century are minimal cost!

There are instructions in the wiki on how to integrate, and please get in touch if you have any questions.

The Garmin G1000 (which the FG1000 is a very close emulation) has been fitted to a huge range of aircraft. It would be great to see this being used, and to help drive further development.

Thanks,

-Stuart
G-MWLX
User avatar
stuart
Moderator
 
Posts: 1469
Joined: Wed Nov 29, 2006 9:56 am
Location: Edinburgh
Callsign: G-MWLX

Re: FG1000 ready for integration into aircraft

Postby StuartC » Tue Dec 18, 2018 2:20 pm

Having issues installing this.

I can get the FG1000 to sit in the cockpit, but the display is blank, no life at all.
I have addressed to from the default locations in Instruments-3d.
I have a nasal file running that's starts things off and loads fg1000.nas.
I can see no reason whi its not starting up. I checked against the dr400 and apart from it using some extra code to tie it to the electrical buss, I can see no difference.
To make matters worse, another FGUK member has loaded the aircraft and the display works just fine for him.
I am using FG version 2018.3.1 for Windows.

The console output on loading is this:-
Multiplayer mode active!
osgDB ac3d reader: could not find texture "torque.png"


Could not find at least one of the following objects for animation: 'PANDown'
G:/games/flightgear/FGUKaircraft/aircraft/bell430/Models/Bell-430.xml: Use of <global> in material animation is no longer supported.
G:/games/flightgear/FGUKaircraft/aircraft/bell430/Models/Bell-430.xml: Use of <global> in material animation is no longer supported.
Volcanic activity off.
initialising the mp lag system

############
# FG1000 #
############

PFD_Device: Error loading MAP - STORMSCOPE: svg layer StormscopeGroup
PFD_Device: Error loading MAP - WEATHER DATA LINK: svg layer WeatherDataLinkGroup
PFD_Device: Error loading MAP - TAWS: svg layer TAWSBGroup
PFD_Device: Error loading WPT - AIRPORT DIRECTORY: svg layer AirportDirectoryGroup
PFD_Device: Error loading WPT - AIRPORT DEPARTURE INFORMATION: svg layer AirportDepartureGroup
PFD_Device: Error loading WPT - AIRPORT ARRIVAL INFORMATION: svg layer AirportArrivalGroup
PFD_Device: Error loading WPT - AIRPORT APPROACH INFORMATION: svg layer AirportApproachGroup
PFD_Device: Error loading WPT - WEATHER INFORMATION: svg layer AirportWeatherGroup
PFD_Device: Error loading WPT - USER WPT INFORMATION: svg layer UserWPTInfoGroup
PFD_Device: Error loading AUX - TRIP PLANNING: svg layer TripPlanningGroup
PFD_Device: Error loading AUX - UTILITY: svg layer UtilityGroup
PFD_Device: Error loading AUX - GPS STATUS: svg layer GPSStatusGroup
PFD_Device: Error loading AUX - XM RADIO: svg layer XMRadioGroup
PFD_Device: Error loading AUX - XM INFORMATION: svg layer XMInfoGroup
PFD_Device: Error loading AUX - SYSTEM STATUS: svg layer SystemStatusGroup
PFD_Device: Error loading FPL - ACTIVE FLIGHT PLAN: svg layer ActiveFlightPlanWideGroup
PFD_Device: Error loading FPL - FLIGHT PLAN CATALOG: svg layer FlightPlanCatalogGroup
PFD_Device: Error loading FPL - STORED FLIGHT PLAN: svg layer StoredFlightPlanGroup
PFD_Device: Error loading NRST - NEAREST USER WPTS: svg layer NearestUserWPTGroup
PFD_Device: Error loading NRST - NEAREST AIRSPACES: svg layer NearestAirspacesGroup
Lightpack light system initialized
This aircraft uses yasim version 'YASIM_VERSION_CURRENT' (3)

installing osm2city nasal.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby Michat » Wed Dec 19, 2018 3:57 pm

Have a friend who has test dr400 with G1000. No blank instrument problem for him on the very last release of FG.
User avatar
Michat
 
Posts: 962
Joined: Mon Jan 25, 2010 6:24 pm
Location: Spain
Version: 191b
OS: GNewSense

Re: FG1000 ready for integration into aircraft

Postby wlbragg » Wed Dec 19, 2018 6:03 pm

I saw an experimental Cub on-line that had a glass cockpit. I think we need a PA-18 version with the glass. Easy way to get a fully functioning PA-18g :D
I'm excited, new project time.
Kansas(2-27-15)/Ohio/Midwest scenery development.
KEQA (2-27-15), 3AU, KRCP Airport Layout
User avatar
wlbragg
 
Posts: 4909
Joined: Sat Aug 25, 2012 11:31 pm
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Debain/nVGT640

Re: FG1000 ready for integration into aircraft

Postby StuartC » Wed Dec 19, 2018 10:30 pm

ihave tested on a second windows pc now, with a clean instal of 2018.3.1, still a blank screen.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby legoboyvdlp » Wed Dec 19, 2018 10:38 pm

I've seen this error too albeit the display works for me. However, on the dr400 I couldn't get the flight plan pages and so on to show up, just the main map and pfd. Probably user error though, not the fg1000!
User avatar
legoboyvdlp
 
Posts: 7091
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: FG1000 ready for integration into aircraft

Postby StuartC » Thu Dec 20, 2018 9:20 am

The errors s not on the DR400, it happens when its fitted to any other aircraft.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby stuart » Thu Dec 20, 2018 11:33 am

Hi StuartC,

I assume you're assigning the MFD and PFDs and calling .show() (http://wiki.flightgear.org/FG1000#Load_ ... 000_system)?

Could you send me a link to the aircraft, and I'll take a look.

Thanks,

-Stuart
G-MWLX
User avatar
stuart
Moderator
 
Posts: 1469
Joined: Wed Nov 29, 2006 9:56 am
Location: Edinburgh
Callsign: G-MWLX

Re: FG1000 ready for integration into aircraft

Postby StuartC » Thu Dec 20, 2018 2:20 pm

I have PM'd you a link.
thanks.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby stuart » Fri Dec 21, 2018 9:08 pm

Thanks. I think I found the problem. You need to call fg1000.show(); to show the displays. You can use this so that the FG1000 is only shown when powered on, for example.

This function was added relatively recently (well, in the last 6 months?), so I suspect the other FGUK person is using an older FG version.

I've enhanced the example on the wiki to make this more obvious.

-Stuart
G-MWLX
User avatar
stuart
Moderator
 
Posts: 1469
Joined: Wed Nov 29, 2006 9:56 am
Location: Edinburgh
Callsign: G-MWLX

Re: FG1000 ready for integration into aircraft

Postby StuartC » Sun Dec 23, 2018 4:00 pm

Thanks for the reply. Updated the nasal ant its done the trick.

thanks.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby StuartC » Mon Dec 31, 2018 7:00 pm

Or not so much...………

Although the PFD is fully lit up and looks fine, Its not actually displaying airspeed, altitude, pitch/roll etc, its all static.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby stuart » Tue Jan 01, 2019 8:12 pm

Hi StuartC,

Happy new year!

I think the problem is you haven't started the interfaces that map from the properties into the FG1000: http://wiki.flightgear.org/FG1000#Load_the_Interfaces_to_provide_data

Code: Select all
var nasal_dir = getprop("/sim/fg-root") ~ "/Aircraft/Instruments-3d/FG1000/Nasal/";
io.load_nasal(nasal_dir ~ 'Interfaces/GenericInterfaceController.nas', "fg1000");

var interfaceController = fg1000.GenericInterfaceController.getOrCreateInstance();
interfaceController.start();


I expect when you do this, most of the instruments will work, but some won't - for example the engine displays, which assume a single piston engine. So you'll need to copy the GenericInterfaceController.nas to the aircraft and then probably create your own version of GenericEISPublisher.nas to map an appropriate set of properties. You'll also need to create your own EIS display, as described in the wiki. That involves creating an SVG. I've just updated the wiki to provide more detail on how to do this http://wiki.flightgear.org/FG1000#Create_an_EIS_Display. Shout if it isn't clear - writing good documention for this is hard when you're so familiar with how it works.

Good luck!

-Stuart
G-MWLX
User avatar
stuart
Moderator
 
Posts: 1469
Joined: Wed Nov 29, 2006 9:56 am
Location: Edinburgh
Callsign: G-MWLX

Re: FG1000 ready for integration into aircraft

Postby StuartC » Wed Jan 02, 2019 12:47 pm

Extra nasal did the trick. PFD now works.

Modified versions in the Development version of the wildcat:-

Image

Happy new year everyone.
StuartC
 
Posts: 2737
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: FG1000 ready for integration into aircraft

Postby wlbragg » Tue Jan 08, 2019 6:43 am

First attempt at getting the FG1000 PFD integrated into the J3Cub and PA-18.
The AI and Autopilot still not working but everything else appears to be functioning.
I wish I had room for another MFD.

Image
Kansas(2-27-15)/Ohio/Midwest scenery development.
KEQA (2-27-15), 3AU, KRCP Airport Layout
User avatar
wlbragg
 
Posts: 4909
Joined: Sat Aug 25, 2012 11:31 pm
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Debain/nVGT640

Next

Return to Cockpit development

Who is online

Users browsing this forum: MSN [Bot] and 1 guest