Date
1 - 8 of 8
Digipeater talks to other digipeaters but not users
|
Dave Hunter
Can someone help me out with the XML file to edit the <DigiXform> part to digipeat properly?
|
|
|
|
Adam Mahnke
What is your current setting? Adam KC2ANT On Thu, Mar 30, 2023, 20:06 Dave Hunter <n3yfo1954@...> wrote: Can someone help me out with the XML file to edit the <DigiXform> part to digipeat properly? |
|
|
|
Rob Giuliano
There is only one xml file (aprsis32.xml), but you must ensure the application is closed when you edit it.
toggle quoted message
Show quoted text
Next, the <xdigiform> outsie (after) the RFPorts is the only one used - and used for all ports. Search the WIKI for details on setting up this function. I've hsd issues searching inside the WIKI, so best to use your regular search engine (Duckduckgo, startpage, or whatdver - even Google) with aprsis32 wiki xdigiform Robert Giuliano
|
|
|
|
Dave Hunter
Wide1,wide2 On Thu, Mar 30, 2023, 8:08 PM Adam Mahnke <kc2ant@...> wrote:
|
|
|
|
Adam Mahnke
Dave, Please take a look at http://aprsisce.wikidot.com/doc:digipeating for the correct placement and version that you are looking for. As Rob mentioned, the program must be closed while editing the xml file otherwise your changes will not be applied. Adam KC2ANT On Fri, Mar 31, 2023 at 6:58 AM Dave Hunter <n3yfo1954@...> wrote:
|
|
|
|
Rob Giuliano
Even better, post the exact line(s) in the xml that you are using to have APRSIS32 function as a DIGI.
toggle quoted message
Show quoted text
I am not near my computer to post examlpes, but the wiki is quite descriptive. ------- Robert Giuliano
|
|
|
|
Lynn Deffenbaugh
"Wide1,wide2" is never a valid path entry unless you are trying to trigger specific digipeaters whose callsign is "WIDE1" or "WIDE2". Any new paradigm digipeater term would be "WIDE1-1" or "WIDE2-1" or "WIDE2-2". Some old TNCs that don't support the new paradigm might have you configure them to react to "WIDE1" or "WIDE2", but APRSIS32 isn't one of those. In fact, if you read the wiki page that Adam has posted several times, you'll notice that APRSIS32 requires explicit rules for each path component that you expect to handle. Seeing your current <DigiXform>
entries will go far to explaining what might be happening. Also,
there are several Digi* trace logs that you should be able to find
under Enables / View Logs. Make sure you enable those logs once
you make them visible.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 3/31/2023 6:57 AM, Dave Hunter
wrote:
|
|
|
|
Ben Miller
Put this just after all the "RF Port" items... For fill-in digi: <DigiXform>WIDE1-1=WIDE1*</DigiXform> For a wide area digi you can add the following, but this will digi everything coming from the big guns. Only do this in a remote area, generally not for a home station or you will create a lot of extra unnecessary traffic. <DigiXform>WIDE2-1=WIDE2*</DigiXform> <DigiXform>WIDE2-2=WIDE2-1</DigiXform>
On Thu, Mar 30, 2023 at 7:06 PM Dave Hunter <n3yfo1954@...> wrote: Can someone help me out with the XML file to edit the <DigiXform> part to digipeat properly? |
|
|