[Xastir] Using OTUSB & Xastir but NOT in KISS mode

[F1MHV]

Good day,

I am looking for to use Xastir but not in KISS mode, therefore i am trying-it with, alternating, ArgentData's OpenTracker USB & SCS Tracker DSP/TNC. With both TNCs i have some issues which are not exactly the same, but i presume could be sort-out in the same way (see discussion bellow): does there is a way to customise or to create a script for each TNC with just the needed commands? Digging Xastir config sub-folder, i found some "tnc-startup.(tnc-name)" files in-it...

Thank you for help

Début du message réexpédié :

> Scott Miller scott at opentrac.org [tracker2]

> Most of those TNC2 commands aren't needed and aren't supported on the OTUSB.  Presumably it's not using the proper exit commands either, but I don't know what Xastir is trying to send on exit.  If you insist on running it without KISS mode, I would suggest rewriting Xastir's command script to use only the commands you need.
> 
> Scott
> 
> On 11/25/2014 11:46 PM, F1MHV F1MHV at free.fr [tracker2] wrote:
>> Good morning Scott,
>> 
>> 
>> I installed according to "Howto" Xastir V2.0.6. and to connect the OTUSB, i am using /dev/cu.usbmodemxxxx (with /dev/tty.usbmodemxxx... Xastir freeze immediately) and according to the log bellow, i can connect and transmit as well (didn't tried rx for the time being), but when i want to stop/disconnect from OTUSB, then Xastir freeze. Beside the OTUSB, i have the SCS Tracker DSP-TNC and i don't have all these errors showing in the connection log, only few of them, and i can stop the interface without freezing Xastir.
>> 
>> You are mentioning console entries, but there are not so much setting when you add an "interface":
>> 
>> - i choose "Serial TNC"
>>  
>> 
>> - Then:
>> 
>> 
>> Before asking Xastir, i would like to check with you and other users, if there is anything specific to sort-out my issues...
>> 
>> 73 de Cyril - f1mhv - df1chb/am
>> 
>> ps: connection log bellow
>> ps2: for info, with OS X, i ma using Serialtools V1.2 (AppStore) to access the OTUSB with command line and it's working like a charm...
>> 
>> " 1:TNC-> DIGI on
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> EXP on
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> Filt off
>>  1:TNC-> FILTER OFF
>>  1:TNC-> 
>>  1:TNC-> FLow off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> FUll off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> HEA off
>>  1:TNC-> HEADERLN OFF
>>  1:TNC-> 
>>  1:TNC-> LFadd off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> LFSup on
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> AUTOLF off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MCOM off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MFILT off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MON on
>>  1:TNC-> MONITOR ON
>>  1:TNC-> 
>>  1:TNC-> MResp off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MRPt on
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MSTamp off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MXMit off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> NEWmode off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> PASSALL off
>>  1:TNC-> PASSALL OFF
>>  1:TNC-> 
>>  1:TNC-> PID off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MNOAX25 off
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> PIDCHECK on
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> MPROTO OFF
>>  1:TNC-> Invalid Command
>>  1:TNC-> 
>>  1:TNC-> SCR 0
>>  1:TNC-> SCRIPT OFF
>>  1:TX -> DF1CHB>APX206,WIDE2-2:=5114.00N/00648.00ExXASTIR-Darwin
>>  1:TNC-> 
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> 
>>  1:TNC-> UNPROTO APX206 VIA WIDE2-2
>>  1:TNC-> Error
>>  1:TNC-> 
>>  1:TNC-> k
>>  1:TNC-> CTRL-C to Exit
>>  1:TNC-> =5114.00N/00648.00ExXASTIR-Darwin
>>  1:TX -> DF1CHB>APX206,WIDE2-2::F1MHV    :testing...{0h}
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> 
>>  1:TNC-> UNPROTO APX206 VIA WIDE2-2
>>  1:TNC-> Error
>>  1:TNC-> 
>>  1:TNC-> k
>>  1:TNC-> CTRL-C to Exit
>>  1:TNC-> :F1MHV    :testing...{0h}
>>  1:TX -> DF1CHB>APX206,WIDE2-2::F1MHV    :testing...{0h}
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> MYCALL DF1CHB
>>  1:TNC-> 
>>  1:TNC-> UNPROTO APX206 VIA WIDE2-2
>>  1:TNC-> Error
>>  1:TNC-> 
>>  1:TNC-> k
>>  1:TNC-> CTRL-C to Exit
>>  1:TNC-> :F1MHV    :testing...{0h"
>> 
>> Le 26 nov. 2014 à 06:10, Scott Miller scott at opentrac.org [tracker2] a écrit :
>> 
>>> 
>>> 
>>> It *should* work if you're careful about the console entry requirements (it needs a couple of carriage returns before you get a cmd: prompt) but I haven't tried it in a long time.
>>> 
>>> Scott