Date   

Re: K0SI packet down?

Ryan Raney
 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

I would like a packet round table/chat net.  I’m in.

73, NO0I

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Wednesday, September 16, 2020 7:09 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Excellent, I saw you join the chat. I said hi but looks like you left before you saw it. I'll work on making the connect message a bit more intuitive for first time users soon. 

 

Thanks for giving it a go. If there's any interest in doing a packet net in the node chat at some point in the future that could be interesting. 

 

I'm working on getting a friend in Moberly up and running on packet so hopefully we'll have another player soon

 

73

 

On Wed, Sep 16, 2020, 7:06 PM John Beatty <jebeatty@...> wrote:

Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:

Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:

Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 

Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:

I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Excellent, I saw you join the chat. I said hi but looks like you left before you saw it. I'll work on making the connect message a bit more intuitive for first time users soon. 

Thanks for giving it a go. If there's any interest in doing a packet net in the node chat at some point in the future that could be interesting. 

I'm working on getting a friend in Moberly up and running on packet so hopefully we'll have another player soon

73

On Wed, Sep 16, 2020, 7:06 PM John Beatty <jebeatty@...> wrote:
Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:
Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

John Beatty
 

Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:
Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi Fred,

MMJY is a mersweb packet node in Centralia on 145.070. it's linked to a similar node in Jefferson City called MJEF on the same frequency. There used to be two other nodes that would make the trip over to STL but they appear do be down indefinitely.

These nodes allow low power stations to relay through them to reach nodes or winlink servers they couldn't reach otherwise. For instance you can connect to my packet node KE5SUI-14 through them if you can't hit it directly. 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

C MMJY
CONN
C K0SI-10
CONN

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 


Thanks!
-Ryan KE5SUI

On Wed, Sep 16, 2020, 5:37 PM Fred Dittrich <fdittric@...> wrote:
Ryan

What is MMJY?

73

Fred AE0FD


At 05:36 PM 9/16/2020, you wrote:
Hi Fred,

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Fred Dittrich
 

Ryan

What is MMJY?

73

Fred AE0FD


At 05:36 PM 9/16/2020, you wrote:
Hi Fred,

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Ryan Raney
 

Hi Fred, 

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Fred Dittrich
 

Ryan

Directly.

73

Fred AE0FD


At 05:24 PM 9/16/2020, you wrote:
Hi Fred,

Did you connect to K0SI-10 directly or through MMJY / MJEF?Â

On Wed, Sep 16, 2020, 4:34 PM Fred Dittrich <fdittric@...> wrote:
Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 


On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi Fred,

Did you connect to K0SI-10 directly or through MMJY / MJEF? 

On Wed, Sep 16, 2020, 4:34 PM Fred Dittrich <fdittric@...> wrote:
Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

John Beatty
 

Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Fred Dittrich
 

Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: Two Meter Opening

John Beatty
 

Nice job Chris.   Really wishing I had a beam!

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Chris Swisher
Sent: Wednesday, September 16, 2020 8:50 AM
To: main@CMRA.groups.io
Subject: [CMRA] Two Meter Opening

 

There has been a major opening to the east coast on VHF. It started last night and is still active. Even with my modest 20 watts on USB FT8 into a vertical pair of yagis, I confirmed a 778 mile contact into eastern Virginia. I was into a FM repeater in Wauseon, OH that was being received at 10 over S9 here. Some fun is available if interested. https://pskreporter.info/pskmap.html and http://aprs.mennolink.org/ have excellent graphical displays of where it it hot!


Two Meter Opening

Chris Swisher
 

There has been a major opening to the east coast on VHF. It started last night and is still active. Even with my modest 20 watts on USB FT8 into a vertical pair of yagis, I confirmed a 778 mile contact into eastern Virginia. I was into a FM repeater in Wauseon, OH that was being received at 10 over S9 here. Some fun is available if interested. https://pskreporter.info/pskmap.html and http://aprs.mennolink.org/ have excellent graphical displays of where it it hot!


Chance to win a couple of radios from Bridgecom

AD0UK
 

Click here to enter: ENTER HERE



73

Brian
ADØUK


Re: K0SI packet down?

Ryan Raney
 

