[Xastir-dev] xastir as pvd

[Owen DeLong]

Ah... I misunderstood your desire.  I thought you were trying to use XASTIR
as a MFD within the flight simulator.  Give what you have now described...

A couple of questions come to mind... This sounds like a perfect
fit with the internet APRS formats, except for your insistance on UDP.
Is there a reason you can't do TCP?

If you can do TCP, then, you could spit out APRS format messages (basically
NMEA with an AX25 wrapper), and you'd have callsign, altitude, course, 
speed,
and just about any data you wanted.

I think you can do it with minimal additional code in XASTIR.

I think if you can do TCP and pretend to be an internet APRS feed, you
then only need to add functionality we already want in XASTIR, but haven't
had time to implement:

	Symbol Rotation
	Alternate Symbol Library
	Over-the-air Symbol definition

I think if you were to add those features to the mainline XASTIR code, and,
code up your end to spit out TCP APRS Daemon format stuff, you'd be done
and we'd all be happy.

Someone tell me what I'm missing here.

Owen


--On Wednesday, April 14, 2004 22:38 -0400 Wendell Turner 
<wendell at adsi-m4.com> wrote:

> Maybe I should go over my objectives.
>
> I'm looking for a "radar display", sometimes called a Plan
> View Display, Plan Position Indicator, etc.  My company's
> radio (VHF/aviation band) will be receiving Automatic Dependent
> Surveillance Broadcast (ADSB, basically GPS position) messages
> from aircraft.  Our radio will decode the bits and output
> messages for each of the targets it receives.  That is, the
> one radio that the computer is connected to will send out UDP
> messages for ownship and for targets (the format is not
> particular,
> NMEA will suffice, as I don't suppose xastir has any desire
> to input Asterix(!).  I think Garmin has invented some
> proprietary
> NMEA sentences with altitude and callsign.  That would be fine.)
>
> gpsd is fine for what is designed for (multiplexing
> data from a serial port to multiple receivers), but that does
> not fit my scenario. I don't want a gpsd for each target, as
> they will come & go.  If xastir could just listen to one udp
> port, decode messages it receives over that port, and plot them
> (with heading), that would be great.
>
> I've already written my own mapping program that does
> this, but it is extremely lame now that I've seen what xastir
> can do.
>
> Will it be possible for me to include this functionality into
> xastir without perturbing the mainline function?  Maybe as a
> run-time command line option to enable it, or a ./configure
> option to compile it in?
>
> Thanks,
>
> Wendell
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at xastir.org
> https://krypton.hscs.virginia.edu/mailman/listinfo/xastir-dev



-- 
If this message was not signed with gpg key 0FE2AA3D, it's probably
a forgery.