Thanks Jeff. There is a LOT of info out there. Sometimes it can be difficult to locate that one small nugget your are hunting.
--

I haven't and don't own any DMR radios currently. DMR is not a rabbit hole I have ran down yet.


--

Thanks Jason I don't know why I just can do the right search.? Well you convinced me to go Patreon.
73's Jeff KO4NCC

Hello Jason,

Have you tried building/using DUDEstar, for DMR, on a Pi4B?? I am building it on an atomic pi as I type, but the Pi4B/8G will be next, and I am interested in your thoughts.? I have only come across builds on x86 Linux, and the Windows build is available on github, but the Windows version is stated as being unsupported (compared to the Linux version).? Perhaps it is about time to have a go with an arm processor on our favorite, the Pi4B??

ks
K4GMV

What Brian Dale said.?
--
Don
W6CZ
DM07bk

So on another topic...
After watching some vids by Jason & others, I'm interested in building an APRS Pi utilizing Direwolf and Xastir, connected to my old 60w Yaesu FT-2600M, which I bought for a song....particularly because it has a data out jack.?

From what I can tell, the "missing link" for me right now is the audio piece between the radio and the Pi.... including a cable.
I'm not really set up to make my own cables, so whatever way I go, I may have to goto ebay or find some sort of 'cables-r-us' type ham buddy.
But then there's the soundcard.
I already have the super cheapie Sabrent usb soundcard that everyone has.? So, I guess one question would be... is that sufficient, or am I looking at buying a Signalink? A follow up question would be...even if the Sabrent is "good enough," should I go with the Signalink anyway, as that would simplify the cable question?

Would love to hear from someone who's got a similar setup working.

Thanks, and 73!

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

Hey Jason
Yeah, I know that the 'correct levels' settings within the TNC3 app need to be set appropriately..... so far, tho, my experience is that this at times seems to border on magic/alchemy. Getting the output power level correctly with just the naked ear is a roll of the dice. In the absence of sophisticated electronic equipment, I've downloaded a decibel app for my phone that detects differences in noise. And in terms of getting the input level set.... I've discovered that when I'm using my FT-2600M with its data-out jack, I can't get the LEDs to just 'tickle' the max. Input level is pegged to the max even when both sliders are turned all the way down. When I use the auto-adjust feature it usually leaves the gain at 0, but often sets the twist between 3 and 5 db. I'm assuming that it's the INPUT settings (along with my antenna) that determine how well I 'hear' other beacons.?
In the end I'm not really sure that my TNC3 is the final solution, especially for use with my FT-2600M mobile rig.

Which brings me to another topic.
But I'll post that as a separate item.

73!

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

I posted the same question about a month ago but got no response. For that reason I just ended up eliminating all Conky mods.

Installed all one by one

pat mail start 100%

ptt is set to true
select a freq to connect
then following messages on screen

that is where i get stuck. Something in later updates as all was working perfect

please advice where to type, change etc?

de v51pj
pieter jacobs

On Fri, Sep 3, 2021 at 12:09 PM, Scott wrote:

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.

Running conky-prefs installs a default template for Conky. Anytime you mod the conky file, don't use conky-prefs. The more interesting part is why you need to run conky-prefs to get the gridsquare to display? Please post a new thread since it is off topic for this post and let's see if we can figure that out. The grid square should load automatically.
?
--

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.