Рубрика «Форумы»

Troubleshooting Help • Re: Received 433MHz signal not as expected

Did you use the same hardware, softwareversion and settings to record the files?
Did you use a soundcard and windows? Selecting not the correct device maybe the reason for the second one, selecting microphone instead of line in an explanation for the clipping in the old one.

The old one is not offset and symetrical around 0 reaching ±1 most of the time. The recent one looks linear and unclipped like the one, but shows ±0 and and the center at -50 (what unit?) which also makes no sence to me. The resolution in time also looks different, unless you recorded a different telegramme where duration differed to old one.

Statistics: Posted by snn47 — Wed Jan 22, 2020 1:13 am

FCC ID for a different product AND business??

I dont know where else to post this but since I'm using an rtl-sdr maybe someone can help. Can a FCC ID be used for a different product lineup in a different company? I ask this because I am having trouble tracking down info on a product that should have an ID. So here is the break down:

I have started a simple project using my rtl sdr to identify and record a door bell signal. Basically when the door bell rings I am going to use a reciever hooked up to a raspberry pi to take the signal and use it as a trigger for a camera to boot and do a few other things. The door bell I have is the sadotech model c.

I have deconstructed it and looked at the electronics inside to identify the fcc id but no luck. So I found the manual online and it has the frequency but no id. But the pdf manual has the fcc logo in it.

So I search the fcc database but nothing is registered under sadotech. I then proceed to email support for the fcc id and I recieve RWEFORRINX as the id. Not only is this a different company(Shenzhen forrinx electronics instead of sadotech) but a completely different doorbell on the wrong frequency. (Mine is 433.95 MHz and the one listed under the ID is 315.1 MHz) I tried replying to the support staff saying this is the wrong one but they continue to tell me that this is the one for model c at sadotech.

Is there something I am missing or is this product falsely advertising an fcc logo?

submitted by /u/t-velocity
[link] [comments]

Can anyone pick up a 400 MHz beacon from the CASSIOPE satellite?

Hi everyone,

I need to test a new radio system which is meant to receive at 400 MHz (or thereabouts). I researched the CASSIOPE satellite, which apparently has an instrument called CERTO which sends out a 400 MHz beacon, which sounds perfect for me. However, I'm not picking up that signal. I'm not sure if my system has a problem, or if the beacon is just non-operational. It would be great to have a sanity check here.

Please let me know if somewhere else online is better to ask this. Thanks!

submitted by /u/WaitForItTheMongols
[link] [comments]

Rooted Android + GNU Radio

So I went all about the works to get some programs working in Android, such as multimon, direwolf, rtl_433 and dump1090, without root. I managed this with Termux and a proot of Debian. However, it still depends on the Android APK driver and uses rtl_tcp, so not everything will work well with it, needs piping or other jiggery-pokery that can easily overload an older Android (rtl_tcp, sox and multimon really hammers a 2013 quad core with 1GB RAM).

So, can it be done better with root? Short answer, is yes.

Using a Debian chroot with correct mounts (dev, pts, shm etc) and we can now have programs directly access the USB. Android kernel, at least both devices I've tested with (Stock OEM Pie (Sony) and OmniROM 7.1.2) have drivers for the RTL-SDR. Installed GNU Radio, plugged in the OTG and fired up rtl_power. Low and behold, it directly accesses the dongle without the Android APK driver, and can start up rtl_tcp for SDRTouch and others to use. Less piping, less running, faster scans and more functionality.

Now have to find a way of merging rtl_power with GPS to make proper heatmaps, Kismet style.

submitted by /u/DutchOfBurdock
[link] [comments]

KerberosSDR • Re: KerberosSDR Developments in 2020

unixtime, lat, lng, GPS travel direction bearing, compass travel direction bearing, RDF bearing, confidence, power

Statistics: Posted by rtlsdrblog — Tue Jan 21, 2020 6:04 am

Troubleshooting Help • Re: Received 433MHz signal not as expected

Are you using the AM demodulator?

Statistics: Posted by rtlsdrblog — Tue Jan 21, 2020 6:03 am

Troubleshooting Help • Re: Hardware issues with NooElec NESDR Nano 3, or software?

The first Nooelec Nano dongle must have been faulty, since the error "No supported tuner found" usually means a failed R820T2 tuner chip.

The second unit, i'm not sure if it's a hardware issue. The Nano dongles do get very hot and they don't have enough metal to sink to, so try running a fan over it. Double check that your USB power supply is stable.

You can also try a slightly different branch of rtl_tcp that we have at https://github.com/rtlsdrblog/rtl-sdr-blog.

Statistics: Posted by rtlsdrblog — Tue Jan 21, 2020 6:01 am

User Projects • Re: Full disc weather satellite images from GK-2A

Thanks :)

Statistics: Posted by JEL — Mon Jan 20, 2020 10:37 pm

Digital speech decoder sounds like garbled mess? More info in comments.

Digital speech decoder sounds like garbled mess? More info in comments. submitted by /u/JaredButters
[link] [comments]

KerberosSDR • Re: Spacing Calc Help

Ok. so measure the yellow line, and that goes in the software (obviously in meters)

Cable lengths are all within 1-2" of each other. they were all brand new mounts with cables on them. I am just not sure how accurate my friend was when he stripped the end and put the PL259's on for me last night (his job is in the radio world, so if he is available I make him put the ends on - much quicker LOL)

Statistics: Posted by k2gc — Mon Jan 20, 2020 8:44 pm

Январь 2020
Пн Вт Ср Чт Пт Сб Вс
« Дек