You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
o<br />
Find another station who can reliably digipeat your signals.<br />
o<br />
Set your UNPROTO path to TEST via the callsign of the station who<br />
can digipeat your signals.<br />
o Set the MONITOR command to at least 1.<br />
o<br />
o<br />
o<br />
Go to CONVERSE mode and send a few packets by pressing the<br />
key. Note that you should see them on your own screen<br />
when they are digipeated by the other station.<br />
Start reducing TXDELAY by units of 5 each time making sure the<br />
other station is still digipeating ALL your UNPROTO packets.<br />
Eventually you will find a value where the other station can no<br />
longer copy your packets to digipeat them.<br />
When this happens, increase TXDELAY in units of one or two until<br />
the other station again digipeats ALL of your packets. This will<br />
be the optimum setting of TXDELAY.<br />
After TXDELAY is adjusted as indicated above you may want to adjust<br />
the audio delay (AUDELAY) as indicated in the Command Summary.<br />
The next sections of this chapter will discuss some of the more<br />
advanced packet features including Multiple Connects, Packet Timing<br />
and Protocol, and HF Packet Operation.<br />
4.4.8.2 AXDELAY and AXHANG<br />
Although it is not common, packet can be used through voice repeaters.<br />
When sending packets through an audio repeater you may require a<br />
longer key-up delay than is normally needed for direct communications.<br />
The AXDELAY command adds more key-up delay in your <strong>PK</strong>-<strong>232</strong> so that the<br />
repeater can lock-up. The AXHANG command sets the time your <strong>PK</strong>-<strong>232</strong><br />
assumes is needed for the repeater to drop.<br />
4.5 Packet Protocol Basics<br />
Here we will talk a little about the AX.25 packet protocol. You do<br />
not need to understand this to use packet, but it is helpful in<br />
understanding the packet protocol parameters.<br />
There are two modes of packet transmissions Connected mode and<br />
Unconnected mode. Most of the time when you use packet, you will be<br />
conversing with another packet station in Connected mode. Still the<br />
Unconnected or Unprotocol mode comes in handy for beacon transmissions<br />
and roundtable conversations.<br />
All packets are constructed basically the same. Packets contain<br />
source and destination callsigns (and any digipeaters if they are<br />
used), as well as information identifying the type of packet. This<br />
packet identification can be seen with the MONITOR command discussed<br />
earlier. All packets contain an error check code called the CRC.<br />
This ensures that when a packet is received, it will not contain a<br />
single error. The command PASSALL can disable the CRC error check,<br />
but this should only be done for experimental purposes only.<br />
4/91 4-19<br />
From The <strong>N3UJJ</strong>.COM Document Library