Friday, 13 June 2014


I made another trip to Eggardon Hill today and replaced the broken Tiny2 with a KPC3 TNC. All seem to be working as it should again.
The TNC is at an angle because the power lead was not long enough. When I made the leads up for the radio to TNC link many years ago, I put an adaptor in the lead so that I could use it with both makes of TNC. I am rather glad I did!

Thursday, 12 June 2014

It appears that the Tiny2 TNC is broken at G0ROZ-3. The lights are flashing to show that it is transmitting and receiving, but nothing is getting to the COM port.
I do not have a spare TNC at Eggardon, so I have had to come back to base to dig another TNC out of the supply cupboard and set it up.
I expect it will be tomorrow (Friday) before I go back and replace the TNC
When I looked at the APRS map this morning, I was amazed to see G0ROZ-3 on the map! Unless Gremlins do exist or somebody has been to site and fixed it, I can think of no reason why it should suddenly start working after four days.
I am making a trip up to site later on today, so will see if I can catch the Gremlins in the act!

Wednesday, 11 June 2014


G0ROZ-3 appears to have stopped working at around 1500 Hours on Saturday. I have been trying to get to site to find out what is wrong, but there have been other calls on my time. I will go to site tomorrow (Thursday) and sort it out.

Monday, 2 June 2014

I was a bit concerned that M1ABD-3 was not performing as it should, so yesterday I went to Headquarters and checked the SWR on the aerial. There did not appear to be any problem and the SWR was 1.5:1. When I turned the computer back on it started to boot, but just as Windows was starting, it flashed up a BSOD and re-booted itself. It kept doing this over and over again and the only way to stop it was to turn the power off. The BSOD flashed up too quick to read, but I thought it must be a disk problem.
So, I connected up the spare computer and brought the broken computer home.
I booted up into the Recovery Console and ran CHKDSK. After whirring away to itself for some time it reported no errors on the disk. So, fingers crossed, I started the computer normally and it burst into life again.
Can only assume that the disk must have had a problem and CHKDSK sorted it out.
Back to Headquarters tonight to replace the computer.