Date   
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










Re: Download and install

Gurdon Wolfe
 

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
 

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








On Thursday, November 7, 2019, 08:49:04 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


Is the TNC locked into KISS mode?  And did you use a Simply(KISS) type port in the configuration?

The other thing to try is closing APRSIS32 and open the COM port to the TNC in a simple terminal emulator.  Wait until a packet has likely been decoded and you should see something in the terminal emulator.  If not, the issue is between the TNC and the Radio or the wrong COM port.  If you see non-printable followed by a printable payload, then you're seeing a KISS packet.  If the entire packet is readable, it's not in KISS mode.

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

On 11/7/2019 5:56 PM, Gurdon Wolfe via Groups.Io wrote:
Lynn,
 The tnc is an MFJ1279X and yes, it's configured in APRSIS32. Received nothing.

 73, Don
 W4GCW






On Thursday, November 7, 2019, 05:35:48 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


What TNC is it?  How do you have it configured in APRSIS32?  What port type did you use?  So many questions that need answers!

Are you seeing any packets from the radio which would be shown in the packet scroller with an *?

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

On 11/7/2019 4:45 PM, Gurdon Wolfe via Groups.Io wrote:
HI Lynn and thanks for taking the time to reply to my call for help.I found and deleted the xml file and was able
to download APRSIS32 with only one problem. The radio/tnc won't transmit. I've run through the help file that
outlines what to do if the program won't transmit and so far that's what got me stumped. The radio/tnc works
as it connects to K4EOC-7 on SEDAN. Your thoughts?

 73, Don
 W4GCW






On Thursday, November 7, 2019, 01:13:17 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: Download and install

Lynn Deffenbaugh
 

Is the TNC locked into KISS mode?  And did you use a Simply(KISS) type port in the configuration?

The other thing to try is closing APRSIS32 and open the COM port to the TNC in a simple terminal emulator.  Wait until a packet has likely been decoded and you should see something in the terminal emulator.  If not, the issue is between the TNC and the Radio or the wrong COM port.  If you see non-printable followed by a printable payload, then you're seeing a KISS packet.  If the entire packet is readable, it's not in KISS mode.

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

On 11/7/2019 5:56 PM, Gurdon Wolfe via Groups.Io wrote:
Lynn,
 The tnc is an MFJ1279X and yes, it's configured in APRSIS32. Received nothing.

 73, Don
 W4GCW






On Thursday, November 7, 2019, 05:35:48 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


What TNC is it?  How do you have it configured in APRSIS32?  What port type did you use?  So many questions that need answers!

Are you seeing any packets from the radio which would be shown in the packet scroller with an *?

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

On 11/7/2019 4:45 PM, Gurdon Wolfe via Groups.Io wrote:
HI Lynn and thanks for taking the time to reply to my call for help.I found and deleted the xml file and was able
to download APRSIS32 with only one problem. The radio/tnc won't transmit. I've run through the help file that
outlines what to do if the program won't transmit and so far that's what got me stumped. The radio/tnc works
as it connects to K4EOC-7 on SEDAN. Your thoughts?

 73, Don
 W4GCW






On Thursday, November 7, 2019, 01:13:17 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: Download and install

Gurdon Wolfe
 

Lynn,
 The tnc is an MFJ1279X and yes, it's configured in APRSIS32. Received nothing.

 73, Don
 W4GCW


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







On Thursday, November 7, 2019, 05:35:48 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


What TNC is it?  How do you have it configured in APRSIS32?  What port type did you use?  So many questions that need answers!

Are you seeing any packets from the radio which would be shown in the packet scroller with an *?

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

On 11/7/2019 4:45 PM, Gurdon Wolfe via Groups.Io wrote:
HI Lynn and thanks for taking the time to reply to my call for help.I found and deleted the xml file and was able
to download APRSIS32 with only one problem. The radio/tnc won't transmit. I've run through the help file that
outlines what to do if the program won't transmit and so far that's what got me stumped. The radio/tnc works
as it connects to K4EOC-7 on SEDAN. Your thoughts?

 73, Don
 W4GCW






On Thursday, November 7, 2019, 01:13:17 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: Download and install

Lynn Deffenbaugh
 

What TNC is it?  How do you have it configured in APRSIS32?  What port type did you use?  So many questions that need answers!

Are you seeing any packets from the radio which would be shown in the packet scroller with an *?

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

On 11/7/2019 4:45 PM, Gurdon Wolfe via Groups.Io wrote:
HI Lynn and thanks for taking the time to reply to my call for help.I found and deleted the xml file and was able
to download APRSIS32 with only one problem. The radio/tnc won't transmit. I've run through the help file that
outlines what to do if the program won't transmit and so far that's what got me stumped. The radio/tnc works
as it connects to K4EOC-7 on SEDAN. Your thoughts?

 73, Don
 W4GCW






