Topics

APRSIS23 HF APRS & PTC-IIex


John Brent - VA7WPN
 

Good afternoon,

I am putting together an HF APRS station, or attempting to anyways. I am using a TS-2000 and SCS PTC-IIex as hardware. I am using APRSIS32 to control it all. But I am finding it not so easy to get it to work with my equipment. I will explain below.

A) When I set the baud rate to 300 baud, it saves but when I reopen the port configuration it is set to 1200 again. I can confirm this is the same in the XML file, even if I edit the XML to be 300 baud it will revert to 1200 again.
B) Editing the XML file, when I edit it as per instructions on the instructions on the Robust Packet website for HF APRS and APRSIS32... the PTC-IIex restarts, the LED's go off, and is non responsive. How ever if I dont edit anything, it sends packets... but not at 300 baud. APRSIS32 was off when I edited the XML file. 

Any ideas what is going on?

thanks a ton. 

PS : I have read other posts before I posted this one.


Lynn Deffenbaugh
 

Answers interspersed below...


On 1/22/2020 3:24 PM, John Brent - VA7WPN wrote:
I am putting together an HF APRS station, or attempting to anyways. I am using a TS-2000 and SCS PTC-IIex as hardware. I am using APRSIS32 to control it all. But I am finding it not so easy to get it to work with my equipment. I will explain below.

A) When I set the baud rate to 300 baud, it saves but when I reopen the port configuration it is set to 1200 again. I can confirm this is the same in the XML file, even if I edit the XML to be 300 baud it will revert to 1200 again.
The port setting for baud rate is a red herring.  It is not used.  The RF baud rate is completely under the control of the TNC, not APRSIS32.  This dates back to my start when I really didn't understand how it all worked.

B) Editing the XML file, when I edit it as per instructions on the instructions on the Robust Packet website for HF APRS and APRSIS32... the PTC-IIex restarts, the LED's go off, and is non responsive. How ever if I dont edit anything, it sends packets... but not at 300 baud. APRSIS32 was off when I edited the XML file.
Can you provide a link to the instructions you are following? And what port type you are specifying in APRSIS32?  I'm not familiar with the PTC-IIex, but maybe someone else is.


Any ideas what is going on?
Yeah, it's not working!  (Couldn't resist...)

thanks a ton.

PS : I have read other posts before I posted this one.

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


John Brent - VA7WPN
 

Here are the instructions I have been following :

https://robust-packet.net/Robust-Packet-Network-Manual.pdf

Specificaly : 


John Brent - VA7WPN
 

I have done the capacitor mod, with no change. 

SCS has given me instructions to do a memory dump / check in the sys mode to try and clear the flash memory.

more to follow.


Wolfgang Bieber
 

Hello John,

I do have a quite similar difficulty with SCS card modem "TRXPTC". My observation is, that the modem is waiting for a reply to several OPEN commands and then disconnecting. I checked the Log for the relevant port and found this:

Port(5.354):2020-02-07T11:57:50.354 Missed Expected Response(cmd:) From Command(QUIT!cmd:)
Port(5.354):2020-02-07T11:57:50.354 Terminating after 60496 msec vs 60000 Quiet

Maybe you check your log as well? Is it the same/similar message showing.

73,s Wolfgang OH6DL


Rob Giuliano
 

I am not familiar with the SCS TRXPTC.  Everything comes up Pactor.

However, my first question would be:
1. Is the modem capable of going into KISS mode?
   APRSIS32 expect the data coming in to be KISS

2. Second.  Is the modem capable of staying in KISS mode over power cycles?

3. Last, and most important, is the modem already in KISS mode?

A quick check would be to disable that port and create a new port on the same interface, except as Simply(KISS).
  This will send no commands and just start listening.

Also, you can set the Quiet to zero for testing.  If no data is received in the time set in QUIET, APRSIS32 will try and reset the modem.
If the radio frequency is not very active, ...

Robert Giuliano
KB8RCO



On Friday, February 7, 2020, 7:35:36 AM EST, Wolfgang Bieber <oh6dl@...> wrote:


Hello John,

I do have a quite similar difficulty with SCS card modem "TRXPTC". My observation is, that the modem is waiting for a reply to several OPEN commands and then disconnecting. I checked the Log for the relevant port and found this:

Port(5.354):2020-02-07T11:57:50.354 Missed Expected Response(cmd:) From Command(QUIT!cmd:)
Port(5.354):2020-02-07T11:57:50.354 Terminating after 60496 msec vs 60000 Quiet

Maybe you check your log as well? Is it the same/similar message showing.

73,s Wolfgang OH6DL


Wolfgang Bieber
 

Hello Robert,

thanks for your comments. The answer to all questions is YES, the test with Simply Kiss was done with same result. However, I have been connecting today the modem using APRSDROID via Bluetooth to work in RPR as a tracker. So I assume the recommended XML file for use with APRSIS32 is not compatible.

73´s, Wolfgang - OH6DL


Rob Giuliano
 

I remember seeing something about waiting for cmd: and that it times out.
Can you post your open and close commands from the XML?
  The original ones you used that expected the cmd:, not the Simply(KISS) ones.
  I assume that is the response from the unit when in command mode?
  Couldn't find that in the manual, and I don't have one to check.
  If not, what do you see in HyperTerminal (or TeraTerm, etc.) when connected and you power up the unit and it is waiting for input?

From what i can find, I think something like this might work:
<OpenCmd>^013!cmd:!2</OpenCmd>
<OpenCmd>@K^013!cmd:!2</OpenCmd>
<CloseCmd>^192^255^192^013!cmd:!2</CloseCmd>

