rdunajewski

What is your callsign? Has it been at least 24 hours since it was issued by the FCC?

Hey everyone, there was an issue this morning with showing the repeaters. It's been fixed, so let me know if you still have any issues.

Just in case anyone checks the forums before the main site... we have a new myGMRS! After well over a year of fooling around with the new website, I have finally launched it. This is a big leap in technology since the original website was created in 2006 and only had a few incremental updates over the years. This new platform will allow us to put out quicker updates, brand-new features, and bonus features for Premium Members. Premium Membership is an optional subscription where you can remove ads from the website, generate PDF reports of repeaters and licenses in any state, and create your own Club listing (part of the forums) so you don't need to create your own website! All of the existing features of myGMRS will remain free, of course. A new mobile app is also in the works, although we're not close to a release date for that. The long-awaited iOS version will be part of the release, as well as a completely new Android app. Since this is such a radically different website, I'm sure there will be some issues along the way. If anyone runs into bugs or problems of any kind, please don't hesitate to submit a bug report at this Google Forms URL rather than the forums or by email (as it'll be much easier to review): https://docs.google.com/forms/d/e/1FAIpQLSe6XLmCW-UU0Bp9lN9zM3L9gO_TCkArIN2oY-hOLG9x01B3lg/viewform Thank you everyone for the wonderful support and thank you to our Beta testers. You know who you are! Have a Happy New Year!

We do carry the URIxB's separately on our store: https://shop.mygmrs.com/products/dmk-engineering-urixb?_pos=1&_sid=9be424275&_ss=r You're right, the supply of the Raspberry Pi 3B+'s is really slim right now. There's lots of price gouging going on from any vendors who still have stock of them. For anyone who has the Pi 3, you can get the software configured for you by purchasing an SD Card from us, or you can download the image and run the configuration script yourself if you know your way around Linux.

Just chiming in here in case anyone has a similar issue. It looks like the SimpleUSB configuration file needs to be set to only care about a valid CTCSS signal as a receive indication for the radio interface used here (RIM-Maxtrac). Pin 8 is set properly but SimpleUSB by default expects to see a valid COR signal AND valid CTCSS signal before it believes it's receiving a valid signal. So if only pin 8 is working, the node is waiting for the COR pin (not used in this case) to also change. The signal polarity also matters, since Pin 8 is set to active high, the simpleusb.conf file should be set to use "carrierfrom = no" and "ctcssfrom = usb" for active high logic.

Hi Larry, Your callsign follows the pattern WXXX###, so that's the letter I in your callsign, not the number one. The callsign is available in our database so you should be able to register with no issues.

There isn't one planned just yet, but it's a good idea. For now, I recommend the Chrome plugin called Dark Reader which will work on all websites, and you can choose to allow the light or dark mode for certain sites if they look bad in dark mode. I know it saves my eyes when I'm working late at night with two monitors. You can also change the contrast to suit your vision needs in case the default doesn't offer enough.

LMR400 is known to have noise (static) issues when used on a repeater. It has to do with the foil and braid being in contact with each other on the shielding, which can cause noise on the RX side when the TX is active. Heliax is preferred over LMR400 or anything else with a foil/braid combo in contact with one another. LMR400 is perfectly fine for non-repeater use, however.

Your order was sent to the warehouse and should be shipping out today. You'll get a tracking number as soon as it actually ships. If anything changes I will email you.

@lee.lockwood @btrogdon I think some of the TX nodes and the NC nodes are the main ones still affected.

It should be set to 10MB maximum storage with no limit on the size of the photo or screenshot.

Oh and I strongly recommend backing up any .conf files you may edit because it's easy to foul them up and then Asterisk won't load. Make a copy before you edit them.

There's a file called rpt.conf under the directory /etc/asterisk which has lots of settings for tweaking the courtesy beeps, morse/voice ID, hang timer, and scheduling. It can act as a full-featured repeater controller if you wish. You just need to reload the configuration with "rpt reload" from the Asterisk CLI (by running "sudo asterisk -r") or just restarting the Asterisk service with "sudo service asterisk restart".

Assuming you're using the SimpleUSB audio interface, you can run "simpleusb-tune-menu" from the SSH command line. You'll get a menu where you can tune the RX and TX levels. The proper way to tune the RX audio is to have a service monitor inject a 1 kHz tone at 3 kHz deviation (for narrowband) or 5 kHz deviation (for wideband) and use the "rxdisplay" feature to get the audio level to be right around the 3 kHz or 5 kHz marks on the audio meter. With practice, you can tune by ear and get very, very close. A common thing to watch out for is the pre-emphasis setting. If you audio sounds too tinny or too bassy, the pre-emphasis settings on the node, repeater, or both are set wrong. If you're using the myGMRS image, don't run the "asl-menu" tool or you can mess up your node, since that is meant for hooking up to the Ham AllStarLink network.

For anyone who was interested in the new RT97 repeater that can work with the myGMRS Network, we have a limited number in stock right now (9 left as of my last count). The new model is the RT97S and it features a new metal case and a DB-9 port on the side for connecting an external repeater interface. These are FCC certified with the ID 2ASNSRT97. We're going to offer plug-and-play linking bundles with this repeater so the audio levels should be preset and ready to go very soon. https://shop.mygmrs.com/collections/featured-products/products/retevis-rt97s-portable-gmrs-repeater Also, as of right now we're only stocking this new model instead of the original RT97. It doesn't make sense to stock both versions since they are so expensive, so we're just carrying the new one now.

BuyTwoWayRadios is the exclusive dealer for the NA-771G model, so you would need to purchase from them. Anyone else selling them may be selling counterfeit products, so beware even on Amazon. However, the NA-701C model covers the GMRS band and also covers MURS, the 2m and 70cm Ham bands, so it is also compatible. We have these in stock and they are genuine Nagoya products.

There indeed was an issue with the FCC data that has been resolved this morning. So if you were unable to register, please try now. They changed how they publish the data to us and stopped updating the old place.

There was indeed an issue with the data coming from the FCC (they changed how they share the data, and stopped updating the old method that was still working). As of this morning, it's been resolved and updates should be coming in as usual.

The hubs don't have repeater interfaces because they are only hubs -- not directly connected to a radio or repeater. Think of them as a reflector or chat room. Multiple repeater nodes can join the hub and cross-communicate while connected.

PM me with your new email address and I'll update the account so you can reset the password.

Alive and well, just incredibly busy! I didn't get a text, but I did see your email a while back and replied to that. I think it was about switching out your SD card for your node. You can send me a PM on here and I'll get to it as soon as possible.

The only issue I had with this is that they declined to enforce a Busy Channel Lockout for automatic data/location bursts. You could set up your radio to transmit every 30 seconds, for example, and it'll beacon regardless of whether the channel is busy with voice traffic. Add in multiple radios in the same range, and I fear the GMRS channels will start to sound like APRS with data bursts all over the place. I had proposed the busy channel lockout feature but they specifically rejected it, claiming it was up to the licensee to ensure their radio is not causing interference. But once you enable an automatic location report, the licensee is relinquishing control to the radio for some period of time. It only seems like common sense for the radio to hold off the transmission until the channel is clear again. I'd also think the manufacturers would voluntarily add this feature as it would increase the reliability of their messages in the presence of co-channel interference. As far as FM on CB, I think it's great. It throws a lifeline to the CB radio manufacturers who can now introduce new FM-capable radios and revitalize the service a little bit. Seems GMRS has been taking over for quite a while, which is why some companies like Midland have all but given up on CB and moved onto making mobile GMRS products. For me, the interesting thing is that the reasons the FCC rejected digital voice on GMRS are the same reasons they initially denied Cobra's request to allow FM on CB. It fundamentally changes the nature of the service, it creates a compatibility issue between existing users and FM users, etc. They chose to mandate that AM is required on any FM-capable radios to ensure backwards compatibility. Using the same workaround, we could petition for digital voice on GMRS as long as digital radios are backwards compatible with analog on these channels so you can always talk to the analog people and hear the traffic on the channel. So for that, I'm very excited for the next round of interest in digital voice on GMRS. Seems a no-brainer now, we just need to file a well-organized petition for it with support from users and manufacturers.

It's a 10W transmitter but by the time the signal is passed through the notch duplexer inside, the output is 5W. Because of this, we market these as 5W repeaters and that's the power the FCC has certified them at. If the transmit and receive frequencies were further apart than 5 MHz, the duplexer would not have as much loss and you'd see something closer to 10W.

If you're in support of the integration, we need your help to post on the bug linked above on the Chirp website. If there's not enough interest on that website, the author won't add the support. Posting here is nice but that won't bump up the priority at all.

Will, your callsign was just issued today. The FCC won't publish this callsign in their Public Access File for another day or two. Please check back after 12pm ET tomorrow to see if your callsign has been added.