Date   

Trace Log Clipboard (was: Which Log is for the Data-Port?)

Lynn Deffenbaugh
 

Note to all:  The trace log windows in APRSIS32 support the clipboard!  You don't need to do screen captures and post pictures.

To copy the entire window contents, just hit the Copy menu option.  Boom.  Paste the text wherever you want it.

To copy a selection, drag the mouse over the desired lines and hit Control-C (as in Copy).  You can then paste those lines as text wherever you need them.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 11/15/2019 9:12 AM, KD7YZ Bob wrote:
I can address both of your two paragraphs better with some of the screenshots.

--
73
Bob KD7YZ
AMSAT LM #901


Re: Which Log is for the Data-Port?

KD7YZ Bob
 

On 11/14/2019 18:08, Rob Giuliano via Groups.Io wrote:

The port definitions you show are ports for the D710's "built in TNC", not AGW
True. I setup both APRS and Packet via APRSIS32's setup pre-caned D710 methods.

In AGWPE I used the Soundcard approach to see/read SignaLink's conn to DATA on the D710 back. This is then made available to APRSIS32 via an "AGW" Pre-Canned port I called 127.0.0.1:8000 but have used localhost too.

I also read that AGWPE MUST see the D710GA in Packet mode when first being activated. Took me long time to understand why I wasn't seeing AGW thru APRSIS32. (one of many manifestations of my lack of skill-sets with Packet/Kenwood/APRSIS32 interactions).

    I am quite certain that when using the head TNC port, only 1 side of the radio is connected to this internal TNC and thus sent to the attached computer running APRSIS32.
You also appear to have the "data jack" (6-pin audio I/O and PTT) connected through the SignaLink and AGW.  Having both connected,  are you are using the radio for 2 different functions at the same time?  I am quite sure that the radio is not designed for this.

I can address both of your two paragraphs better with some of the screenshots.

First off, let ac knowledge that I understand I loose maybe 3DB or more, whatever, by running the D710GA on the same Frequency Band. So far it is inconsequential.

SO, right-hand channel(B) is on the AX.25 up/down links for the pitifully few Satellites carrying Packet, at the moment.
Screenshot shows USNAP-1 ARISS from the SignaLink connection, the ONLY one with that Frequency. It also show a local, N4TNA beacon.


Left-Hand channel A Band is on APRS.

One screenshot of the Scroller shows my ubiquitous Beacon. I have yet to tell it that I am not testing batteries. But anyway, I left it in SmartBeaconing .... as per one of a dozen GREAT PDF's recommended by people. Randy has a great three page PDF which got me "going" on this lashup, BTW .

I have noted that I must be in Radio-Mode Packet to interface to AGW ...I see though I can't DigiPeat even though I have that setting in D710GA's menu set to Digipeat .

anyway, N4TNA, and my Beacon are copied off Left-Hand (chan A) and Satellites off the right-hand Ch-B 145.825.

Also. I have the program SDR-Console running on 144.390 sending output to VSPE-Line#1 VAC1 ...through AGWPE-Telnet to APRSIS32(port)

So far, The missing SSID problem has not popped up. I am guessing your comment about not trying to tell APRSIS32 to run both Ports at the same time was likely the cause.

The last couple days I have noted a SERIOUS lack of 144.390 APRS traffic. Neither the 15 element nor the stacked loops has seen anything more than my beacon and N4tna.

This is another manifestation of my limited knowledge of interconnection all this stuff.




I am no sure if you can connect the UISS application and APRSIS32 application at the same time, but I think the AGW protocol can handle it.


UISS has ONE trait that helps me make AX.25 QSO over ISS ... there are three buttons with text fields I can fill in then tap a button and have a UI go out ...if anyone copies the DigiPeat from ISS ... they send something ACKing it back to me and I fore off a 'In The Log Book type call ... and Voila! another grid on 2m (usually).

I can't figure out how tro make APRSIS32 let me INSTANTLY select one of three UI type messages and fire them back up to the bird(s). It's crazy-fast to try to make a 145.825 AX.25 QSO.


You will have to disable the Port(D710) ones you were using.  Using
APRSIS32 with an AGW port will allow the data to be displayed from any stream, however, I am sure it can only TX on "stream zero" - first AGW port.
this I will have to mull-over as I am not sure the connotations nor where Stream-Zed is.

But thanks for the great tips.


--
73
Bob KD7YZ
AMSAT LM #901


Re: Which Log is for the Data-Port?

j.lineback
 

Some relevant input...

"You also appear to have the "data jack" (6-pin audio I/O and PTT) connected through the SignaLink and AGW.  Having both connected,  are you are using the radio for 2 different functions at the same time?  I am quite sure that the radio is not designed for this.

710 will happily run two functions.  Mine has a Kantronics KPC-3 Plus USB connected to the radio body’s DATA jack configured against Band B. 

Meanwhile, the good cable from RT Systems (or can be Kenwood’s own) is patched between the COMM port on the radio’s head and computer on Band A, utilizing Internal TNC.

She just sits there and successfully behaves like a pair of radios- and TNCs, doing two separate things, simultaneously, under a single PC running two softwares, with one antenna, and never complains.

73,
Jerry K4WOF


On Nov 14, 2019, at 6:08 PM, Rob Giuliano via Groups.Io <kb8rco@...> wrote:

Now I am totally confused.

The port definitions you show are ports for the D710's "built in TNC", not AGW.
    APRSIS32 has 2 ways of connecting to the serial TNC interface of the D710 (head via PG-5G cable or equivilent).  One is PKT and the other APRS. The difference is in the state of the radio when APRSIS32 connects, and the commands sent.  You will need to review the D710 information on the WIKI for how each works, but I know one of these port types has an issue with the callsign-ssid of the radio vs APRSIS32.  That is most likely what you are seeing in the pictures witha callsig n-ssid in one and not the other.
    I am quite certain that when using the head TNC port, only 1 side of the radio is connected to this internal TNC and thus sent to the attached computer running APRSIS32. 

You also appear to have the "data jack" (6-pin audio I/O and PTT) connected through the SignaLink and AGW.  Having both connected,  are you are using the radio for 2 different functions at the same time?  I am quite sure that the radio is not designed for this. 

There is no way to directly connect APRSIS32 to the sound card (SignLink or other).  APRSIS32 connects to TNCs (or at least serial data streams from them).  The function of AGWpe (or ther such software TNC/modems) is to take in the audio from the radio and decode the tones to turn it into a TNC data stream (software TNC).

You can connect APRSIS32 to AGW through an AGW port:
Example:
   Port Type:   AGW
  Port name:  D710_AGW
     <Create>
for Port Type pop up: TCP/IP
  IP or DNS:    LocalHost     (or your IP address of the compuiter running AGWpe)
           Port:    8000            (default)

I am no sure if you can connect the UISS application and APRSIS32 application at the same time, but I think the AGW protocol can handle it.  You will have to disable the Port(D710) ones you were using.  Using APRSIS32 with an AGW port will allow the data to be displayed from any stream, however, I am sure it can only TX on "stream zero" - first AGW port.

Robert Giuliano
KB8RCO



On Thursday, November 14, 2019, 11:08:20 AM EST, KD7YZ Bob <kd7yz@...> wrote:


On 11/13/2019 15:21, Rob Giuliano via Groups.Io wrote:
> If you are using AGWpe to interface with the SignaLink, then the RF port
> would be of TYPE AGW.  WHat are you using to show the "AGWPE decode"? 
> AGWMonitor, AGWTerm, or something else?
> Thanks numerous helpful replies though My Thunderbird never got Lynn's
reply; go figure.

I use AGWPE the paid version thereof, Packet Engine Pro.
It allows me to define any soundcard.

I was using UISS to gather the AGW Telnet output and display same ....
though I can see either Individual AGW ports I've define OR I can see
the ALL PORTS tab also on Packet Engine Pro.

So I created an AGWPE/Packet-Engine-Pro port off the SignaLink Soundcard
TX and RX definitions.

In APRSIS32 I see where I can define an AGW Port.

I do NOT find a way in APRSIS32 to create a port from a "Device" such as
LINE#1/VAC#1 which comes out of SDR-Console.
I didn't find a way to Directly have APRIS32 look at the output of the
SignaLink's Soundcard, which appears in Device Manger under
Sound/vid/game as USB Audio Codec.

SO ... I have external Data on the D710GA set to Band or channel, "B:"

Turns out this appears then in  the output  'Data Socket' of the
D710GA..... readable by the program APRSIS32 ... butttt, sometimes
there's garbage which appears to me to be some internal commands from
one thing or the other.

Though in my first email u can see the decoded Sats telemetry ... and
only one radio was connected to that 145.825 frequency //// CH-B

As there is no APRSIS32 "Port" defined for CH-B, there are no "View"
items for me to see; and there appears no way to tell iGate to seek
meaningful data from the D710GA's right-side display (145.825). And I
call it CH-b

This all my be related to an ongoing issue with either the PKT or the
APRS Ports I try to make, in APRSIS32.

Sometime, maybe today or maybe in the morning, the SSID box is blank and
my "Home" icon is missing too. See screen shots jpgs, if I am able to
send jpgs here otherwise tell me how rto send them please. I have the
before and after's.

Tnx all the help guys.

--
73
Bob KD7YZ
AMSAT LM #901





Re: Which Log is for the Data-Port?

Rob Giuliano
 

Now I am totally confused.

The port definitions you show are ports for the D710's "built in TNC", not AGW.
    APRSIS32 has 2 ways of connecting to the serial TNC interface of the D710 (head via PG-5G cable or equivilent).  One is PKT and the other APRS. The difference is in the state of the radio when APRSIS32 connects, and the commands sent.  You will need to review the D710 information on the WIKI for how each works, but I know one of these port types has an issue with the callsign-ssid of the radio vs APRSIS32.  That is most likely what you are seeing in the pictures witha callsig n-ssid in one and not the other.
    I am quite certain that when using the head TNC port, only 1 side of the radio is connected to this internal TNC and thus sent to the attached computer running APRSIS32. 

You also appear to have the "data jack" (6-pin audio I/O and PTT) connected through the SignaLink and AGW.  Having both connected,  are you are using the radio for 2 different functions at the same time?  I am quite sure that the radio is not designed for this. 

There is no way to directly connect APRSIS32 to the sound card (SignLink or other).  APRSIS32 connects to TNCs (or at least serial data streams from them).  The function of AGWpe (or ther such software TNC/modems) is to take in the audio from the radio and decode the tones to turn it into a TNC data stream (software TNC).

