¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. W0NE-Winlink-Net
  2. Topics

W0Ne Winlink Net Reminder - Week 11

 

Good Evening Everyone,

Tomorrow is our Winlink net.

Since we have been at this 10 weeks now, and most are able to check in over RF, Let's try some P2P this week.? P2P messages don't need the internet at all and send directly from one Winlink client to another.

I have my packet station set up for P2P connections, starting now through Friday morning to take P2P check-ins.? Since almost nobody is in simplex range of me, despite being in the middle of the group, anyone who wants to try this will likely have to also digipeat through W0NE-7 for Winona and La Crosse folks, or MNROC2 in Rochester.? My station should be reachable from either.

To send simplex (this time) you must be using packet.? When you compose the message, Change the "Winlink Message" drop down to "Peer to Peer."? If you are using Pat, check the P2P check box.? You can check in with a normal one-line check-in this week, nothing fancy is needed.

To connect, use 145.670MHz and connect to W0NE (no SSID).? PAT should respond and take your message.

If you aren't set up for packet, feel free to check in any other way you can.

Since this is my first time trying P2P as well, I'd like to hear everyone's experiences so I can learn and improve for next time.

73 all,
Ben - KU0HN
 

I tried this setup but didn't have any success:

Screenshot 2023-12-14 055557.png

Any ideas on what I did?wrong?

Thanks,
Chris


On Wed, Dec 13, 2023 at 9:43?PM Ben Kuhn via <ku0hn=[email protected]> wrote:
Good Evening Everyone,

Tomorrow is our Winlink net.

Since we have been at this 10 weeks now, and most are able to check in over RF, Let's try some P2P this week.? P2P messages don't need the internet at all and send directly from one Winlink client to another.

I have my packet station set up for P2P connections, starting now through Friday morning to take P2P check-ins.? Since almost nobody is in simplex range of me, despite being in the middle of the group, anyone who wants to try this will likely have to also digipeat through W0NE-7 for Winona and La Crosse folks, or MNROC2 in Rochester.? My station should be reachable from either.

To send simplex (this time) you must be using packet.? When you compose the message, Change the "Winlink Message" drop down to "Peer to Peer."? If you are using Pat, check the P2P check box.? You can check in with a normal one-line check-in this week, nothing fancy is needed.

To connect, use 145.670MHz and connect to W0NE (no SSID).? PAT should respond and take your message.

If you aren't set up for packet, feel free to check in any other way you can.

Since this is my first time trying P2P as well, I'd like to hear everyone's experiences so I can learn and improve for next time.

73 all,
Ben - KU0HN

 

¿ªÔÆÌåÓý

Chris,?
Ben is going to look into the issue.? It may be that?
using W0NE-7 to digi to W0NE is the culprit.??
Ken W9GM?





-------- Original message --------
From: Chris Muller <mullman71@...>
Date: 12/14/23 5:57 AM (GMT-06:00)
Subject: Re: [W0NE-Winlink-Net] W0Ne Winlink Net Reminder - Week 11

I tried this setup but didn't have any success:

Screenshot 2023-12-14 055557.png

Any ideas on what I did?wrong?

Thanks,
Chris


On Wed, Dec 13, 2023 at 9:43?PM Ben Kuhn via <ku0hn=[email protected]> wrote:
Good Evening Everyone,

Tomorrow is our Winlink net.

Since we have been at this 10 weeks now, and most are able to check in over RF, Let's try some P2P this week.? P2P messages don't need the internet at all and send directly from one Winlink client to another.

I have my packet station set up for P2P connections, starting now through Friday morning to take P2P check-ins.? Since almost nobody is in simplex range of me, despite being in the middle of the group, anyone who wants to try this will likely have to also digipeat through W0NE-7 for Winona and La Crosse folks, or MNROC2 in Rochester.? My station should be reachable from either.

To send simplex (this time) you must be using packet.? When you compose the message, Change the "Winlink Message" drop down to "Peer to Peer."? If you are using Pat, check the P2P check box.? You can check in with a normal one-line check-in this week, nothing fancy is needed.

To connect, use 145.670MHz and connect to W0NE (no SSID).? PAT should respond and take your message.

If you aren't set up for packet, feel free to check in any other way you can.

Since this is my first time trying P2P as well, I'd like to hear everyone's experiences so I can learn and improve for next time.

73 all,
Ben - KU0HN

 

Thanks for letting me know.

I have changed the listening call to KU0HN, so if you want to retry sending to my call, and connecting to KU0HN via W0NE-7, we can see if it's an issue with digipeating or something else.

73,
Ben - KU0HN
 

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.

73,
Ben - KU0HN
 

No Joy:

Screenshot 2023-12-14 164252.png


On Thu, Dec 14, 2023 at 10:38?AM Ben Kuhn via <ku0hn=[email protected]> wrote:
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.

73,
Ben - KU0HN

 

I'm listening on 145.670.? I'm not sure if you have rig control set up, but that might be why as well.

Ben
On Thursday, December 14th, 2023 at 10:43 AM, Chris Muller <mullman71@...> wrote:

No Joy:

Screenshot 2023-12-14 164252.png

On Thu, Dec 14, 2023 at 10:38?AM Ben Kuhn via <ku0hn=[email protected]> wrote:
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.

73,
Ben - KU0HN


 

W9GM worked and I think you're right, I changed to 145.670 manually - rig control didn't do it

Screenshot 2023-12-14 164938.png


On Thu, Dec 14, 2023 at 10:46?AM Ben Kuhn via <ku0hn=[email protected]> wrote:
I'm listening on 145.670.? I'm not sure if you have rig control set up, but that might be why as well.

Ben
On Thursday, December 14th, 2023 at 10:43 AM, Chris Muller <mullman71@...> wrote:

No Joy:

Screenshot 2023-12-14 164252.png

On Thu, Dec 14, 2023 at 10:38?AM Ben Kuhn via <ku0hn=[email protected]> wrote:
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.

73,
Ben - KU0HN


 

¿ªÔÆÌåÓý

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
Sent: Thursday, December 14, 2023 10:39 AM
To: [email protected]
Subject: Re: [W0NE-Winlink-Net] W0Ne Winlink Net Reminder - Week 11

?

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.

73,
Ben - KU0HN

 

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

1 - 10 of 10