Re: [Flightgear-devel] Garmin 400
"Curtis Olson" wrote: > It would be great if it was possible to drive the windows based 400-series > simulator software, but I don't have any idea if it's setup to respond to > serial input. My understanding is that it had a graphics front end combined > with a backend engine that communicated via network packets. But I could be > wrong. Last time I checked, several years ago, the simulator/trainer had a 'serial' config option which should allow the user to hook this onto everything that is getting declared a being a serial interface by the underlying OS. Therefore, with a small to medium amount of fancywork it _should_ be possible to route FlightGear's serial output into a serial interface in Wine. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
On Mon, Jan 19, 2009 at 3:56 PM, Martin Spott wrote: > This sounds great to me. Even though I would not count the GNS430/530 > as being among my personal favourites, I know they are _very_ popular > and I've been using such thing at least in two different aircraft. If > I'm not mistaken, this would probably allow FlightGear to drive the > Windows-based series 400 simulation software - buying a real GNS430 > just as an add on might be somewhat expensive for the casual user :-) It would be great if it was possible to drive the windows based 400-series simulator software, but I don't have any idea if it's setup to respond to serial input. My understanding is that it had a graphics front end combined with a backend engine that communicated via network packets. But I could be wrong. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
On Mon, Jan 19, 2009 at 2:53 PM, Torsten Dreyer wrote: > > Will you also commit the Garmin 400, so everybody can download one? Alas, I haven't yet figured out how to commit physical hardware to CVS ... maybe with GIT? I can commit the protocol updates soon though. :-) Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
"Curtis Olson" wrote: > There is a set of messages that the Garmin 295/296/400/430/530/etc. emit. I > previously implmented this message set which you can activate with the > --AV400=[...] option. This works for driving a Garmin 295/296 gps. > However, the 400/430/530 gps expect a different command set from the > simulator which is what I have implemented. This sounds great to me. Even though I would not count the GNS430/530 as being among my personal favourites, I know they are _very_ popular and I've been using such thing at least in two different aircraft. If I'm not mistaken, this would probably allow FlightGear to drive the Windows-based series 400 simulation software - buying a real GNS430 just as an add on might be somewhat expensive for the casual user :-) Please note, while you/we are at it, than "fgfs --help --verbose", among others, lists the "--garmin=" option, but not the "--AV400=". Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
> I'm excited! I just got FlightGear connected up to a Garmin 400 which > speaks the same protocol as the 430/530. I haven't looked at sending over > fuel and radio information, but all the positional / velocity stuff is > working. I'm going to do some more testing here before committing the new > protocol. > > GPS training is a *huge* thing that people want to do these days with > flight simulators. > > (Oh and sorry for the small fire I started in the middle of KSFO when I hit > the VOR shack.) > Will you also commit the Garmin 400, so everybody can download one? Torsten -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
On Mon, Jan 19, 2009 at 3:06 PM, Martin Spott wrote: > Hi Curt, > > "Curtis Olson" wrote: > > > I'm excited! I just got FlightGear connected up to a Garmin 400 which > > speaks the same protocol as the 430/530. I haven't looked at sending > over > > fuel and radio information, but all the positional / velocity stuff is > > working. I'm going to do some more testing here before committing the > new > > protocol. > > In which sense is this different from the I/O protocol you enable via > the "--garmin=[...]" switch ? The --garmin= protocol outputs basic NMEA strings with some (a) garmin extension. What I am implementing is the ARNAV format which I've also heard called the AV400 format or RS-232 Type 1. There is a set of messages that the Garmin 295/296/400/430/530/etc. emit. I previously implmented this message set which you can activate with the --AV400=[...] option. This works for driving a Garmin 295/296 gps. However, the 400/430/530 gps expect a different command set from the simulator which is what I have implemented. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Garmin 400
Hi Curt, "Curtis Olson" wrote: > I'm excited! I just got FlightGear connected up to a Garmin 400 which > speaks the same protocol as the 430/530. I haven't looked at sending over > fuel and radio information, but all the positional / velocity stuff is > working. I'm going to do some more testing here before committing the new > protocol. In which sense is this different from the I/O protocol you enable via the "--garmin=[...]" switch ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