Looks like i'm still having trouble connecting to the k0si packet node. It took 7 attempts to send an email today. logs below, i'd appreciate any advice on what I can do about this. Running a Kenwood TH-D74 with a built in TNC, so no audio levels to adjust. 

Thanks,
-Ryan KE5SUI

 

*** Starting to call with connection script mjef to k0si10

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\mjef to k0si10.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 15:58:55

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C K0SI-10

   C K0SI-10

*** Looking for 'CONN' in: MJEF:K0ETY-2} CONNECTED TO K0SI-10

 

*** Found connection response: CONNECTED TO K0SI-10

 

*** End of connection script

MJEF:K0ETY-2} Connected to K0SI-10

[WL2K-5.0-B2FWIHJM$]

;PQ: 90996305

CMS via K0SI >

   ;FW: KE5SUI

   [RMS Express-1.5.31.0-B2FHM$]

 

   ;PR: 86294502

   ; K0SI-10 DE KE5SUI (EM38TW)

   FC EM KNRQRF15LLLO 4274 2297 0

   F> F6

FS Y

*** Sending KNRQRF15LLLO.

*** Disconnected at 2020/09/08 16:00:42

 

*** Disconnect reported.

 

~~Second Try~~

 

*** Starting to call with connection script mjef to k0si10

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\mjef to k0si10.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:01:12

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C K0SI-10

   C K0SI-10

*** Aborting script due to response: *** ERROR CHECK FAILED ON RECEIVING B2 MESSAGE. [RECEIVED DATA STREAM NOT A CORRECT FORMAT] - DISCONNECTING (63.239.57.158)

 

*** Aborting connection script.

*** Terminating connection script.

*** Sending Bye to drop the connection.

*** Disconnected at 2020/09/08 16:01:20

 

*** Disconnect reported.

 

 

~~third try~~

 

 

*** Starting to call with connection script mjef to k0si10

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\mjef to k0si10.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:02:38

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C K0SI-10

   C K0SI-10

*** Looking for 'CONN' in: MJEF:K0ETY-2} CONNECTED TO K0SI-10

 

*** Found connection response: CONNECTED TO K0SI-10

 

*** End of connection script

MJEF:K0ETY-2} Connected to K0SI-10

[WL2K-5.0-B2FWIHJM$]

;PQ: 08911159

CMS via K0SI >

   ;FW: KE5SUI

   [RMS Express-1.5.31.0-B2FHM$]

 

   ;PR: 83186824

   ; K0SI-10 DE KE5SUI (EM38TW)

   FC EM KNRQRF15LLLO 4274 2297 0

   F> F6

FS Y

*** Sending KNRQRF15LLLO.

*** Disconnected at 2020/09/08 16:04:22

 

*** Disconnect reported.

 

~~4th try~~

 

*** Starting to call with connection script round the world

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\round the world.txt

*** Starting connection script with 10 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:05:15

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C MJEF6

   C MJEF6

*** Timeout on connection step while executing connection script.

*** Terminating connection script.

*** Sending Bye to drop the connection.

*** Disconnected at 2020/09/08 16:06:16

 

*** Disconnect reported.

 

~~5th try~~

 

*** Starting to call with connection script round the world

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\round the world.txt

*** Starting connection script with 10 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:06:46

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C MJEF6

   C MJEF6

*** Looking for 'CONN' in: MJEF:K0ETY-2} CONNECTED TO MJEF6:K0ETY-6

 

*** Found connection response: CONNECTED TO MJEF6:K0ETY-6

 

*** Sending script line 5: C MMJY6

   C MMJY6

*** Looking for 'CONN' in: MJEF6:K0ETY-6} CONNECTED TO MMJY6:K0SI-6

 

*** Found connection response: CONNECTED TO MMJY6:K0SI-6

 

*** Sending script line 7: C MMJY

   C MMJY

*** Looking for 'CONN' in: MMJY6:K0SI-6} CONNECTED TO MMJY:K0SI-2

 

*** Found connection response: CONNECTED TO MMJY:K0SI-2

 

*** Sending script line 9: C K0SI-10

   C K0SI-10

*** Looking for 'CONN' in: MMJY:K0SI-2} CONNECTED TO K0SI-10

 

*** Found connection response: CONNECTED TO K0SI-10

 

*** End of connection script

