Date   

Re: Where to start? #pi

Michael Mohaupt
 

@N5XMT

This is what was recommended to me to by another APRS user. Once I get my radio I will figure out what I am going to do about a sound card. 

-Mike


Re: Where to start? #pi

N5XMT
 

I just picked up the FE-PI V2 board.  I think it was 15 bucks or so.  Very nice, works perfectly with direwolf

On Sep 10, 2020, at 08:51, kj7owd@... wrote:
David,

Thanks for the reply! I am checking out the link while drinking coffee now. I will say this though. Las Vegas has ONE rx/tx iGate and it is on the FAR south side of the valley 22 miles from where I live. It only puts out 9 watts (according to APRS.fi) so I can't reliably receive data from it. There is another one way iGate about half way between me and the other. Now, north of me there is NOTHING until you Reno or Ely to gate a packet. I feel that adding even TWO more rx/tx iGates in the valley will really help the entire network. Apparently the iGate south of town is getting over 40,000 packets a month and is gating everything from northern AZ, California, and all of central and southern NV. With it only putting out 9 watts a lot of those messages do not get replied. 

John,
I have seen that unfortunately it is higher than I want to spend on this project. If I cannot find another solution though I will go that way. 

N5XMT and WB2OSZ,
Thanks for the clarification. I will look at sound card options. 

Terry,
I read the article from N1AAE and that's where I got the idea for using RBPI. I don't want to go with an HT because it will be going in my attic crawl space so I don't want to use a battery eliminator and I would like to get more than 5 watts on the air. I am hoping for something closer to 25-50 watts. I hope to hear you on the air! I occasionally get to use my work radio and chat on 20m. I made my first HF contact during the Indy 500 Contest. It was really cool! I am hoping next year I can get a mobile HF rig. Maybe then I will spend more time learning CW. 

Thanks for all the replies so far. I have some homework to do. If anyone has more to add please do!
-Mike


Re: Where to start? #pi

Michael Mohaupt
 

David,

Thanks for the reply! I am checking out the link while drinking coffee now. I will say this though. Las Vegas has ONE rx/tx iGate and it is on the FAR south side of the valley 22 miles from where I live. It only puts out 9 watts (according to APRS.fi) so I can't reliably receive data from it. There is another one way iGate about half way between me and the other. Now, north of me there is NOTHING until you Reno or Ely to gate a packet. I feel that adding even TWO more rx/tx iGates in the valley will really help the entire network. Apparently the iGate south of town is getting over 40,000 packets a month and is gating everything from northern AZ, California, and all of central and southern NV. With it only putting out 9 watts a lot of those messages do not get replied. 

John,
I have seen that unfortunately it is higher than I want to spend on this project. If I cannot find another solution though I will go that way. 

N5XMT and WB2OSZ,
Thanks for the clarification. I will look at sound card options. 

Terry,
I read the article from N1AAE and that's where I got the idea for using RBPI. I don't want to go with an HT because it will be going in my attic crawl space so I don't want to use a battery eliminator and I would like to get more than 5 watts on the air. I am hoping for something closer to 25-50 watts. I hope to hear you on the air! I occasionally get to use my work radio and chat on 20m. I made my first HF contact during the Indy 500 Contest. It was really cool! I am hoping next year I can get a mobile HF rig. Maybe then I will spend more time learning CW. 

Thanks for all the replies so far. I have some homework to do. If anyone has more to add please do!
-Mike


Re: Where to start? #pi

David Ranch
 


Hello Mike,

You've already received some great details and hints on how to get started.  One thing that you need to pay attention to is that adding more iGates can actually hurt the network but that's more common when setting up high level APRS digis and Igates say on a nearby mountain, etc.  Anyway, if you're looking for more of a holistic Raspberry Pi setup guide to get everything fully built up, you might want to check out my guide:

   http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi4-setup.html

This doc should compliment the APRS specific docs that WB2OSZ (the author of Direwolf) shared.  Beyond that, there are many MANY other good guides out there on the Internet so search around and see what's available to you.

--David
KI6ZHD



On 09/09/2020 09:44 PM, KJ7OWD@... wrote:
Hello group!

