Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Solar
SFI 128
SN 73
A 6
K 1 Quiet
X-Ray C2.2
Wind 403.6 km/s
Aurora 2
Updated 23:00 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots
Select a band above to load spots
Ready — select a band to fetch live spots

Steven Taylor

Members
  • Joined

  • Last visited

  1. so ive been using N1MM for probably 4 or 5 years now and honestly it just works, i know where everything is and the contest support is basically unbeatable for the stuff i do like CQWW and SS. but a buddy of mine keeps telling me to try Log4OM and i finally installed it last week to poke around and honestly the interface is way nicer for day to day logging, the QSL tracking and DXCC stats stuff is actually usable without having to dig through seventeen menus here's my actual question though — does anyone run both? like N1MM for contests and Log4OM for regular rag chew and DX chasing? i was messing around with the ADIF export trying to get them to stay in sync and it kinda works but feels janky. also i have WSJT-X in the mix for FT8 and getting all three of these to play nice with each other without duplicate entries is becoming a whole thing. UDP port conflicts, WSJT-X wants to log to one place, N1MM is listening on another port, its a mess anyway not sure if im overcomplicating this or if there's a cleaner workflow that people actually use. running windows 10 if that matters
  2. so i passed my technician exam about three weeks ago and finally got my callsign last week. been listening around on my baofeng mostly but i keep hearing people talk about checking into nets and i guess i dont really understand how that works. like do you just tune to a frequency and wait? or is there a schedule somewhere? i found some stuff on the arrl website but it was kind of overwhelming and i wasnt sure what was current vs old information. also someone at my local club mentioned there are special event stations sometimes and that logging a contact with one gets you something? a certificate maybe? i didnt want to ask too many questions at the meeting because i already felt like i was slowing everything down with basic stuff. anyway any help appreciated, just trying to figure out where to actually start participating instead of just listening
  3. im kind of in the same boat as you tbh, been using an app called Morse Mania on my phone just because its there when im waiting for something. not sure if its the best but its something. also theres a guy on youtube who does videos of slow CW QSOs with the text on screen and i found that weirdly helpful just to see what an actual contact sounds like even before i could copy any of it
  4. so ive been messing with this for about three days now and im losing my mind a little. running a Kenwood TM-D710G with the built in TNC, got it set to beacon every 10 minutes on 144.390, SSID is set right as far as I can tell, the radio shows the packet going out in the log, but when I pull up aprs.fi and search my callsign nothing shows up. not even old data. my buddy two miles away can see his own packets just fine. I double checked the audio levels, PTT seems to be keying, I can actually hear the packet burst go out over the air. path is set to WIDE1-1,WIDE2-1 which should be fine for my area. not sure what im missing here. is there some kind of validation or registration thing on aprs.fi I dont know about? or is this more likely a digipeater coverage issue in my neighborhood. I'm in a pretty suburban area but there's supposed to be a few igates within range according to the map.
  5. I actually just got my ticket a few months ago and havent tried 6m at all yet, didnt realize it did stuff like that. I thought it was basically dead most of the time? maybe i need to dust off that old beam i found in the garage and see if it covers 6. this hobby keeps surprising me every time i think i have a handle on it
  6. the oscillator and filter questions tripped me up too but i just kept doing practice exams until i was consistently hitting like 85% and then went and took it. didnt fully understand all of it but enough to pass. the actual exam felt easier than the practice pools for some reason, maybe just nerves going away once i sat down as for the bands yeah the extra segments on 20 and 40 are worth it if you do any CW or chasing DX, thats where a lot of the action is during pileups
  7. i just passed mine last month so this is fresh in my mind. the filter design and transmission line questions tripped me up the most, theres a handful of questions where you really do need to understand whats happening not just guess. like the ones about standing wave ratios and how a mismatched load affects the input impedance of a feedline, that stuff requires actual understanding or youll get it wrong under pressure. but the question pool is public so you can just drill it on HamStudy until you hit 90% consistently and youll probably be fine. took me about 8 weeks going slow. and yeah the Extra segments on 80 and 40 are genuinely less chaotic, noticed that immediately after i upgraded
  8. honestly the rate thing is real but people oversell how seamless it is when you're starting out. the first contest i tried SO2R i probably made it worse because i was spending mental energy on the second radio instead of working the pile on the first one. the real gain comes from using radio 2 to find your next CQ frequency or grab a multiplier while youre in a slow period on radio 1, not trying to literally work two stations at the same time which is where people get themselves into trouble. with a K3 and 590 you actually have a decent setup for it. the interlocking and audio routing is the part that'll take you a weekend to sort out before you even think about a contest. N1MM has the SO2R stuff built in pretty well now but you need to spend some real time with the config. i'd say try it on a shorter contest first, like a state QSO party or something low stakes, before you throw yourself into SS or CQ WW with it. the contacts per hour improvement is real once its muscle memory but it doesn't happen in your first attempt
  9. yeah im kind of in the same boat haha, been licensed two years and i still have a stack of incoming cards on my desk that i keep meaning to reply to. my buddy told me if its a bureau card you have maybe 6 months before it looks rude but honestly most people are pretty understanding i think. the LoTW thing though — make sure your callsign certificate is actually current because mine expired and i didn't notice for like three months and none of my uploads were going through, that was annoying to sort out
  10. yeah the audio level thing bites everybody at least once. in Vara HF theres that little drive level indicator and you really want it sitting around 30-40% on transmit, not pegged. if the Signalink TX knob is cranked up youll overdrive the vara modem and it just wont decode properly on the other end. also double check that the IC-7300 isnt doing any compression or processing on the TX side — turn all that off, data mode should be clean passthrough basically. for the dial frequency, Vara HF on 40m most people use around 7.101 or check the RMS list in Winlink Express itself, it shows the exact dial freqs for each gateway. the list can be a bit stale sometimes so if a gateway shows green but wont connect try the next one down the list. and yeah peer to peer is totally different, thats for connecting directly to another station without going through any gateway infrastructure, useful for field day or emcomm when internet is down but not what you want for normal message handling to the internet side.
  11. ok so i just passed my general last month and got my sequential call which is fine but honestly its pretty ugly and long and i was looking into getting a vanity call instead. ive been reading the FCC ULS stuff and some old posts on here and im getting kind of contradictory info about how the whole thing actually works now. from what i understand there used to be some kind of preference system where like extra class licensees got priority over generals during the application window, and certain groups like close relatives of silent keys could claim a call before it went general public. is that still a thing or did they change it? i keep seeing references to the old system and im not sure what still applies. also is it literally just whoever submits first once a call becomes available, or is there still some kind of window period where multiple apps get batched together and then sorted by preference? i really dont want to go through the whole process and miss out because i didnt understand how the timing works. any help appreciated, been lurking here for a while and you all seem to know your stuff
  12. completely normal, dont worry about it. that 7-10wpm wall is real and pretty much everyone hits it. the writing thing -- honestly just keep doing it for now. the whole 'copy in your head' advice is good advice but its more for when youre trying to break through the 15-20 range. at 10 theres nothing wrong with writing, youre still building the character recognition reflex and your brain hasnt fully automated it yet. what helped me more than anything was listening to actual QSOs on the air even when i couldnt copy most of it. like i'd tune around 40m in the evenings and just let it wash over me. your brain starts picking out callsigns and common words like CQ and 73 and DE without even trying. took me almost a year to get comfortable at 15wpm but i wasnt super consistent about practicing either. if youre doing 20-30 min every single day youll probably get there faster than i did.
  13. so i've been wanting to do this for probably two years now and i finally just committed and built one of those Pennywhistle kits, the 40m version. took me about three evenings spread across a couple weeks because i kept second-guessing my solder joints and redoing stuff that was probably fine to begin with. anyway got it done, threw it in a bag with my little notebook and a 9ah lipo i had from a drone project, and drove out to the county park about 20 minutes from my house. strung up a wire antenna between two trees — just a simple end fed with a 9:1 unun i built last winter — and honestly i was not expecting much. figured id make one or two contacts and call it a win. worked 11 stations in about 90 minutes running around 4 watts. one guy in new mexico who was pretty loud, couple stations in the southeast, even heard but couldnt pull a european station out of the noise. the whole setup weighs almost nothing and i genuinely had more fun than i have on my home station in months. something about the constraints of it, the low power and simple wire, makes every contact feel like it actually means something. if anyone is on the fence about getting into QRP or building a kit i really cant recommend it enough. my soldering is mediocre at best and the kit still works fine.
  14. so ive been a ham for about two years now and i keep hearing about go-kits and emergency preparedness stuff especially at the club meetings but nobody really sits down and explains what they actually have in theirs. like i get the general idea — radio, power, antenna — but beyond that i dont know where to start. my situation is i have an FT-857D which i love but its kind of big, and i also have a little Yaesu FT-65 HT. i was thinking maybe build around the HT for portability but then i lose a lot of capability obviously. also i live in tornado country so the go-kit isnt just for served agencies stuff, i genuinely might need it someday for real. that kind of changes my thinking a little. what do you guys actually have packed and ready to go? and how do you handle power — are you running LiFePO4 or just sticking with a big SLA? i priced out a 20ah LiFePO4 and it wasnt cheap but maybe worth it. anyway any thoughts appreciated, even just telling me what you wish youd done differently when you built yours
  15. had almost the exact same thing happen when i first set up my remote. turned out the issue wasnt the upload bandwidth itself but the router at the remote site was doing some kind of traffic shaping or QoS thing that was deprioritizing the UDP audio packets once the TX keying traffic started hitting at the same time. basically the router saw two simultaneous streams and just decided the audio was less important. i threw the remote station machine into the DMZ temporarily just to test and the dropouts went away completely. not a permanent fix obviously but it told me where to look. also worth checking if your ISP at the remote end does any burst throttling. 35mbps sounds like enough headroom but some cable providers will let you sustain that for a bit and then quietly step it down when you hold the connection open for more than a minute or two. RemoteHams audio stream isnt huge but if the pipe is getting squeezed even a little it shows up pretty fast.

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.