MMJY:K0SI-2} Connected to K0SI-10

[WL2K-5.0-B2FWIHJM$]

;PQ: 56678025

CMS via K0SI >

   ;FW: KE5SUI

   [RMS Express-1.5.31.0-B2FHM$]

 

   ;PR: 09635238

   ; K0SI-10 DE KE5SUI (EM38TW)

   FC EM KNRQRF15LLLO 4274 2297 0

   F> F6

FS Y

*** Sending KNRQRF15LLLO.

*** Disconnected at 2020/09/08 16:11:22

 

*** Disconnect reported.

 

 

~~6th try~~

 

*** Starting to call with connection script mjef to k0si10

*** Attempting to open packet script: C:\RMS Express\KE5SUI\Scripts_WL2K\mjef to k0si10.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:13:14

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C K0SI-10

   C K0SI-10

*** Looking for 'CONN' in: MJEF:K0ETY-2} CONNECTED TO K0SI-10

 

*** Found connection response: CONNECTED TO K0SI-10

 

*** End of connection script

MJEF:K0ETY-2} Connected to K0SI-10

[WL2K-5.0-B2FWIHJM$]

CMS via K0SI >

   ;FW: KE5SUI

   [RMS Express-1.5.31.0-B2FHM$]

 

   ; K0SI-10 DE KE5SUI (EM38TW)

   FC EM KNRQRF15LLLO 4274 2297 0

   F> F6

*** [2] Login failed - no response to challenge - Disconnecting (63.239.57.158)

MJEF:K0ETY-2} Welcome back.

*** [418] Protocol error - response to proposals does not match.

*** Disconnecting due to timeout

*** Disconnected at 2020/09/08 16:14:18

 

*** Disconnect reported.

 

~~7th try~~

 

*** Initial connection node for packet script is MJEF

*** Opening serial port COM4; 9600 baud; KISS

*** Connecting to MJEF

*** Connected to MJEF at 2020/09/08 16:18:00

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C K0SI-10

   C K0SI-10

*** Looking for 'CONN' in: MJEF:K0ETY-2} CONNECTED TO K0SI-10

 

*** Found connection response: CONNECTED TO K0SI-10

 

*** End of connection script

MJEF:K0ETY-2} Connected to K0SI-10

[WL2K-5.0-B2FWIHJM$]

;PQ: 03112112

CMS via K0SI >

   ;FW: KE5SUI

   [RMS Express-1.5.31.0-B2FHM$]

 

   ;PR: 67898103

   ; K0SI-10 DE KE5SUI (EM38TW)

   FC EM KNRQRF15LLLO 4274 2297 0

   F> F6

FS Y

*** Sending KNRQRF15LLLO.

FF

*** Completed send of message KNRQRF15LLLO

*** Sent 1 message.  Bytes: 2335,  Time: 02:02,  bytes/minute: 1144

   FQ

*** --- End of session at 2020/09/08 16:20:41 ---

*** Messages sent: 1.  Total bytes sent: 2335,  Time: 02:41,  bytes/minute: 867

*** Messages Received: 0.  Total bytes received: 0,  Total session time: 02:41,  bytes/minute: 0

*** Disconnecting


September VE Test Session Location

Jon Cole
 

Hello All,

Due to the changing seasons and the sun setting earlier, I have rented the Harris Shelter at Cosmo Park for the VE Test Session on Tuesday September 15 at 7:00 PM.  The shelter has lights to help us see as the sun sets.  The Harris Shelter is located in the southwest corner of the park.  Go in the main entrance, turn 'left' at the roundabout and zig-zag slightly left along the driveway to the southwest corner of the park.  At one point the road dips and looks like a maintenance road,  but keep going.

Harris Shelter
Cosmo Park
1615 Business Loop 70W
Columbia, MO

If anyone has any questions, feel free to call or email me.

Jon Cole, N0OFJ
VE Liaison

(573) 864-4551
ColePLS@...


Reminder - we have an election for next weeks club meeting - we have two nominees for the Member at Large position:

AD0UK
 

Paul Watt (KEØIKG) and Ernest Shaw (KCØEZE)


Please respond to k0si@... to make your votes for the person you want to be in the position, if you do not wish to take a vote on the air - or make it more convenient for counts of votes on the air.


