Range and noise tests at Ankeny National Wildlife Refuge

[Rich Schramm has been having issues with lots of noise pulses at 166Mhz at Ankeney Nat’l Wildlife refuge and he’s done a number of tests, incl. with the LNA+SAW filter I made over which we’ve been exchanging emails. I thought it would be nice to move our discussion to the forum so (selfishly) we might get others to chime in with ideas, and so others may glean something useful from Rich’s tests.]


From Rich Schramm [with some edits by TvE]

Attached are some results of my reccent 166 Mhz tag testing at Ankeny using an LNA-Filter on loan from Thorsten von Eicken and some clamp-on ferrite cores as suggested by Glenn Pollock (very active Motus tower installer and contributor with RF experience residing in Omaha NE)

I would be very happy to get your interpretations and feedback on my results as well as any suggestions on where I might go from here.

(Apologies about the length… I wanted to capture as much as I could before I forget..)

Goal:

See if we can knock down very high numbers of non-motus pulses being received and see if we can improve the detection SNR of real tag pulses.

  • Testing periods were made both with and without Thorsten von Eicken’s Low Noise Amplifier+Filter
  • Also tested with and without ferrite cores on coax as suggested by Glenn Pollock, using Fair-Rite Products PN:0446164281 Access to this page has been denied.

Setup:

  • 166Mhz test tag with burst interval of 38.2 second.
  • Test tag ~230 meters away, ~3 meters off ground on plastic pole, taped to a piece of fruit (small orange).
  • 9-element Mapleleaf yagi, on tripod 3 meters off ground (and up-slope from tag)
  • Sensorgnome (SG) V2 running SG 2024-157 release.
  • Test duration of ~ 3.5 hours
  • FuncubePro+ V2 with (bias-t turned enabled)

Observations:

SG is still receiving a high number of false (non-motus) beeps/hits/pulses. Over the course of 4 hours the SG logged over 32000 hits. Occasionally as many as 600-700 hits were received between each 38.2 second burst.

At the bottom of the attached figure I show a roughly computed value of “Pulses Per Second” which should ideally be 0.1 but range at times from 5 to 15 per second or more.

During the day there were six major burst periods lasting around 15 minutes each, separated by relatively quiet periods of between 20 to 30 minutes (with one quiet period of 60 minutes).

Motus.org processing detected the tag 279 times over the ~3.5 hours. There were several instances where I would expect to have missed detections (such as when the tag tripod got blown over or when I was connecting/disconnection the LNA-Filter). Overall there were only about 7 missed detections that could not be explained. Those missing detections appeared to be mostly during the periods when the highest numbers non-motus hits were being received.

The figure also shows signal, noise and snr of all the tag detections from motus.org processing. It is annotated to show periods with and without the LNA-filter, and also with the ferrite cores recommended by Glenn Pollock.

I computed the avg signal, noise and snr for the following categories:

TAG PULSES SIG NOISE SNR
No LNA-Filter: -42.8dB -57.5dB 13.6
With LNA-Filter: -32.7dB -43.6dB 10.4
Ferrite Cores: -46.4dB -67.5dB 21.1

(I did not have time to test with the LNA-Filter combined with ferrite cores)

I have also computed the average signal, noise and snr of only the non-Motus tag pulses in each of the three configurations:

NON-TAG PULSES SIG NOISE SNR
No LNA-Filter: -55.1dB -63.2dB 7.3
With LNA-Filter: -36.0dB -44.2dB 7.4
Ferrite Cores: -62.7dB -70.6dB 7.3

Preliminary conclusions

  1. Motus.org processing seems very good at identifying tag bursts even during periods of high non-tag pulse interference as high as 14 per second. It seemed to start to have difficulties beginning at ~15 pulses per second or higher.

  2. Performing short duration tests for Motus receiver site selection or antenna orientations may give a false impression in locations such a the Ankeny Hill site due to the periodic nature of non-Motus interference.

  3. Presence moderate to high non-Motus pulse rates would seem to only be a concern in cellular or satellite connected system due to cost of transmitting the extra data. (This conclusion may break down as the tag distance from the receiver is increased).

  4. Im not sure how to interpret the value of the LNA-filter or the ferrite cores - partly due to the tag being only ~230 meters away. I would like to repeat testing moving the tag 500 and 1000 meters away to see what changes. Is the LNA-filter making the kind of improvement expected?

  5. The ferrite cores did appear to cause a slight reduction in the non-motus pulse rate although other testing would be needed to be sure.

  6. The ferrite cores made the most dramatic change in SNR but also significantly lowered both the overall received signal strength and noise measurement. Are these results surprising? Is further testing worth pursuing?

  7. Next time I could also add test of combined LNA-filter and ferrite cores if that seems useful.