I live in Vegas and am realizing that the iGate network here is severely lacking. With your help I want to set up a Rx/Tx iGate using Raspberry Pi. I just ordered my Pi 4 starter kit and am waiting to send out an email about radio's to the local club until I get a better idea on how I can interface the Tx portion to my Pi 4. The unit I ordered does come with a 4 pole stereo audio input so I am guessing I will not need a sound card hat, I think?

There are so many posts here and I am new to Groups.io I was wondering if y'all could help point me in the right direction. My goal is to run a single band antenna off of the roof of my two story house and leave my radio and Pi running in the crawl space. I already have power up there and have some idea's on where to run the coax. 

Any knowledge you would like to impart would be great! Power suggestions, radio suggestions, ways to get the radio to interface with Pi, anything you can think of would be helpful. 

Thanks in advance!
Mike
KJ7OWD
73


Re: Where to start? #pi

N5XMT
 

You will still need a sound card, as none of the Pi's have an audio input, only output.  The 4 pole trrs jack is left and right audio, composite video and ground

On Sep 9, 2020, at 21:50, kj7owd@... wrote:
Hello group!

I live in Vegas and am realizing that the iGate network here is severely lacking. With your help I want to set up a Rx/Tx iGate using Raspberry Pi. I just ordered my Pi 4 starter kit and am waiting to send out an email about radio's to the local club until I get a better idea on how I can interface the Tx portion to my Pi 4. The unit I ordered does come with a 4 pole stereo audio input so I am guessing I will not need a sound card hat, I think?

There are so many posts here and I am new to Groups.io I was wondering if y'all could help point me in the right direction. My goal is to run a single band antenna off of the roof of my two story house and leave my radio and Pi running in the crawl space. I already have power up there and have some idea's on where to run the coax. 

Any knowledge you would like to impart would be great! Power suggestions, radio suggestions, ways to get the radio to interface with Pi, anything you can think of would be helpful. 

Thanks in advance!
Mike
KJ7OWD
73


Re: Where to start? #pi

 

The RPi only has audio output.  For audio input, you will need to add some sort of audio adapter.

These documents should be useful in your quest.

https://github.com/wb2osz/direwolf/blob/dev/doc/Raspberry-Pi-APRS.pdf

https://github.com/wb2osz/direwolf/blob/dev/doc/Successful-APRS-IGate-Operation.pdf


Re: Where to start? #pi

 


On Wed, Sep 9, 2020, 21:50 <KJ7OWD@...> wrote:
Hello group!

I live in Vegas and am realizing that the iGate network here is severely lacking. With your help I want to set up a Rx/Tx iGate using Raspberry Pi. I just ordered my Pi 4 starter kit and am waiting to send out an email about radio's to the local club until I get a better idea on how I can interface the Tx portion to my Pi 4. The unit I ordered does come with a 4 pole stereo audio input so I am guessing I will not need a sound card hat, I think?

There are so many posts here and I am new to Groups.io I was wondering if y'all could help point me in the right direction. My goal is to run a single band antenna off of the roof of my two story house and leave my radio and Pi running in the crawl space. I already have power up there and have some idea's on where to run the coax. 

Any knowledge you would like to impart would be great! Power suggestions, radio suggestions, ways to get the radio to interface with Pi, anything you can think of would be helpful. 

Thanks in advance!
Mike
KJ7OWD
73


Re: Dual purpose DMR hotspot and HF digimodes

Bryan Waller
 

Thank you. That is helpful to know. Just got Pi-star up and running and my next step was to see if other apps could be installed, so that answers that question. I'll take a look at blueDV now.


Re: Where to start? #pi

Terry L. Morris
 

Hello Mike,
I have no experience with iGate network but I am schooled in Internet networking. The latter not really important. I searched this forum for iGate network and found nothing. I left this forum and went to DuckDuckGo and searched for iGate network.

I found Curtiss Mann, N1AAE of Madison, IN that has an iGate through APRS and tells how to build it for under $100. The URL is: https://n1aae.com/raspberry-pi-aprs-direwolf-linux-igate-digipeater/  APRS RX/TX iGate and digipeater for less than $100.

Have you checked for iGate's in the Las Vegas area? It would be prudent to do so. You might that your area, Las Vegas, is already saturated with sufficient iGates and learn from those have them in use.

I quickly read Curtiss' webpage and it seems doable if you have interest in that party of this glorious hobby. I prefer CW on HF and bands above.
Best 73,


Where to start? #pi

Michael Mohaupt
 

Hello group!

