• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

Three new software utilities for chasers

Joined
Feb 20, 2019
Messages
41
Location
Decatur, GA
I've taken advantage of the pause in a lot of my normal activities due to corona to reinforce my chasing ability. In addition to the hardware side in my truck, I've been working on the software side of things. Some of these arose just due to my unique setup, but one in particular should hopefully have a good bit of use within the wider community. Now I recognize that I'm a low-post, not well known member. As a software developer, I fully appreciate the hesitation people would have in downloading a program like this which is one reason I have open-sourced this software. That way, you can pull the source yourself and build it and not rely on a third party binary. If you're not familiar with building code yourself, then the best I can say is wait for a more trusted member here to check everything out, or have a friend do it. So, all that fun stuff aside, here are the three programs I've written.

APRS2SN
I've mentioned this in a few threads, but I've come up with a stopgap individual solution to the APRS integration with SpoterNetwork being broken. The idea behind this program is you run it on a home computer with a stable internet connection before going into the field. As you broadcast APRS position packets, if they're picked up by an iGate and routed to APRS-IS, then this program will update your SpotterNetwork position using the web API. It doesn't care about SSIDs currently, though that's certainly something I can look at, but I did set it up to optionally look for a particular sequence in the APRS comment field. I did this mainly for backwards-compatibility with the old !SN! character sequence in the comment field. If your APRS transmitter is already setup for the old system, then configure this to look for !SN! and you should be good to go. But if want to look for something else, you have that freedom too.

GPSD2SN
This is a Python script intended to send position information from the GPSD daemon to SpotterNetwork. In my chase vehicle, I have a RaspberryPi computer mounted under my backseat and a GPS puck mounted behind my cab on my antenna rack for a nearly unobstructed view of the sky. GPSD allows me to share the single puck and its location with many devices. Since I have the location, this script lets me send it directly to SpotterNetwork rather than needing another computer running a SN Position app or program.

GPSD2COM
As I said before, my chasing setup involves a RaspberryPi computer with a GPS puck attached. I wrote this program to allow applications that require a COM port GPS (such as GRLevel3 at least for me) to receive position information over a network from GPSD using GPSD's ability to send data in the NMEA format. Using this program requires a virtual com port pair, there are several solutions out there.

If you have any questions, comments, suggestions or any other feedback, please let me know! I hope some of these can be useful to the community. I know I'll be using all three when I chase next.
 
I am going to look into building something similar. I am also looking for a way to log my gps location for future use in recap videos and with Qgis.
 
I don't know if anyone actually uses this stuff, but if someone does, I updated my GPSD2SN script last week and tested it in the field today. Biggest change was correcting the speed information, I was sending the raw m/s to SpotterNetwork instead of MPH. I also updated its connection to GPSD and set an automatic reconnect after 45 minutes. Last time I was chasing, I had to stop and restart the script about once an hour for it to keep updating. GPSD is the only part of the script that maintains a continuous connection, the updates to SpotterNetwork are through HTTP POST requests when needed.
 
Back
Top