You can connect APRSIS32 to AGW through an AGW port:
Example:
   Port Type:   AGW
  Port name:  D710_AGW
     <Create>
for Port Type pop up: TCP/IP
  IP or DNS:    LocalHost     (or your IP address of the compuiter running AGWpe)
           Port:    8000            (default)

I am no sure if you can connect the UISS application and APRSIS32 application at the same time, but I think the AGW protocol can handle it.  You will have to disable the Port(D710) ones you were using.  Using APRSIS32 with an AGW port will allow the data to be displayed from any stream, however, I am sure it can only TX on "stream zero" - first AGW port.

Robert Giuliano
KB8RCO



On Thursday, November 14, 2019, 11:08:20 AM EST, KD7YZ Bob <kd7yz@...> wrote:


On 11/13/2019 15:21, Rob Giuliano via Groups.Io wrote:
> If you are using AGWpe to interface with the SignaLink, then the RF port
> would be of TYPE AGW.  WHat are you using to show the "AGWPE decode"? 
> AGWMonitor, AGWTerm, or something else?
> Thanks numerous helpful replies though My Thunderbird never got Lynn's
reply; go figure.

I use AGWPE the paid version thereof, Packet Engine Pro.
It allows me to define any soundcard.

I was using UISS to gather the AGW Telnet output and display same ....
though I can see either Individual AGW ports I've define OR I can see
the ALL PORTS tab also on Packet Engine Pro.

So I created an AGWPE/Packet-Engine-Pro port off the SignaLink Soundcard
TX and RX definitions.

In APRSIS32 I see where I can define an AGW Port.

I do NOT find a way in APRSIS32 to create a port from a "Device" such as
LINE#1/VAC#1 which comes out of SDR-Console.
I didn't find a way to Directly have APRIS32 look at the output of the
SignaLink's Soundcard, which appears in Device Manger under
Sound/vid/game as USB Audio Codec.

SO ... I have external Data on the D710GA set to Band or channel, "B:"

Turns out this appears then in  the output  'Data Socket' of the
D710GA..... readable by the program APRSIS32 ... butttt, sometimes
there's garbage which appears to me to be some internal commands from
one thing or the other.

Though in my first email u can see the decoded Sats telemetry ... and
only one radio was connected to that 145.825 frequency //// CH-B

As there is no APRSIS32 "Port" defined for CH-B, there are no "View"
items for me to see; and there appears no way to tell iGate to seek
meaningful data from the D710GA's right-side display (145.825). And I
call it CH-b

This all my be related to an ongoing issue with either the PKT or the
APRS Ports I try to make, in APRSIS32.

Sometime, maybe today or maybe in the morning, the SSID box is blank and
my "Home" icon is missing too. See screen shots jpgs, if I am able to
send jpgs here otherwise tell me how rto send them please. I have the
before and after's.

Tnx all the help guys.

--
73
Bob KD7YZ
AMSAT LM #901




Re: Which Log is for the Data-Port?

KD7YZ Bob
 

On 11/13/2019 15:21, Rob Giuliano via Groups.Io wrote:
If you are using AGWpe to interface with the SignaLink, then the RF port would be of TYPE AGW.  WHat are you using to show the "AGWPE decode"? AGWMonitor, AGWTerm, or something else?
Thanks numerous helpful replies though My Thunderbird never got Lynn's
reply; go figure.

I use AGWPE the paid version thereof, Packet Engine Pro.
It allows me to define any soundcard.

I was using UISS to gather the AGW Telnet output and display same .... though I can see either Individual AGW ports I've define OR I can see the ALL PORTS tab also on Packet Engine Pro.

So I created an AGWPE/Packet-Engine-Pro port off the SignaLink Soundcard TX and RX definitions.

In APRSIS32 I see where I can define an AGW Port.

I do NOT find a way in APRSIS32 to create a port from a "Device" such as LINE#1/VAC#1 which comes out of SDR-Console.
I didn't find a way to Directly have APRIS32 look at the output of the SignaLink's Soundcard, which appears in Device Manger under Sound/vid/game as USB Audio Codec.

SO ... I have external Data on the D710GA set to Band or channel, "B:"

Turns out this appears then in the output 'Data Socket' of the D710GA..... readable by the program APRSIS32 ... butttt, sometimes there's garbage which appears to me to be some internal commands from one thing or the other.

Though in my first email u can see the decoded Sats telemetry ... and only one radio was connected to that 145.825 frequency //// CH-B

As there is no APRSIS32 "Port" defined for CH-B, there are no "View" items for me to see; and there appears no way to tell iGate to seek meaningful data from the D710GA's right-side display (145.825). And I call it CH-b

This all my be related to an ongoing issue with either the PKT or the APRS Ports I try to make, in APRSIS32.

Sometime, maybe today or maybe in the morning, the SSID box is blank and my "Home" icon is missing too. See screen shots jpgs, if I am able to send jpgs here otherwise tell me how rto send them please. I have the before and after's.

Tnx all the help guys.

--
73
Bob KD7YZ
AMSAT LM #901


Re: Which Log is for the Data-Port?

Rob Giuliano
 

