W9DR/b 50.072.1

JA7QVI reception recording of NW0W on 50.053 MHz

HackRF One - EXTIO DLL - HDSDR (WORKS!)

I've been searching for an EXTIO DLL for the HackRF One that will work with HDSDR for years now.

https://github.com/jocover/ExtIO_HackRF

Finally came across this today!  AND BONUS!  IT WORKS!

I contacted the author and asked him to add some smaller sample rates of 4 and 2 MSPS.  He did that and posted the new release in just about 1-2 hours.  This is useful for weak-signal stuff I most do.  It allows the ability to get HDSDR's "Resolution Bandwidth" down to 7.6 hz when MSPS is @ 2.  Which in my experience shows weak CW signals up very well!

A little about how I use HDSDR. 

I use the 9 MHz IF OUTPUT from my Yaesu FTDX-5000 as the input source to whatever SDR I'm using to feed HDSDR.   I've been using a TCXO based Nooelec RTL and an OCXO upconverter I built myself.  Even with all that 'stability' the TCXO RTL drifts all the time.  Which is a total pain in the butt for CW over the coarse of a day.

After swapping out the EXTIO for RTL in my HDSDR install I fired it up with HackRF.   Although the HackRF has advertised a low range of 30 MHz or my experience has been that it works just fine down as far as 3.5 MHz in it's stock config.  Mine is about 1.5 years old now with recent firmware installed.

Anyway I setup HDSDR initially to use 9,000,000 hz.  HDSDR has a nifty option to display the VFO frequency of the Yaesu FTDX-5000 as it's frequency regardless of what input you're really using (9 MHz in my case).

There is also a way to automatically remove the DC Spike that would show up in the middle of the display if left as noted above.  To accomplish this I set the OPTIONS > RF Front-end Frequency "IF frequency" to 9098000 and the Global Offset to 98067.  This pushes the DC Spike well below my normal viewing area, and then the 'Auto RX DC Removal' notches it down to nothing.

In this way the DC spike goes away but everything stays lined up PERFECTLY for CW.

I also connected a GPSDO I've had around for a long time that I use with my Apache Labs "Hermes" SDR.  Tee GPSDO emits a super stable 10 MHz signal that Hermes and now the HackRF lock onto.  

In a 24 hour test just completed there was 0 hz drift noted on the HackRF.  Which is what I had expected (and hoped for).  This has been my experience with the GPSDO and Hermes so I didn't expect any difference.

------------