Thanks,

Brian
ADØUK
President, CMRA


Re: FCC fees for Amateur radio services

AD0UK
 

 Better upgrade as far as you can go, as soon as you can if you are going to - looks like the upgrades will cost you as well.  Get to Extra and only pay it once, before its too late!!!  That's my 2 cents.


73

Brian
ADØUK


On Sat, Aug 29, 2020 at 8:56 PM Jon Cole via groups.io <colepls=yahoo.com@groups.io> wrote:
The FCC fees have varied widely over the last few decades. I was frankly surprised when they were reduced to zero and I assumed it was only a matter of time before they raised it again. I think that less is better, but even if they charge $100, it would only be $10 a year. Annoying but not bad. I was more concerned with the cost of an official copy of your license. 

Jon Cole, N0OFJ 

On Aug 29, 2020, at 7:22 PM, Ralph Howard <wd6bgn@...> wrote:


I hold every individule radio liscense avaiable from the FCC.  The comerical liscenes now never expire.  But I had to pay for them.  Perhaps the FCC is going to do the same for Amature Radio.  Ie a lifetime license.
We used to pay a fee for ham and CB liscense.

So we have been lucky for the past few years.  Times change.


Ralph Howard
WD6BGN


From: main@CMRA.groups.io <main@CMRA.groups.io> on behalf of Tim Spurgeon <tims173@...>
Sent: Saturday, August 29, 2020 7:12:44 PM
To: main <main@CMRA.groups.io>
Cc: main <main@cmra.groups.io>
Subject: Re: [CMRA] FCC fees for Amateur radio services
 
FCC, are you kidding me?

You know, it is not the so much the money as it is the lack of respect the HAM community gets for its hard work:

We spend our time and money to pass examination for Tech., General, and Extra,
We spend our money and time to purchase our radios, antennas, power supplies, go kits,
We spend our money and time to be prepared for times of emergency,
We spend our time and money to participate in CMRA and BCARES club activities,
We spend our time and money to join and participate with Boone County Emergency organizations,
We spend our time and money to join and participate with S.E.M.A.
We spend our time and money to join and participate with F.E.M.A.
We spend our time and money to pass S.E.M.A. and F.E.M.A. training classes and tests,
     (as many of these courses I have taken, reimbursement has been offered to police, firefighters, and first responders in the class
      for travel, lodging, and food; I have paid my own way for the same.)
We spend out time and money to practice our skills in radio sport through S.E.T.s and Field Days,
We spend out time and money to learn radio theory of computer aided radio, Software Defined Radio, and Morse Code,
We spend our time and money to Elmer new HAMs and some of us through serving as V.E.,
We spend our time away from wives, husbands, and kids.

If the Federal government wants to regulate and control the radio waves in its jurisdiction, the least it can do is not stand in our way
and make it harder on us and make it more expensive to be ready for public service.  They should be ashamed of this proposal!

Keep this up, FCC, and I will take my toys and go home!

Sincerely,

Tim E. Spurgeon
"Expecting the best; prepared for the worst."

************************************************

----- Original Message -----
From: "John Beatty" <jebeatty@...>
To: "main" <main@cmra.groups.io>
Sent: Saturday, August 29, 2020 10:34:53 AM
Subject: Re: [CMRA] FCC fees for Amateur radio services

I don't favor reinstituting fees as defined.  We're doing our best to lower the cost of entry.  Our numbers are shrinking as it is. This just adds more "friction".

Get BlueMail for Android<http://www.bluemail.me/r?b=15997>
On Aug 29, 2020, at 8:09 AM, Gary Vaught - W9TIG <gdv.pops@...<mailto:gdv.pops@...>> wrote:
While I dislike the potential for this to discourage some from becoming new operators, I think that this is a responsible move - IF it's truly a cost-based fee.

-
Best Regards,
Gary D Vaught


We can engineer a solution to nearly any problem you can accurately define.

- somewhat anonymous


On Fri, Aug 28, 2020 at 5:50 PM paul watt < pbw65@...<mailto:pbw65@...>> wrote:
Check it out ..

http://www.arrl.org/news/fcc-proposes-to-reinstate-amateur-radio-service-fees

--
73
W9TIG

Gary Vaught






421 - 440 of 4512