Strange, I sent this message, and about 10 replies that weren't there before all showed up - with dates that should have already been in my inbox.Seems this had been answered.

Not sure if this is on Yahoo (my email) or groups.io.

Robert Giuliano
KB8RCO



On Wednesday, November 13, 2019, 3:21:41 PM EST, Rob Giuliano <kb8rco@...> wrote:


If you are using AGWpe to interface with the SignaLink, then the RF port would be of TYPE AGW.  WHat are you using to show the "AGWPE decode"?  AGWMonitor, AGWTerm, or something else?

Logging is in Menu >Enables >Logging then enable the desired options:
  Port(AGWpe) => or whatever you named it.
It should open a log window for each selected port.

Robert Giuliano
KB8RCO



On Wednesday, November 13, 2019, 8:32:59 AM EST, KD7YZ Bob <kd7yz@...> wrote:


I do not see a way in APRSIS32 to read or see or log data coming in from
the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
  3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

  3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
>ARISS - International Space Station

----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read
and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS]
KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz
T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901




Re: Which Log is for the Data-Port?

Rob Giuliano
 

If you are using AGWpe to interface with the SignaLink, then the RF port would be of TYPE AGW.  WHat are you using to show the "AGWPE decode"?  AGWMonitor, AGWTerm, or something else?

Logging is in Menu >Enables >Logging then enable the desired options:
  Port(AGWpe) => or whatever you named it.
It should open a log window for each selected port.

Robert Giuliano
KB8RCO



On Wednesday, November 13, 2019, 8:32:59 AM EST, KD7YZ Bob <kd7yz@...> wrote:


I do not see a way in APRSIS32 to read or see or log data coming in from
the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
  3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

  3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
>ARISS - International Space Station

----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read
and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS]
KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz
T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901




Re: Which Log is for the Data-Port?

Glenn OConnor <kf0ed@...>
 

-----Original Message-----
From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Greg D
Sent: Wednesday, November 13, 2019 11:21 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] Which Log is for the Data-Port?

Lynn,

FYI, there's:

- IGate
- IGate(Filter)
- Igate(NOT)
- iGateEnabled

Greg KO6TH


Lynn Deffenbaugh wrote:
Look for a Trace Log called Port(<YourPortName>) and enable it. You
should also see these in the IGate Trace Log if the correct options
are chosen on the port configuration dialog to gate the received
packets. At least I think the name is IGate! I don't have one
running at the moment having switched my IGate over to APRSISMO.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 11/13/2019 8:32 AM, KD7YZ Bob wrote:
I do not see a way in APRSIS32 to read or see or log data coming in
from the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
ARISS - International Space Station
----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read
and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS]
KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77
KG4DVE-1>Wr146.940MHz
T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901





Re: Which Log is for the Data-Port?

Greg D
 

There is a separate Port(xxxx) logging enable for every port that has been defined.  Enable the one you want, then enable the View Logs for that port, and you should see a new window open with the logging displayed in real time.

Greg  KO6TH


Randy Love wrote:

I think, tho, that he's asking if there's a log to show the packets that are being received from the port that he's defined as the Signalink port. 
Kinda like a live monitor window of incoming RF traffic.

I did that sometime back to monitor incoming traffic, but I don't recall which log it was.

Randy
WF5X


On Wed, Nov 13, 2019 at 12:21 PM Greg D <ko6th.greg@...> wrote:
Lynn,

FYI, there's:

 - IGate
 - IGate(Filter)
 - Igate(NOT)
 - iGateEnabled

Greg  KO6TH


Lynn Deffenbaugh wrote:
> Look for a Trace Log called Port(<YourPortName>) and enable it.  You
> should also see these in the IGate Trace Log if the correct options
> are chosen on the port configuration dialog to gate the received
> packets.  At least I think the name is IGate!  I don't have one
> running at the moment having switched my IGate over to APRSISMO.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 11/13/2019 8:32 AM, KD7YZ Bob wrote:
>> I do not see a way in APRSIS32 to read or see or log data coming in
>> from the SignaLink Soundcard which is plugged into the D710GA data port.
>>
>> However, AGWPE can see it as here is a recent decode:
>>
>> -------------------------------------------------------
>>  3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
>> HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA
>>
>>  3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
>> >ARISS - International Space Station
>>
>> ----------------------------------------------------------------
>>
>> I had hoped to iGate these back to wherever the Sat owners might read
>> and see their respective Birds were seen over Kentucky.
>>
>> I have Packets Log turned on. But they are all APRS-IS , typically :
>>
>> 2019-11-13T13:06:26.952 IS[APRS-IS]
>> KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz
>> T107 R25m KG4DVE/R
>>
>>
>> The AGWPE Setup is for
>>
>> Microphone (23- USB Audio CODEC )
>> Speakers (23- USB Audio CODEC )
>>
>> which IS the SignaLink plugged into the Data Port.
>>
>> I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
>> Thus I see the D710GA IS decoding stuff off the data port. Or ?.
>>
>> How would I gather those decodes and iGate them from APRSIS32?
>>
>> Thank you.
>>
>> --
>> 73
>> Bob KD7YZ
>> AMSAT LM #901
>>
>>
>>
>>
>
>
>






Re: Which Log is for the Data-Port?

Randy Love
 