From Thorsten von Eicken

Hi Rich, thanks for doing the tests and the report! Here’s what I see:

  • The LNA+filter is expected to make a difference when used with RTL-SDRs because the LNA has a significantly better noise figure than the RTL-SDR input and the RTL-SDRs lack narrow filtering. I have not investigated the FCD input but expect less of an improvement on the SNR front, if any, which is kind’a what you observe.

  • The filter is about 8Mhz wide, which is rather broad WRT to the signal bandwidth (~1kHz?). It will help where “distant” signals cause issues due to intermodulation and such, a commonly quoted example is FM stations. If that’s not the problem you have, the filter will make no difference. To me it looks like your situation is in the second category. Also, the FCD has switchable input filters, they’re not 8Mhz narrow, but they do cut out FM stations, for example. The RTL-SDR doesn’t have these.

  • I don’t understand the use of ferrites on the coax, my ignorance. The specific ones you use have peak attenuation in the 100Mhz-300Mhz range which to me implies that they attenuate the signals you want to receive. The results you list show that happening. That seems counter-productive to me. What is the intent?

  • Your test shows SNRs roughly around 12dB for 230m. Given that the detection limit is at 6dB and doubling the distance reduces signal by 6dB (theory) you should barely get detections somewhere around 450-500m.

  • In my tests I have a noise figure very similar to yours (high 50’s to low 60’s using an FCD). What I observe is that if I compare FCD with RTL-SDR + LNA/SAW then the latter shows a couple dB better SNR and continues to detect the tag at distances where the FCD no longer does. That’s the main success criterion for me.

  • 450m detection range, pfffft, disappointing, isn’t it? (I’m getting results very compatible with yours, to get more range you have to adandon your location and find a spot that results in less than -70dB noise…)


From Rich Schramm

Thanks for the review Thorsten.

  1. This URLGlenn sent about the ferrite cores What is a balun and why do I need one? - Innovantennas - Home of the Low Noise LFA Yagi - Ham Radio antennas The paragraph that may be relevant is:

Filtering stray signals picked up on the outer sleeve of the coax - Often in urban environments, many modern-day electronic devices generation noise with is picked up by the receiver. However, it is often the case that these signals are along the route of the coax form the radio to the antenna and are picked up along outer sleeve of the coax, travels up towards the antenna and enters the reciever chain this way. The ferrite core balun not only prevent common mode currents from travelling from the antenna back down the coax, it also prevents these unwanted noises picked out on the outer sleeve of the coax from entering the reciever chan which results in a lower noise floor on your receiver.

  1. NEW FACTS HAVE COME TO LIGHT… **** I am now completely confused ****

Today I went and downloaded the raw SensorGnome csv files for the adjacent AHNC motus receiver (see photo). I uncompressed the -all.csv.gz files for the overlapping test period and loaded them into excel. They DO NOT show all of the non-motus pulses that I see in the RPi sensorgnome data that I sent yesterday.. there are a very few spurious beep - but the files for the 9-element and 3-element antennas that point roughly the same direction as my test antenna - both have total of ~1500 pulses. (ideal would be ~1300) - nothing like 30000 I got on my test SG.

Attached are quick plots of the CTT station. (Remember… these are straight from the ‘production’ CTT station… no LNA-filter, or ferrites involved). Its just a different station and two different antennas listening to the same tag.

So I have absolutely no idea what is going on with my testing setup or procedures. Still a lot more to learn!

I’m about to do some traveling so my time in September to play will be limited.

As always - I appreciate all of your collective input.


From Thorsten von Eicken

Hi Rich, thanks for the updates! More thoughts:

Thanks for the link about the ferrite cores: much to learn! According to your revised numbers, the ferrites dropped the signal by ~4dB and the noise by ~10dB. The SNR went up by ~7.5dB. I have to try that here!

I wonder what happens if the SDR is directly attached to the antenna w/out extra coax. These antennas have a piece of coax already, so can’t quite eliminate that but it would certainly reduce the supposed noise pick-up by the long coax. (Yours looks very thin, btw.) I have to try that also!

I don’t know what to make of your noise-pulse-count results. If you get the high number of noise pulses regardless of where you point the antenna then I would assume that they’re not picked up by the antenna itself but rather have to do with the rest of the equipment?

