Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
igate assistance
I have the ports setup..
KISS over TCPIP to direwolf.? APRS-IS aprsc loca FIRENET firenet.us all three ports work as expected and data appears on the map properly. however, I am unable to get traffic from firenet to transmit over the KISS port.. what i am missing? the igated station screen shows nothing.? |
The normal operation of a transmit-capable I-gate is to transmit only two types of packets:
1. text message packets from the Internet addressed to a station that the I-gate heard on local RF (i.e., there is a local RF recipient to receive the packet), and 2. the next position report packet from the sender of an above text message packet, so the RF recipient knows where the sender is. Since no FireNet station (except those that are duplicates of aprs2.net-heard RF stations) would ever be heard on RF or send text messages to an RF station that your I-gate heard, the packets from the FireNet sensors would never meet either of the above rules and therefore would never automatically be forwarded to RF by the APRS-IS servers and I-gate logic. Now, it is theoretically possible to force transmitting additional APRS-IS packets (which could include FireNet) to RF, but you need to ask yourself, "WHY are you forcing this additional traffic?" Those packets are on FireNet instead of regular APRS-IS for a reason. They aren't being sent by stations licensed in the Amateur Radio Service, they are being sent at rather high transmission rates which could easily overload the limited bandwidth of a 1200-baud RF channel, and they aren't addressed specifically to RF stations in the immediate vicinity of your I-gate station. So, unless said packets are of interest to a large proportion of the RF stations local to your I-gate, they shouldn't be forced onto RF. Even if the packets _are_ truly of interest to local RF stations, you should be _extremely_ selective of what you force onwards to prevent channel overload, i.e., if you are forwarding earthquake sensors, only forward ones within the RF range of your I-gate, not every earthquake sensor on the planet. Someone on RF in Chicago doesn't really care about sensor reports in Beijing, China or vice versa (if they did, they would have an Internet connection to the FireNet themselves to get the distant data). Remember, as a transmit-capable I-gate operator, YOU are legally responsible for anything you forward to RF. Note that the same reasoning applies to the non-amateur-radio weather stations on the CWOP network. So please don't break your local RF channel by flooding it with unlicensed FireNet traffic. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Glen Briggs <kb0rpj.glen@...> Sent: Saturday, October 14, 2023 10:46 PM I have the ports setup.. KISS over TCPIP to direwolf. APRS-IS aprsc loca FIRENET firenet.us all three ports work as expected and data appears on the map properly. however, I am unable to get traffic from firenet to transmit over the KISS port.. what i am missing? the igated station screen shows nothing. |
Fire net traffic would clog up the channel? On Oct 14, 2023 10:46 PM, Glen Briggs <kb0rpj.glen@...> wrote: I have the ports setup.. |
to navigate to use esc to dismiss