On Thursday, November 7, 2019, 01:13:17 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: Download and install

Gurdon Wolfe
 

HI Lynn and thanks for taking the time to reply to my call for help.I found and deleted the xml file and was able
to download APRSIS32 with only one problem. The radio/tnc won't transmit. I've run through the help file that
outlines what to do if the program won't transmit and so far that's what got me stumped. The radio/tnc works
as it connects to K4EOC-7 on SEDAN. Your thoughts?

 73, Don
 W4GCW


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







On Thursday, November 7, 2019, 01:13:17 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

Lynn Deffenbaugh
 

The "OK" message simply means that the port has been opened and the connection configuration is valid.  It does not reflect "proper" operation of the protocols over the port because "proper" does not have a definitive meaning.

APRSISCE/32 does not support digipeating over a KWD710(APRS) protocol port because this port type is a kludge and hack and is not directly supported by Kenwood.  What APRSIS32 actually does is yank the radio out of APRS mode any time it needs to transmit something and then puts it back into APRS mode when the transmission is complete.  During these mode switches, packets can be lost.  As you can imagine, the frequency with with a digipeater transmits would not be good.

Also, because Kenwood didn't envision this use of APRS mode in their firmware, the radio can (and does) get confused about what MYCALL is while operating in this mode.  Sometimes it is the callsign-SSID configured into the radio, but after APRSISCE/32 transmits, the radio will adopt the callsign-SSID of APRSIS32 until the next time the TNC is reset.

KWD710(APRS) mode is nice when you want to use the 710's internal APRS capabilities and still pass packets on to APRSIS32 for mapping and better display.  But it really isn't good for APRSIS32 to do much transmitting IMHO.

But, given that APRSIS32 is trying to digipeat, at least we know that packets are coming in from the radio now!

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

On 11/7/2019 3:26 PM, KD7YZ Bob wrote:
I have the D710 APRS port config box set with every box checked (on) except No-Gate-ME is unchecked.

Something I do notice, and keep seeing from port to port, is that when I just checked that D710 APRS port, the SSID name is missing (KD7YZ-15) and the comment line is now also blank/greyed-out.

yet the status at the top of the scroll column rotates through KWD710(APRS) OK


so is it or isn't it?

