Here are the settings that we used installing the KG6VYD-2 digipeater in Oakhurst, south of Yosemite National Park in central California. Please note that the settings are for Paccomm version 5.0.0 or greater EPROMs. See: http://www.paccomm.com/cmdrefcrd.html http://www.paccomm.com/rel5.html http://web.usna.navy.mil/~bruninga/aprs/fix14439.html http://www.ew.usna.edu/~bruninga/aprs/PacComm-settings.txt For a slightly different digi configuration, see: http://www.theworks.com/~wa6ylb/PACCOMM.TXT but note that it does not conform to the "new N-n paradigm". If you're installing this Paccomm TNC200 firmware in a MFJ1270C, you need to perform the following modification. Paccomm's tnc200 firmware will work "AS IS" in an MFJ1270B,1274B tnc without any modifications. If you happen to install it in a late model 1270C, you must do a couple of things to return a 1270C model to basically a 1270B configuration. It doesnt work in a 1278 at all. The 1270C version tnc, as shipped by MFJ, has two 32K static ram chips plus the firmware (32K also) installed on the main board. The Paccomm tnc200 firmware was written for only a single 32K static ram chip. The modification below is covered in the 1270C manual as for use with NET ROM node software, and is paraphrased here. It is very simple, and doesnt hurt the tnc in any way, and the tnc can someday be returned to MFJ firmware by reversing the steps. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= After removing the lid, look for U40 , a .3 wide 20 pin IC next to the large IC's. Remove U40 and tape it upside down on the state EPROM U6 so that if some day you want to return the tnc to MFJ firmware you will still have U40 around. U40 is used to bank switch between two 32K ram chips. Remove IC in U24. Hang on to it. You will want re install it if returning to MFJ firmware. Put the Paccomm eprom (27C256) firmware in U23. Add a shorting jumper on JU16 near pin 5 of U23. This selects only one ram chip, instead of the bank switched ram that they use with MFJ firmware. JU16 is shown on the schematic. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Features: 4 aliases, Call-swapping (Mycall in place of Myalias callsign upon digipeating) and digipeat once. Also two paths for beaconing the position of the digi are availible. Remote control of the digi and personal message system are possible. (and recommended) Here are the settings we used. Some of the settings pertain to use of the TNC at a users station. Only the settings that are unique to Digipeater use are mentioned here. It is possible to remotely set up the TNC with minimum settings, and connect to it and "fine tune" the settings remotely. Make sure the remote sysop stuff is turned on before doing so. (PASSWD needs to be installed too!) MYCall K6DBG-2 <- digipeater callsign HId OFF <- make sure this is off! MYAlias WIDE1-1 MY1alias WIDE2-1 MY2alias WIDE2-2 <- these simulate xxn-N, but MY3alias WIDE3-3 <- only give one hop! DIGipeat 7 <- ON, SWAP, NOT-OWN, ONCE MON 3 <- monitor all received frames TXDelay 7 <- 70msec - very radio dependent! --- fairly limited choices in beacons... --- Beacon locally every 12 minutes --- small offset (bslot) based on SSID to try to avoid RF collisions BRA 3 <- set the beacon multiplier (range) to 10 seconds Beacon EVERY 72 <- this beacons the first path every 10 mins. BSLOT 2 <- send on the "2" second, may not work Unproto APNP50 EBEacon ON <- monitor beacon text on terminal port --- Beacon in a wide area every 31 minutes --- small offset (bslot) to try to avoid collisions LRA 3 <- set the location range to 10 secs LOCation EVERY 186 <- this beacons the second path every 30 mins. LSLOT 12 <- send on the "12" second, may not work LPATH APNP50 VIA WIDE2-2 ELOC 2 <- monitor location text on terminal port --- 10W, 20' HAAT, omni, 3db gain, both texts the same BText !3724. NP11937. W#PHG3130/W11,W21,W22,W33 Cedar Valley, Oakhurst, CA LTEXT !3724. NP11937. W#PHG3130/W11,W21,W22,W33 Cedar Valley, Oakhurst, CA | | Puts P in digi star +-> "new paradigm" digi (for PacComm) -- we don't enable PMS, this is just a digipeater CONOk ON <- allow user to connect to digi to get Ctext CMSg ON <- now give them the Ctext msg CText Not a NODE. For more info about this DIGI, email kg6vyd@arrl.net <- this is the message they get when connected CMSGDisc ON <- then the digi disconnects them REtry 15 <- retry on a connect UIMODe OFF CONStamp OFF LOGonmsg OFF REMote ON <- allows remote control use REMSysop ON <- must be on to remote access it. RMTCall K6DBG-15 <- remote sysop callsign PASSWD place up to 31 characters here to respond to the character vs position question. Make yourself a look up table I.e. "Mary had a little TNC" would be: Mary had a little TNC 000000000111111111122 123456789012345678901 And when the digi asks for 20,01,08,11,17, you type in NMd e as your response. Upper/lower case matters along with spaces! Make sure you set the CLOCK in the tnc. This can be done locally or remotely with the DA yymmddhhmmss command. When you do, the MHE command output will have timestamps on them: CMD> <-helpful to know what the digi can MHE hear. WA6YLB-1 USER 06/23/97 13:59 N6QOG USER 06/23/97 13:59 <- calls w/o * are heard direct. KF6HJO USER 06/23/97 13:55 KC6YRU * USER 06/23/97 13:54 <- a * shows it was heard via another WA6YLB USER 06/23/97 13:54 digi. W6BXN * USER 06/23/97 13:54 KE6FOA * USER 06/23/97 13:54 W6UR -1 NODE 06/23/97 13:52 <- X1J-4 node AC6KT * USER 06/23/97 13:49 WA6YLB-3 * USER 06/23/97 13:47 KD6DX * USER 00/00/00 00:00 <- when clock isn't set, time is 0's. KF6HJO-12* USER 00/00/00 00:00 WA6AFT-3 * USER 00/00/00 00:00 W6IKR * USER 00/00/00 00:00 BFLD USER 00/00/00 00:00 WA6FQM * USER 00/00/00 00:00 WH6DT * USER 00/00/00 00:00 KF6HDO * USER 00/00/00 00:00 KE6AFE * USER 00/00/00 00:00 N6TBQ * USER 00/00/00 00:00 WR6ABD * USER 00/00/00 00:00