You will need to make sure that the TNC levels are configured correctly. This can have an impact on how many stations you are hearing. The mobilinkd team offers an Android app to assist. Check their documentation or their forum /g/mobilinkd/topics

As for the connection in xastir coming/going, it would be helpful to start the connection to the mobilind manually instead of using Pat Menu to start the TNC connection. This is a bit more of a pain but would allow you to see if it is the connection between the Pi/Mobilinkd that is becoming unstable or the connection between Xastir/Mobilinkd. In other words, when the interface shows either down or error in xastir, does the bluetooth connection between the Pi and the Mobilnkd still exist?


--

The listen mode is used for peer to peer (P2P) connections. So when you enable listen mode, your station is listening for other stations to call your station.

--

Tim,
Thanks for sharing this, recently got the TX500 and look forward to connecting to the pi
73
Jerry
N8MAC

Hi everyone

[errgh, posted this to the wrong groupsio page earlier. If at first you don't succeed...]
I know it's 'old news' by now, but SUPER shout-out to Jason for all of the hard work he's done to make the BAP experience something that a newb can really dive into.? I've spent the morning getting my Mobilinkd TNC3 & xastir playing together.

It's been a more or less WIN!

Only thing is, there have been some quirks.
For instance, even with the TNC3 'started' using the PAT menu, I notice that it *sometimes goes "down" in the xastir interface control box. When that happens, *sometimes when I click 'start' on the device in interface control it will come back up.... and sometimes not. There have also been a couple of times that clicking on the start tnc3 modem button in the PAT menu... it goes through the scan, and comes back saying it didn't locate a TNC3.?
Wondering if this is something in the Pi ... or if I have a flakey TNC3?? BTW, I'm using Pi3B+.

Regardless, when it's worked, it's been WAY COOL.

I think I may also have to do some 'dialing in' re the TNC3/Mobilinkd settings, as I'm in the Chicago area and seems like I should be able to 'hear' a lot more stations (aka see a lot more things populating on the map) than the 7 or 8 stations that did show up. I'm assuming that's an audio-in tweak in the TNC3 setup app.? For what it's worth, I've now tried it on both my HT (IC-V86) and my packet rig Yaesu FT-2600M....both using roll up J-Pole 20ft up in a tree by my garage. In comparison when running both on APRSDROID, I tend to see/hear more stations.

Thanks again Jason!

73,

T.M.
KD9LAI
Rev. Tim Manwell, MDiv, BCC
Chaplain Specialist, Alexian Rehab Hospital

开云体育

开云体育

I use a 10ahm lifepo4 battery with my g90..I use a 7” hdmi touch screen bought on Amazon. I also use a wireless folding keyboard. This setup works for me.?

I am wondering if portable HDMI displays might be simpler for field use, ?I have installed the Hotspot and VNC and have had lukewarm success in getting it all to work with my tablet (Apple). ?There are several 10” HDMI displays that are fully portable and not very heavy consumers of power. ?Currently using Bioenno 12v 12ah battery with my G90 and Raspberry Pi. ?That can go much longer than I can! ?The HDMI screen requires only a cable to get the Pi displaying it’s desktop. ?Thoughts and ideas are welcomed.

A partial result. Got remote gpsd to be usable by local utils, but not by the local gpsd (yet).
For example, I altered the bin/conky/get-grid Ruby script to connect to the remote gpsd directly, and now I see my grid square on the conky display.
Local calls to the local gpsd, though, don't work.

The answer was pretty well hidden over in
That does a "real world example" at the very bottom of the file. There they reveal that adding a -G option to gpsd is not enough.
You also have to alter the gpsd.socket configuration so that systemd will allow connection from remote hosts.
For completeness, I include the instructions below (in case the link changes or disappears).? The parts that aren't told elsewhere are in yellow.
Notice that after this, cgps 192.168.0.200 and xgps 192.168.0.200:2947 work great, and the local gpsd connects fine.
However, the local gpsd gets a? {"class":"ERROR","message":"Unrecognized request ''"} error when it is asked to retrieve data from the remote gpsd (triggered by running 'cgps' locally to the local gpsd).

Real World Example

For security, gpsd by default is shipped set up to listen only on the loopback interface, thereby restricting its audience to clients on the same computer. We'd like to allow other computers to listen in as well. This means:

• Opening the firewall at the gpsd assigned port, 2947. That is beyond the scope of this document.
• Adding the appropriate switch to the command line for gpsd. While we're at it, we'll also add the -n switch.
• Changing the gpsd.socket unit so that other clients can connect to the daemon.

Once we know gpsd is running, we modify /etc/default/gpsd to provide the options we want. One to listen on all the interfaces (-G), and one to tell gpsd not to wait for a client to connect before polling (-n). The GPSD_OPTIONS stanza now looks like:

# Other options you want to pass to gpsd
# GPSD_OPTIONS=""
GPSD_OPTIONS="-Gn"

We can stop gpsd. Systemd will restart it for us, this time with the options in place. We then verify that the options are there:

root@orca:~#  gpsd.socket gpsd.service
root@orca:~# ps aux | grep -i gpsd | grep -v grep
gpsd     14547  0.5  0.0  18092  3504 ?        S<sl 15:44   0:00 /usr/sbin/gpsd -Gn
root@orca:~#

But we aren't there yet. gpsd may be listening on all interfaces, but systemd's hold on the socket means gpsd can't hear anything on interfaces other than the loopback. We have to tell systemd to allow gpsd to hear other interfaces. We run . Then we can edit it. After editing, the [Socket] stanza looks like so:

[Socket]
ListenStream=@RUNDIR/gpsd.sock
ListenStream=[::1]:2947
# ListenStream=127.0.0.1:2947
ListenStream=0.0.0.0:2947
SocketMode=0600

When you are done editing, systemctl does what it needs to do internally to preserve your changes from being over-written during upgrades. It also does the equivalent of a systemctl daemon-reload for you.

We now restart both gpsd units like so:

 gpsd.socket gpsd.service

Now check with a local client, and a client on the remote computer:

xgps 

Where in our example is orca. As usual, if you see data in the client, you're done.

Ron,
73 de KO4RON

All that work to make it function properly and when I ran conky-prefs it was gone!? What a waste.? Since I have to run conky-prefs every single time the Pi boots to get gridsquare, I'll just pass on this for now.

开云体育

Hi Mikehow to add wifi driver to Debian linu

I can't answer your question directly, I have the same software but my wifi worked right away. But I

did a Google search using "how to add wifi driver to Debian linux" and got several answers. This

might get more information for you if you add Debian to the search to narrow it down a bit more.

I did see some answers to my search so I know there are answers.

Hopefully someone will have an answer here and speak up to help more.

Marty kd8bj

Here is a step-by-step set of instructions to get you started:

Post questions as needed.

The image used was 2021-01-11-Raspios-buster-i386. It is a Debian Raspberry desk top for PC and has iso's for amd64 and well as several other platforms. After the install I was exploring the loaded files and it included sever programs that are HAM based, as well as a full office type suite. I just cannot found out how to the driver package I found. The only issue I have found is the wi-fi is not usable, and need b43/ucode5.fw b43-open/ucode5.fw, what ever they are. Like I said I found what is reported to contain the solution for those files, but when I attempt to install, it fails. I don't think I am doing the install correctly, but since I have never work with Linux style systems, I have way of know what I am doing. So if anyone has any suggestions??
--
72 & GL de KE5WCT
Mike

Where can I find documentation of how the PAT Listen function is supposed to work.
I'm running PAT on 2m and Telnet and I've activated Listening on Telnet and then on AX25 and they don't seem to have any effect.
What I thought would happen is if I sent an email to my WinLink address somehow it would be automatically received in the PAT WinLink In Box.
73 de Jeff KO4NCC

?Something like these lines in .conkyrc in your home directory should work:

${if_match ${exec bluetoothctl info 98:D3:31:F7:55:37?| grep "Connected: yes"} == "Connected:yes" ${color green}BluetoothConnected! \

$else \

${color red}{blink?'Bluetooth Disconnected!'}

${endif}

On Thu, Sep 2, 2021 at 11:17 AM, Chris wrote:

bluetoothctl info 98:D3:31:F7:55:37

I haven't played with this and can't say specific for Conky but to parse the data you could use:
bluetoothctl info 98:D3:31:F7:55:37 | grep Connected
which should just show you the connected statement. Taking it one step more:
bluetoothctl info 98:D3:31:F7:55:37 | grep Connected | awk '{ print $2 }'
should leave you with yes or no.

Hope that helps
?
--

On Thu, Sep 2, 2021 at 09:06 AM, Pieter V51PJ wrote:

Question. Must i delete hamlib4.3

No need to delete as it never installed to begin with. Please post other questions in a new thread so we don't derail this topic.
?
--

开云体育

Hi

I assume you are answering my post. But I didn't have any trouble with wifi, only the display

showing funny. I think though I would like to get a copy of that distro to try. What I would like

is to be able to try running the BAP on Debian 10 to see if it will work, I expect most of it will

or can be played with.

Something to try, I like the fact that I could run my laptop, I think, from a 12 V battery, for the

POTA attempt from a close park. For a short time I do have a Phone battery that could power

my Rpi plus monitor, maybe. Or play with a buck converter to power them with.

Marty kd8bj

Ah, forgot about that one. It is very stripped out. It would be better to just run the real Debian Buster (10) or Bullseye (11), and have easier access to the full tools and drivers, unless there is a specific reason for running it (like the net-boot server functionality)...

开云体育

I think you misunderstood the OS he is using. It is one I use on my HP laptop. It is an OS

labeled for I386 I think on the Rpi site. I have most everything working on my i386 64 system. I am

seeing an issue in the display. Works but is not up to what you see on a pi display.

I am still working with it, I could easily make due in a POTA situation. I would have a hard

time in a POTA event using my Rpi providing power with out a Generator.

Marty kd8bj