Sunday, 16 July 2017

Setting up raspberry pi 3 and QSSTV latest 9.2.4 GB8SSD special update / ARISS 20 anniversary

You need an external usb sound card

Next set up alsa mixer and increase the microphone gain!

In a command line window type:
Sudo alsamixer

Press the F6 key to select sound card

Choose the usb sound card using up and down arrow keys and press enter.

Use arrow right key to select Mic, use up arrow to increase to about 52.

Press escape key to return to command line

To install QSSTV type:

sudo apt-get install g++ libfftw3-dev qt5-default libpulse-dev
sudo apt-get install hamlib-dev libasound-dev  libv4l-dev
sudo apt-get install libopenjp2-7 libopenjp2-7-dev

Next download and install QSSTV

mkdir downloads
cd downloads
wget http://users.telenet.be/on4qz/qsstv/downloads/qsstv_9.2.4.tar.gz
tar -xvzf qsstv_9.2.4.tar.gz
cd qsstv_9.2.4
qmake
make
sudo make install

You can now run the program by typing qsstv at the prompt of a terminal session, or make a short cut on your desktop.
qsstv




Click on configuration



Click on sound and copy the above settings
Input and output set to your usb sound card.
Set the sound to alsa.
Plug an external microphone into the sound card. Turn up your radio and watch your pictures get decoded.
Space station is 145.800 fm
However 14.230 upper side band is more regular broadcast.
You can also hold the microphone near a sstv recording or YouTube video.

Have fun let me know how you get on!


We were really happy to hear from Lee DV8BVK:
"Hello Chertsey Radio Club,
My name is Lee, DV8BVK here in the Philippines. I am very thankful of your article/blog re install of QSSTV to Raspberry Pi 3 with the USB sound card. I followed all the instruction and put it to the test last july 22,2017 of the ARISS SSTV event. Thank you very much. "









RETEVIS RT-82 testing on Satellites in the UK


Wednesday, 12 July 2017

Birds satellites

BIRD – J   (Japan)
CallSign – JG6YJO
Downlink – [ CW - 437.372 MHz ] [AFSK(1200bps),GMSK(9600bps) - 437.375 MHz]
Digital-Singer -  [FM – 437.375 MHz]
Songs : 
1.       Japan National Anthem ,
2.       Kyushu Institute of Technology (KIT) Anthem,
3.       Famous Sakura Song

BIRD – G ( Ghana)
CallSign – JG6YJP
Downlink – [ CW - 437.372 MHz ] [AFSK(1200bps),GMSK(9600bps) - 437.375 MHz]
Digital-Singer -  [FM – 437.375 MHz]
Songs :
1.       Ghana National Anthem
2.       Ghana Independence Song – E.T Mensah
3.       Ghana Independence Song – “Yen Ara Ya Saase ne”


BIRD – M  ( Mongolia)
CallSign – JG6YJQ
Downlink – [ CW - 437.372 MHz ] , [AFSK(1200bps),GMSK(9600bps) - 437.375 MHz]
Digital-Singer -  [FM – 437.375 MHz]
Songs :
1.       Mongolia National Anthem



BIRD – N  (Nigeria)
CallSign – JG6YJR
Downlink – [ CW - 437.372 MHz ] , [AFSK(1200bps),GMSK(9600bps) - 437.375 MHz]
Digital-Singer -  [FM – 437.375 MHz]
Songs :
1.       Nigerian National Anthem


