We seek to understand and document all radio transmissions, legal and otherwise, as part of the radio listening hobby. We do not encourage any radio operations contrary to regulations. Always consult with the appropriate authorities if you have questions concerning what is permissable in your locale.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ultravista

Pages: 1 [2] 3 4 5
16
What can I use to identify digital radio signals to determine the signal type (FSK, MFSK, PSK, PSK31, STANAG 4***), then the Mode (LSB/USB), and Bandwidth to determine whether or not it is encrypted?

Knowing the details of the signal is the first step in decoding.

The question is for signals found outside of the amateur radio bands.

17
Spy Numbers / Re: UNID CW at 4870 KHZ
« on: January 06, 2019, 0218 UTC »
It looks like I resolved the problem .. removing VAC 4.51 and installing a different VAC application.
CW & NOAA images are working now.

18
Spy Numbers / Re: UNID CW at 4870 KHZ
« on: December 31, 2018, 1914 UTC »
Token, perhaps you can help ... if not, I understand.

I cannot get FLDIGI to decode anything decent. CW is a completed mess and WEFAX images are nearly impossible to read.

FLDIGI is configured for the VAC Line 1 and can 'see' the data streams from HDSDR when Windows 10 pipes the audio through VAC Line 1. This configuration appears to be working; however, the output of the FLDIGI decoder is gibberish.

In Windows 10, Line 1 (VAC) is the primary playback device - not recording device. FLDIGI is configured with Line 1 (VAC) for capture. When I change the SDR output to Line 1 (VAC), the waterfall display in FLDIGI does display the signal; however, it does not decode anything until I enable the Audio Repeater (KS - Kernal Streaming) for Line 1 (VAC).The VAC version is 4.15 (https://vac.muzychenko.net)

For example, CW is unreadable despite being tuned properly in HDSDR and FLDIGI. Squelch on/off doesn't matter - everything is trash.

The FLDIGI decoder becomes legible only if I enable the Audio Repeater (KS) that comes with FLDIGI. When running, the FLDIGI ouput appears to be correct. Validated with WEFAX and CW. In other words, FLDIGI only works properly with the Audio Repeater (KS) running; otherwise the output is trash. I though the Audio Repeater was to pipe the audio elsewhere post FLDIGI, not into FLDIGI.

My FLDIGI settings have been defaulted more than once and the VAC control panel is setup following instructions on the net.

Despite hours of fiddling around with nearly every setting, I still cannot effectively decode anything. I must have done something wrong.

Any ideas?

19
Spy Numbers / Re: UNID CW at 4870 KHZ
« on: December 31, 2018, 1843 UTC »
Interesting, thanks for the quick reply.

I am amazed with what this active mini-whip is receiving. Mine is the PA0RDT from Roelof Bakker himself. My neighborhood is noisy, lots of RFI everywhere and a suspected marijuana grower using crappy RFI producing ballasts. I theorize it is a grow light as it is on approximately 12 hours a day. When it starts, my SDR display goes wonky until it stabilizes in approximately 5 minutes.

Despite the noise, I am able to receive quite a lot with just the active antenna. In the AM, the NDBs like XSG Shanghai Coastal Radio come in strong.

Thanks again for the feedback, I'll check your logs.

20
Spy Numbers / Re: UVB-76 "The Buzzer" mixed with odd digital signal
« on: December 31, 2018, 1821 UTC »
Token, are you able to receive the buzzer @ your location? We're pretty close (CA - NV) but I am unable to find the buzzer using an active mini-whip @ approximately 20ft.

I am on your SDR now and hear CODAR @ 4625. I too pickup several CODAR 'stations' here in Las Vegas, in the AM and PM. I suspect the stronger CODAR signal competes for the weaker buzzer.

21
Spy Numbers / Re: UNID CW at 4870 KHZ
« on: December 31, 2018, 1815 UTC »
Token - how did you determine the RIS9 callsign? I assume you too are able to receive this station?

Do you run the audio through a program or just know Morse well enough?

22
Spy Numbers / UNID CW at 4870 KHZ
« on: December 31, 2018, 1654 UTC »
UNID CW at 4870 KHZ received most mornings in Las Vegas, NV.

Didn't find much on the net other than references to M89 Chinese Military. When I am able to receive this unknown CW station, Asia SW stations are also very strong.

I am unable to decode the CW - can't figure out how to get HDSDR, FLDIGI, and the Virtual Audio Cable to play nice to decode anything. Something with my configuration is wrong as I can't decode anything despite being able to see it in the tools. If anyone is willing to help, I will sure appreciate it!

Anyone know what/who is broadcasting CW @ 4870 KHZ?

23
Equipment / Re: Some more LoG (Loop on Ground) results
« on: December 24, 2018, 0141 UTC »
Are either loops amplified or run straight to the radio?

24
I plan on installing an under the eaves horizontal loop antenna for receive only. The wire is spooled so I don't know the exact length but I estimate it to be 250 - 300 feet.

The wire 'mount' is a long screw to bring the wire off the wood. I wrapped the wire once around the screw to keep it taught until the next screw.

A few questions:
1) For a receive only loop, what is the best way to attach the coax feedline?
2) Which is better - using it as a long wire (free terminating end) or a loop (coax attached to each end)?
3) Would a dipole (terminated or not) perform better than the random length wire or not?
4) Does wrapping the wire around the screw 1 time affect performance?

