I need to be next to my node

Recently I now need to be right next to my node for it to pick up my signal.... If I get about 20ft away it does not hear my signal? On the parrot node, my voice just cuts out...

My pi is connected by an ethernet cable, I have moved it as far as my current network cable will take me.

Edit...
Logs:
8:16 AM hwmon hwmon1: Undervoltage detected! kernel 73Occurrences

8:14 AM Failed to set mode: Failed (0x03) bluetoothd

8:14 AM hwmon hwmon1: Undervoltage detected! kernel

8:14 AM /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring. systemd-udevd

8:14 AM /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_std" has no matching label, ignoring. systemd-udevd

Edit: Question??? Could it be the antenna? I should put the antenna on an analyzer, however it transmits just fine, I can hear my node from a mile away...

The log indicates undervoltage, so that's one problem. Get a better power supply.

As for the rest, I know nothing about your setup. What radio is being used? What antenna? What band? Possibly an issue with a connector?

I am using a Baofeng uv 5r Mini, on 446.100 both Radio and Node are using the stock "Rubber Ducky" antenna.

Yes, I have tried a different radio.

As an aside, I don't know how using 446.100 became a thing; it's a repeater input (at least in much of the US). You should go 438-440 or 431-433. When I was involved with the old Bay Area Black Mt 441.100 (now defunct), we would have hunted you down and put you out of our misery.

441/446 being used for repeaters is very locale specific (mainly California)? The normal voluntary bandplan is 446.0 - 446.9 is simplex UHF within 445-447's "shared, aux, simplex, repeaters" allocation. Only very crowded areas use 441/446 for repeaters. All of my simplex systems are within 446.0 somewhere. :slight_smile:

What type of Pi and/or device are you using and what else is connected to it? These errors are often seen in Pi 3 and Pi 4 with undersized power supplies. Will definitely cause squirrely behavior.

If that doesn't fix it (i.e. you made those errors go away) and you're still having problems what power level are you transmitting on? You could be desensing the front end of a low-quality HT.

I don't mind changing frequencies, but when I researched several sites including Mr AI Bot, said that 446.100 was simplex.

And I never have been on 441.100..... Sound like there is a story behind that comment... Tell me more?:grin:

I don't want to mark this solved yet, I need to do some more testing, but I changed power supplies, and the outlet, and it is working so far.

I am using a Pi 3B, running only the node.... How many amps should my supply be? I really need to order a new power supply, the USB power supplies I have are maybe 5v 1.5 amps. I will order a 5v 3amp one unless there is a 4 amp.

The max in that spec family is 5V @ 3A. Alternatively, get an externally powered USB hub to sit between the Pi and its outboard devices.

Great idea, thank you!

I was talking about WA6FUL 441.100, which used to be on Black Mountain, above Cupertino, CA. Very high-level box that was there when I got licensed in 1990. Lost the site in around 2013.
Unless a locality is upside-down from normal (ie. SoCal, some Colorado, etc.), repeater outputs are 440.0000-444.9875 and inputs are 445.0000-449.9875. The only simplex freqs I've ever seen above 440 are 441.0000 and 446.0000, but I spent most of my life in NorCal. I guess I need to travel more...

430's are also RF quieter.

Aside concluded...

ADD'L: (my 2 cents) Standard Pi-3 PS are 2.5A

Yeah, that's very California-/West Coast-specific in my experience. In Ohio, PA, etc. repeater outputs are 442-444 and inputs are 447-449. 440-441 and 445 are all for site links and other auxiliary usage. 446 is shared between site links and simplex. I think the "local option" to use 440-441 and 445-446 for repeaters was only ever exercised in very dense areas long ago. The massively different topology around here doesn't call for huge linked systems to provide coverage.

Here in Iowa (moved 11 years ago), I can do 20 MHz offsets if I want and no-one cares (or hears...).

The NYC metro is definitely one of those places. There are even some repeaters with odd splits in the 438/439 mHz range, as well as 440 plus and 445 minus. It's a real mess.

446.100 mHz, the default frequency for Kits4Hams SHARI radios, is a repeater input in Brooklyn, which used to be very high coverage, and is now much less so. That repeater had a huge jamming problem, and it did get a couple of SHARIs on it's input frequency before it's coverage was severely degraded.

I ended up sticking my personal duplex node, when I had one that operated on UHF for both RX and TX, on 445.075 minus, because there is nothing coordinated there, I didn't hear anything after monitoring for weeks with a high gain antenna in a good location, and the noise floor was actually a bit quieter than frequencies around 432/433 and 438 mHz.

So far so good I have been testing it today, and it is working again, I just plugged it into a new power strip.

Thanks for the replies.

I did not know this when I picked that frequency... I just jumped .100 above the calling frequency.