I think, tho, that he's asking if there's a log to show the packets that are being received from the port that he's defined as the Signalink port. 
Kinda like a live monitor window of incoming RF traffic.

I did that sometime back to monitor incoming traffic, but I don't recall which log it was.

Randy
WF5X


On Wed, Nov 13, 2019 at 12:21 PM Greg D <ko6th.greg@...> wrote:
Lynn,

FYI, there's:

 - IGate
 - IGate(Filter)
 - Igate(NOT)
 - iGateEnabled

Greg  KO6TH


Lynn Deffenbaugh wrote:
> Look for a Trace Log called Port(<YourPortName>) and enable it.  You
> should also see these in the IGate Trace Log if the correct options
> are chosen on the port configuration dialog to gate the received
> packets.  At least I think the name is IGate!  I don't have one
> running at the moment having switched my IGate over to APRSISMO.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 11/13/2019 8:32 AM, KD7YZ Bob wrote:
>> I do not see a way in APRSIS32 to read or see or log data coming in
>> from the SignaLink Soundcard which is plugged into the D710GA data port.
>>
>> However, AGWPE can see it as here is a recent decode:
>>
>> -------------------------------------------------------
>>  3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
>> HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA
>>
>>  3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
>> >ARISS - International Space Station
>>
>> ----------------------------------------------------------------
>>
>> I had hoped to iGate these back to wherever the Sat owners might read
>> and see their respective Birds were seen over Kentucky.
>>
>> I have Packets Log turned on. But they are all APRS-IS , typically :
>>
>> 2019-11-13T13:06:26.952 IS[APRS-IS]
>> KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz
>> T107 R25m KG4DVE/R
>>
>>
>> The AGWPE Setup is for
>>
>> Microphone (23- USB Audio CODEC )
>> Speakers (23- USB Audio CODEC )
>>
>> which IS the SignaLink plugged into the Data Port.
>>
>> I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
>> Thus I see the D710GA IS decoding stuff off the data port. Or ?.
>>
>> How would I gather those decodes and iGate them from APRSIS32?
>>
>> Thank you.
>>
>> --
>> 73
>> Bob KD7YZ
>> AMSAT LM #901
>>
>>
>>
>>
>
>
>





Re: Which Log is for the Data-Port?

Greg D
 

Lynn,

FYI, there's:

- IGate
- IGate(Filter)
- Igate(NOT)
- iGateEnabled

Greg KO6TH


Lynn Deffenbaugh wrote:

Look for a Trace Log called Port(<YourPortName>) and enable it. You
should also see these in the IGate Trace Log if the correct options
are chosen on the port configuration dialog to gate the received
packets. At least I think the name is IGate! I don't have one
running at the moment having switched my IGate over to APRSISMO.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 11/13/2019 8:32 AM, KD7YZ Bob wrote:
I do not see a way in APRSIS32 to read or see or log data coming in
from the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
ARISS - International Space Station
----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read
and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS]
KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz
T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901





Re: Which Log is for the Data-Port?

Lynn Deffenbaugh
 

Look for a Trace Log called Port(<YourPortName>) and enable it.  You should also see these in the IGate Trace Log if the correct options are chosen on the port configuration dialog to gate the received packets.  At least I think the name is IGate!  I don't have one running at the moment having switched my IGate over to APRSISMO.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 11/13/2019 8:32 AM, KD7YZ Bob wrote:
I do not see a way in APRSIS32 to read or see or log data coming in from the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
 3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

 3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
ARISS - International Space Station
----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS] KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901



Which Log is for the Data-Port?

KD7YZ Bob
 

I do not see a way in APRSIS32 to read or see or log data coming in from the SignaLink Soundcard which is plugged into the D710GA data port.

However, AGWPE can see it as here is a recent decode:

-------------------------------------------------------
3:Fm BIRDMY To APTT4 Via WIDE1-1 <UI pid=F0 Len=50 >[03:15:55]
HELLO! THIS IS APRS-DIGIPEATER OF UiTMSAT-1 CUBESA

3:Fm RS0ISS To CQ <UI pid=F0 Len=36 >[06:02:54]
ARISS - International Space Station
----------------------------------------------------------------

I had hoped to iGate these back to wherever the Sat owners might read and see their respective Birds were seen over Kentucky.

I have Packets Log turned on. But they are all APRS-IS , typically :

2019-11-13T13:06:26.952 IS[APRS-IS] KG4DVE-1>APMI06,TCPIP*,qAS,KG4DVE:;146.94-TR*111111z3823.97N/08239.77Wr146.940MHz T107 R25m KG4DVE/R


The AGWPE Setup is for

Microphone (23- USB Audio CODEC )
Speakers (23- USB Audio CODEC )

which IS the SignaLink plugged into the Data Port.

I had CH-B/Band-B tuned to 145.825 and the decodes came from that.
Thus I see the D710GA IS decoding stuff off the data port. Or ?.

How would I gather those decodes and iGate them from APRSIS32?

Thank you.

--
73
Bob KD7YZ
AMSAT LM #901


Re: Download and install

Rob Giuliano
 

They have pretty good technical service (662-323-0549) and their full 12-month warranty is described on the last page of the manual.
They had a 1 year "no matter what" warranty, but it doesn't look like their products say that any more.

I will say I have had good luck with their tech support.

