We want to set up ad data server giving us various satellite data on OSC.

One possible method is using predict in server mode, fetching data with a script and broadcasting data in the form of OSC messages.

predict manual page and glossary: PredictGlossary

We are implementing this on the esc server.


- predict: http://www.qsl.net/kd2bd/predict.html is to be launched in "server mode" with "predict -s". TODO: using a cron job, update the TLE data frequently, see man predict:

wget -qr www.celestrak.com/NORAD/elements/amateur.txt -O amateur.txt
wget -qr www.celestrak.com/NORAD/elements/visual.txt -O visual.txt
wget -qr www.celestrak.com/NORAD/elements/weather.txt -O weather.txt
/usr/local/bin/predict -u amateur.txt visual.txt weather.txt

for more satellites, go to http://www.celestrak.com/

For general information:

                        PREDICT's Socket Commands


PREDICT Socket Command Summary
The following are the socket commands interpreted by PREDICT when the
program is running in either the single satellite or multi-satellite
tracking mode:

Command: GET_SAT
Argument: satellite name or object number
Purpose: To poll PREDICT for live tracking data.
Return value: Newline ('\n') delimited string of tracking data.
Data returned:


Description: The values are identified by the order in which they are
returned.  Referring to the example above,

Name:           ECHO
Long:           151.79 (degrees West)
Lat:            -70.04 (degrees North)
Az:             203.75 (degrees)
El:             -60.01 (degrees)
Next AOS/LOS:   1126395990 (seconds since 01-Jan-1970)=Sat Sep 10 23:46:30 2005
Footprint:      5988.49 (kilometers)
Range:          11881.33 (kilometers)
Altitude:       773.71 (kilometers)
Velocity:       7.47 (kilometers/hour)
Orbit Number:   6292 (revolutions)
Visibility:     D (see below)
Orbital Phase:  279.37 (degrees)
Eclipse Depth:  -32.42 (degrees)
Squint:         360.00 (degrees, or 360.0 if squint is not applicable)

If the satellite is in either a geostationary orbit or an orbit that
does not permit AOS to occur at the groundstation, a zero (0) is returned
for the next AOS/LOS time.  Otherwise, the next AOS time is provided for
satellites not currently in range of the ground station.  If the satellite
is in range, then the LOS time is provided.

The name provided as an argument to GET_SAT must match the full length
name contained in PREDICT's orbital database, and may contain spaces.
The command string passed to PREDICT must end with an end of line ('\n')
character.  The satellite's object number may be used in lieu of the
satellite name.

The visibility codes returned are the same as those displayed in PREDICT's
multi-satellite tracking mode.  An 'N' indicates the satellite is not in
sunlight, nor is it optically visible at the ground station.  A 'D'
indicates that the satellite is in sunlight, but not optically visible
at the ground station.  A 'V' indicates the satellite is in sunlight,
while the ground station is in darkness, meaning the satellite may be
optically visible at the ground station.

If the satellite has decayed, the Next AOS/LOS time will be reported
as 0.  All other values will also be set to zero.  The visibility code
will be set to 'N'.

perl osc translator

More Info on this page: PerlOscScript

OSC messages

See OscMessagesFormat

Broadcast OSC data over WAN

We want to broadcast satellite data from different Ground Stations. It would be nice to use oscgroups http://www.rossbencina.com/code/oscgroups for brodacasting OSC over WAN.

Proceedings: See this page: SatelliteDataOscBroadcasting

sat: SatelliteDataServer (last edited 2011-08-24 12:25:32 by NorbertMath)