-------------------------------------------------------------------
WinMain:2019-11-07T19:40:19.771 Restore Saved ALWAYS Enable
WinMain:2019-11-07T20:00:35.436 Digipeating N4TNA-9 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2019-11-07T20:00:35.436 Original(N4TNA-9>SX2Y0P,WIDE1-1,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 Transmit(N4TNA-9>SX2Y0P,KD7YZ-15*,WIDE1*,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
----------------------------------------------------------------------------


Not sure where to look for this as UIDIG is "ON".

--
73
Bob KD7YZ
AMSAT LM #901


KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

KD7YZ Bob
 

I have the D710 APRS port config box set with every box checked (on) except No-Gate-ME is unchecked.

Something I do notice, and keep seeing from port to port, is that when I just checked that D710 APRS port, the SSID name is missing (KD7YZ-15) and the comment line is now also blank/greyed-out.

yet the status at the top of the scroll column rotates through KWD710(APRS) OK


so is it or isn't it?

-------------------------------------------------------------------
WinMain:2019-11-07T19:40:19.771 Restore Saved ALWAYS Enable
WinMain:2019-11-07T20:00:35.436 Digipeating N4TNA-9 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2019-11-07T20:00:35.436 Original(N4TNA-9>SX2Y0P,WIDE1-1,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 Transmit(N4TNA-9>SX2Y0P,KD7YZ-15*,WIDE1*,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
----------------------------------------------------------------------------

Not sure where to look for this as UIDIG is "ON".

--
73
Bob KD7YZ
AMSAT LM #901

Re: Trying to understand the Log from "Port(KWD710(Pkt)"-- Solved

KD7YZ Bob
 

I discovered that the setup did not like me using VSPE Virtual Serial Port Emulator. I'd made COM4:, the D710GA Port virtual to COM12: (for sundry reasons.


now I see a brief listing which ended quite a while ao)

WinMain:2019-11-07T19:40:20.070 Starting Port(KWD710(APRS))
Port(KWD710(APRS)):2019-11-07T19:40:20.070 CpReader Running on COM4:9600,N,8,1 (31 OpenCmds, 6 CloseCmds)
Port(KWD710(APRS)):2019-11-07T19:40:20.070 Opening COM4:9600,N,8,1
Port(KWD710(APRS)):2019-11-07T19:40:20.071 Opening COM4 with 4 Args
Port(KWD710(APRS)):2019-11-07T19:40:20.075 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 31 OpenCmds

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


now I see the next problem which I shall open in another thread.

Bob KD7YZ

Re: Download and install

Lynn Deffenbaugh
 

You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW





Re: Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob
 

So I just deleted most "Ports" ... leaving the ore-configured NMEA and APRs-IS

I made a new port from the Drop-Down ...

Port(KWD710(APRS)

checked ALL the boxes just in case I might leave one un-checked that was supposed to be "ON".

APRSIS32 (min) has beaconing ON, fwiw

Enable Ports "ALL", Log All
RX... -- unchecked

and here is what I see, again


------------------------------------------------------
Port(KWD710(APRS)):2019-11-07T12:20:23.456 Missed Expected Response(cmd:) From Command(^M~!cmd:!1)
WinMain:2019-11-07T12:23:11.155 Stopping Port(KWD710(APRS))
WinMain:2019-11-07T12:23:11.155 Waiting at line 742
WinMain:2019-11-07T12:23:11.256 Waiting at line 742
WinMain:2019-11-07T12:23:11.357 Waiting at line 742
Port(KWD710(APRS)):2019-11-07T12:23:11.426 Terminating after 331330 msec vs 0 Quiet
Port(KWD710(APRS)):2019-11-07T12:23:11.426 Closing COM12:9600,N,8,1
WinMain:2019-11-07T12:23:11.457 Waiting at line 2877
---------------------------------------------------------

I need some serious assistance here.


Bob KD7YZ with a month old TM D710GA and APRSIS32 which are way smarter than me.

Re: Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob
 

Well, I spoke too soon.
With cable in the COM port on the D710 Display, lookie what I see, again:

-------------------------------------------------------------------
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Terminating after 240279 msec vs 240000 Quiet
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Closing COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Command[2]:^M
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Output[2]:<0D 0D>
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Missed Expected Response(cmd:) From Command(^M!cmd:!1)
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Command[5]:LTM 0
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Output[6]:LTM 0<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Missed Expected Response(cmd:) From Command(LTM 0)
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Command[4]:TC 1
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Output[5]:TC 1<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Missed Expected Response(TS 1) From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Command[6]:TN 0,0
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Output[7]:TN 0,0<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Missed Expected Response(TN 0,0) From Command(TN 0,0!TN 0,0)
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Restarting Reader...
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 CpReader Running on COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Packet Length 64 Version 2
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:ServiceMask 0x1 Reserved1 0x0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:MaxQueue Tx 0 Rx 0 Baud 268435456
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Provider SubType 1 Capabilities 0xFF
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Settable Params 127 Baud 0x10000FFF Data 0xF StopParity 0x1F07
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Current Queue Tx 0 Rx 0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Provider Specifics 0x0 0x0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 CpOpen:Port COM12 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(0) !InXoff(0) DTR_ENABLE !DSRSense RTS_ENABLE
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opened COM12:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Command[7]:^C^C^C~
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Output[3]:<03 03 03>
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Command[4]:TC 1
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Output[5]:TC 1<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:06.389 CmdResp[12]:?<0D>?<0D>?<0D>?<0D>?<0D>?<0D>
---------------------------------------------------------------------------

Bob KD7YZ

Re: Trying to understand the Log from "Port(KWD710(Pkt)"

Randy Love
 

Yeah, those RT systems cables are pretty solid... 
They used the FTDI chip set, so they aren't nearly as flakey as cheaper USB dongles.
I had a Keyspan once... key word being HAD... it was never reliable for me, so I give it to someone that swore by them.. 
I'm sure he swore AT that one tho...

73,
Randy
WF5X


On Wed, Nov 6, 2019 at 6:06 PM KD7YZ Bob <kd7yz@...> wrote:
On 11/6/2019 11:19, Randy Love wrote:
> Just a quick check, the cable is into the back of the control head, correct?
>
> Randy
> WF5X

Crikey!
So today I used the programing from RT Systems ... THEN never unplugged
from the back to put it back on the Control display box.

Thanks. And before I ask the next in a line of "How do I do this"
questions, I will pull the list and see if they exist when the cables go
to the right places.

I am using the USB-K5G Radio Cable that came with theTM-D710G Programmer.

Previously I was using a Keyspan which converted the Rig's RS232 to USB
...HOWEVER, I had a lot of trouble with the Keyspan "going missing" on
my Dell ....I tried activating (did) the COM1: and jut plugging in the
serial cable as designed ....Dev Man showed COM1: at 9600b but the
computer never saw the rig on COM1 ..... thus I decided to use the RT
systems' already programmed cable.

But it would help if I plugged it back onto the "COM" socket instead of
leaving it on "PC" .

thanks for the help.

--
73
Bob KD7YZ
AMSAT LM #901