[Xastir] Xastir 1.9.9 help

[John Wilson]

On Thu, 2010-09-16 at 10:12 -0700, Curt, WE7U wrote:

> Have you checked the View->Incoming Data dialog to see what Xastir
> thinks it is getting?
> 
> You can also start Xastir from an xterm in debug mode and see what
> Xastir spits out as it receives a packet.  Try this invocation:
> 
>      xastir -v 4095 &
> 
> If you want to capture all the output to file you might try this:
> 
>      (xastir -v 4095 2>&1) | tee xastir.log
> 
> 
> 


I don't think there is a day that goes by, I learn something new. I am
going to have to hit this when I get home later to see if it is seeing
anything. This is what I was looking for...figured there was something
to see the raw data.



> Not just Linux, try "Any other OS besides DOS/Windows."  MS really
> did a job on everyone else by making their stuff non-case-sensitive.
> Now all these Windows people are looking for something better and
> having trouble adapting to the way the rest of the world does
> things.
> 
> Don't get me started on line-end characters (Unix/Mac/Windows all
> had to use something different), or how MS must invent new names for
> everything yet still implement the same types of things as everyone
> else, but choose to change them just enough to be incompatible with
> everyone else. 


Didn't mean to strike a nerve there...was just commenting on my
realization of the caps difference. I think it is inevitable, each day,
I get further and further away from the "other" OS.

On Thu, 2010-09-16 at 12:48 -0400, Michael Lewis wrote:

>   hmm I'm in the same boat as you John.. I checked to see which port
> was 
> given to my Serial-to-USB by typing in "demsg" and it's
> on /dev/ttyUSB0 
> Ok so with that said I go in xastir and enter in that info and so on
> and 
> click on start and it "connects" or so.. However after getting my GPS 
> lock and all and pressing transmit now nothing never happens.
> Incoming 
> packets cause the Carrier Detect light to blink rapidly. I looked  at 
> the PK commands in the config to see what my own packets looks like
> and 
> it never showed anything unless I did something wrong.


Forgot about dmesg. I was using lsusb but wasn't seeing which USB it was
plugged into. That only gives Bus and Device. After having done that, I
found that it is connected to ttyUSB3. Again, I will have to put this
off til this evening for further testing. More to follow.

73 John