I live in Vegas and am realizing that the iGate network here is severely lacking. With your help I want to set up a Rx/Tx iGate using Raspberry Pi. I just ordered my Pi 4 starter kit and am waiting to send out an email about radio's to the local club until I get a better idea on how I can interface the Tx portion to my Pi 4. The unit I ordered does come with a 4 pole stereo audio input so I am guessing I will not need a sound card hat, I think?

There are so many posts here and I am new to Groups.io I was wondering if y'all could help point me in the right direction. My goal is to run a single band antenna off of the roof of my two story house and leave my radio and Pi running in the crawl space. I already have power up there and have some idea's on where to run the coax. 

Any knowledge you would like to impart would be great! Power suggestions, radio suggestions, ways to get the radio to interface with Pi, anything you can think of would be helpful. 

Thanks in advance!
Mike
KJ7OWD
73


Re: Dual purpose DMR hotspot and HF digimodes

Neon22
 

Pi-star takes over the whole pi but BlueDV can run while other apps are running.
But on the Pi - not sure if blueDV is same specs as windows version...


Re: C++ TCP code differences Pi-3 to Pi-4?

Larry K8UT
 

Bernard - That did it! THANK YOU!

I am embarrassed to admit how many hours I spent trying to solve this problem. Your fix enables users to select the hardware of their choice.

Thanks again!


Re: C++ TCP code differences Pi-3 to Pi-4?

Eric
 

What is the value of errno after the failed accept?   When you get the value of errno, you can look it up in errno.h to find the meaning.

Eric

On Wed, Sep 9, 2020, 02:49 Larry K8UT <K8UT@...> wrote:
Thanks for the hints and suggestions. On a whim, I loaded a microSD card with the beta Raspberry Pi 64 bit OS and ... it works! Fearing my success was a fluke, I loaded/reloaded microSD cards with production 32 bit versions and beta 64 bit versions, inserting them in 2gb and 8gb Pi-4 hardware. Identical results in all tests: 32 bit platform fails at socket Accept stage; 64 bit succeeds.

Here's the code. Works on 32 bit Pi-3, on 64 bit Pi-4; not on 32 bit Pi-4:
//----- get TCP Packet String from CLIENT console-----------------------
string getTcpPacketString(int localSocket ) {
 
socklen_t clilen;
struct sockaddr_in cliaddr;
int newsockfd;
 
signal(SIGCHLD, SIG_IGN);// delete zombie fork processes
// waiting for poll()
int pResult = poll(fds, nfds, timeout);
if ( pResult == -1 ) { error("ERROR on socket poll()\n"); }
if ( pResult == 0 ) { usleep(10000); return ""; } // no client connected during this cycle
 
    newsockfd = accept(localSocket, (struct sockaddr *) &cliaddr, &clilen);
    if (newsockfd < 0) {
cout << "Error on accept..." << endl;
usleep(10000);
return "-1";
//error("ERROR on accept");
}
uint maxPacketSize = 2048;
char packet_data[maxPacketSize];
memcpy(packet_data, "\0", maxPacketSize);
 
uint received_bytes = read( newsockfd, packet_data, maxPacketSize);
if (received_bytes < 0) { error("ERROR reading from socket"); }
 
string localString(packet_data);
localString = localString.substr(0, received_bytes); 
// return a substring, else that entire DIM size is returned with trailing random chars
 
close(newsockfd);
return localString;
} // end getTcpPacketString ------------------------------------------
 


Re: C++ TCP code differences Pi-3 to Pi-4?

Bernard Littau
 

Hi Larry,

Change your use of accept to accept(localSocket, NULL,NULL); and remove all the client addr and len stuff. 

I think you are getting stack garbage in your clilen parameter that is causing accept to fail.  Since you are not using the return values just get rid of them.  

Bernard
KE7FEQ 

On Wed, Sep 9, 2020 at 02:49 Larry K8UT <K8UT@...> wrote:
Thanks for the hints and suggestions. On a whim, I loaded a microSD card with the beta Raspberry Pi 64 bit OS and ... it works! Fearing my success was a fluke, I loaded/reloaded microSD cards with production 32 bit versions and beta 64 bit versions, inserting them in 2gb and 8gb Pi-4 hardware. Identical results in all tests: 32 bit platform fails at socket Accept stage; 64 bit succeeds.