So all of this Eliminates use of an RTL (which are drifty little bastards, but VERY VERY useful I've used them for over 5 years now with very good success), and because the RTL's are limited to 24 MHz I have always used an Upconverter which has the potential to add noise from it's OSC, and add drift to the resulting signal input to the RTL.

I'm using the HackRF because it's what I have currently and because this EXTIO is now FINALLY available.

I plan to also buy and test the AirSpy and SDRPlay at some point since I've read they hear better than the HackRF.  BUT at this point I think I can actually relax after years of muxing around with RTL's that drift like crazy and spending way to much to make a $8 device do something it doesn't really wanna do LOL.

Time will tell, but for now I'm setting my upconverters and RTL's to the side to collect some MUCH NEEDED DUST.

Ameren UE Missouri - RFI Complaint Filed (and any followup)

2015-01-20 @ 3:30pm (via email)

Today I filed a complaint with Ameren UE (Missouri) the local power company provider related to the my previous posts on this blog.  This is the second complaint in 5 years with them.  The last time was in May of 2011 and they were VERY QUICK to respond.  I'm hoping this will have a similar result.  Considering the possible safety hazard involved at a nearby Middle School.

I filed the complaint via Email (the same way I did in 2011) at around 3:30pm local time on 2015-01-20 and I am now awaiting a response.

2015-01-22 @ 8:18pm (via email) 

sent a second request (asking for a ticket number)

2015-02-02 @ 9:00-9:15am (via phone call)

CALLED: 9am-9:15am feb 2 2015:

800.552.7583 - 5,5

spoke to: nikki (wouldn't provide last name or operator number)

ticket: 150333237

Didn't really seem to understand what Amatuer Radio and the FCC was.  She was friendly and curtious.  Just didn't really seem to clearly understand the issue.

She said it could be up to 3-5 days before a tech would contact me.

2015-02-02 @ 11:00-11:15am (IN PERSON)

SERVICE TECH: Skip

Location: My Home

Skip and I talked about the issue.  I believe he's a lineman/service tech, arrived in a small ladder utility truck anyway.

I provided him with pole numbers, and some of the issues related to those poles.

He said it would probably be a few days before I heard back from the Service Tech Group
but that he would relay the pole numbers and info I gave him to them.  A very friendly, nice fellow.  He DID understand the issue, and let me know they wanted to fix it as much as I wanted it fixed.

This is more like the Ameren UE I remember from 2011!  Finally.  I guess no one is checking their "Contact US" email service anymore LOL.  Because a phone call sure got a fast reaction time!

2015-02-02 @ 11:38am (AUTOMATED VOICE MESSAGE)

Spoke to: (no one, this was an automated notification message)

Return number: 1-800-552-7583

The gist of the message indicated that a service tech came out to investigate my complaint and that a problem was found that would require further investigation.

I guess this was just confirmation of what I'd spoken to the tech (Skip) who'd come here just a little while ago about.

GOOD!

2015-02-07 @ 12:29pm (email update requested via Contact US)

Reference YOUR Ticket Number: 150333237

It was my understanding when I last spoke to a Ameren Service Tech named "Skip" that I should have heard back from your service department by now.

Please provide an update to this ticket at your earliest convenience."

SEE ALSO

2015-02-18 @ 2:25pm (phone call from Jerry who still works with Rob Duncan)

Jerry called to discuss the issue related to the same ticket number noted above.

Depending on Weather (which has been a mess lately) he will tentatively try to come down to check out the poles with me this Friday 2015-02-20 sometime.  If not then, he'll try to reschedule.

I mentioned I would email him (at rob's address) the results of my testing so far.

2015-02-18 @ 3:15pm (email sent to rob duncan relaying information about this issue which we spoke of on the phone a bit ago)

2015-02-21 @ 6:43pm 

Yesterday came and went 2015-02-20, no contact from Ameren Tech Services.  I assume due to the bad weather we were supposed to get late in the afternoon that their plans had changed.  So will wait to hear from them again hopefully sooner than later.

2015-03-30 @ 11pm

Emailed RD as a followup, explaining that I didn't wish to escalate the matter and asking for a followup contact.

2015-03-31 @ 9am

Jerry and a new trainee arrived in a van and we went to the worse sources I'd found where they poles were shown to be actively making noise still today.  They drew maps, took pole numbers, discussed what to do, and showed the trainee how to hunt for RFI.

We were also able to locate another area near the City Water supply which is about 230 degrees from my tower which was the strongest source we found all day.  Jerry found that one while we were looking at a source on Mill St that I'd ID'd previously.  We worked our way down the line right to the source.  Jerry wiggled the guy on the pole and it went nuts.

This is an area that would be on the back of my antenna when I'm pointed to EU which is one of the worse RFI / PLN areas I've got.  So kudos to Jerry for finding that one so FAST.

Jerry and the Trainee were very nice, enjoyable to talk with, and listened to what I had to say.  It was obvious that they wanted to resolve the issue as much as I wanted to resolve it.

So THANKS Ameren for coming through, albeit 3 months after I initially contacted them.  Apparently Jerry's been out of work a while with a shoulder problem and he's the only guy that does this type of work for Ameren, MO. (I guess that's why they had a trainee with him)

All in all it was a good 2.5 hours they spent with me going form source to source.  Afterwards they confirmed the noise signature by connecting they're equipment to my antenna. (seems like that should've been done first, but that's ok).  

Looks like they plan to fix everything I pointed out, and then some.  The one Jerry found while walking with me, was bigger than anything I'd found to-date.  So that was impressive.

Jerry also said on average it takes them about 3 weeks to get back out to start doing the work.  (in my experience it took 2x that, but I'd still be happy with that!)

2015-04-21 @ 9:40am

Noticed line crews were working on one of the locations we'd spec'd out.  So I drove past all of the locations.  It appears that 3 of 4 have had some work done on them.  I'll check the 4th one tomorrow.  It's in a location that's more difficult to get to and it was raining today when I drove around to inspect them.

2015-04-23 @ 12:30pm

Drove to all 4 locations last reported for work, found 3 of 4 completed.  Noise at station appears slightly improved.  4th location checked had not been worked on yet, this was the worst of the 4 that needed work.  So will continue to monitor if/when it is completed.  This 4th location has a locked chain blocking the entrance to it for vehicles, which means somehow Ameren will need to contact the city to gain entrance there in order to do the work, or walk in ladders to the pole and do the work like that.  I'll continue to check this location for work completed.  Once it's confirmed done, I'll review noise issue changes at the station.

I plan to head out to check this location today at some point.

Once this final spot has been resolved I'll drive-test again.  I suspect there are more locations besides the 4 we reviewed that require more work.  Virtually everything in town seems to emit RF noise on the power lines.  So I'm certain there is more work to be done.  My goal is to reduce the noise by 60% *at least* if possible.  Anything above that would be great, but I need to at least reduce the noise 60% of what it has been for years now.

(before)

(After - different angle same pole - notice replaced insulators)
-------

(before)

(after all new insulators top,sides, and new top/over wire)

EME - S57RR Copied, not completed tho

(click to see larger)

Building 10 MHz OCXO

As part of my experimenting with building a double conversion up-converter I'm working on building a 10 MHz OCXO for the first LO.  I'm using a 3.3vdc LDO voltage regulator to power the OCXO.  This regulator is really simple to setup.  And aside from the IC itself it just takes two small ceramic capacitors to be stable.  When built the little DC-DC converter takes up less space than a US quarter.  The downside of this device is HEAT.  If input to the IC is > 10vdc it gets pretty hot trying to bring it output down to 3.3v.  So I'm limiting the input to 10vdc.

I'll probably eventually require this using an LM117 as those can take up to 40vdc input and run output as low as 1.25vdc (+-).  The way I've used them in the past I added a potentiometer and some resistors and caps to create variable voltage output.  But these devices can also just run a static voltage output by using a fixed resistor and some caps.  

The trouble with just about any of these is disapation of heat.  The process of dropping 13.8vdc to 3.3vdc if not done properly can generate enough heat to burn your finger when touching the device or heatsink.  So there's a balance that needs to be made.

ANYWAY...Here's a photo of the 10 MHz OCXO with the LDO Regulator onboard. 

Here's a shot of the LM117 variable supply I'm using to drop 13.8vdc to 10vdc which then drops to 3.3vdc that feeds the OCXO.

This is not the final configuration, this is just a test setup to verify the Variable Frequency adjustment of the OCXO using a voltage divider resistor network.  See the adjustable 1k Ohm Pot for that.

Common Use Capacitance Chart

I find I'm looking these conversions up all the time these days.  Just posting this in one place so I don't have to hunt it down all the time.