Robert Giuliano
KB8RCO



On Monday, November 11, 2019, 9:46:06 PM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Rob,
  I wasn't aware they had one but I'll check it out. Thanks for the head's up.

 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Monday, November 11, 2019, 08:40:02 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Don't forget the MFJ gaurantee.  I'd definitely contact them, and let them know.
I do have to say that I am very surprised as the TNC-X (MFJ-1270X) are such simple devices.  Not much to go wrong.

Robert Giuliano
KB8RCO



On Monday, November 11, 2019, 2:39:22 PM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Rob and Lynn,
  Thank you guys for your help and assistance. I've changed all cables and replaced the MFJ 1270x tnc
with an old KAM and now APRSIS32 is working like a champ. 

 73, Don
 W4GCW








On Sunday, November 10, 2019, 01:59:29 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


The MFJ-1270X only has KISS mode.  The PIC16F628P firmware is a KISS TNC only.
Encode and decode iof the audio tones are done through an old BELL202 modem chip (not firmware).
  The DCD LED is controlled by the PIC.  The MX614P chip is the "TONES" setting on most TNC detection.

When you connected to the terminal program, you used thge same "Serial cable" or the USB cable?
  Did you let the terminal program "auto baud"?  Sorry, just saw you said you set baud rate (JP1 OPEN and JP2 SHORTED).
  I assume you used the same RS232 cable, not the USB port for the terminal test.
 
Are you using external power?  Obviously you have power because the LEDs are showing (typing as I think).

Don't forget to shut down the port connection from the terminal before openeing APRSIS32.
Have you looked at the port logs when using APRSIS32 connected to the MFJ-1270X?

Unfortunately a KISS TNC is not easy to interface to directly.  You could try going through AGWpe and using AGWTermTCP and AGWMonitor to trouble shoot the TNC interface.  Available at: SV2AGW Applications and Services

About 2/3 of the way down is AGWTermTCP and AGWMoinitor.  The free AGWpe version (not pro) if you are just testing it.  I'd go to the PRO version if you want to use that as the interface in a perminant setup.

  Choose
  Select Port: COM1:
  Serial/modem BaudRate 9600
  Tnc Type: TAPR TNC2
  Tnc Sub Type KISS Simple      then delete InitKiss1, InitKiss2,and InitKiss3 commands.  Uncheck Exit Kiss On Exit
  SinglePort

To start with, you can use AGWTerm and AGWMonitor to test all the settings on the TNC (both TX and RX can be done through AGWTerm) and make sure that part is working.  Once that is working, you can change the APRSIS32 port to AGW type (localhost:8000) and leave AGWMonitor running.  If AGWMonitor has data, it should also show in APRSIS32.  With all that working, you can eliminate AGW apps all together and set APRSIS32 to the COM1: 9600.

I find them very handy for troubleshooting KISS TNCs.

Robert Giuliano
KB8RCO


On Sunday, November 10, 2019, 9:29:49 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Gurdon Wolfe
 

Rob,
  I wasn't aware they had one but I'll check it out. Thanks for the head's up.

 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Monday, November 11, 2019, 08:40:02 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Don't forget the MFJ gaurantee.  I'd definitely contact them, and let them know.
I do have to say that I am very surprised as the TNC-X (MFJ-1270X) are such simple devices.  Not much to go wrong.

Robert Giuliano
KB8RCO



On Monday, November 11, 2019, 2:39:22 PM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Rob and Lynn,
  Thank you guys for your help and assistance. I've changed all cables and replaced the MFJ 1270x tnc
with an old KAM and now APRSIS32 is working like a champ. 

 73, Don
 W4GCW








On Sunday, November 10, 2019, 01:59:29 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


The MFJ-1270X only has KISS mode.  The PIC16F628P firmware is a KISS TNC only.
Encode and decode iof the audio tones are done through an old BELL202 modem chip (not firmware).
  The DCD LED is controlled by the PIC.  The MX614P chip is the "TONES" setting on most TNC detection.

When you connected to the terminal program, you used thge same "Serial cable" or the USB cable?
  Did you let the terminal program "auto baud"?  Sorry, just saw you said you set baud rate (JP1 OPEN and JP2 SHORTED).
  I assume you used the same RS232 cable, not the USB port for the terminal test.
 
Are you using external power?  Obviously you have power because the LEDs are showing (typing as I think).

Don't forget to shut down the port connection from the terminal before openeing APRSIS32.
Have you looked at the port logs when using APRSIS32 connected to the MFJ-1270X?

Unfortunately a KISS TNC is not easy to interface to directly.  You could try going through AGWpe and using AGWTermTCP and AGWMonitor to trouble shoot the TNC interface.  Available at: SV2AGW Applications and Services

About 2/3 of the way down is AGWTermTCP and AGWMoinitor.  The free AGWpe version (not pro) if you are just testing it.  I'd go to the PRO version if you want to use that as the interface in a perminant setup.

  Choose
  Select Port: COM1:
  Serial/modem BaudRate 9600
  Tnc Type: TAPR TNC2
  Tnc Sub Type KISS Simple      then delete InitKiss1, InitKiss2,and InitKiss3 commands.  Uncheck Exit Kiss On Exit
  SinglePort

