Other Parts Discussed in Thread: CC1310
Hi,
This is a continuation of a thread posted a few months ago (https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1112545/launchxl-cc1310-strategy-for-working-in-noisy-environment). Firstly, thank you for your previous responses. While they led us to perform further tests, we haven't managed to solve this issue.
From the last post, I have a question regarding blockers, which I didn't pick up on last time. The comment from engiNerd read:
"By the way, if you have a very strong blocker, it will desensitize the whole radio such that it will look like you have a flat noise floor. It would be interesting to check the noise floor with a narrowband setting (like 10kHz) - it is still flat?"
Firstly, I'm not entirely sure what is meant by "blockers" in the given context. I did a little search for blockers and found a quote on your tech summary for the cc1310. The summary reads:
"Long range operation, the sensitivity parameter is -110dBm at data rate of 50kbps and down to -124dBm when the data rate is 0.625kbps. Interference from other wireless communications can be overcome with 90dB of blocking."
Does this quote mean that a 90dB blocking needs to be added? If so how?
In any case, we are still seeing interference/noise across the whole 915 band:
- Can't achieve a sensitivity of lower than -80dBm (~range of <150m).
- The radio profile we use is WB-DSSS/FEC/500kbps/D=8/K=4/30ksps/RX BW 622KHz - taken straight from SmartRF Studio without changes.
- Using launchpads instead of our h/w shows the same noise floor on every channel at 915 as our hardware and has the same sensitivity problems.
- Sites we have tested are across the whole of Colorado and at least one site in Texas. All test sites are remote Farms in arid conditions.
- When we test the same kit here in the UK we get 800m and a sensitivity down to -107dBm (exact kit was shipped to the US to rule out differences in h/w).
- Channel hopping doesn't help.
- CCA before sending doesn't help.
- We do see improvements if we narrow the bandwidth to sub ~80KHz, but that's not legal to use in the US.
Our current suspicions are:
- We do not believe there is other radio interference across the whole permissible bandwidth and across the whole of Colorado and into Texas - that's really unlikely.
- The environment may be causing issues where we are testing, maybe the arid conditions or the rock/stone ground. This could maybe cause excessive reflections or high static condition (large amount of dust particles carried in wind) - we're not sure how to test that though.
- The front end of the RX side is configured too sensitively (e.g. loop bandwidth lock needs to be higher, AGC reference level is out, front-end filter is not filtering sufficient).
Is there anything further you might be able to suggest to help us investigate and solve this issue?
- What's a 90dB blocker (see above)?
- Any tweaks to the overrides or set up parameters what would help in a noise environment?
- Anything? Anything at all?
Sincerely,
- Oliver