[mdmars_members] Re: \\MARS R\ New RMS under test in central MDC

  • From: John AAR3CK / AAM3MD <aar3ck@xxxxxxxxxxx>
  • To: mdmars_members@xxxxxxxxxxxxx
  • Date: Sun, 15 Nov 2009 00:42:44 -0500

Thanks Shane and John -

Well, connected the TNC back to the original computer and there you go!  OK, will leave it there for tonight and then look at my other set up tomorrow.  What I am trying to do is run the same software but on another computer.  Apparently that is not going to work as easily as I had hoped.  Might be time to do another station re-configuration, eh?

I thought I was the only night owl.. Get some rest and thanks again!

John  AAR3CK



John Yost wrote:
Just connected and passed a msg...its working now

John

AAT3NT


From: John AAR3CK / AAM3MD <aar3ck@xxxxxxxxxxx>
To: mdmars_members@xxxxxxxxxxxxx
Sent: Sun, November 15, 2009 12:23:41 AM
Subject: [mdmars_members] Re: \\MARS R\ New RMS under test in central MDC

Thanks for forwarding those logs, Allan.  I will try to compare what I am seeing during this testing phase here with what you are getting.  The quick disconnects are typical of what Shane seemed to be experiencing when he connected here .  As an aside, I was able to connect to you earlier this evening.

OK, all, I just switched the TNC to the original computer that ran this RMS at AAA3MD's QTH.  The TNC is a KAM+ and the big difference is that when the RMS software "resets" the TNC, the LED bar turns on the far left light and then just stays there (it doesn't come back into the middle like a typical reset.)  You are welcome to try this setting and please let me know what you find out, good or bad.  It'll be on all night.

If that doesn't get it I will swap out the TNC with another one.  This shouldn't be this difficult.

Thanks to all for your help.

73,

John  AAR3CK



Allan Hubbert wrote:
Shane
 
Here are the TNC and TCP logs from AAM3MD-2.  Your first connect was not acknowledged as an Airmail connection.  The second connect did show Airmail.  I see this on occasional connections from several MARS members.  I don't think that this issue is exclusive to your setup.  Perhaps the MDFTM digi is a little flakey.
 
2009/11/15 04:27:13
2009/11/15 04:27:13 [10] *** CONNECTED TO AAR3EA VIA MDFTM
2009/11/15 04:27:13 *** US Army MARS RMS Packet Node, Washington, DC
2009/11/15 04:27:16 [10] [WL2K-2.0.2.1-B2FIHM$]
2009/11/15 04:27:17 [10] SanDiego CMS via AAM3MD-2 >
2009/11/15 04:28:47 [10] *** DISCONNECTED
2009/11/15 04:50:12
2009/11/15 04:50:12 [10] *** CONNECTED TO AAR3EA VIA MDFTM
2009/11/15 04:50:12 *** US Army MARS RMS Packet Node, Washington, DC
2009/11/15 04:50:13 [10] [WL2K-2.0.2.1-B2FIHM$]
2009/11/15 04:50:14 [10] Wien CMS via AAM3MD-2 >
2009/11/15 04:50:23 [10] [AirMail-3.3.081-B2FHIM$]
2009/11/15 04:50:23 [10] ; AAM3MD-2 de AAR3EA (FM19pb)
2009/11/15 04:50:23 [10] FF
2009/11/15 04:50:24 [10] FQ
2009/11/15 04:50:33 [10] *** DISCONNECTED
 
Here are the TCP logs
 
2009/11/15 04:27:13 [10] Connecting AAR3EA to SanDiego.Winlink.org
2009/11/15 04:27:14 [10] Connected...
2009/11/15 04:27:14 [10] Callsign :
2009/11/15 04:27:14 [10] .AAR3EA
2009/11/15 04:27:14 [10] Password :
2009/11/15 04:27:14 [10] LBXVR-TFQLS AAM3MD-2 148650000 0
2009/11/15 04:27:14 [10] [WL2K-2.0.2.1-B2FIHM$]
2009/11/15 04:27:15 [10] SanDiego CMS via AAM3MD-2 >
2009/11/15 04:28:47 [10] Disconnected
2009/11/15 04:50:12
2009/11/15 04:50:12 [10] Connecting AAR3EA to Wien.Winlink.org
2009/11/15 04:50:12 [10] Connected...
2009/11/15 04:50:12 [10] Callsign :
2009/11/15 04:50:12 [10] .AAR3EA
2009/11/15 04:50:12 [10] Password :
2009/11/15 04:50:12 [10] LBXVR-TFQLS AAM3MD-2 148650000 0
2009/11/15 04:50:13 [10] [WL2K-2.0.2.1-B2FIHM$]
2009/11/15 04:50:13 [10] Wien CMS via AAM3MD-2 >
2009/11/15 04:50:23 [10] [AirMail-3.3.081-B2FHIM$]
2009/11/15 04:50:23 [10] ; AAM3MD-2 de AAR3EA (FM19pb)
FF
2009/11/15 04:50:24 [10] FQ
2009/11/15 04:50:29 [10] Disconnected
 
 
 

Allan, AAR3EB
Sysop AAM3MD-2 RMS Packet Node

--- On Sun, 11/15/09, Shane J. Wolfe <shanewolfe@xxxxxxx> wrote:

From: Shane J. Wolfe <shanewolfe@xxxxxxx>
Subject: [mdmars_members] Re: \\MARS R\ New RMS under test in central MDC
To: mdmars_members@xxxxxxxxxxxxx
Date: Sunday, November 15, 2009, 4:33 AM

John,

Just tested it out.  I can't hit it direct from my location in Odenton so I digi'ed in through Fort Mead.  I've never digi'ed into a Winlink system before, so I tried both AAM3MD-2 and AAM3MD-3.  I get initial connections on both systems but the sequence seems to stop there.  I don't get the typical mail checking sequence as usual.  Probably an oversight/inexperience on my part there.  Connection wise, it seems to be working fine. 

-Shane
AAR3EA




On Nov 14, 2009, at 9:50 PM, John AAR3CK / AAM3MD wrote:

> Hi, All -
>
> We are currently testing the configuration for a re-located RMS, call sign AAM3MD-3,  located in central Carroll County.  If you cannot hit this directly, you can digi through MDFTM or MDFTR, as well as some other local stations.
>
> While this was operating previously, we have changed a few things and it might not be quite right yet.  Please take a few minutes and see if you can access WL2K through this RMS.  If you have any problems at all, please document what you run into and shoot a quick email to me at aar3ck@xxxxxxxxxxx.  Your help and patience is appreciated.  It may take a few tries to get this right.
>
> 73 and thanks!
>
> John  AAR3CK / AAM3MD
>
>
>
>
> Web Site: http://mdarmymars.home.comcast.net/%7Emdarmymars/index.htm
>
> List Serve Administrator:  John aar3ck@xxxxxxxxxxx

Web Site: http://mdarmymars.home.comcast.net/~mdarmymars/index.htm

List Serve Administrator:  John aar3ck@xxxxxxxxxxx

Web Site: http://mdarmymars.home.comcast.net/~mdarmymars/index.htm List Serve Administrator: John aar3ck@xxxxxxxxxxx



__________ Information from ESET Smart Security, version of virus signature database 4608 (20091114) __________

The message was checked by ESET Smart Security.

http://www.eset.com
Web Site: http://mdarmymars.home.comcast.net/~mdarmymars/index.htm List Serve Administrator: John aar3ck@xxxxxxxxxxx

Other related posts: