tweiss3

So you can't hear it on I10, but you can at Red Cloud? That could mean it is directional, like the microwave links, could be a bad horn causing a mix of something else and transmitting it only south. It could also be some of the SCADA equipment making a heterodyne, or a bad 932MHz pager transmitter. If it's that bad, I wonder why there isn't one of the UHF systems guys up there all the time trying to figure out why their repeaters are deaf/desensitized.

Holy crap, there is a ton of things licensed there, 2 FM stations, 1 AM station for Ontario Int Airport, 3 AMR trunk systems (2 vhf, 1 UHF), ATT Cellular, State of CA 800, VHF, UHF Trunking systems, VHF low conventional, microwave links, Riverside County VHF, VHF low and 700 systems, plus a ton of private companies. Could be a mix of that much RF, or could be UHF over the horizon radar, or both.

The "by the rules" answer is the manufacturer has to ask for it to be certified for Part 95 for it to be certified. That other sentence is acknowledging that commercial UHF radios have the ability program more than just GMRS frequencies, and also the fact that the technical requirements of Part 90 meet and/or exceed the requirements of Part 95. That being said, as some have said, and other have concluded, there isn't a currently sold new commercial radio that carries Part 95 certification, and meeting or exceeding the requirements of Part 95 (frequency accuracy, deviation, etc.), nobody is going to notice unless you do something stupid. The asterisk here is that ham equipment is not certified for frequency accuracy, and not certified for use outside of the ham bands. UHF commercial radios are usually 380-470, 450-512 or 380-512, which just happens to have GMRS within it's certified limits of operation. Using modified ham equipment is problematic and should be avoided.

This tracks. I never thought about the crossband as links to eliminate duplexers though, that's a good back pocket solution. By the numbers, to get 50db isolation: @145MHz, you need either 700' horizontal separation or 24' vertical separation @440MHz, you need either 22' horizontal separation or 8' vertical separation 50db isolation isn't great, but a repeater will probably "operate" at that level. A decent duplexer will exceed 60db isolation: @145MHz, you need either 2100' horizontal separation or 43' vertical separation. @440MHz, you need either 650' horizontal separation or 14' vertical separation. When discussing separation, it is from the closest part of each antenna, usually clamp to clamp for horizontal separation and top of the bottom antenna to the bottom of the top antenna.

This will be annoying when I have to travel there. Another reason why I wish Kenwood didn't discontinue the KCT73/72, which would be completely "handsfree". I hope it gets shot down. I know there are other exceptions beyond ham in other states. I think the real problem is a few highly urban cities have issues with all laws being followed, yet they actually account for less than 5% of the state area.

For an all in one deck radio, the 100M is hard to beat. I can now test VHF Lo, but I haven't had the time or equipment to mess with it, as I only have the 1 100M. I still love my NX5700/5800 dual deck setup, but it also helps that I have scanners also installed next to the Kenwood.

221-229 is way off from the bottom end of UHF 380, no it won't go that far. I still love mine.

Check the pin layout and give it a try. It is likely to work with an extended cable, but you can't know until you try.

I don't listen to SW too much, but occasionally I will tune around SW on my IC7300. I have an old 1934 RCA Victor C7-6 (6 tube) "wideband" (540kHz-18.0MHz) receiver that I collected from my grandfathers estate that I need to have someone put on a varriac to see if I need a to recap the whole thing or not. I'd love to have it as a centerpiece in the shack one day.

I'll add, based on your current footprint and what you are trying to accomplish, you need to bring in a professional that can discuss specific sites and coverages. Your scenario and goals exceed "recommendations" available on a forum. You are now in a detailed design stage, and all of your moving parts need identified and you need to realistically look at cost per site to see if you are willing to spend the money to achieve your goal. From a 10,000 foot view, you appear to be at the go/no-go decision point between leave it alone and spend 6 figures to get started in your linked enterprise.

So there is significant overlap in "communities" that have more than 1 repeater. You may have to do some prioritization of which repeater is linked. You will not be able to link all "4" repeaters to the other systems, as they will clash and you won't hear anything. If you have to have each, lets call them cells, cell completely linked, you will need to simulcast that cell. You don't need to simulcast each area, as those without overlap will be able to operate as an independent repeater. You should be able to link all communities together, simulcast or not, without too much of an issue using an asterisk system like MyGMRS uses, just point it to your master "server". But it sounds like you will have issues in quite a few areas that will require a true simulcast operation, which is not inexpensive.

