Keyboard Shortcuts
Likes
- W0NE-Winlink-Net
- Messages
Search
|
Re: W0NE WInlink Net Roster - Week 16
I use a Kenwood TM D710A with a built-in TNC. With just the radio alone, I can send a very short email to any email address through the APRS functions.? For next week¡¯s check-in, I will send two. One via APRS with no form, and a second via Winlink with whatever form you choose.? |
|
Re: W0NE WInlink Net Roster - Week 16
I agree. That sounds like a terrific idea to practice. On Sat, Jan 20, 2024 at 9:04?PM W9GM, Ken <ken@...> wrote:
|
|
Re: W0NE WInlink Net Roster - Week 16
toggle quoted message
Show quoted text
-------- Original message -------- From: Shawn Hicks <eistim68@...> Date: 1/20/24 8:57 PM (GMT-06:00) Subject: Re: [W0NE-Winlink-Net] W0NE WInlink Net Roster - Week 16 Ben: I'm game for any challenging exercise.? Your doing an excellent job and I appreciate the effort you're?putting into this weekly exercise. Best Regards, Shawn A. Hicks ??? On Sat, Jan 20, 2024, 20:13 Ben Kuhn via <ku0hn=[email protected]> wrote:
|
|
Re: W0NE WInlink Net Roster - Week 16
Ben: I'm game for any challenging exercise.? Your doing an excellent job and I appreciate the effort you're?putting into this weekly exercise. Best Regards, Shawn A. Hicks ??? On Sat, Jan 20, 2024, 20:13 Ben Kuhn via <ku0hn=[email protected]> wrote:
|
|
W0NE WInlink Net Roster - Week 16
We had 6 net check-ins this week, 5 with pictures attached, and one via HF 300 Baud packet.? More on that later.? Here is the roster: I mentioned Paul's check-in at the beginning.? He sent the check-in this week from my gateway using 300 baud packet on 40 meters.? As we probably all know, 300 baud packet is not a supported mode for Winlink.? What you might not know is you can send Winlink messages without using a client at all--a packet terminal is all you need--and this is how Paul sent this message.? If this seems like fun trivia consider the following situation: |
|
W0NE WInlink Net Remider - Week 15
Hello Everyone,
For this week's check-in, let's try sending an image as an attachment.? Send a regular one-line check-in in the following format: Name, Callsign, City, County, State, Country, Mode (and Gateway if applicable) ?
Then, attach a picture to the message.? The picture should be small, probably under 16k.? To resize a picture in Windows, you can do the following:From Within Winlink Express, Click on: ATTACH Click ADD at top of page, this lets you browse your computer, find a picture.? Click on OPEN, then click on EDIT/RESIZE Image.
On the next page click on RESIZE, and reduce it to 15.0 kb, click on Change?Size, then SAVE.
Then on top left of page, click on Save Changes, then next click on?Finished and it will go to the message attachment. A video of this process can be found here:?? If you are on Linux with PAT, you have to resize manually before attaching.? You can use imagemagick on the command line to get it close using something like:?convert test.jpg -define jpeg:extent=15k testout.jpg.? If it still isn't under 15K you can use your editor of choice (gimp) to crop it down a little and reduce it further. Going forward, I will try to keep my station set up for P2P every Thursday.? P2P isn't part of this week's exercise but you can send that way if you want. Stay warm everyone. 73, Ben - KU0HN |
|
Re: W0NE Winlink Roster - Week 15
¿ªÔÆÌåÓýGood morning all,? I was able to digipeat, but I did do a test run ahead of the check-in just to see if I had things set correctly.? 73, Ken? W9GM? -------- Original message -------- From: "Ben Kuhn via groups.io" <ku0hn@...> Date: 1/12/24 11:13 PM (GMT-06:00) Subject: [W0NE-Winlink-Net] W0NE Winlink Roster - Week 15 Ben, KU0HN, Lewiston, Winona, MN, USA, VHF Packet P2P
Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, VHF P2P Packet
Ken, W9GM, La Crosse, La Crosse, WI, USA, Packet
Martin, W2ILT, Laurel Springs, Camden, NJ, USA, VHF Packet, via RMS W3DRA-10 in Wilmington, DE on 145.070
Chris Muller, KD9CZM, Holmen, WI, USA, VHF
It looks like everyone except Martin was able to check in using P2P, although Shawn mentioned he had to use a connect script rather than digipeating.? Did anyone else have trouble with the digipeater? As promised, here is the check-in map:?? Keep warm this week. 73, Ben - KU0HN |
|
W0NE Winlink Roster - Week 15
We had 5 check-ins this week and one first-time checking.? Welcome Martin, W2ILT.
Ben, KU0HN, Lewiston, Winona, MN, USA, VHF Packet P2P
Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, VHF P2P Packet
Ken, W9GM, La Crosse, La Crosse, WI, USA, Packet
Martin, W2ILT, Laurel Springs, Camden, NJ, USA, VHF Packet, via RMS W3DRA-10 in Wilmington, DE on 145.070
Chris Muller, KD9CZM, Holmen, WI, USA, VHF It looks like everyone except Martin was able to check in using P2P, although Shawn mentioned he had to use a connect script rather than digipeating.? Did anyone else have trouble with the digipeater? As promised, here is the check-in map:?? Keep warm this week. 73, Ben - KU0HN |
|
W0NE Winlink Net Reminder - Week 15
Hello Everyone,
It's time for our weekly Winlink Net. This week's activity will be combining several of our past activities.? If you aren't able to do some or all of the activity, feel free to do what you can.? As always check-ins using any mode, using forms or just a regular message, are accepted. Part 1:? Compose an P2P message (Use a normal Winlink message if you are unable to do Packet P2P) and select the ICS-213 Template.? Fill it out as follows: 1.? Check the "This is an Exercise" box. 2. Incident Name: W0NE Winlink Net? ? ? ?? 3. To (Name and Position): Ben Kuhn/Net Control
4. From (Name and Position): Your Name/Net Participant
5. Subject: W0NE Net Check-in
6. Date: Current Date
7. Time: Current Time
8. Message:?
?
Use the Normal net check-in: Name, Callsign, City, County, State, Country, Mode (and Gateway if applicable)
?
9. Approved by: Your Name
9a. Position/Title: Net Participant
10. Include your GPS coordinates if you like, and I will add them to a map of check-ins
If you aren't able to use templates, just send a normal message with the check-in text Part 2: Send the form as a P2P message to KU0HN on 145.030 MHz.? If you don't have packet capabilities or are out of the area, send as a regular Winlink message via whatever method you are able to W0NE. 1.? If using Winlink Express, choose Open Session -> Packet P2P 2a.? If you are in the La Crosse or Winona area, Choose "Digipeater" for connection type and enter W0NE-7 in the "Via" box. 2b.? If you are in the Rochester area tune to 145.670 MHz, Choose "Digipeater" for connection type and enter MNROC2, W0NE-7 in the "Via" box..? The W0NE-7 node is configured to digipeat across ports so this should work. 3.? Connect 1.? If Using PAT, choose "Action" -> "Connect" 2.? Choose AX.25 as the transport 3a.? In the La Crosse or Winona area, enter W0NE-7/KU0HN.? Choose 145.030 as your frequency. 3b.? If you are in the Rochester area, enter? MNROC2/W0NE-7/KU0HN.? Choose 145.670 as your frequency. 4.? Click "Connect." I will map the results on Friday. 73, Ben - KU0HN |
|
W0NE Winlink Net Results - Week 14
Only 4 check-ins this week.? Here is the roster:
Ben, KU0HN, Lewiston, Winona, Minnesota, USA, HF ARDOP (40 Meters) Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, Packet V HF
Ken, W9GM, La Crosse, La Crosse County, WI, USA, ARDOP
Chris, KD9CZM, Holmen, La Crosse, WI, USA, VARA FM
Chris, regarding your comment last week about the EMP Proof kit, I can't say I have any experience with anything quite like that so no advice here.? I did make a note to look it up though since it sounds interesting.? Keep us posted. Does anyone by chance have a KAM Plus laying around that they wouldn't mind opening up?? I was working on recapping mine last night to fix an issue with the negative voltage regulator and I ended up making the problem worse (supposed to be -5v, was -4v, and is now -3v after recapping) so I think I screwed up one of the replacement cap values.? The schematic I have (and all that I have found online) look like someone took some typewriter eraser tape and white-out to some of the values so I guessed, apparently incorrectly, that all 3 caps are 10uf.? The cans were pretty beat up so I couldn't be sure of the values there either.? If anyone has one they could open up and post the values of C48, C49, and C51 right behind the yellow LED I'd greatly appreciate it. 73 and see everyone next week. Ben - KU0HN |
|
W0NE WInlink Net Remider - Week 14
Hello Everyone,
I hope that everyone had a happy new year and a great start to 2024. This week's activity is to get out of your comfort zone.? This week, check in with either the one line check-in, or the net check in template, but use either a mode or band you don't usually use.? You never know when it might come in handy. Also if anyone has any suggestions for future net activities, feel free to put them in the comment field, or on a separate line. 73, Ben - KU0HN |
|
W0NE Winlink Net Roster - Week 13
We had 5 check-ins this week.? Here is the roster:
Ben KU0HN, Lewiston, Winona, MN, USA, VHF Packet, I would like to make at least one Hellschreiber QSO.
Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, VHF Packet, Looking to do some POTA using the Shark Ham Sticks I got for Christmas.
Lance Tagliapietra, AD0UT, Winona, Winona, Minnesota, United States, Telnet
Chris, KD9CZM, Holmen, La Crosse, WI, USA, VARA HF,?Planning to make an EMP proof go kit using Condition 1 hard case. Any advice from the team on how to configure it???
Ken, W9GM, La Crosse, La Crosee, WI, USA, VARA HF, VA3EMN,?2024 Radio Goals:? Organize the shack and the portable gear.? I need to reduce the amount of gear I take along for field trips, whether POTA or vacations.? I'm also toying with the idea of changing out the QRP rig.
Happy New Year Everyone! 73, Ben - KU0HN |
|
W0NE Winlink Net Reminder - Week 13
Good Evening everyone,
Tomorrow will be the final net of 2023.? Since many of us are still busy with the holidays, we will keep it simple again. Either send a plain message with the following in the body: Name, Callsign, City, County, State, Country, Mode (and Gateway if applicable), or use the check-in form. On the next line, or in the comments, list any radio-related goals you have for 2024. 73, Ben - KU0HN |
|
W0NE Winlink Net Results - Week 12
We had 5 check-ins this week.? Here is the roster:
Ben KU0HN, Lewiston, Winona, MN, USA, VHF Packet
Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, VARA HF
Lance Tagliapietra, AD0UT, Winona, Winona, Minnesota, United States, Telnet
Chris, KD9CZM, Holmen, La Crosse, WI, USA, VARA FM
Ken, W9GM, La Crosse, La Crosse, WI, USA, VHF Packet Have a Merry Christmas everyone.? See you next week. 73, Ben - KU0HN |
|
W0NE Winlink Net Reminder - Week 12
Sorry about the late reminder this week.? I've been wrapping presents every evening this week.? I think we are finally done.
This week let's just do a standard check-in to keep everything simple for the holiday week.? Either the standard 1-line check-in or the check-in form are fine. Hopefully I remember to send the results email tomorrow :-) 73, Ben - KU0HN |
|
W0NE Winlink Net Results - Week 11
Hello All,
It was an interesting net this week.? There were some technical issues, mostly mine.? I know I learned a lot.? Thanks to everyone who checked in. There were 6 check-ins this week, 4 were P2P.? Next week I think we will just do a simple one-line check in using whatever mode is easiest since I know time is short around the holidays. Here is this week's roster: Ben KU0HN, Lewiston, Winona, MN, USA, Packet P2P
Shawn, KD9KGQ, Holmen, La Crosse County, WI, USA, VHF Packet
Lance Tagliapietra, AD0UT, Winona, Winona, Minnesota, United States, Telnet
Chris, KD9CZM, Holmen, La Crosse, WI, USA, VHF Packet P2P
Ken, W9GM, La Crosse, La Crosse, WI, USA, VHF Packet (P2P)
Mark, K0GMK, Rochester, Olmsted, MN, USA, Telnet
See you all next week. 73, Ben - KU0HN |
|
Re: W0Ne Winlink Net Reminder - Week 11
I did some troubleshooting after work and it looks like Direwolf crashed sometime overnight and restarted but was sending from the wrong sound card.? That'll cause issues...
After figuring that out I was able to connect to W0NE-10 on both frequencies so it looks like everything is configured and working again. I am now (hopefully) listening for P2P traffic sent to KU0HN on 145.670 if anyone wants to give P2P another try.? If you do, please let me know how it goes. 73, Ben - KU0HN |
|
Re: W0Ne Winlink Net Reminder - Week 11
¿ªÔÆÌåÓýW9GM is listening on 145.670 for P2P.? ? My normal Gateway is also operational at 145.030, but not for this exercise¡? Use 145.670 ? 73, Ken W9GM ? From: [email protected] [mailto:[email protected]] On Behalf Of Ben Kuhn via groups.io ? Ken just messaged me that he is also listening for P2P, so you can also try sending to, and connecting to, W9GM.? We will coordinate the check-ins tomorrow. |
|
Re: W0Ne Winlink Net Reminder - Week 11
W9GM worked and I think you're right, I changed to 145.670 manually - rig control didn't do it On Thu, Dec 14, 2023 at 10:46?AM Ben Kuhn via <ku0hn=[email protected]> wrote:
|