Had I set the power amplifying transistor's bias high enough, or did the radio always work this way with the amp? It's good to have data!
I've been collecting reverse beacon spots and QSO data since around the start of this year. The reverse beacon data is collected automatically, inspired by a productivity and documentation talk by Simon Willison.
Last night, rain got into the Project Toucans radio. It's not waterproof enough yet, I guess. Turns out there are whole issues in using Tuna and fruit cans as radio cases that I'd never thought through. The lid is corrugated making it difficult to seal holes against water. Anyway...
Earlier this evening, I had the radio/amplifier combination back up and running, but were they running well enough? Fortunately I had data for that. I queried the data using datasette. I asked about reverse beacon spots since the amplifier was added into the station mix a few days back:
select rowid, id, tx_lng, tx_lat, rx_lng, rx_lat, timestamp, strftime('%H:%M:%S',timestamp) as tod, dB, frequency, Spotter from rm_rnb_history_pres where "timestamp" > :p0 and tod > strftime('%H:%M:%S','00:01:01') and tod < strftime('%H:%M:%S','03:01:01') and dB < 99 order by dB desc
The 'dB < 99' clause removes QSOs (a ham radio abbreviation—Q code—for a two-way contact) which are all reported with a 3 digit RST—another abbreviation, this time meaning Readability (0-5), Strength (0-9), Tone (0-9). The query returned 219 rows of data. It was a little bit much for me to be able to get a handle on. In the meantime, while I was thinking through the data analysis I made two QSOs, one to KN6SSO in California with a received RST of 339 and one to N7SE in Colorado with RST equal to 539. I mean, two QSOs in one night is way above average for the Rockmite, but the reported signal strengths were comparatively small, 3 out of a possible 9. Whether or not the radio and amplifier were working as good as before the fix was still inconclusive.
I finally remembered that I had turned down the bias on the power transistor in the amplifier. That would indeed reduce signal strength, so I brought the radio down to turn the bias up on the amp. That netted me a report of a 10 dB from K3PA-1. That was pretty good, but was it as good as before? Then, it occurred to me, I could limit my search down to just K3PA-1 and find out.
select rowid, id, tx_lng, tx_lat, rx_lng, rx_lat, timestamp, strftime('%H:%M:%S',timestamp) as tod, dB, frequency, Spotter from rm_rnb_history_pres where "timestamp" > :p0 and tod > strftime('%H:%M:%S','00:01:01') and tod < strftime('%H:%M:%S','03:01:01') and dB < 99 and Spotter = "VE6JY" order by dB desc
Here are the results:
Ignoring the single exception in the first row, 10 dB at the time of night I was operating was a respectable result for the radio/amplifier pairing. The bias adjustment did the trick!
Just to make really sure, I also cohse VE6JY which had just in at 20 dB. The results
once again showed that while 20 dB wasn't the best signal that had ever come out of the Project TouCans rig with respect to VE6JY, it was solidly within the range of historical results! The fix had worked well enough!
Here's a map of this evening's spots and QSOs. The link will take you to an interactive map in Google Earth. Yellow markers with the letter 'R' represent reverse beacon spots. Blue circles with antenna symbols represent QSOs, including my first ever QSO to Stockton, CA!
Comments
Post a Comment
Please leave your comments on this topic: