JS8CAll/FT8/JT65 Log Scrapers
Ok, for a bit of background and description of this. It exists because I was working with JT65 a few years ago and wanted a way to visualize the gridsquares of the stations I was copying. So I implemented in my favorite position mapping and display tool, APRSIS32. Here's what I posted when this support was originally implemented for JT65 on 8/8/2012 8:39PM:
Ok, here's the feature that I mentioned earlier today. This is NOT the final implementation, but I'm releasing it in this form to solicit feedback. If you use JT65-HF, then you should have a JT65hf-log.csv somewhere. You can tell where it's at via JT65-HF's Setup / Configuration tab at the bottom labeled "Location of RX/TX history file". Make a note of that as you'll need to navigate to it to set up the JT65 visualizer object.
Well, that was longer than I expected and I'm not sure how much, if any of it, changed since then. But that's the gist of it.Kick it all off with Configure / Objects / New JT65 Confirm Yes to Create JT65 Object At ME (the only place you can create it) A file browser dialog will appear asking you to locate the JT65hf-log.csv file. When you find the proper directory and file, click Open. In the Object dialog, you'll want to check Enabled. The default name is <yourcall>-JT and the default symbol is DX (primary table %). Whatever -SSID you give the object will be added to the JT65 spot callsigns when their objects are created (-JT is used if you don't specify an -SSID). The symbol of this object is also used to create the spots. The only other functioning control in this configuration is the Reset checkbox. If you check that, then on the next update, ALL of the spots are processed instead of only the new ones. Of course, spots older than <Stations.MaxAge> aren't loaded no matter what, but Reset is a handy way to pull in more spots if you've increased <Stations.MaxAge> across a restart. When you Accept the new object, you should see a series of <callsign>-JT (or your object's -SSID) show up in the packet scroller as internal packets. And your map should show them as a grid-square ambiguous stations (purple rectangle). If you have too many and you're using a new instance, you may have to increase Configure / Screen / Label / Max Visible to see them. You'll probably also want Screen / Labels / Callsign checked to be most useful. If you want to see ONLY the JT65 objects, you should have a View / Shrieks / !JT65! that will filter the view. Kind of handy in a MultiTrack if you're doing this in an instance that's also getting an APRS-IS feed. I bring up a MultiTrack on my own -JT object and save it as "Always". Oh, and Configure / Messages / Lookup(WHO-IS) / Full Address is also a handy thing to check for quick full lookups of a *-JT station. For those of you that do JT65, let me know what you think. For the rest of you, please pardon the distraction, but this is a test bed for some of the other future visualization features that will be more directly related to APRS.
What's new is the ability to process the ALL.TXT files from
JS8Call and FT8 the same way. The default -SSIDs for the objects
are different (-J8 and -F8), and they are #hashes instead of
!shriek!s. JT65 objects remain as !JT65! however.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 4/27/2020 1:58 PM, Arnold Harding. - KQ6DI wrote: