David,
>
> I also enjoyed the pulsar information on your website and your
> calculations. I particularly like the reality check you provided which
> really drives home the point that pulsar detection isn't easy and with a
> single dipole and narrow bandwidth, even the strongest will be
> undetectable
> in any reasonable length of time.
>
Thanks - even though I primarily write it up for as an exercise for own my
benefit it is pleasing to know others are getting some use out of the
effort.
>
> I'm on a quest to detect pulsars myself and realized that software defined
> radios could be a valuable new tool to detect them. I began testing in
> the
> 30 to 50 MHz range using a QS1R software defined radio with a 2.5 MHz
> bandwidth.
>
Sounds interesting. I am not currently 'into' SDRs (as Joe Walsh says -
'I'm an analog man"...) but I look forward to learning about them -
especially for RA.
>
>Compared to 2.4 kHz bandwidth, one should expect a
> (2500000/2400) = 1041x = 30 dB improvement in sensitivity which in itself
> would make up the gap from the Reyes effort.
>
Using narrow bandwidth of 2.4KHz is a major handicap for sure, but a
restriction due to dispersion as you say.
Unfortunately going from 2.4kHz to 2.5MHz only gains you ~15dB - not 30dB.
It's that ever present square root nuisance.
.
>
> I've
> played around with a couple of these things and while their internal clock
> is pretty unstable, I would imagine that if you used a series of FFT-based
> pulsar detection method instead of epoch folding (after dedispersion),
> that
> they might have good enough stability.
>
What short/long term stability did you find ? 10ppm would be fine for 4
hours observation for pulsars near 1Hz.
>
> The other way to make up the gap on the Reyes effort is on the antenna
> side
> by combining dipoles in phase. I phased 16 inverted V antennas together
> cut for 50 MHz which gives ~20 dBi gain versus 8.16 dB for a single
> antenna.
>
Unfortunately such an array would require a divorce first if put on our 3/4
acre block.... :-)
>
> The LOFAR group can detect pulsars with arrays of 96 inverted
> V's (see link below), so I think pulsar detections are achievable at the
> amateur level. The LOFAR group has a lot of information about sky noise
> limiting performance at low frequencies which I found interesting.
> Basically, one doesn't need to even have their dipole matched at low
> frequencies so broadband performance is easy to come by a low frequencies.
>
Yes - I have examined the LOFAR work and was encouraged, but the complexity
of the antenna is a little too high. With increasing gain comes narrower
beamwidth. Unless it can be electronically steered the extra gain is
effectively halved due to the shorter time in the beamwidth. This can be
minimised by narrower the beamwidth in declination and keeping the RA
beamwidth wide. Unfortunately there is nowhere that orientation would fit
in this 'backyard astronomer's' backyard (even after a divorce...).
>
> However, my experience has been frustrated by some serious RFI issues in
> my
> suburban environment, so getting out to a remote location will be key. At
> 50 MHz, RFI was absolutely terrible for me, at 150 MHz it was better but
> still too severe and at 408 MHz, conditions are much better, but still
> probably too poor to make any progress. My feeling is that if you can't
> see a noise floor rise from the galactic plane passing through your
> antenna
> beam, things will not work out.
>
Agreed - RFI is a killer. Doing a drift scan here at 45MHz shows lots of
intermittent RFI spikes as well as step jumps. The galactic hump is there
but it needs a number of days integrating to get a reasonable curve. One
way of cleaning up the curve would be instead of averaging successive days,
take the minimum reading across the days for each sample point. This would
eliminate many RFI spikes if they were randomly occuring. I think I read
somewhere a paper of someone coming up with this idea already so I am
certain it is not new.
Cheers
Steve VK2XV