If your radio's manufacturer publishes detailed specifications to include sensitivity, selectivity and spurious response/emissions then you can view exactly how dirty/clean the transmitter is. Here is a hint, if they don't publish that information, you probably don't want that radio.

Reading back through this, I'm not 100% sure you need "simulcast". Do you have significant overlapping coverage of multiple repeaters or do you just have a ton of coverage pockets without overlapping? If the second, you wouldn't need simulcast, just need some version of linking. If you do have overlapping coverage, you would need true simulcast with GPS sync and voting. The RTCM module is only part of the simulcast solution, but it does require IP links. Another option is new hardware. I can't find a definite answer, but the NXR-1800e has simulcast capabilities baked in (its a license feature), and will permit IP or RF backhaul. Just remember, if you are doing RF backhaul, you must remain within GMRS frequencies, you cannot mix/match the RF link with ham or Part 90 frequencies.

Simulcast is not cheap. You can "roll your own", still about $1000+/site with https://allstarsimulcast.com/. Note, you cannot link into Allstar/Echolink. Second option, which is widely commercially available is JPS: https://jps.com/products/snv-12/ I would also suggest you reach out to your Motorola vendor and discuss if there is a Moto solution to simulcast on analog for your chosen hardware.

Yea, I know of one analog smart net system still being used today. Anyways, if you have eligibility 90.35 (a), then it's only time & money at that point.

The coordination thing is pretty big. The same Line A & Line C that cause issues with GMRS cause more issues with business band licensing. This should be discussed with the coordinator. If you have to coordinate with Canada, that can take months to clear, and if there is a conflict, you pay for coordination again. If you want to go down this path, I would recommend reading all of eCFR Part 90 top to bottom, then read it again in 2 days after you had time to process it the first time. The number one thing you will hear from your consultants is to not buy the equipment BEFORE you get licensed, and I agree with that. Lastly, there are fees you pay to the coordinator, then there are fees paid to the FCC. If I remember correctly, initial filing was $205, and a major modification is $105. Also don't be surprised if your license pops up with conditions of approval noted. It's not necessarily hard, but time consuming, and the actual application on the FCC website is not well designed.

With the EFHW, you can pick to either cover the digital/cw portion of 80, or the phone portion. I chose digital. The 7510 is phone portion of 80, and the 8010 is digital portion of 80. I've used it on phone, SWR is something like 5:1, was only used for quick checkins to an 80 meter net.

I have a MyAntennas EFHW for 10 through 80. I have mine between two trees, but the feed side is only 25' up, and the far side is up about 40. It's no where near as tall as recommended, but it's logged nearly 5000 contacts. You don't have to have the far tree right at 160', it could be 200+, just use paracord to finish the bridging.

Voice scramblers (inversion scrambling) won't prevent the tones from being scanned. Audio will just noise, but the tone still gets transmitted in the same place.

No, the RSM cord is not used as a counterpoise. On some it was used as an extension for the antenna to get RF above the user (see @Lscott above), but it's designed to be isolated from the RF. Kenwood actually had to redesign the KMC-45 to the KMC-45D to add additional isolation because the DMR TDMA RF was causing issues with the audio circuit. The reason you are probably getting worse reception is due to its proximity to your computer/monitor/etc. You have to remember, almost everything today that has electricity running through it does and can cause RFI and make "radio" frustrating to use and track down this interference. For example, I live 1.5 miles south of 1350AM (5kW) and 98.1FM (50kW) and 1 mile north of 1150AM (5kW), and boy does their mix cause an issue on some bands.

Here is the thing, how often do you actually think you will need to use your repeater? Your actual need will be much less than you think. Most things times its used, simplex works just fine.

This x100

Thanks for the input. The 67i looks like a better unit for my use, the 7+ days of battery life is huge, where as the Montana way underperforms in that category. This device is intended to way outlast a cell phone, 18 hours is not acceptable.

My club offers an online course every few months, both for the Tech and General. It's done via Zoom, and allows for questions and discussion.

Which InReach device do you have. I've been meaning to get a handheld GPS for various trips, and was looking GPSMAP 67 with the InReach included.