BIRD – B ( Bangladesh)
CallSign – JG6YJS
Downlink – [CW - 437.372 MHz], [AFSK (1200bps), GMSK (9600bps) - 437.375 MHz]
Digital-Singer `- [FM – 437.375 MHz]
Songs :
1.       Bangladeshi National Anthem

Dhono Dhanne

Monday, 10 July 2017

Lovely day to go portable and catch some satellites

Retevis RT-82 Free *big* code plug and a few video reviews







*fixed link* 11/06/2019
Download your free code plug here: https://www.dropbox.com/s/aio5eh6mfba9gbv/RT-82%20updated%2005092017.rdt?dl=0













Quick demo showing advanced DMR features, remote monitor, alarm, disable and re-enable







GB1SS special event call sign celebrating International Space station

We had great fun using the special event call sign GB1SS over the packet digi onboard the ISS






GB8SSD *33 years after the launch of Discovery** update





Dave G7HCE was able to receive our packet radio messages via the International Space Station






We had some fun running portable in the sunshine
Working on satellites and HF


We also received the first FunCub message and send / received ISS Packet messages





Another successful Fitter message download from the FunCube-1 satellite
Carrying our greetings message







We were also very lucky to make contact with Gilwell Park Scouts GB2GP via ISS


We were very happy to receive a few electronic QSL cards very quickly






Chertsey Radio Club win RSGB Region 10 Small club of the year award

We are very happy to receive Small club of the year award in region 10, as a new club trying a new and diverse approach to all things Amateur radio, this shows we must be getting things right. Thanks to everyone involved and we look forward to see how we fair in September.

Mick (G4EFO ) Region 10 Manager and M0JFP , at Kempton park rally
The regional winners of the Club of the Year 2016 competition, sponsored by Waters & Stanton, were announced at the RSGB General Meeting in Cardiff on 22 April 2017.
The National competition winners will be announced at the National Hamfest in September.
RegionSmall clubLarge club
1*Cockenzie & Port Seton ARC
2Caithness ARS*
3*Stockport RS
4*Wearside Electronics ARS
5Staffordshire Portable ARCTelford & DARS
6Meirion ARC*
7Barry ARS*
8Lough Erne ARCMid-Ulster ARC
9*The Radio Society of Harrow
10Chertsey RCHilderstone R&E Club
11South Bristol ARCPoldhu ARC
12Norfolk Coast ARSLoughton and Epping Forest ARS
13South Kesteven ARSWorksop ARS
*No entries received

Saturday, 8 July 2017

Several QSO via D-700 onboard the ISS

Live from the shack of M0JFP, A couple of QSO via  D-700 onboard the ISS


EA4SG de M0JFP (glad you confirmed the uplink for me!)



EA4SG, M0NPT, TM24TDF, F4DXV, F8CHM (copied MX0MXO and M0JFP)

Friday, 7 July 2017

Greetings messages from Tanusha-2 from inside the ISS

Live from the shack of M0JFP greeting messages fromTanusha-2 inside the ISS.
Notice call sign is S7S





 



 

Wednesday, 5 July 2017

Greeting messages recorded from Tanusha-1 from inside the ISS

Live from the shack of M0JFP here are several short videos from Tanusha-1 greetings messages in various languages, notice the cass sign S6S









Thursday, 22 June 2017

GB8SSD *Space Shuttle Discovery* Celebrating 33 years years since Launch

Space Shuttle Flight 12 (STS-41D) 

Launch attempts

AttemptPlannedResultTurnaroundReasonDecision pointWeather go (%)Notes
125 Jun 1984, 12:00:00 amscrubbed---Failure of Orbiter's back-up General Purpose Computer forced the scrub.[11] (T-9:00 minutes and holding)
226 Jun 1984, 12:00:00 amscrubbed1 day, 0 hours, 0 minutesPost-SSME start RSLS abort due to anomaly in number three main engine (T-0:06)Discovery returned to OPF for engine replacement; launch delayed over two months
329 Aug 1984, 12:00:00 amscrubbed64 days, 0 hours, 0 minutesDiscrepancy with master events controller relating to SRB fire commands
430 Aug 1984, 1:41:50 pmsuccessful1 day, 13 hours, 42 minutesdelayed 6 minutes, 50 seconds when private aircraft strayed into KSC airspace

June 26: Abort flight:



June launch attempt

During the 26 June launch attempt, there was a launch abort at T-6 seconds, followed by a pad fire about ten minutes later.[3][4]
Commentary: "We have a cut off."
"NTD we have a RSLS (Redundant Set Launch Sequencer) abort."
Commentary: "We have an abort by the onboard computers of the orbiter Discovery."
"Break break, break break, DLS shows engine one not shut down."
"OK, PLT?"
"CSME verify engine one."
"You want me to shut down engine one?"
"We do not show engine start on one."
"OTC I can verify shutdown on verify on engine one, we haven't start prepped engine one."
"All engines shut down I can verify that."
Commentary: "We can now verify all three engines have been shut down."
"We have red lights on engines two and three in the cockpit, not on one."
"All right, CSME verify engine one safe for APU shutdown."
"If I can verify that?"
"OTC GPC go for APU shutdown."[5]
Mission Specialist Steve Hawley was reported as saying following the abort: "Gee, I thought we'd be a lot higher at MECO (Main Engine Cut-Off)!".[6] About ten minutes later, the following was heard on live TV coverage:
"We have indication two of our fire detectors on the zero level; no response. They're side by side right next to the engine area. The engineer requested that we turn on the heat shield fire water which is what could be seen spraying up in the vicinity of the engine engine bells of Discovery's three main engines."
While evacuating the shuttle, the crew was doused with water from the pad deluge system, which was activated due to a hydrogen fire on the launch pad caused by the free hydrogen (fuel) that had collected around the engine nozzles following the shutdown and engine anomaly.[7] Because the fire was invisible to humans, had the astronauts used the normal emergency escape procedure across the service arm to the slidewire escape baskets, they would have run into the fire.[8]
Changes to procedures resulting from the abort included more practicing of "safeing" the orbiter following aborts at various points, the use of the fire suppression system in all pad aborts, and the testing of the slidewire escape system with a real person (Charles F. Bolden, Jr.). It emerged that launch controllers were reluctant to order the crew to evacuate during the STS-41-D abort, as the slidewire had not been ridden by a human.[6]
Examination of telemetry data indicated that the engine malfunction had been caused by a stuck valve that prevented proper flow of LOX into the combustion chamber.



About the mission

Tuesday, 20 June 2017

Trying out satellite video's

XW-2F TM17USA and G0ABI XW-2F TM17USA and G0ABI XW-2A

XW-2A Morse heard

AO-73 Funcube1 tenementary

Nayif-1 Funcube3 telemetry


AO-73 telemetry

AO-73 funcube1 telemetry

 FO-29

Ukube1 funcube2

Ukube1

XW-2D

FO-29 2M0SQL

XW-2a beacon

XW-2A heard G7LJA Peter

Thursday, 15 June 2017

Lilacsat 1 and 2 decoder now available on Raspberry Pi (3) image

We spent some time installing and testing out fitting all the GNU radio and demodulators onto a pi image.

Results We needed to trim and trim again but it now works




The image is available here



So we build GNU radio and gr-satellites and gr-lilacsat from scratch along with all dependencies



GNU radio loads and imports the lilacsat modules (detects funcube / airspy dongles)



The proxy loads and run OK



The front end module loads and displays the graphs just fine




Twitter: @chertseyrc