Here's the code. Works on 32 bit Pi-3, on 64 bit Pi-4; not on 32 bit Pi-4:


//----- get TCP Packet String from CLIENT console-----------------------


string getTcpPacketString(int localSocket ) {


 


socklen_t clilen;


struct sockaddr_in cliaddr;


int newsockfd;


 


signal(SIGCHLD, SIG_IGN);// delete zombie fork processes


// waiting for poll()


int pResult = poll(fds, nfds, timeout);


if ( pResult == -1 ) { error("ERROR on socket poll()\n"); }


if ( pResult == 0 ) { usleep(10000); return ""; } // no client connected during this cycle


 


    newsockfd = accept(localSocket, (struct sockaddr *) &cliaddr, &clilen);


    if (newsockfd < 0) {


cout << "Error on accept..." << endl;


usleep(10000);


return "-1";


//error("ERROR on accept");


}


uint maxPacketSize = 2048;


char packet_data[maxPacketSize];


memcpy(packet_data, "\0", maxPacketSize);


 


uint received_bytes = read( newsockfd, packet_data, maxPacketSize);


if (received_bytes < 0) { error("ERROR reading from socket"); }


 


string localString(packet_data);


localString = localString.substr(0, received_bytes); 


// return a substring, else that entire DIM size is returned with trailing random chars


 


close(newsockfd);


return localString;


} // end getTcpPacketString ------------------------------------------


 









Re: C++ TCP code differences Pi-3 to Pi-4?

Larry K8UT
 

Thanks for the hints and suggestions. On a whim, I loaded a microSD card with the beta Raspberry Pi 64 bit OS and ... it works! Fearing my success was a fluke, I loaded/reloaded microSD cards with production 32 bit versions and beta 64 bit versions, inserting them in 2gb and 8gb Pi-4 hardware. Identical results in all tests: 32 bit platform fails at socket Accept stage; 64 bit succeeds.

Here's the code. Works on 32 bit Pi-3, on 64 bit Pi-4; not on 32 bit Pi-4:
//----- get TCP Packet String from CLIENT console-----------------------
string getTcpPacketString(int localSocket ) {
 
socklen_t clilen;
struct sockaddr_in cliaddr;
int newsockfd;
 
signal(SIGCHLD, SIG_IGN);// delete zombie fork processes
// waiting for poll()
int pResult = poll(fds, nfds, timeout);
if ( pResult == -1 ) { error("ERROR on socket poll()\n"); }
if ( pResult == 0 ) { usleep(10000); return ""; } // no client connected during this cycle
 
    newsockfd = accept(localSocket, (struct sockaddr *) &cliaddr, &clilen);
    if (newsockfd < 0) {
cout << "Error on accept..." << endl;
usleep(10000);
return "-1";
//error("ERROR on accept");
}
uint maxPacketSize = 2048;
char packet_data[maxPacketSize];
memcpy(packet_data, "\0", maxPacketSize);
 
uint received_bytes = read( newsockfd, packet_data, maxPacketSize);
if (received_bytes < 0) { error("ERROR reading from socket"); }
 
string localString(packet_data);
localString = localString.substr(0, received_bytes); 
// return a substring, else that entire DIM size is returned with trailing random chars
 
close(newsockfd);
return localString;
} // end getTcpPacketString ------------------------------------------
 


Re: Raspberry PI "hears" its own transmission

rvnash@...
 

Thank you gentlemen. I took John's advice first because it was easy to do. I turned down the unconnected Right channel to 0 volume, and the problem went away. So, I'll take that as a win and not try the other good suggestions from David.

Thanks again,
-- Rich
KC3ARY


Re: Raspberry PI "hears" its own transmission

 

Sometimes it is cross talk.  Adjusting alsamixer so that only the left or right channel is active (depending on your wiring), may be a solution, as well as David's list.  Direwolf is extremely sensitive so it will work to decode the faintest signal.

On Tue, Sep 8, 2020 at 12:41 PM <rvnash@...> wrote:
Hi All,

I have set up a new iGate/Digipeater as KC3ARY-7. It all seems to going well using a Raspberry PI with a Kenwood rig. You can see my documentations, such as it is, here.

The one remaining oddity seems to be that the USB sound card echos back the FSK packet from its speaker output back through its own microphone, and Direwolf interprets it as if it heard the packet over the air. It really doesn't cause any issues, but I would like to eliminate this problem.