Looking for feedback on making this antenna efficient.

25
In Windows 10, Line 1 (VAC) is the primary playback device - not recording device. FLDIGI is configured with Line 1 (VAC) for capture. When I change the SDR output to Line 1 (VAC), the waterfall display in FLDIGI  does display the signal; however, it does not decode anything until I enable the Audio Repeater for Line 1 (VAC).

Should VAC be setup for playback or recording?

26
I hope someone w/experience can help with this problem.

To the best of my knowledge, the Audio Repeater isn't necessary for FLDIGI to work.

27
I am running Windows 10 with HDSDR & FLDIGI configured with VAC 4.51.

FLDIGI is configured for the VAC Line 1 and can 'see' the data streams from HDSDR when Windows 10 pipes the audio through VAC Line 1. This configuration appears to be working; however, the output of the FLDIGI decoder is gibberish.

For example, CW is unreadable despite being tuned properly in HDSDR and FLDIGI. Squelch on/off doesn't matter - everything is trash.

The FLDIGI decoder becomes legible only if I enable the Audio Repeater (KS) that comes with FLDIGI. When running, the FLDIGI ouput appears to be correct. Validated with WEFAX and CW.

In other words, FLDIGI only works properly with the Audio Repeater (KS) running; otherwise the output is trash.

I though the Audio Repeater was to pipe the audio elsewhere post FLDIGI, not into FLDIGI.

Does everyone else run the Audio Repeater too?

It doesn't make sense (to me) that I can see the signal in FLDIGI with and without the Audio Repeater running.

28
Equipment / FLDIGI w/HDSDR Controlled by a Yaesu-FT-950
« on: July 12, 2018, 2040 UTC »
I control HDSDR with a Yeasu-FT-950 via an RSP2 and OminiRIG. All is good here ...

I would like to use FLDIGI to decode digital modes. For reasons unknown, I cannot get anything into FLDIGI.

Nothing appears in the FLDIGI waterfall and the output screen is just a string of gibberish characters. The gibberish characters appear with and without the radio on.

Since the rig is controlled by OmniRIG, I cannot get rig control to work within FLDIGI. Not that big of a deal.

I would like FLDIGI to 'listen' in the background and decode what is hears. With that said, how the heck can I get this to work?

Using the machines microphone, and configured in FLDIGI, doesn't seem to do anything. I must me missing something and it is driving me nuts.

29
HF Beacons / Re: hiker 7998 khz
« on: July 07, 2018, 0344 UTC »
Hearing solid tones @ 7998 in Las Vegas, NV tonight.

30
Other / 6666.66 KHZ UNID CW
« on: July 01, 2018, 1548 UTC »
Received July 1 @ 8:40 AM PT from Southern Nevada.

Pages: 1 [2] 3 4 5