Saturday, 18 February 2012

Friday, 17 February 2012

Flex 1500 settings



PowerSDR setup for audio and CAT. COM6 is a virtual serial port.

TX audio is set to -5dB as this is the level which gives just under 100% output power on SSB when fed through a virtual audio cable from WSPR. I got an email from someone telling me my WSPR signal was spreading all over the (200Hz wide) band, so trying to be careful to avoid any distortion. I think the distortion might have been to do with getting 20ms breaks in the audio though, sometimes the receive audio was getting clicks and whatever was holding up the USB interface would have been doing it on transmit too. Re-installing the Flex1500 driver sorted that out. To WSPR, these clicks made all the received signals look like they were spreading over a wider bandwidth.
The RX audio might not need to be so low but anything higher usually puts data software into the red on waterfall type displays.

Had a problem with the radio recently where the transmit power was next to nothing (it just about moved the needle on my power meter). I thought the PA might have gone (the software was showing 100% output power and a normal looking spectrum) but when I installed an older version of PowerSDR (version 2.0.19 instead of 2.2), it went back to normal.

Thursday, 2 February 2012

Flex 1500



Flex 1500 SDR and LDG auto tuner. The tuner and radio are supplied from the 4 way splitter cable. Another useful little cable I have a few of is a 2.5mm into 1.7mm power lead, with which you can run an FT-817 (or Alinco DJ-G7) from the more common power supply connectors.


The photos were taken with my Samsung Galaxy Note

PC Clock


Changed the BIOS lithium cell in my main PC tonight as the clock had started to drift by about 10 seconds per hour. With this amount of drift, WSPR worked for about 15 minutes and then received nothing until About Time adjusted the time on the hour.
The voltage of the cell was about 3.1 when I took it out.



The CPU (Phenom II X4 955) isn't officially supported by Asus with this motherboard (this is an AM2+ board so has some support for the newer AM3 CPUs but uses DDR2 RAM). Even with the newest BIOS version I still get this message.