|
Re: XASTIR unable to start interface
jgindc1@...
Basil, I tried the first, setuid solution. Also worked like a charm. As always, many thanks for your support. John KM7LJ
On Fri, Feb 7, 2020 at 4:04 PM Basil Gunn <basil@...> wrote:
|
|
|
|
Re: XASTIR unable to start interface
Hi John,
toggle quoted messageShow quoted text
Two solutions First it is mentioned in the Xastir INSTALL file and in their FAQ https://xastir.org/index.php/Frequently_Asked_Questions#I_run_Xastir_under_Linux.2C_and_try_to_set_up_an_ax25_device.2C_but_get_a_.22Hard_Fail.22_error_on_the_interface._There_is_a_.22permission_denied.22_error_in_the_terminal_from_which_I_started_Xastir. that to use AX.25 the xastir run time file must be setuid. sudo su cd /usr/local/bin chmod u+s xastir After the xastir binary permissions should look like this: ls -al -rwsr-xr-x 1 root root 1178192 Jan 6 13:34 xastir Also you could try using Xaster interface AGWPE localhost:8000. I will add this to the Xastir install script. /Basil n7nix jgindc1@gmail.com writes:
Basil,
|
|
|
|
XASTIR unable to start interface
jgindc1@...
Basil,
Now with XASTIR running I am attempting to set up the interface with DRAWS via Interface Control: Interface type AX25 TNC, and AX.25 Device Name udr0. Interface START has no effect, the interface remains DOWN. I have tried moving the radio (FT-817) mini-DIN connector to the DRAWS right mini-DIN and set the AX.25 Device Name to udr1. This interface also does not START. I have checked that. 1. Direwolf and AX25 are running (ax25-status) 2. APRS packets are being received successfully (tail -f /var/log/direwolf/direwolf.log) 3. APRS position beacon sent ok (verified with aprsfi). Again, I have had XASTIR operating successfully using the same XASTIR interface setup with earlier versions of the Compass image. I wonder if there is some other parameter(s) that I have forgotten about. Thankls, John KM7LJ
|
|
|
|
Re: Nixtracker
Just remember, if gpsd is running and connected to /dev/ttySC0 then you should access it via the gpsd socket. If you are going direct to /dev/ttysSC0 then gpsd should be stopped.
On Thu, Feb 6, 2020 at 3:31 PM David Lowry <huskyrunnr@...> wrote: Thank you, that works. One less cable! --
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: Nixtracker
Thank you, that works. One less cable!
|
|
|
|
Re: Compass image V15, XASTIR, Missing Library?
jgindc1@...
Basil, Library install worked like a charm, may thanks for replying so quickly John KM7LJ
On Thu, Feb 6, 2020 at 1:53 PM Basil Gunn <basil@...> wrote:
|
|
|
|
Re: Nixtracker
Ruben .
I'm a bit late in this discussion, but if you're looking for a quick and sure way to set up a hotspot on a DRAWS image try KM4ACK's youtube video. His scripts do all the work. https://www.youtube.com/watch?v=qMT-0mz1lkI
|
|
|
|
Re: Compass image V15, XASTIR, Missing Library?
Hi John,
With version 15 I am unable to load XASTIR, either via the XASTIRNot sure why this library is missing. It is spelled out in the xs_install.sh script. To fix do this: sudo apt-get update sudo apt-get install libgeotiff-dev To be safe I would install all the packages required by Xastir maps. sudo apt-get install shapelib libshp-dev libgeotiff-dev libwebp-dev libgraphicsmagick1-dev Thus, am I correct in assuming image v15 is missing a library, and if
|
|
|
|
Re: Nixtracker
Thanks for trying out nixtracker
I have Nixtracker running on my pi 3b with draws hat installed. I haveGreat! However in the Sats window I have Zero sats. theLink following is the commit for zero sats problem fixed for the DRAWS gps device about 10 days ago. https://github.com/n7nix/nixtracker/commit/15ec32a5c05a3e7aa84d5defcae1abe26177c4f5 Below are the instructions for updating the nixtracker source. I will have a script that does this by the end of the day. Also make sure the port = line in the [gps] section is commented out in the nixtracker config file. The change is in a C file so you will need to get the new file and rebuild. In the config file /etc/tracker/aprs_tracker.ini make sure in the [gps] section that 'port =' line is commented out like this: #port = /dev/ttyUSB0 To get new source file, rebuild & install. cd cd dev/nixtracker git pull make cp aprs ~/bin cd cd bin sudo ./tracker-down sudo cp ~/dev/nixtracker/aprs /usr/local/bin sudo ./tracker-up The nixtracker web page should display an 1006 error, you should be able to refresh the page & have the tracker running again. /Basil n7nix I read in this forum that there is something that needs to beWhen an ax.25 app (like nixtracker) starts up it binds to an ax.25 socket which requires a physical port. So there is no easy way to select a port other than changing the 'port =' parameter in the [ax25] section in the nixtracker config file & restarting the app.
|
|
|
|
Compass image V15, XASTIR, Missing Library?
jgindc1@...
Basil,
I have recently returned to working with DRAWS and RPi. In earlier image versions I had been able to load XASTIR (via the desktop icon) without any issues. With version 15 I am unable to load XASTIR, either via the XASTIR desktop icon, or invoking directly from the folder /usr/local/bin. Using the desktop icon the busy icon appears for approximately 20 seconds, then nothing. The direct approach serves up the following error: error while loading shared libraries: libgeotiff.so.2 cannot open shared object file: No such file or directory I used sudo find / -name "libgeotiff*" with result of nothing found. Using an earlier image version 13 which loads XASTIR, sudo find / -name "libgeotiff*" produced much output: pi@draws:~ $ sudo find / -name "libgeotiff*"
/usr/share/doc/libgeotiff2
/usr/share/doc/libgeotiff-dev
/usr/lib/arm-linux-gnueabihf/libgeotiff.so
/usr/lib/arm-linux-gnueabihf/libgeotiff.so.2
/usr/lib/arm-linux-gnueabihf/libgeotiff.so.2.1.2
/usr/lib/arm-linux-gnueabihf/libgeotiff.a
find: ‘/run/user/1000/gvfs’: Permission denied
/var/cache/apt/archives/libgeotiff-dev_1.4.2-2+b1_armhf.deb
/var/cache/apt/archives/libgeotiff2_1.4.2-2+b1_armhf.deb
/var/lib/dpkg/info/libgeotiff2:armhf.symbols
/var/lib/dpkg/info/libgeotiff2:armhf.triggers
/var/lib/dpkg/info/libgeotiff2:armhf.list
/var/lib/dpkg/info/libgeotiff2:armhf.md5sums
/var/lib/dpkg/info/libgeotiff2:armhf.shlibs
/var/lib/dpkg/info/libgeotiff-dev:armhf.list
/var/lib/dpkg/info/libgeotiff-dev:armhf.md5sums
find: ‘/proc/732/task/732/net’: Invalid argument
find: ‘/proc/732/net’: Invalid argument
find: ‘/proc/1457/task/1457/net’: Invalid argument
find: ‘/proc/1457/net’: Invalid argument
pi@draws:~ $
Thus, am I correct in assuming image v15 is missing a library, and if so how do I find the correct package(s) and load/install? Thanks for all the hard work you put in to supporting DRAWS/RPi. John KM7LJ
|
|
|
|
Re: Nixtracker
Jim Erickson
Someone else smarter than me will chime in I’m sure, but for the DRAWS hat, the GPS is located at /dev/ttySC0
I’m not familiar with the Nixtracker, though I am interested. It looks like your gpsd is correct:
There must be a config for Nixtracker to point it at GPS? In which case /dev/ttySC0 is where the GPS is located, at least for the DRAWS hat. ------ 73, Jim VA7SHG - Phone VE7TGZ/VA7TGZ - Other
|
|
|
|
Re: Nixtracker
In trying to figure out why the gps is not reporting the info to nixtracker I entered
"sudo systemctl status gpsd" and the result I received is: gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-02-06 15:09:24 EST; 48s ago
Process: 511 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 519 (gpsd)
Tasks: 3 (limit: 2200)
Memory: 1.4M
CGroup: /system.slice/gpsd.service
└─519 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Feb 06 15:09:24 Draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Feb 06 15:09:24 Draws systemd[1]: Started GPS (Global Positioning System) Daemon.
Feb 06 15:09:26 Draws gpsd[519]: gpsd:ERROR: response: {"class":"ERROR","message":"No such device as /dev/ttyUSB0"}\x0d\x0a
when I try to cat/Dev/tty/USB0 I receive cat: /Dev/ttyUSB0: No such file or directory any help would be appreciated. Thanks, Rich, KR4PI
|
|
|
|
Re: Nixtracker
Good afternoon all,
I have Nixtracker running on my pi 3b with draws hat installed. I have two radios connected. UDR0 is attached to a radio on our local packet freq and runs a Winlink Gateway. UDR1 is connected to a radio on our local aprs freq. I am able to see aprs info on the Nixtracker on another machine. However in the Sats window I have Zero sats. the window reports nodata. gpsd is running on the Pi and has a good lock. I read in this forum that there is something that needs to be done to make this work but it appears those instructions were taken offline. The other question I have is there a way in the MSG tab to select which port on draws the aprs message goes out? Thanks for all the help! Rich, KR4PI
|
|
|
|
Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF
Dave Christensen
I hooked up my Pi3B+ to a Signalink and ran FLDigi, JS8Call, and Direwolf and measured the audio drive levels on transmit. They were all within 20 mV of each other so the USB Audio Codec (Signalink) is being handled differently than the DRAWS interface for some reason. I don't know if this simplifies or complicates this issue.
|
|
|
|
Charles Blackburn <wx4cb@...>
not using a draws yet, but i am using ham radio deluxe on my laptop and i have the settings as below, just remember for it to accept out of the data port, you need to tell it specifically to use the correct TX cat command (there's two). as per page 21 of the command manual: https://www.kenwood.com/i/products/info/amateur/ts_480/pdf/ts_480_pc.pdf
toggle quoted messageShow quoted text
IIRC it's TX1 TX - Sets the transceiver in TX mode. Parameters: P1 0: Normal (SEND) transmission using MIC input 1: DTS transmission using ANI input 2: TX Tune transmission If no P1 parameter is specified, P1=0 is used. radio: HRD PTT: CAT TX Audio Source Rear/Data ModeL None Split: None hope this helps charlie
On 2/5/2020 12:00 AM, Jonathan Visser via Groups.Io wrote:
I am working to test WSJT-s on the latest image of DRAWS image.
|
|
|
|
Jonathan Visser
I am working to test WSJT-s on the latest image of DRAWS image.
I have connected a USB to serial adapter plugged in to the COM port on the radio and have a DIN cable between the UDC0 and the data port on the radio. I have configured FLRIG and I have seemingly full control of the radio. I have the ability to transmit and the tune button will tune the antenna. WSJT-X is configured using FLDIGI as the transmitter. I can see the waterfalls and the messages are decoded. I can change the frequency of the radio through WSJT-X. Th issue I am trying to figure out is WSJT-X will not transmit. If you press the tune button or enable TX the radio never keys up. I am sure I am missing something basic, and was hoping someone could point me in the correct direction. Thanks, Jonathan N9TJX
|
|
|
|
Re: #Desktop file manager and screen blanking issues
#desktop
My suspicions are that since this is a known issue with the Raspian
image then they must have fixed the issue and the update/upgrade
pulled in the 'fix'...
toggle quoted messageShow quoted text
On 2/2/2020 1:52 PM, f6bvp wrote:
|
|
|
|
Re: #Desktop file manager and screen blanking issues
#desktop
Hi Basil, sudo apt update suggesred by david, Ke7rgp
|
|
|
|
Re: #Desktop file manager and screen blanking issues
#desktop
This means that something should be repaired in nwdr14 and 15 ?I will not be spinning a new image. The pcmanfm reinstall has been added to 'app_config.sh core' with this commit: https://github.com/nwdigitalradio/n7nix/commit/bf885816fe434007f649aaf3ec05d0b253fc9cba For new installs pcmanfm will automatically get reinstalled if directions are followed in the "Getting Started Guide" ie. you need to do a 'git pull' before running 'app_config.sh core' For those who have already done an install you can fix the symptom, as previously posted by opening a console running: apt-get install -y -q --reinstall pcmanfm I will see if screen blanking issue is also gone.I think these 2 issues are unrelated. /Basil n7nix
|
|
|
|
Re: #Desktop file manager and screen blanking issues
#desktop
David, This means that something should be repaired in nwdr14 and 15 ?
|
|
|
