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 B9.3
Wind 433.7 km/s
Aurora 2
Updated 23:30 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

Michael Moore99

Members
  • Joined

  • Last visited

Everything posted by Michael Moore99

  1. Hey welcome to the hobby. So for your situation - you generally only need the transmit tone set, not the receive tone. The receive CTCSS (sometimes called decode) is optional and just filters out what you hear on your end, which honestly most people leave off so they can hear everything coming through. The fact that you're hearing others is a good sign your radio is in the right ballpark. The not hearing yourself come back is worth looking into though. Could be your offset is wrong - most 2m repeaters use a standard -600 kHz offset but not all of them, so double check that against whatever directory you found it in. Also some repeaters have a courtesy beep that comes after you unkey, if you're hearing that then you're definitely hitting it fine and people just might not be around at that time. As for getting on - yeah just key up, say your callsign, and something like "[callsign] monitoring" or "listening" is totally normal. Some people say "for any traffic" which sounds old fashioned but you hear it. Dont overthink it, most repeater regulars are pretty welcoming to new folks.
  2. yeah the compression thing is real. i made the mistake of listening to myself on the monitor output of my own radio for months and thought i sounded great, then got a recording from someone who recorded off the air and it was pretty rough. the monitor doesnt tell you the whole story because its pre a lot of the processing stages depending on the radio honestly the best thing i ever did was ask a local guy i trust to just give me honest feedback while i tweaked settings in real time. not glamorous but it works. took about 20 minutes to get somewhere reasonable
  3. so anyway i finally got it working after like three weekends of messing around. went with a Yaesu FTM-300DR in the truck and honestly the hardest part wasnt the radio itself it was figuring out where to run the power cable without it looking like a disaster in the cab. ended up going under the carpet along the sill and straight to the battery with an inline fuse close to the battery like youre supposed to do. the antenna is a Diamond NR770HNMO on a NMO mount i drilled through the roof of the bed cover which i was kinda nervous about but it worked out fine. SWR came in under 1.5 across most of the 2m band so im calling that a win. the reason it took so long is i kept going back and forth on whether to do a trunk lip mount or just drill. everyone online has opinions and half of them contradict each other. eventually just committed to drilling and im glad i did, no flexing or movement at all compared to my old mag mount situation. if anyones on the fence about the FTM-300DR vs the 500D, i went with the 300 because i didnt need the extra power and the price difference was pretty significant. so far so good, hits all the local repeaters no problem and ive been having fun just driving around monitoring the county ARES net. anyway just wanted to share in case someone is going through the same decision paralysis i was
  4. so we finally ran our big tabletop-turned-actual-exercise last Saturday and I wanted to share how it went because honestly it was way more eye-opening than I expected going in. The scenario was a multi-day severe weather event cutting off the county EOC from the state, and we had to pass health and welfare traffic plus coordinate shelter assignments using just HF and a couple VHF repeaters. The stuff that tripped us up most wasn't the radio part — it was the paperwork and the handoffs. Like someone would pass a message perfectly on the air and then the person on the receiving end at the EOC table would write it down wrong or not at all. We had ICS forms everywhere but nobody was really sure who was supposed to fill out what. Also one of our main guys had a laptop with all the Winlink templates and his battery died about 2 hours in and we hadn't tested whether anyone else had the same setup. Spoiler: we hadn't. The HF side actually held up better than I thought. Got into the state net with my IC-7300 running off a deep cycle and the end-fed seemed fine even with all the people walking around. But there was this one period where we lost the local repeater because somebody forgot to check the backup power at the repeater site before the drill. So that was a fun 20 minutes of scrambling. Anyway curious if others have run exercises like this recently and what lessons came out of it. Feels like every time we do one we find three new things to fix.
  5. so i passed my technician exam last thursday and just got my callsign in the ULS system two days ago. spent the first day just listening on my baofeng (yeah yeah i know) and finally worked up the nerve to key up on the local 2m repeater yesterday afternoon. the net control was super patient with me, i totally fumbled my callsign the first time i tried to give it phonetically, mixed up november and november... wait no i mean i said november twice instead of going to the next letter lol. anyway the guy on the other end just waited and then came back to me like it was totally normal. talked for maybe 3 minutes about signal reports and weather which i know sounds boring but honestly felt like the coolest thing ive done in a while. already studying for general now because i want to get on HF so bad
  6. honestly the best thing I did was just join a local ARES or RACES group and see what everyone else was using before I bought anything. saved me from making a bunch of expensive mistakes. your county emergency coordinator has probably already thought through a lot of this and has preferences about what frequencies and modes the group actually operates on — theres no point building an elaborate HF setup if your local group is all on 2m FM for the first 48 hours of any activation anyway. that said a basic kit with an IC-705 or similar and a decent battery plus a j-pole you can hang somewhere gets you pretty far. dont overthink the antenna situation too much at first, a mag mount on a car roof works fine for a lot of situations.
  7. had a similar setup running for about a year with a 7300, totally worth doing even if the first couple weeks of config is kind of a pain. one thing that tripped me up was the audio routing on the shack PC — you really have to nail down which virtual audio cables are going where or you'll end up with feedback loops or the PTT not keying right. VAC or VB-Cable both work but get that sorted before you even think about the SDR side of things. also worth mentioning, fixed wireless can have latency spikes that come and go depending on tower load and weather. i'd run something like PingPlotter from the shack box out to a server for a few days and see what the jitter looks like before deciding if CW is even viable for you. SSB was totally fine for me even when latency was a bit inconsistent.
  8. that quiet period thing is so real and nobody talks about it enough in training. every exercise is kind of go go go but a real activation can have these long dead spots and yeah you gotta stay disciplined. what i usually do is use that time to double check my gear, make sure my antenna connections are still solid, review any messages that came through, keep my paper log current even if nothings happening. basically give yourself small tasks so your brain doesnt wander too far. also 11 hours on your first real one is no joke. good on you for sticking through it. the paper log backup thing your EC pushed for is exactly right, ive seen digital setups fail at the worst times and if youre not keeping parallel records you can end up in a real mess trying to reconstruct a comms log after the fact. sounds like you've got a solid group.
  9. so i finally finished my first scratch built QRP rig, been working on it for about 3 months on and off. its a single band 40m CW rig loosely based on the Pixie design but i made some changes along the way mostly because i couldnt find the exact parts. ended up with somewhere around 500mw output which i know isnt much but i was honestly just happy it made any RF at all when i first keyed it up. got my first contact with it last weekend, guy in ohio, im in michigan so not a huge distance but man it felt like i worked dxcc or something. the whole thing runs off a 9v battery and i took it out to a park with my end fed wire and just sat there for a couple hours calling CQ and working a few stations. couple things im not sure about tho. my sidetone sounds a little weak and i cant figure out if thats a component value issue or something else. also im getting what sounds like a slight chirp on my signal, had one guy mention it. i think its a power supply stability thing but im not sure. anyone dealt with chirp on a homebrew rig before and found a fix that actually worked? dont want to add a ton of complexity but also dont want to be that guy with the ugly signal
  10. lcwo.net if you havent tried it already. i was in the exact same spot last year and switching to that site helped a lot, plus theres a whole community of people tracking their progress which kept me motivated. also honestly just getting on the air even when you feel like youre not ready -- there's a slow net on 40m that runs weeknights and everyone there is super patient. copying real QSOs is different from copying practice files in a way thats hard to explain but it really does help
  11. yeah i dont have experience with RemoteHams specifically but the sharing-an-SDR-with-the-club thing is something we looked into a while back. we ended up going with OpenWebRX running on a local server at the club station and just punching a hole through the firewall for club members, which sounds scarier than it is if you lock it down properly. worked great for letting people monitor 20m and 40m without giving them actual transmit access, which was the whole point the internet linking question kind of depends what you mean by linking, if you mean tying it into like an Allstar node or something that's a whole different rabbit hole and probably overkill for HF monitoring purposes
  12. not going to lie the commercial band decoders are pretty decent and not that expensive if you shop around. microHAM makes a nice one and theres some eastern european stuff on ebay that people seem to like. but building it yourself is half the fun right so dont let me talk you out of it. one thing i will say — if you go the Pi route, look at a Pi Zero 2W instead of a full Pi 4 or whatever, way less overkill for something that just needs to read a voltage and flip some relays. and you can run a little flask app on it and have a webpage showing your current antenna state which is kinda neat for shack monitoring. i did something like that for my rotor controller and it works surprisingly well.
  13. so ive been messing around with an arduino uno i had sitting in a drawer for like two years and finally found a use for it in the shack. the idea is pretty simple — i want it to handle PTT keying for some digital modes and maybe eventually tie in a relay board to switch antennas based on band conditions. im running an IC-7300 and the USB CAT control is already working fine in WSJT-X, but i want to do some more custom automation stuff that doesnt fit neatly into whatever the software offers. right now ive got a basic sketch going that just monitors a serial command and triggers a relay to pull the PTT line low. its working but the timing feels a little sloppy, like theres a noticeable lag before it actually keys up. not sure if thats a software timing thing or the relay itself being slow. using one of those cheap SRD-05VDC-SL-C relays from a board i got off amazon. wondering if i should switch to a solid state relay or maybe just a transistor circuit instead. also thinking about adding a Raspberry Pi to the mix to run like a headless logging server or something. has anyone bridged arduino and pi over serial or I2C for a ham project? feels like it could get complicated fast but im curious if its worth the rabbit hole.
  14. honestly you just absorb them, thats really it. after a while QRM just means interference from other stations the same way a regular word would, you stop thinking about what the letters stand for. the ones that come up constantly on HF are QRM (interference from other signals), QRN (static/natural noise), QSB (fading, like your signal going up and down), QRZ (who is calling me, or sometimes used wrong as like 'is the frequency in use' which bugs some people), QRT means shutting down, QRX means standby, QTH location, QSL confirmed. those probably cover like 80% of what youll hear day to day. the voice thing youre noticing is real, some guys do use them kind of performatively on phone. purists will tell you Q codes were designed for CW and written communication so using them on voice is technically redundant since you could just say the words, but its so ingrained in the hobby at this point nobody really cares. just dont let anyone make you feel weird about it either way.
  15. near the fence might actually be fine depending on what the fence is made of, chain link is obviously going to cause issues but wood or vinyl should be okay. i ran my vertical about 8 feet from a wooden fence for a year with no real problems. the radial thing is the real pain though yeah. i did like 20 radials cut to about 33 feet each and just laid them on the ground, stapled down eventually got buried by the grass. took an afternoon but it wasnt that bad. made a real difference compared to when i only had like 6 radials in there. 40m DX definitely opened up for me after that. worked JA regularly which i almost never did with the dipole.
  16. the noise when the engine is running is almost certainly alternator whine getting into the coax through the mag mount. mag mounts don't always make a great ground connection especially if there's any paint or coating under them, even a thin factory clear coat can mess with the RF ground. an NMO mount drilled through the roof with a proper ground to the body of the truck will make a huge difference. its the right way to do it long term anyway. on the coax through the door jamb thing -- yeah i'd be a little careful with that. over time the flexing when you open and close the door can work the center conductor loose or crack the dielectric. most people i know either go through a grommet in the firewall or use one of those flat coax pieces that are made to run under a door seal. takes a bit more work but its worth not having a intermittent connection six months from now when you cant figure out why your SWR is suddenly bad.
  17. so ive been messing around with this idea for a while now and finally started actually building it. the basic concept is that i want the arduino to read the band data output from my IC-7300 and then trigger the appropriate relay to switch between my HF antennas automatically. the 7300 puts out CI-V over USB so im reading that with a small python script on a raspberry pi zero W, and then the pi sends serial commands to the arduino which controls the relays. it mostly works but the timing is kind of janky — like if i spin the VFO fast through multiple bands the relay clicks like crazy and sometimes ends up in the wrong position. im thinking i need to add some kind of debounce delay in the python side but not sure if thats the right approach or if theres a smarter way to do it. also using a 4-relay module i grabbed off amazon, nothing fancy, probably SRD-05VDC-SL-C relays if i had to guess. anyone gone down this road before? curious if theres existing software for this kind of thing or if im just reinventing the wheel here
  18. just wanted to second the thing about logging software pulling in spots directly — that was kind of a game changer for me when i set it up. i was doing the same thing you are, tabbing between browser windows and getting confused. once your logger is watching the cluster and highlighting callsigns you still need on your DXCC list it feels like a totally different hobby almost lol also dont sleep on the DX Alert features some of these sites have, you can set it to email or push notify you when a specific entity gets spotted. i have a few set up for entities im still missing on 40m and its saved me from missing some good ones
  19. so ive been doing morse code practice for about 3 months now and im stuck somewhere around 8-9wpm and honestly its starting to feel like a wall. when i first started i went from basically nothing to 5wpm pretty fast, felt good, thought this was gonna be easy. then from 5 to where i am now took forever and i feel like im not making progress anymore even though im practicing every day for like 20-30 minutes. i'm using the lcwo.net site and also occasionally just listening to W1AW practice sessions. somebody told me i should be using the koch method and setting my character speed higher than my overall speed — like 20wpm characters but 5wpm spacing or whatever — is that actually how people do it? i tried it and it feels completely alien, like my brain just cant keep up. anyway just curious how long it realistically took people to get to 20wpm because right now that number feels like a fantasy. also wondering if theres a point where it just clicks and you start hearing whole words instead of individual letters
  20. so ive been putting off the mars/cap mod on my FT-857D for like two years because honestly the inside of that radio is terrifying to look at. finally sat down with it last weekend and got it done, transmits on all the out of band freqs i needed for some EMCOMM stuff our group has been working on. the mod itself is just a couple diodes on the main board, nothing crazy, but the disassembly is where i lost like 45 minutes because the RF board has this one ribbon cable that is NOT obvious how to release. i ended up looking at three different youtube videos before i figured out there's a little locking tab you push down not up. would have been nice if anyone mentioned that in the written guides. anyway while i had it open i also went ahead and replaced the stock cooling fan with a quieter noctua-style 40mm fan because the original whines like crazy on digital modes when it spins up. big improvement honestly. had to print a little adapter bracket but ran it off the same fan header, works fine. one thing im still thinking about is the IF shift mod i saw on one of the german ham sites, supposedly sharpens up the filtering response a bit. anyone actually done that on an 857 or similar radio? feels like it might be more trouble than its worth but im curious if there's a real audible difference.
  21. okay so i just got my general last month and ive been reading about vanity callsigns and im honestly more confused than when i started. from what i can tell the FCC has this sequential assignment thing where they just give you the next available call in your district, but then theres also the vanity process where you can apply for a specific call? and people are saying there are different application windows depending on whether you have a deceased relative who held the call or something like that? my sequential call that came through is fine i guess but its kind of a mouthful and i was hoping to maybe grab something shorter or just something that feels more like mine. ive been eyeing a couple 2x2 calls in my district that look like they might be available. does anyone know how the timing actually works, like do i just submit on the ULS and hope for the best or is there more to it than that also does it cost anything now, i thought i read the FCC started charging fees but not totally sure if that applies to vanity too or just new licenses
  22. honestly this is something i struggle with, im still pretty new to chasing DX seriously and pileups kind of intimidate me. how do you even know where to transmit when the DX just says QSX 14.195 to 14.210 or whatever — do you just pick a spot randomly at first or what. i feel like im always stepping on someone when i try to find a clear frequency in the split.
  23. The field day rule changes — i think what you might be thinking of is there was a discussion thread on the ARRL members forum about possibly adjusting how remote operation gets scored. its been a point of contention for a while now and i remember seeing something from a section manager mentioning it could come up for review. Dont hold me to that though, could easily be one of those things that gets talked about every year and nothing actually changes. 6m has been exceptional this solar cycle, we're riding pretty high on solar flux right now and it shows. worked EU twice last month which doesnt happen for me often living out here on the west coast. good times to be on HF and low VHF for sure.
  24. so i relocated my 40m dipole a few weeks ago, moved it from a more or less flat inverted-v configuration centered on a 30ft mast to kind of a sloper setup because i ran out of room on the other side of the yard after we got a new shed put in. its still about 66ft total length which should be right but my SWR is all over the place now and im getting like 3.5:1 at the feedpoint on 7.150 which is where i normally hang out. before the move it was pretty flat, maybe 1.4:1 across most of the band. ive checked the feedline connections and they look fine, coax is the same run of LMR-400 i had before, maybe 75ft of it going back to the shack. the far end of the dipole is lower than it used to be, probably only about 15ft off the ground at the drooping end, and im wondering if thats whats killing me. or maybe the angle of the sloper is doing something weird with the impedance? i dont have an antenna analyzer right now, borrowed one before and thats how i got the original tune. just using the rig's built in meter. any thoughts before i climb back up there and start messing with lengths again
  25. oh man dont stress about the doubling thing at all — that happens to everyone including people who've been doing this for decades. it's just RF, sometimes two people have the same idea at the same moment. net control has dealt with it a thousand times and honestly they probably forgot about it before the net was even over. as for "over" — on FM repeater nets most folks around here dont bother with it, it's more of an HF or formal traffic net thing. what you do want to say is something like your callsign when you're done transmitting, especially if it's a busy net, just so people know you're finished. something like "...and that's all I have, W5XYZ" is totally fine. you'll pick up the local habits fast just by listening. sounds like youre doing everything right honestly, showing up and checking in is the whole thing.

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.