I release this will actually give 2 <Enter> commands (^013 and the one already provided), but I sometimes find this enusre the cmd: reply comes up.
That and setting QuietTime to 0 (at least for a day) and see if that provides any success.

The cmd: must match the response fromt he unit when waiting for input.

Robert Giuliano
KB8RCO



On Saturday, February 8, 2020, 12:12:55 PM EST, Wolfgang Bieber <oh6dl@...> wrote:


Hello Robert,

thanks for your comments. The answer to all questions is YES, the test with Simply Kiss was done with same result. However, I have been connecting today the modem using APRSDROID via Bluetooth to work in RPR as a tracker. So I assume the recommended XML file for use with APRSIS32 is not compatible.

73´s, Wolfgang - OH6DL


Wolfgang Bieber
 

Hello Rob,

solution found - when creating a new port in APRSIS32, instead of taking the Bluetooth connection (originally I used this one, because the modem connects via Bluetooth only), I took COM-Port connection using settings of the PC serial to Bluetooth connection. Now the modem is running without problem in RPR mode controlled by APRSIS,

Thanks for your efforts!

73´s, Wolfgang - OH6DL


Rob Giuliano
 

Thanks for sharing!

Yes, Windows seems to like the COMM port connection created by BlueTooth better than using the BlueTooth wizard and settings.

Robert Giuliano
KB8RCO



On Sunday, February 9, 2020, 5:49:40 AM EST, Wolfgang Bieber <oh6dl@...> wrote:


Hello Rob,

solution found - when creating a new port in APRSIS32, instead of taking the Bluetooth connection (originally I used this one, because the modem connects via Bluetooth only), I took COM-Port connection using settings of the PC serial to Bluetooth connection. Now the modem is running without problem in RPR mode controlled by APRSIS,

Thanks for your efforts!

73´s, Wolfgang - OH6DL


John Brent - VA7WPN
 

This is the output from the trace(port(10.147.30))

WinMain:2020-02-14T02:44:41.877 Starting Port(10.1473)
Port(10.1473):2020-02-14T02:44:41.877 CpReader Running on COM2:9600,N,8,1 (11 OpenCmds, 3 CloseCmds)
Port(10.1473):2020-02-14T02:44:41.877 Opening COM2:9600,N,8,1
Port(10.1473):2020-02-14T02:44:41.877 Opening COM2 with 4 Args
Port(10.1473):2020-02-14T02:44:41.878 Opened COM2:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 11 OpenCmds
Port(10.1473):2020-02-14T02:44:45.534 Missed Expected Response(pac1:) From Command(PAC!pac1:)
Port(10.1473):2020-02-14T02:44:47.535 Missed Expected Response(pac1:) From Command(USER 0!pac1:)
Port(10.1473):2020-02-14T02:44:49.536 Missed Expected Response(pac1:) From Command(PRBOX 0!pac1:)
Port(10.1473):2020-02-14T02:44:51.537 Missed Expected Response(pac1:) From Command(BAUD R300!pac1:)

I belive it is looking for a pac1: responce but the PTC gives a pac:. A number of people have told me that the pac1: is correct. but I am doubting that.

thank you again,

John Brent


Lynn Deffenbaugh
 

If you use a terminal emulator, what is the prompt after entering each command manually?  That's what should follow the ! in your <Open/CloseCmd>s.  Test it on your TNC and you'll know what is correct regardless of what other people with other hardware and/or firmware might be telling you.

But those messages are not fatal, they only slow down the opening as it has to wait for the default 1 second timeout before going on.

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

On 2/13/2020 9:55 PM, John Brent - VA7WPN wrote:
This is the output from the trace(port(10.147.30))

WinMain:2020-02-14T02:44:41.877 Starting Port(10.1473)
Port(10.1473):2020-02-14T02:44:41.877 CpReader Running on COM2:9600,N,8,1 (11 OpenCmds, 3 CloseCmds)
Port(10.1473):2020-02-14T02:44:41.877 Opening COM2:9600,N,8,1
Port(10.1473):2020-02-14T02:44:41.877 Opening COM2 with 4 Args
Port(10.1473):2020-02-14T02:44:41.878 Opened COM2:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 11 OpenCmds
Port(10.1473):2020-02-14T02:44:45.534 Missed Expected Response(pac1:) From Command(PAC!pac1:)
Port(10.1473):2020-02-14T02:44:47.535 Missed Expected Response(pac1:) From Command(USER 0!pac1:)
Port(10.1473):2020-02-14T02:44:49.536 Missed Expected Response(pac1:) From Command(PRBOX 0!pac1:)
Port(10.1473):2020-02-14T02:44:51.537 Missed Expected Response(pac1:) From Command(BAUD R300!pac1:)

I belive it is looking for a pac1: responce but the PTC gives a pac:. A number of people have told me that the pac1: is correct. but I am doubting that.

thank you again,

John Brent


John Brent - VA7WPN
 

I used that script, I had to change the pac1: to pac: as my PTC-IIex output is pac:, otherwise I was getting errors.

But..

Once the command "pac baud r300" is issued, when the next command "pac" or "kiss" is sent, it resets the TNC. 

But.. when I check the baud rate using "pac b" it tells me that its in R300 (Robust Packet) mode. It won't start kiss via "K", "Kiss" or "@K", or enter the packet menu without rebooting. The only way I can correct this is by using the command "pac b 1200" or any other baud rate to get out of robust packet mode.

John Brent
 VA7WPN