New user - APRS issues

[RC32]

Hi - new user here trying to get my DigiPi working to TX/RX ARPS.  

[Setup]  
- DigiPi 1.9.3 + Pi Zero + PiTFT 1.3" LCD  
- Power via 4000mAh power bank, ferrite choke on USB power cable  
- Baofeng UV-5R + N9TAX 2m/70cm Slim J-Pole  
- Frequency set to 144.390 MHz (Narrow FM)  
- Radio Squelch = 0, Digipi volume = 61, gain = 100  
- NA6D AIOC with USB cable, ferrite choke on USB  

[Issue]  
- When sending APRS over WebChat, I hear packet audio on another HT, but there is no indication of TX on the DigiPi LCD.  
- No incoming RX packets show up on the LCD or in logs.  

[Steps to Replicate]  
1. Load DigiPi onto SD card and configure WiFi and initialize parameters.  
2. Set call sign, APRS password, grid square, latitude/longitude, screen type (ST7789).  
3. Detected radio/GPS shows ttyACM0: usb-AIOC All in One.  
4. Detected audio interface shows 0 [AllInOneCable].  
5. Apply changes and restart the system.  
6. Set Baofeng to 144.390 MHz and log into DigiPi.  
7. Activate TNC GW and WebChat, set volume to 61, gain to 100.  
8. Review PacketLog, which shows:  
*Using /dev/hidraw0 GPIO 3 for channel 0 PTT control*
   - This makes me wonder if DigiPi is using GPIO for PTT instead of the AIOC interface.  
9. Send "Wxbot" location via WebChat:  
   - TX packet is heard on another HT in the same room.  
   - Red TX LED lights on both DigiPi and AIOC, indicating PTT is triggering.  
   - No TX activity displayed on DigiPi LCD.  
10. Repeat the test using zip code and sending to Wxbot, same results.  
11. Log into APRS.fi and see my call sign, but only via APRS-IS (Internet), not RF.  
12. Other HTs receive APRS traffic, suggesting RF reception works, but TX isn't reaching an iGate.  

[Questions]  
1. Could the AIOC be misconfigured, triggering PTT but not actually transmitting?  
2. Are there settings in DigiPi to explicitly force PTT via the AIOC?  
3. What’s the best way to confirm my Baofeng is Tx a valid packet?  

Thanks for any suggestions you may have!

[Craig]

Hi RC32

help me understand "no TX activity displayed on DigiPi LCD"

The red indicator on the little LCD screen should turn red on TX.  The HDMI/web screen will
not show a red indicator.  Your TX packet info will not show up on any screen (only
reception is shown).

If you can hear the Tx on a nearby radio, it's working.  compare volume and sound
quality to other stations in the area.

if it helps,
-craig
KM6LYW

Thanks for any suggestions you may have! --
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/a7408081-6f50-4152-9a4b-347fbf1219c6n%40googlegroups.com.

[Ron Startzel]

Should the radio also be set to FM wide vice narrow?

I have mine set to wide.  

Not sure if that is the issue but if it is transmitting and you are receiving, might be a reason it isn’t decoding.  

I may have also misunderstood what you typed as well. 

Ron

KB5LNC

To view this discussion visit https://groups.google.com/d/msgid/digipi/b8091466-a48d-48c9-9647-993483658cb6%40gmail.com.

[RC32]

Thanks Craig / Ron for the reply -

The red indicator on the little LCD is turning red, and I can hear the Tx on a nearby radio, so I agree the Tx appears to be working on my end.

I did set the band to wide as well per Ron's suggestion. 

I do notice on the Webchat the 'thumbs down' does not turn into a 'thumbs up', and also I do notice that when I hear APRS packets being sent from another radio, they do not appear on my DigiPi LCD, nor in the WebChat. 

I also check on the ARPS.fi website, and I am not seeing any activity tied to my call sign at this time. Yesterday, I did see activity, but it appeared to be based on internet vs. radio.

I am attaching a screenshot from PacketLog that may or may not be helpful.

[Craig]

Thanks for the PktLog.  It'd help if we saw the complete log, particularly the top/audio portion.

Also the top of Sysinfo should show you the AIOC radio and AIOC audio device.

You're not receiving any packets.  Do you "hear" any traffic on the aprs frequency?  Baofeng's
are poor receivers, only strong packets will appear in my experience.  Also set the 'feng
volume knob about 25%.

Wide is correct in the USA (narrow in Europe).

-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/f675060c-a0ba-4874-aa98-925ed7a6895dn%40googlegroups.com.

[RC32]

Thank you Craig for this info. Wanted to share more details.

First, I swapped the radio out for a Btech DMR-6X2 set to 144.390 (Analog) with squelch set to zero; tried various volume knob levels. This was with a roll up slim-j antenna.

Next I made some attempts with no internet connection then with an internet connection.

I set in direwolf.tnc.conf and rebooted after saving two changes to disable internet aprs and to set the device value:

#IGSERVER noam.aprs2.net

