so I found out about this problem quite by accident... if you run xastir that was installed by apt from the repository and you want to build from the source (for version 2.1.1 or later) you have to re

#draws #xastir #aprs

All DRAWS owners, Setting up xastir for the DRAWS board was not a slam dunk! This message is longish but my discoveries and explanations here may help if you are relatively Raspbian naieve. If you hat

#draws #direwolf #compass #xastir

Once I have A25 and Direwolf running, what Interface option do I select in Xastir? 73s, Ed, KD9FRQ

#xastir

Ed, I am using the AGW interface here. Jack – KD4IZ

#xastir

Thank you.

#xastir

I'm beating my head against the wall with this issue. I've done a fresh beta 11 build on a brand new sdcard and I'm still not able to get GPS data into xastir via GPSD. YAAC gets the GPS data fine, bu

#draws #gpsd #config #xastir

All, I have got things configured to receive in direwolf. Xastir shows heard stations on the map using the direwolf AGW interface. DRAWS UDRC parms were fine adjusted by the bash script and fine adjus

#direwolf #draws #xastir

share your direwolf.conf file (remove IGLOGIN if set) and let us have a look.

#direwolf #draws #xastir

John, As I recall, I did nothing to change the main settings already there, just added MYCALL for the 2 ports and the IGLOGIN call and passcode: ADEVICE plughw:CARD=udrc,DEV=0 ARATE 48000 ACHANNELS 2

#direwolf #draws #xastir

That sounds like you are transmitting at 9600 baud. Is that intentional? A brief burst of static is what you'll hear. Bill

#direwolf #draws #xastir

Hi Bill, I thought of that, but it happened from both 1200 and 9600 ports - there is no sound, not even noise. I know what the 9600 bursts sound like... years ago, I ran an Ottawa PI card. KD4IZ Jack

#direwolf #draws #xastir

In addition – if I use a direwolf.conf for the left port @ 1200 baud and PTT set to GPIO 12, exactly the same as below. PPT is proper timing with no sound. Grrr…. J – KD4IZ

#direwolf #draws #xastir

All, Thanks for your patience on this thread – the problem was not self-evident and I don’t understand why the following situation works for me. The solution was to comment out all references to port

#xastir #direwolf #draws

You could also remove the old xastir and it's config files with: apt-get purge xastir That will remove the config files, then build and install xastir. Or if you want to keep the config files build xa

#draws #xastir #aprs

Debian File System Hierarchy Standard https://wiki.debian.org/FilesystemHierarchyStandard It's a debian convention that locally built binaries use: /usr/local/var /usr/local/etc /usr/local/share /usr/

#draws #xastir #aprs

Ed, If you are referring to XASTIR's Interface drop down window, I use the following after I select "add" which brings up the "Interface type I/F Control" Select AX25 TNC, which brings up "Configure A

#xastir

Update from testing a fix provided by Tom Russo. The code change for Xastir provided in Tom's "feature-supportglonass" branch appears to fix the problem of DRAWS gps not working in Xastir. I am contin

#draws #gpsd #config #xastir

Good research and hopefully the fix proves solid over time.

#draws #gpsd #config #xastir

Will the DRAWS image be updated with the working version of Xastir? What must one do to update the version currently running on DRAWS? Thanks for your (rapid) research and help! Edd - KD5M

#draws #gpsd #config #xastir

Yes. I will probably spin up yet another image to accommodate the new Xastir build. Previously Xastir was installed from a Debian package. It is clear that besides fixing a problem with parsing the DR

#draws #gpsd #config #xastir