User Tools

Site Tools


packet:transceivers_144pk

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
packet:transceivers_144pk [2025/07/29 06:17] g7tajpacket:transceivers_144pk [2025/07/29 06:29] (current) g7taj
Line 81: Line 81:
  
 A quick modification to the C program made a new EPROM image and I was ready to test. A quick modification to the C program made a new EPROM image and I was ready to test.
-On the bench, I plugged it into the dummy load and tested the channels according to what I had calculated from the EPROM image. They were all wrong :-?+On the bench, testing with the original EPROM, I plugged it into the dummy load and tested the channels according to what I had calculated from the EPROM image. They were all wrong :-?
  
 So I double checked the switch connections and EPROM data lines and found that there was a jumper, JP5, that pulls A2 and A3 to ground if bridged, which it was. So I adjusted the address lines in the program and re-ran it and the frequencies matched, wahoo! So I double checked the switch connections and EPROM data lines and found that there was a jumper, JP5, that pulls A2 and A3 to ground if bridged, which it was. So I adjusted the address lines in the program and re-ran it and the frequencies matched, wahoo!
-With the new found addresses, I wrote a new EPROM image. I only had a 27c256 to hand and so I wrote it to both 128k sections. Pulled it out of the programmer and plugged pushed it into the socket on the board. I tentatively powered it up, watching for magic smoke, which there wasn’t any, thankfully!+With the new found addresses, I wrote a new EPROM image. I only had a 27c256 to hand and so I wrote it to both 128k sections. Pulled it out of the programmer and pushed it into the socket on the board. I tentatively powered it up, watching for magic smoke, which there wasn’t any, thankfully!
  
 With a jumper wire for activating PTT, I had the H/H set to 144.950Mhz and went for it. And it only went and bloody worked! I quickly connected a set of headphones to the audio out and repeated the test from H/H to 144 PK on RX and it was working as well. JOB DONE! With a jumper wire for activating PTT, I had the H/H set to 144.950Mhz and went for it. And it only went and bloody worked! I quickly connected a set of headphones to the audio out and repeated the test from H/H to 144 PK on RX and it was working as well. JOB DONE!
 Well, not quite. I wanted to test it on packet, after all, that’s what it was designed for! So I unplugged my Motorola GM350 from the NinoTNC and plugged in the 144PK with the lead that came with it (5 pin DIN to standard 9pin TNC connector, as used by Kantronics and the standard that the Nino also uses).  Well, not quite. I wanted to test it on packet, after all, that’s what it was designed for! So I unplugged my Motorola GM350 from the NinoTNC and plugged in the 144PK with the lead that came with it (5 pin DIN to standard 9pin TNC connector, as used by Kantronics and the standard that the Nino also uses). 
  
-“C MB7NSC” I wrote at the node prompt. The TX light lit and the H/H screeched and “Connected to MB7NSC” appeared. It connected and on 5watts, over 63kms. Wow, impressive. I did a few more test over the air, getting nodes lists, going to GB7IOW and posting on this wall there etc+“C MB7NSC” I wrote at the node prompt. The TX light lit and the H/H screeched and “Connected to MB7NSC” appeared. It connected and on 5watts (the brick PSU it was connected to was limiting the output power), over 63kms. Wow, impressive. I did a few more test over the air, getting nodes lists, going to GB7IOW and posting on this wall there etc
  
 <code>(07-Jul 17:32) < G7TAJ > Testing using 144PK Wood&Douglas TcRX with modified frequencies</code> <code>(07-Jul 17:32) < G7TAJ > Testing using 144PK Wood&Douglas TcRX with modified frequencies</code>
packet/transceivers_144pk.1753769850.txt.gz · Last modified: by g7taj