To start with, you can use AGWTerm and AGWMonitor to test all the settings on the TNC (both TX and RX can be done through AGWTerm) and make sure that part is working.  Once that is working, you can change the APRSIS32 port to AGW type (localhost:8000) and leave AGWMonitor running.  If AGWMonitor has data, it should also show in APRSIS32.  With all that working, you can eliminate AGW apps all together and set APRSIS32 to the COM1: 9600.

I find them very handy for troubleshooting KISS TNCs.

Robert Giuliano
KB8RCO


On Sunday, November 10, 2019, 9:29:49 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Rob Giuliano
 

Don't forget the MFJ gaurantee.  I'd definitely contact them, and let them know.
I do have to say that I am very surprised as the TNC-X (MFJ-1270X) are such simple devices.  Not much to go wrong.

Robert Giuliano
KB8RCO



On Monday, November 11, 2019, 2:39:22 PM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Rob and Lynn,
  Thank you guys for your help and assistance. I've changed all cables and replaced the MFJ 1270x tnc
with an old KAM and now APRSIS32 is working like a champ. 

 73, Don
 W4GCW








On Sunday, November 10, 2019, 01:59:29 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


The MFJ-1270X only has KISS mode.  The PIC16F628P firmware is a KISS TNC only.
Encode and decode iof the audio tones are done through an old BELL202 modem chip (not firmware).
  The DCD LED is controlled by the PIC.  The MX614P chip is the "TONES" setting on most TNC detection.

When you connected to the terminal program, you used thge same "Serial cable" or the USB cable?
  Did you let the terminal program "auto baud"?  Sorry, just saw you said you set baud rate (JP1 OPEN and JP2 SHORTED).
  I assume you used the same RS232 cable, not the USB port for the terminal test.
 
Are you using external power?  Obviously you have power because the LEDs are showing (typing as I think).

Don't forget to shut down the port connection from the terminal before openeing APRSIS32.
Have you looked at the port logs when using APRSIS32 connected to the MFJ-1270X?

Unfortunately a KISS TNC is not easy to interface to directly.  You could try going through AGWpe and using AGWTermTCP and AGWMonitor to trouble shoot the TNC interface.  Available at: SV2AGW Applications and Services

About 2/3 of the way down is AGWTermTCP and AGWMoinitor.  The free AGWpe version (not pro) if you are just testing it.  I'd go to the PRO version if you want to use that as the interface in a perminant setup.

  Choose
  Select Port: COM1:
  Serial/modem BaudRate 9600
  Tnc Type: TAPR TNC2
  Tnc Sub Type KISS Simple      then delete InitKiss1, InitKiss2,and InitKiss3 commands.  Uncheck Exit Kiss On Exit
  SinglePort

To start with, you can use AGWTerm and AGWMonitor to test all the settings on the TNC (both TX and RX can be done through AGWTerm) and make sure that part is working.  Once that is working, you can change the APRSIS32 port to AGW type (localhost:8000) and leave AGWMonitor running.  If AGWMonitor has data, it should also show in APRSIS32.  With all that working, you can eliminate AGW apps all together and set APRSIS32 to the COM1: 9600.

I find them very handy for troubleshooting KISS TNCs.

Robert Giuliano
KB8RCO


On Sunday, November 10, 2019, 9:29:49 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Gurdon Wolfe
 

Rob and Lynn,
  Thank you guys for your help and assistance. I've changed all cables and replaced the MFJ 1270x tnc
with an old KAM and now APRSIS32 is working like a champ. 

 73, Don
 W4GCW








On Sunday, November 10, 2019, 01:59:29 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


The MFJ-1270X only has KISS mode.  The PIC16F628P firmware is a KISS TNC only.
Encode and decode iof the audio tones are done through an old BELL202 modem chip (not firmware).
  The DCD LED is controlled by the PIC.  The MX614P chip is the "TONES" setting on most TNC detection.

When you connected to the terminal program, you used thge same "Serial cable" or the USB cable?
  Did you let the terminal program "auto baud"?  Sorry, just saw you said you set baud rate (JP1 OPEN and JP2 SHORTED).
  I assume you used the same RS232 cable, not the USB port for the terminal test.
 
Are you using external power?  Obviously you have power because the LEDs are showing (typing as I think).

Don't forget to shut down the port connection from the terminal before openeing APRSIS32.
Have you looked at the port logs when using APRSIS32 connected to the MFJ-1270X?

Unfortunately a KISS TNC is not easy to interface to directly.  You could try going through AGWpe and using AGWTermTCP and AGWMonitor to trouble shoot the TNC interface.  Available at: SV2AGW Applications and Services

About 2/3 of the way down is AGWTermTCP and AGWMoinitor.  The free AGWpe version (not pro) if you are just testing it.  I'd go to the PRO version if you want to use that as the interface in a perminant setup.

  Choose
  Select Port: COM1:
  Serial/modem BaudRate 9600
  Tnc Type: TAPR TNC2
  Tnc Sub Type KISS Simple      then delete InitKiss1, InitKiss2,and InitKiss3 commands.  Uncheck Exit Kiss On Exit
  SinglePort

To start with, you can use AGWTerm and AGWMonitor to test all the settings on the TNC (both TX and RX can be done through AGWTerm) and make sure that part is working.  Once that is working, you can change the APRSIS32 port to AGW type (localhost:8000) and leave AGWMonitor running.  If AGWMonitor has data, it should also show in APRSIS32.  With all that working, you can eliminate AGW apps all together and set APRSIS32 to the COM1: 9600.