Is it possible for you to set-up next to the station and swap components for a couple of minutes? Like plug the station yagi into your test receiver? You don’ tneed more than a couple of minutes to see what you see…


From Rich Schramm

Great ideas Thorsten, so if im reading you correctly, given the correction to my ferrite numbers they still warrant additional testing?

yes since I’ve moved the ankeny ctt receiver out to the tower and shortend the coaxes to from 100ft to ~35 ft, i could easily test swapping between the SG test station and the ctt sensorstation and also my test antenna to find out why i see so many hits..

I can send you a few ferrites for the 166 and the 434mhz )they are different ) if you want to play.

1 Like

Your test with the ferrites indicates an increase in SNR, since that’s the key metric it seems quite promising! The SNR shown in the latest SGv2 software is exactly the number that the pulse finder uses to threshold pulses: >=6dB = pulse, <6dB = no pulse (there are also pulse duration and freq width criteria).

Thanks for the ferrites offer. I have a shopping cart ready to which I’ll add ferrites after I measure the diameter of my coax, the ones you use would be too small, I believe. It’s easy to get ones that have about the same attenuation in the band but a larger inner diameter.

I use the ferrite core because the are cheap and the idea is the keep the noise from entering the system via the coax. Coax acting as an antenna. There is a low noise antenna design called loop folded antenna. I have used this antenna in one installation. The antennas are reasonably priced but shipping cost doubles the coast.
LFA Yagi Benefits - InnovAntennas - G0KSC - Innovantennas - Home of the Low Noise LFA Yagi - Ham Radio antennas
I obtain a used quarter wave band passed cavity filter for test on one of my site that had high noise. It has a narrow band pass about 1 meg and insertions loss of .5 db. This did not help my noise problem becasue the noise was in band noise. When the arching high voltage power line insulator was repaired the noise when away. In band noise is my biggest problem and trying to find the source and have it eliminated. Just my experience and opinion.

1 Like

I got some ferrites yesterday (same Fair-Rite 0446164281 as Rich used) and tried them out today. So far, no luck…

I mounted them similar to how Rich had them:

Here are the charts. I brought the test tag out of the house around 3:50pm and then went to the station to remove the cable ties that held the coax to the boom so I could add the ferrites. Somehow at the same time as I was removing the cable ties the noise on both antennas jumped up by some 7dB. I first thought it had to do with removing the cable ties, but the other antenna is some 3m higher on the tower and I didn’t touch anything related to that, plus its noise changed a few minutes earlier. Adding the ferrites brought no discernible change. About 10 minutes after I took the screen shot of the charts the noise dropped again by those 7dB (the SNR chart, which was captured a few minutes later, shows the corresponding jump up in SNR). All that time I was sitting at the computer far away from the station. Very confusing…

(SNR graph, captured ~10 minutes later:)
image

After all this I tried something else: attach the FCD directly to the antenna using a long USB cable (blue cable in the photo):

The result was indistinguishable from before. So the high noise in my case doesn’t come from the coax.

Next step for me is to unmount the antenna and set it up on a tripod a bit away from the tower to see whether the noise is coupled through the tower somehow.

Hi Thorsten & Glenn,

I plan to test clamp-on ferrites for our setup next week. To get 12V DC for our SensorStation, we’re currently using a switched-mode power supply. In our setup, this power supply is quite close to the coax cables. It’s possible that the coax shielding picks up some noise from the power supply and starts to radiate or otherwise affect the signal in the coax. We’ve theorised that the ferrite clamps should reduce noise related to the coax shielding. I’ll post the results once I’ve done the tests.

1 Like

Mini update: I did a number of experiments:

  • grabbed an rpi zero 2w powered by battery and hooked it up to the antenna using 2m USB cable and FCD plugged directly into antenna, all this to exclude noise from mains-powered rpi, result: no change
  • unmounted the antenna, still connected to portable SG (rpi zero 2w), held in hand 2-3m away from tower, result: no change
  • walked around little hill to a lower lying area that has no visibility of town, result: noise dropped >10dB! (a bit below -70dB)

I’ve identified a spot where I can set the antenna up on a tripod where it looks like it has about -70dB noise yet can be pointed to a road about 2-3km away. I’ll test that in the coming days…

Another round of tests, incl driving to verify range (ugh). But I believe a picture is forming in my mind…

I figured out that I can set-up the antenna next to my little pond and it’s shielded from town by the hill and that big boulder (it’s actually 3m tall, the perspective makes it look small).

The FCD is directly connected to the antenna and I have an rPi Zero 2W with a battery pack laying on the ground.
The yagi points through a gap at the mountain ridge in the distance:

