Quote: Originally Posted by
toddmw 
Has anyone tried to get the GPS data stream from an AirLink PinPoint modem into GooPs?
I manage about 20 devices remotely and would love to be able to track them in real time using GooPs. They're all accessible via a private IP address on my server.
Is there a specific TCP or UDP port that GooPs is listening on for the AVL data?
Thanks,
Todd
Todd,
GooPs listens on port 51234 for NMEA data. See the FAQ at
http://goopstechnologies.com/faq.htm...application_to
How do I interface my application to GooPs?
GooPs can receive data from other applications via a TCP/IP socket. GooPs listens on port 51234 for messages containing NMEA data. If the message is a raw NMEA sentence GooPs will append it to the local vehicle's data. If the NMEA string is prepended with an ID and host name. GooPs will treat it
as a remote vehicle. GooPs will automatically add any remote vehicle that hasn't already been manually added.
The format is:
<id>@<host>:<nmea sentence>
Example:
joe@joescar:$GPRMC,130043,A,3731.5300,N,12221.2400 ,W,1.0,0.0,082507,0.0,E,A*01
- here is no requirement on the id and host names, they are only used to identify the vehicle in the user interface.
- The socket must be closed and reopened for each message.
- A message can contain multiple NMEA sentences separated by an ascii carriage return/line feed (cr/lf)
- You can save bandwidth by only sending GPRMC, GPGGA, and GPVTG sentences. All others are ignored.
- Unless you need altitude data you can just send $GPRMC sentences.
- Currently only status, timestamp, latitude, longitude, altitude, speed, and heading fields are used)