ADEVICE plughw:0,0

I was able to transmit packets that show in the log, and I was able to hear my tx on another radio. I do not see any rx in the logs however.

Attached are the PktLog, the direwolf.tnc.conf, the arecord and lsusb ouptut, and also the audio settings in DigiPi (I had moved them to various levels without any change)

Note I see an igate station near me (about 3 miles away) WB4GMB via arps.fi.

Hope this info is helpful. I am wondering if my next option is to change my location to see if it is in fact a range issue (I am thinking no).

[Craig]

Everything looks great, thanks for the logs.  I see you transmitting, but not receiving.
You shouldn't need to modify direwolf.conf.

'Feng volume should be about 25%.

Your audio path looks good.  Do you "hear" any packets when you listen to 144.39?
I think you're out of range, in addition to the 'feng not being an ideal receiver.

-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/e6fa6568-4742-4959-aebc-29b1c4a3cc8cn%40googlegroups.com.

[Allan may]

Craig and all,

This is the exact same thing I’m having trouble with except I’m using a IC-705. I’m “hearing packets” but retransmitting them out to my other radios. I have W4HZL-1 not too far from me. It’s all showing up in the PKTLog. Any suggestions?

Allan May, 

Amateur Radio Emergency Coordinator, Charles City ,VA
WD4ITE
CCARC President

To view this discussion visit https://groups.google.com/d/msgid/digipi/4be25790-28ab-45fa-b4b4-b47282c2a6e5%40gmail.com.

[Craig]

digipi APRS Digipeater will only digipeat packets that have WIDE1-1 in the routing header  (not WIDE2-1, and not WIDE1-1*)

if it helps,
-craig
KM6LYW

[Michael Scantlen]

I have been unable to receive packets to my DigiPi APRS WebChat.  Sending position info out to WIDE 1-1 or Default shows outbound packets in pktlog.

I see *many packets from all over the world in pktlog but I can not receive anything direct to me.

Any thoughts as the attached shows possible suggested routing to Ukraine?

[MI7DJT]

Hi Michael,

I had the same issue using a Baofeng.  I could on'y receive packets from my own radios when close by.  I never picked up any local users.  The problem is that Baofengs have a very poor squelch.  It's not sensitive enough to capture the entire packets from any distance.  If you miss the start of the packet, you get no decodes.  Therein lies your problem.  If this is a serious project you really should get a better radio suited for the job.

Using Fengs is really just good for proof of concept.

Good luck,

Eamon - MI7DJT

To view this discussion visit https://groups.google.com/d/msgid/digipi/3d3ae5d9-886b-43ac-ab64-e651637578adn%40googlegroups.com.

[Craig]

Hi guys, a couple things,

1) turn SQL to 0 (off), no squelch
2) send a beacon first on the webchat interface so the backend knows where to reach you
3) check aprs.fi to see if there is a digi/igate near you (green star), within 20 miles maybe

PktLog packet on RF have "audio level" in them, the packets prefixed with ig>tx are
coming in on the internet and don't count (ignored by webchat).

The baofeng receiver is pretty bad, if there is any rf noise nearby on any frequency,
it wont decode packets.  get that antenna outside and away from noise if possible.

cool,
-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/3d3ae5d9-886b-43ac-ab64-e651637578adn%40googlegroups.com.

[Michael Scantlen]

I made progress understanding what wasn't happening today.  I have been using an ICOM-705, not a Baofeng.

My DigiPi was connected to home WiFi in addition to the Radio for RF.

The aprsd.conf  is by default set FALSE for "connected to the internet."

During startup of the APRS TNC/igate the use of the home WiFi registers the callsign at aprs.fi correctly via the internet only.  

Sending a position report in APRS WebChat goes out via RF and never gets an ack.

Craig's statement about 20 miles for a repeater, made me check the repeater I was receiving all my packets from.  (It is beyond the 20 mile distance)

I can receive all day but not transmit to it.  It doesn't know I'm here.

When I turned off connection to my home WiFi for the DigiPi, it didn't register at aprs.fi, I still never got packets ack'd, but confirms the internet was the one doing all the work...

With aprsd.conf setting TRUE for "connected to the internet", I can send now SMS, EMAIL and Messages, no problem through APRS WebChat.   This is NOT through RF though.

I will be installing a secondary antenna this weekend and hopefully reach the next digipeater!  Hopefully this helps anyone troubleshooting their issues.

-Mike KC1IZC

 

"

[MI7DJT]

Hi again Michael,

Thanks for the corrections on your setup.  I think I remember having to setup 2 PBeacon lines in my direwolf.digipeater.conf.

One had the sendto=IG in the line..  the other went out to RF.

Do you have something similar?

Eamon - MI7DJT

To view this discussion visit https://groups.google.com/d/msgid/digipi/CA%2BzxWGd8ETP9snmEwpw_C8AWtsL6DNCUWo5XbNSv4S8xYOcxbw%40mail.gmail.com.