==========================
I really do believe that as time goes on it will be necessary to use 
software and SETI like intercept technology to intercept and decode Voyager 
31 and 32 (craft launch numbers) data.

The hardware Viterbi decoders can only sustain signal interception for so 
long, as signal interception is more or less at the limits of current 
hardware receiver design.

http://cbc.am/dsn.htm

This is my idea, but as of yet there is no way to implement it as I have no 
connections to ESA or NASA or even my own nation (Canada) space programme.

==========================

http://voyager.jpl.nasa.gov/mission/weekly-reports/index.htm


Voyager Mission Operations Status Report # 2005-03-18,  Week Ending  March 
18, 2005

Command Transmission & Verification Operations

Voyager 1 command operations consisted of the uplink of a command loss timer 
reset on 03/15 [DOY 074/1050z].
The spacecraft received the command.

Voyager 2 command operations consisted of the uplink of seven bracketed 
command loss timer resets sent on five-minute centers using 1.0 Hz steps on 
03/16 [DOY 075/0342z].
The spacecraft received two of the seven commands sent


Sequence Generation Operations

Continue sequence development of CCSL A055.

Data Return Operations

Voyager 1 Data Processing and Operations:

There were 65.0 hours of DSN scheduled support for Voyager 1 of which 13.5 
hours were large aperture coverage.
There were no real-time or schedule support changes or significant outages 
during the period

Science instrument performance was nominal for all activities during this 
period.
One frame of GS-4 data was recorded this week.
A second frame of GS-4 data was recorded on day 71 from the AHELIO cyclic.
The EDR backlog is 2 days.

Voyager 2 Data Processing and Operations:

There were 41.1 hours of DSN scheduled support for Voyager 2 of which 22.5 
hours were large aperture coverage.
There were no real-time or schedule support changes or significant outages 
during the period

Science instrument performance was nominal for all activities during this 
period.
One frame of GS-4 data was recorded this week.
The EDR backlog is 2 days.

Flight System Performance

Voyager 1 performance was nominal during this report period.
Activities included a MAGROL on 3/15 (DOY 074) followed by BC gyros OFF.

Voyager 2 performance was nominal during this report period.
Activities included an ASCAL on 3/14 (DOY 073) and a MAGROL on 3/17 (DOY 
076) followed by BC gyros OFF.