[Xastir] Xastir on raspberrypi to SCS PTCIIpro for Robustpacket Radio - SOLVED

Tue Jun 20 05:48:50 PDT 2017

I got the solution to the problem of interfacing Xastir to the SCS PTCIIpro 
modem.
I was unable to use the standard serial TNC interface and a proper startup 
file.
So I selected the serial KISS TNC interface recompiling Xastir by modifying 
the init_kiss_string in the C file interface.c.
The two modifications were
char init_kiss_string[94];
sizeof(init_kiss_string),
                           "\x1BQ\rRESET\rTONES 4\rBRIGHT 6\rFSKA 145\rPSKA 
175\rPAC TXL ASFK 800\rPAC\rUSER 0\rPRBOX 0\rBAUD R300\r at k\r");    // [ESC at K 
sets tnc from terminal- into kissmode
Now the Xastir programmers will suggest me how to clean up the solution, to 
make it general and store it in the repository
Giuseppe
IZ1GCL

-----Messaggio originale----- 
From: Menga
Sent: Friday, June 16, 2017 1:20 AM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] Xastir on raspberrypi to SCS PTCIIpro for Robustpacket 
Radio

Curt,
I followed your suggestion to create a startup file for the SCS PTCIIpro.
In order to put on play the startup and end files I had to change the
interface from serial KISS TNC to serial TNC.
I went on windows were the APRSIS32 is running and using a hyperterminal I
recorder the strings sent from the computer to the TNC during the
initialization.
So I created the startup file for Xastir.
I have to say that serial KISS TNC works, but serial TNC with that startup
file doesn't. It gives me errors on the interface with the TNC.
The reason may be that the file contains some ascii control characters such
as escapes and <CR> that I don't know how Xastir handles. Moreover the
original configuration contained some delays of 1-2 seconds between one
command and the next, that again I don't now how to program in Xastir. For
ending I don't know how to handle the converse mode and the character k in
the configuration. SCS PTC is completely different than usual Packet TNCs.
Looking at some startup files,  e.g. KENWOOD TM-D710, I saw commands of the
type
##META <no-ctrl-c>
##META <ctrl-c>
##META <delay>
Are those macros interpreted by Xastir, does exist a complete set of those?

It should help if I could record a debugging file pointing out which command
the modem doesn't like. Certaintly it can be done, but I haven't found up to
now the right documentation.
Just to give you an idea this is the file with translation in decimal ascii
characters
<ESC>
Q
RESET
TONES 4
BRIGHT 6
FSKA 140
PSKA 170
PAC TXL AFSK 800
PAC
USER 0
PRBOX 0
BAUD R300
@K  (to enter into KISS mode)

027 013 010 ESC
081 013 010 Q
082 069 083 069 084 013 010 RESET
084 079 078 069 083 032 052 013 010 TONES 4
066 082 073 071 072 084 032 054 013 010 BRIGHT 6
070 083 075 065 032 049 052 048 013 010 FSKA 140
080 083 075 065 032 049 055 048 013 010 PSKA 170
080 065 067 032 084 088 076 032 065 070 083 075 032 056 048 048 013 010 PAC
080 065 067 013 010 PAC
085 083 069 082 032 048 013 010 USER 0
080 082 066 079 088 032 048 013 010 PRBOX 0
066 065 085 068 032 082 051 048 048 013 010 BAUD R300
064 075 013 010 @K

Do you have some suggestions?
Giuseppe
IZ1GCL
-----Messaggio originale----- 
From: Curt, WE7U
Sent: Tuesday, June 13, 2017 4:17 PM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] Xastir on raspberrypi to SCS PTCIIpro for Robust
packet Radio

On Tue, 13 Jun 2017, Menga wrote:

> Usually the display of the SCS PTC when in KISS mode shows KISS. In this 
> case it remained in STBY (stand by) even if it worked correctly.
> I don?t know much about preloading and postloading configuration scripts, 
> as well as timing in the configuration of KISS mode (I left the standard 
> values found in the configuration window).
> Have some of you experience to configurate a SCS PTC modem with Xastir, 
> and can give me a suggestion?

I don't believe any of the Xastir developers have one of these modems. At
least I've not heard of any that do.

It's pretty easy though: Take one of the standard scripts for "startup" and
one for "stop" in /usr/local/share/xastir/config/, copy them to new
filenames (maybe your "callsign.scs"?), then modify them to hold your TNC's
commands. You can test each command from a dumb terminal first, connected to
your TNC, while you work on the scripts.

Once you have them the way you like, change Xastir to use those filenames
instead and you're good to go. Save those files away in a good location in
case your hard drive breaks, so you don't have to go through the process
again.

If you get something you like, consider donating them back to the project
and we can add them to Xastir.

-- 
Curt, WE7U.        http://we7u.wetnet.net
APRS in Search and Rescue:  http://we7u.wetnet.net/search_and_rescue.html
_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://xastir.org/mailman/listinfo/xastir 