The reason I want to fix it is that my posting of the packet to APRS-IS occurs slightly before any other iGate that actually does hear my packet, so usually it shows up as if it was an direct post to the iGate, rather than ever going out over the air.

I think it might have something to do with a purposeful feature of these USB sound cards, or maybe the alsa drivers where sound output deliberately gets fed back? Anyone else encountering this?

Thanks and 73s,
Rich KC3ARY



--
John D. Hays
Kingston, WA
K7VE

 


Re: Raspberry PI "hears" its own transmission

David Ranch
 


Hello Rich,

If you search the Direwolf email list and probably this email list, you'll find other similar reports.  Various found issues and resolutions boil down to:

   - You have RFI issues
      - move the Raspberry Pi and sound card as FAR away from the radio and the antenna as possible
      - add ferrite chokes to both sides of all cables on all devices (including power cables)
      - One way to test this is to turn off your radio and then beacon.  Do you still hear your own packets?
         - No?  Turn on the radio but put the radio on low power.  Do you still hear your own packets?  Repeat for all power levels

   - You have a sound card mixer issue:
      - your sound levels are too high
      - your mixer has "monitors" or other features enabled

--David
KI6ZHD


On 09/08/2020 12:33 PM, rvnash@... wrote:
Hi All,

I have set up a new iGate/Digipeater as KC3ARY-7. It all seems to going well using a Raspberry PI with a Kenwood rig. You can see my documentations, such as it is, here.

The one remaining oddity seems to be that the USB sound card echos back the FSK packet from its speaker output back through its own microphone, and Direwolf interprets it as if it heard the packet over the air. It really doesn't cause any issues, but I would like to eliminate this problem.

The reason I want to fix it is that my posting of the packet to APRS-IS occurs slightly before any other iGate that actually does hear my packet, so usually it shows up as if it was an direct post to the iGate, rather than ever going out over the air.

I think it might have something to do with a purposeful feature of these USB sound cards, or maybe the alsa drivers where sound output deliberately gets fed back? Anyone else encountering this?

Thanks and 73s,
Rich KC3ARY


Raspberry PI "hears" its own transmission

rvnash@...
 

Hi All,

I have set up a new iGate/Digipeater as KC3ARY-7. It all seems to going well using a Raspberry PI with a Kenwood rig. You can see my documentations, such as it is, here.

The one remaining oddity seems to be that the USB sound card echos back the FSK packet from its speaker output back through its own microphone, and Direwolf interprets it as if it heard the packet over the air. It really doesn't cause any issues, but I would like to eliminate this problem.

The reason I want to fix it is that my posting of the packet to APRS-IS occurs slightly before any other iGate that actually does hear my packet, so usually it shows up as if it was an direct post to the iGate, rather than ever going out over the air.

I think it might have something to do with a purposeful feature of these USB sound cards, or maybe the alsa drivers where sound output deliberately gets fed back? Anyone else encountering this?

Thanks and 73s,
Rich KC3ARY


ARRL/TAPR Digital Communications Virtual Conference (DCC), September 11 - 12 (THIS WEEK)

Mark Thompson
 


39th Annual ARRL / TAPR Digital Communications Conference (DCC)

THIS WEEK - Friday, September 11th & Saturday, 12th  

DCC will be a virtual conference using Zoom video communications and YouTube video-sharing platforms.

DCC information, Technical Papers, Presentation Schedule & Registration Available at: 


Registered DCC attendees participating via Zoom will be able to interact with presenters and other attendees via a chat room as well as raise a virtual hand to ask questions. 
(you don’t need a Zoom account to register).

Non-registered DCC attendees can watch the live stream for free on YouTube,
however non-registered DCC attendees will not be able to ask questions or chat.

No registration is required for YouTube access.
The YouTube URL will be announced and posted on this webpage preceding the DCC.


DCC registration is free for TAPR members and $30 for non-members.
Members receive a 100% discount at checkout. 

Non-members who would like to join TAPR and receive the free DCC pass can simply add TAPR membership and DCC registration to their shopping carts.
After checkout, they will receive the free DCC pass when their membership is processed.



--

73, Mark, WB9QZB
Mobile: +1 847 867 2774
Email: wb9qzb_groups@...
Skype: markjthompson
Zello: wb9qzb

1161 - 1180 of 13321