the w6vvn-7 packet node W6VVN/K W6VVN-1/B W6VVN-4/C W6VVN-7/N HF ports -------- 1. FX.25 centered on 1000Hz 2. VARA-500 centered on 1500Hz 3. IL2P centered on 2000Hz HF schedule ----------- during the day, 14.1023 MHz USB for FX.25, that makes: MARK 14.1032 MHz SPACE 14.1034 MHz which is compatible with Net 105 (14.105 MHz LSB) during the night, 7.1013 MHz USB for FX.25, that makes: MARK 7.1022 MHz SPACE 7.1024 MHz which is compatible with Net 40 (7.104 MHz LSB). I call this a schedule, really it's not. I don't have a script that automates it, and sometime I use my radio for other things and hence disable my HF modems, or even just try packet on other bands. But this is where I mostly am, since these frequencies at these times work best for me at the moment. VHF port -------- 10. AX.25 centered on 1700Hz this port is -always- tuned to 145.050 MHz FM. neighbors --------- I always have excellent propagation to KC2IHX on 20m during the day. From KC2IHX-7, you can reach N6CTA-7 and VE3QBZ-7 on HF. From VE3QBZ-7, you can reach anyone around Lake Ontario on VHF. VE3VTY-7 is definitely worth a visit! Also on 20m, I usually have acceptable propagation to W7BMH. Often just a tiny bit too marginal for FX.25, but IL2P and VARA work well. W7BMH-7 is a good node for jumping to other places. There is also a VHF path from me to N6CTA, by taking W6VVN-7 -> SOUTH -> CARA-7 -> MIRDOR -> N6CTA-7. If RASNOW is ever operational again, W6VVN-7 -> RASNOW -> N6CTA-7 is a shorter path. On 40m by night, KB9PVH can be reached, but often limited to using VARA. noise ----- Sometimes, particularly in the evenings before I switch to 40m, my receiver gets deafened by QRM from neighbors. I am working on solving this. station info ------------ HF: Running a 58' EFRW in an inverted-L configuration on an 8 meter tall mast. 80ish watts from an IC-7300. VHF: FTM-150R running 50 watts to an N9TAX j-pole hanging off the roof of my garage. Should go up on the mast soon(tm). other toys ---------- besides the usual K2K and BBS, there are some fun things available on my node: CHAT: instead of BPQCHAT, CHAT starts PacketIRC, an IRC client. It is configured to automatically connect to the FARPN IRC. Come say hi! WALL: a graffiti wall. leave a short message! GEM300: a gemini client PALPS: a publishing system using ed, the standard text editor. Currently limited to use by specific people. PacketIRC and WALL are both written by Daria, VE3DTJ. GEM300 and PALPS by myself, W6VVN.