Hiding the tag around the corner gets me noise readings around -75dB, yay! Then comes the driving… I didn’t take scenic photos but I was holding the tag with saline bottle on a stick, the antenna curving more or less horizontal:

I had another test tag in the house, which unfortunately got picked up by the antenna (oops) but the “real” TestTag#1.1 can be identified by the 22/19/24 intervals and the 3.1kHz offset:

So… 4.0km distance, signal -59dB, noise -75dB → detection
Compared to earlier shorter range tests the signal level roughly matches the 6dB per doubling the distance. The difference is the noise level.
In these last 4km tests I get a 15dB SNR which means I should be able to get a bit over twice the distance, so perhaps 8km-10km. Note that this is perfectly on-axis (although the boulder and other obstructions likely do have some negative impact).

What’s the bottom line? Noise floor. Need to work on that…

Note about measuring the noise floor: the software is not actually measuring the noise floor as you would if you attached a spectrum analyzer to the antenna. It’s measuring the noise surrounding a detected pulse. Some of this measured noise is generated by the transmitter (the tag) because the pulse is not pure/perfect/sharp. The result is that there will always be noise about 25dB-30dB below the tag’s signal, this is not what you want to measure. You need to distance/hide/shield your test tag enough so SNR is <20dB, ideally in the 10dB-15dB range. Then the noise shown is external noise as opposed to transmitter imperfections.

On the topic of clamp-on ferrites:

I used my usual testing setup, with a 230V AC → 12V DC adapter, for these tests. Instead of having the adapter inside the steel box, I deliberately kept it outside:

With the tag at 400m, I got signal strengths of -57.5 to -58.5dB, with noise levels of -77 to -77.5dB. To test the effect of the ferrites, I then attached 9 ferrites, in sets of 3, at places I figured noise could be a problem.



My signal strength did not change, but the noise dropped to -79.5dB. I even got to -80dB at one point, which is the lowest noise I’ve seen so far in my setup.

Today, we made some small changes to the setup. We replaced the 5-element Laird with a 6-element Sirio, and also attached the ferrites at the antenna itself. Although we got a boost in signal strength (-55 at 400m), the noise was actually quite a bit worse, varying between -73dB and -76dB. Consequently, the SNR was actually lower as well. Fiddling about with the ferrites did not yield any improvement.

What I will say is that the first test implies that ferrite beads can lower noise in environment where a known possible noise source (such as a switched-mode power adapter) is present.

1 Like

Hi Thorsten. I’ve done some testing to get an idea of whether the noise in general fluctuates at our location (possibly it’d be more quiet at night, for instance). I had a tag at 400m and took hourly averages of the signal strength and noise level, as shown below.

Signal_fluctuations

Looking back, I should have put the tag a little further away, precisely because of the effect you describe here: there appears to be some correlation between signal strength and noise level. I plan to put the tag at ~600m over the weekend and then check the results again. Just wanted to share these results as I don’t know how many people do background noise tests.

1 Like

Weird! Thanks for posting! The fluctuating signal vs. stable noise is curious. Did a car perhaps park in front of the tag or the receiver on 9/4 in the morning causing the 10dB drop in signal strength? Is there some weather pattern that explains the overall signal level pattern? Everything in RF just seems to raise more questions :laughing:

Congrats on getting the noise down below -80dB!

What I didn’t realise when I made the first plot, is that the SensorStation doesn’t actually save tag detections. Even though it displays live tag detections, it only saves live pulses. Consequently, the first plot shows an average of live pulses rather than live detections - that’s the data I physically download from the SensorStation using a USB connection.

As a “quick ‘n’ dirty” way to tackle this, I’ve taken the average signal/noise values of only the pulses that happen at least 2.5 seconds after the previous pulse. The idea is to filter out noise, without having to do any actual processing. This method gives me the following plot:

Where the first half is with the tag at 400m, and the second half with the tag at 600m. The tag-at-600m measurement is actually obscenely noisy, which is why there’s a part where the signal cuts out - it never had (at least) 2.5 seconds between any of its pulses. I’ve never seen this behaviour in action. Whenever I do “live” testing, I always see the live pulses arrive in expected intervals. I’ve never seen a constant stream of noise pulses, yet this is apparently what happened last Saturday.

The plot would probably look different with actual processing done. I’ll have to look into ways to get the R package running from Python so I can process data at will.

Edit: the increase in noise in the second part of the measurements is likely due to a tiny mismatch in burst interval causing the two tag signals to start overlapping - see also Lotek nanotag burst interval precision

1 Like