Hello everyone,
For the proposed experiment on creating a interactive dynamic map of the ampr-ripd systems, I created a special version (2.2).
The daemon accepts a new parameter -L <string>. If this string is defined, it will be sent every 5 minutes to my gateway 44.182.21.1 via UDP to port 59001.
The format I will use is plain and simple gwcallsign@locator, case insensitive e.g. -L yo2loj@kn05or.
If we will ned somehow more data, the string can be replaced wit anything, it is just sent as it is and will be parsed by the backend.
For the moment there is only a simple listener monitoring that port, and I am working on the server and interactive map which will be available at
http://yo2tm.ampr.org/ampr-map/
For those that do not want to participate, there is no need to upgrade.
And even if you do, not setting the -L parameter will not send any data, the result being the same behavior like 2.1.1.
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.2.tgz
http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.2.tgz
Have fun,
Marius, YO2LOJ
Marius.
Just started ampr-ripd-2.2
Would it be possible to use 10 positions long QTH locator?
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
No problem. It is just a string sent in a UDP package.
On 31.05.2017 00:03, SP2L Tom wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius.
Just started ampr-ripd-2.2
Would it be possible to use 10 positions long QTH locator?
Best regards.
Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Messages are coming :-)
root@server:/usr/local/src/ampr-rip-home-server-1.0# ./testserver Listening for home calls... Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.135.85.151: ve3mch@fn03bf Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 11 bytes from 44.165.2.2: sp2l@jo94fm Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.135.85.151: ve3mch@fn03bf Recv 13 bytes from 44.182.21.1: yo2loj@kn05or Recv 13 bytes from 44.182.21.1: yo2loj@kn05or
Marius.
Now, ampr-ripd sends 10 positions QTH locator.
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
As John suggested, I think it would make more sense to send the proposed standard (RFC 1876) Latitude/Longitude LOC record than to use some esoteric ham-only thing like Maidenhead locaters. So what you'd do for a site located at the coordinates 52°22'23"″North 4°53'32"″East at an altitude of -2 meters is put this:
-L 'w1aw LOC 52 22 23.000 N 4 53 32.000 E -2.00m 0.00m 10000m 10m'
Note that many of those fields are optional; you could legitimately put just
-L 'w1aw LOC 52 N 4 E -2'
See the wikipedia article https://en.wikipedia.org/wiki/LOC_record or the RFC for details.
I think this would make it much easier to plot a map point, and it has the advantage that the data could be integrated into the DNS later. - Brian
Note that many of those fields are optional; you could legitimately put just
-L 'w1aw LOC 52 N 4 E -2'
Copy as much as possible from APRS... The goal should be to make it easy to translate between LOC records and APRS posts.
Something like:
"=4742.03NI12207.52W& BPQ32 Igate V 6.0.13.43"
Bill
In my opinion, APRS uses one of the worst protocols in existence; I would avoid having anything to do with it. This is the Internet, we should use Internet Standards. - Brian
On Tue, May 30, 2017 at 03:47:54PM -0700, Bill Vodall wrote:
Copy as much as possible from APRS... The goal should be to make it easy to translate between LOC records and APRS posts. Something like: "=4742.03NI12207.52W& BPQ32 Igate V 6.0.13.43" Bill
And rolling....
root@server:/usr/local/src/ampr-rip-home-server-1.0# ./testserver Listening for home calls... 44.134.32.240 is IR0RM-7 at JN61LR ( Lon: 12.937500, Lat: 41.729172 ) 44.182.21.1 is YO2LOJ at KN05OR ( Lon: 21.187500, Lat: 45.729172 ) 44.88.0.1 is N1URO at FN31NS ( Lon: -72.895836, Lat: 41.770828 ) 44.165.2.2 is SP2L at JO94FM ( Lon: 18.437500, Lat: 54.520828 ) 44.135.85.151 is VE3MCH at FN03BF ( Lon: -79.895836, Lat: 43.229172 ) 44.98.16.2 is W4MLB at EL98QB ( Lon: -80.645836, Lat: 28.062500 ) 44.135.32.201 is VE1JOT at LINUX. (Invalid Grid Square) 44.88.4.1 is K1YON at FN31NX ( Lon: -72.895836, Lat: 41.979172 ) 44.68.220.1 is N2KGC at FN22MO ( Lon: -74.979164, Lat: 42.604172 ) 44.134.32.240 is IR0RM-7 at JN61LR ( Lon: 12.937500, Lat: 41.729172 ) 44.182.21.1 is YO2LOJ at KN05OR ( Lon: 21.187500, Lat: 45.729172 )
@JJ: please put a grid square instead of Linux. @Tom: You can of course put 100 position QTH locator there. I will truncate to 6, since it complicate things to much.
Marius, YO2LOJ
Marius.
Your info duly noted.
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
-
Bill Vodall -
Brian Kantor -
Marius Petrescu -
SP2L Tom