Wow. Now I was also affected by it: My power amplifiers from the FT-817 blew up. After several hundred SOTA and /p activations it happened at home while I was listening to SSB satellites. Especially with the old non-ND versions (like mine) the power amplifier starts to oscillate by itself and destroys itself by self-oscillation then. The older MITSUBISHI RF POWER MOS FET 2SK2975 were not that good. I had already read a lot about this on the internet. The FT-817 suddenly became very hot and had a permanent current consumption of 2 amps. It was clear then that the FETs were short-circuited.

{jcomments on}Recently, I saw a newcomer's post on Twitter regarding his first WSJT-X session. I noticed right away that he only decoded a handful of stations, but those with supposedly extremely good reports. This is what happens when you set your receive bandwidth extremely low. This means that you only receive signals that lie within this range. If we remember again our education, we find out that a normal report refers to a bandwidth of 2.5kHz. In this articel I explain the fundamentals about that.

Some time ago I already built some "loose" interfaces for my FT-817. I used these later on my FT-891. The CAT, respectively the FTDI USB to serial converter I needed at the FT-8x7, I don't need at the FT-891 anymore, because it already has CAT via USB integrated. The FT-891 simply uses a Silicon Labs CP2105-F01 USB/Serial UART converter internally. As with many other TRXs, this is not galvanically isolated, but the engineers thought of something. Apparently it works well anyway. I have had no problems at least in the last 2 years. In this article I show you my solution for this problem.

Today I drove to my nearest SOTA summit (DM/SR-012, Schaumberg) to test my recently bought Raspberry Pi4. Up to now I had a Pi3, but it was too slow sometimes. Today I wanted to do a dedicated SOTA activation in FT8. I have done FT8 from a summit for SOTA before, but always only besides SSB. With -1°C and freezing rain, it was exciting not only for the operator but also for the technical team. Spoiler: When I came back into the warm with the Pi4 it cracked and the blade from the fan broke out of the case at all 3 points. Well, a new one does not cost 2 Euro in China. Of course including shipping. On 40m I was heard well, also in England. But after 15 minutes there was only one station in the log: S57ILF. In SSB my log would probably have been well filled already. On 30m it was better then. At least 5 stations came into the log. Because it was very cold I skipped 20m and called a few times on 17m. K1KZ came into the log.

Wow. Now I was also affected by it: My power amplifiers from the FT-817 blew up. After several hundred SOTA and /p activations it happened at home while I was listening to SSB satellites. Especially with the old non-ND versions (like mine) the power amplifier starts to oscillate by itself and destroys itself by self-oscillation then. The older MITSUBISHI RF POWER MOS FET 2SK2975 were not that good. I had already read a lot about this on the internet. The FT-817 suddenly became very hot and had a permanent current consumption of 2 amps. It was clear then that the FETs were short-circuited.

{jcomments on}Recently, I saw a newcomer's post on Twitter regarding his first WSJT-X session. I noticed right away that he only decoded a handful of stations, but those with supposedly extremely good reports. This is what happens when you set your receive bandwidth extremely low. This means that you only receive signals that lie within this range. If we remember again our education, we find out that a normal report refers to a bandwidth of 2.5kHz. In this articel I explain the fundamentals about that.

Some time ago I already built some "loose" interfaces for my FT-817. I used these later on my FT-891. The CAT, respectively the FTDI USB to serial converter I needed at the FT-8x7, I don't need at the FT-891 anymore, because it already has CAT via USB integrated. The FT-891 simply uses a Silicon Labs CP2105-F01 USB/Serial UART converter internally. As with many other TRXs, this is not galvanically isolated, but the engineers thought of something. Apparently it works well anyway. I have had no problems at least in the last 2 years. In this article I show you my solution for this problem.

Today I drove to my nearest SOTA summit (DM/SR-012, Schaumberg) to test my recently bought Raspberry Pi4. Up to now I had a Pi3, but it was too slow sometimes. Today I wanted to do a dedicated SOTA activation in FT8. I have done FT8 from a summit for SOTA before, but always only besides SSB. With -1°C and freezing rain, it was exciting not only for the operator but also for the technical team. Spoiler: When I came back into the warm with the Pi4 it cracked and the blade from the fan broke out of the case at all 3 points. Well, a new one does not cost 2 Euro in China. Of course including shipping. On 40m I was heard well, also in England. But after 15 minutes there was only one station in the log: S57ILF. In SSB my log would probably have been well filled already. On 30m it was better then. At least 5 stations came into the log. Because it was very cold I skipped 20m and called a few times on 17m. K1KZ came into the log.