I find them very handy for troubleshooting KISS TNCs.

Robert Giuliano
KB8RCO


On Sunday, November 10, 2019, 9:29:49 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Rob Giuliano
 

The MFJ-1270X only has KISS mode.  The PIC16F628P firmware is a KISS TNC only.
Encode and decode iof the audio tones are done through an old BELL202 modem chip (not firmware).
  The DCD LED is controlled by the PIC.  The MX614P chip is the "TONES" setting on most TNC detection.

When you connected to the terminal program, you used thge same "Serial cable" or the USB cable?
  Did you let the terminal program "auto baud"?  Sorry, just saw you said you set baud rate (JP1 OPEN and JP2 SHORTED).
  I assume you used the same RS232 cable, not the USB port for the terminal test.
 
Are you using external power?  Obviously you have power because the LEDs are showing (typing as I think).

Don't forget to shut down the port connection from the terminal before openeing APRSIS32.
Have you looked at the port logs when using APRSIS32 connected to the MFJ-1270X?

Unfortunately a KISS TNC is not easy to interface to directly.  You could try going through AGWpe and using AGWTermTCP and AGWMonitor to trouble shoot the TNC interface.  Available at: SV2AGW Applications and Services

About 2/3 of the way down is AGWTermTCP and AGWMoinitor.  The free AGWpe version (not pro) if you are just testing it.  I'd go to the PRO version if you want to use that as the interface in a perminant setup.

  Choose
  Select Port: COM1:
  Serial/modem BaudRate 9600
  Tnc Type: TAPR TNC2
  Tnc Sub Type KISS Simple      then delete InitKiss1, InitKiss2,and InitKiss3 commands.  Uncheck Exit Kiss On Exit
  SinglePort

To start with, you can use AGWTerm and AGWMonitor to test all the settings on the TNC (both TX and RX can be done through AGWTerm) and make sure that part is working.  Once that is working, you can change the APRSIS32 port to AGW type (localhost:8000) and leave AGWMonitor running.  If AGWMonitor has data, it should also show in APRSIS32.  With all that working, you can eliminate AGW apps all together and set APRSIS32 to the COM1: 9600.

I find them very handy for troubleshooting KISS TNCs.

Robert Giuliano
KB8RCO


On Sunday, November 10, 2019, 9:29:49 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Gurdon Wolfe
 

Hi Rob, I appreciate your reply. Equipment here is an MFJ-1270X powered via serial cable and a Yaesu FT2600.
I'm able to see received packets via the yellow light on the tnc and the signal bar on the radio as well as hearing
the signal. However nothing appears on the screen. When I hit transmit, nothing happens, no red light on the tnc
or the radio. The tnc is set to com1 9600, n,8,1, as well as the settings in APRSIS32. All cables are commercially
made. On Lynn's advice, I connected the tnc to a terminal program and verified by looking at the received text 
that the tnc was in kiss mode. 




 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







On Saturday, November 9, 2019, 08:11:54 PM EST, Rob Giuliano via Groups.Io <kb8rco@...> wrote:


Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don











Re: Download and install

Rob Giuliano
 

Is the TNC in question the MFJ-1270X?
You state MFJ-1279X in another email and I couldn't find that.

You don't state if there are any LEDS on, but I will assume you are powering the TNC-X (MFJ-1270X) through the USB port.
  Green LED ON?
  Does the RED TX LED come on when you start up APRSIS32? (Usually starts by sending a packet over RF)?
  Hop about the receive/DCD LED?

Is the radio an HT or mobile style and are you using a homemade or MFJ cobale between them?

The MFJ-1270X is the same as the TNC-X and is only capable of KISS mode, so the APRSIS32 port should be Simply(KISS).
This is such a simply device that there are only a few settings to be concerned with:
   Baud rate - set with jumpers inside the case.  Must match APRSIS32 port settings.
                      I recommend "all off" for 19200 baud.  Default is both opn at 1200 baud - same as on air
  USB - JP4 to power  NC through USB (pins 2 & 3), JP3 to use USB data lines (not DB9 on back of TNC)

JP5 connects the data pins to the internbal parts or a daughter board (X-version has no daughter board, so these should be on 1,2 (together) and 3,4 (together) shorted with jumpers.

John Hanson at TNC-X is a great source, even if you bought it through MFJ.  It is his designed.
I have several and have not had any issues.  My home station runs one, and I have a very old version before he designed any case.
Knowing the status of the LEDs when receiving and transmitting can be of great help.

Robert Giuliano
KB8RCO


On Saturday, November 9, 2019, 11:51:41 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Lynn,
  It's looking like the problem is with the tnc. I downloaded Pin Point APRS software and
had the same results, no tx or rx with either program. I'm going to take the tnc out of kiss 
and see it it works in terminal mode. Then I'll put it back into kiss and see if it works.

 73, Don
 W4GCW


On Saturday, November 9, 2019, 07:19:04 AM EST, Gurdon Wolfe via Groups.Io <w4gcw@...> wrote:


Good morning Lynn,
  I've verified that the tnc is in KISS mode. What's next?
Thanks.
73, Don