Date   

Re: Trouble with my Pore

Thomas Testa
 

Lynn after I over reacted and sent you multiple messages, for which I apologize, it dawned on me that the transmitting chip in my PK 232 might have blown. Today I will be using my backup to see if this is true. I will keep you posted. I appreciate your prompt response to my questions.

                    TNX , Tom N2UFM




On Monday, January 13, 2020, 10:54 PM, Lynn Deffenbaugh <kj4erj@...> wrote:

The Callsign-SSID shown in the port configuration dialog are a red herring.  They are not used and will eventually be removed.  It was a misguided attempt to give each port its own unique station ID.

The most common reason for not transmitting is a change in the TNC or radio.  What are you using on this particular port?

You may also want to check:

http://aprsisce.wikidot.com/doc:transmitting

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/13/2020 8:23 PM, Thomas Testa via Groups.Io wrote:
For some unknown reason my port has stopped working. I have not changed a thing in my configurations.I can see incoming RF packets on my scroll but can not transmit. When I go to CONFIG/PORT my callsign and SSID have disappeared.I am running Development Version 2019/01/21 17:53


Re: Trouble with my Pore

Lynn Deffenbaugh
 

The Callsign-SSID shown in the port configuration dialog are a red herring.  They are not used and will eventually be removed.  It was a misguided attempt to give each port its own unique station ID.

The most common reason for not transmitting is a change in the TNC or radio.  What are you using on this particular port?

You may also want to check:

http://aprsisce.wikidot.com/doc:transmitting

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/13/2020 8:23 PM, Thomas Testa via Groups.Io wrote:
For some unknown reason my port has stopped working. I have not changed a thing in my configurations.I can see incoming RF packets on my scroll but can not transmit. When I go to CONFIG/PORT my callsign and SSID have disappeared.I am running Development Version 2019/01/21 17:53


Trouble with my Port

Thomas Testa
 

 I don't know if my last message went through so I apologize if this is a redundant message. I am running Development Version 2019/01/21 17:53. For some unknown reason the program has stopped keying my radio. I can receive incoming packets and see RF stations on the scroll. In CONFIGURE/Ports my callsign and SSID have disappeared.


Trouble with my Pore

Thomas Testa
 

For some unknown reason my port has stopped working. I have not changed a thing in my configurations.I can see incoming RF packets on my scroll but can not transmit. When I go to CONFIG/PORT my callsign and SSID have disappeared.I am running Development Version 2019/01/21 17:53


Re: Keeping .gpx and .pos upon closing-Solved

Lynn Deffenbaugh
 

I almost never have my GPXs in the directory with APRSIS32, but always have them elsewhere.

Are you sure the other directory is available every time you started APRSIS32?  If it was a thumb drive or other removable media, APRSIS32 might have marked them unavailable if they weren't there once and then might not ever check them again.

Anyway, I'm glad you have it working, but I wish we knew exactly what was worng (sic).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/9/2020 11:51 AM, Bob KE6GYD wrote:
Set up a new beacon comment under Configure/Beacon/Comment and the check box remained on the new comment created after closing and restarting.  So it's saving the .XML config.

BUT, THE THOUGHT OCCURRED TO ME:  I was now inserting the .gpx and .pos files from a different directory than the APRSIS32 program directory.  So when I inserted them from the same directory, they stayed upon closing the program.  I presume that .XML config file only searches for them in the APRSIS32 program directory.  That's why it worked in the past and not recently. 

I don't know if there is a way to point to a different directory so the .XML file saves the configuration, but if not, no big deal now that I understand what happened.  It was just easier for me to work with the files and backup the files in a separate directory.

Thanks for getting me to do some thinking.

73
Bob
KE6GYD


Re: Keeping .gpx and .pos upon closing-Solved

Bob KE6GYD
 

Set up a new beacon comment under Configure/Beacon/Comment and the check box remained on the new comment created after closing and restarting.  So it's saving the .XML config.

BUT, THE THOUGHT OCCURRED TO ME:  I was now inserting the .gpx and .pos files from a different directory than the APRSIS32 program directory.  So when I inserted them from the same directory, they stayed upon closing the program.  I presume that .XML config file only searches for them in the APRSIS32 program directory.  That's why it worked in the past and not recently. 

I don't know if there is a way to point to a different directory so the .XML file saves the configuration, but if not, no big deal now that I understand what happened.  It was just easier for me to work with the files and backup the files in a separate directory.

Thanks for getting me to do some thinking.

73
Bob
KE6GYD


Re: Keeping .gpx and .pos upon closing

Lynn Deffenbaugh
 

It sounds like APRSIS32 is failing to write out the configuration file.

Try changing your beacon comment and closing and restarting APRSIS32 to make sure the change sticks.  If not, something is preventing the .XML configuration file from being written.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/7/2020 7:17 PM, Bob KE6GYD wrote:
Now using the latest dev version dated January, 2019.  Still not keeping the .gpx and .pos overlays on the map after closing then opening the program.  A year or so ago, I thought it did keep them, but I don't remember what may have changed as I had to manually delete the overlays then. 
Bob


Re: Keeping .gpx and .pos upon closing

Bob KE6GYD
 

Now using the latest dev version dated January, 2019.  Still not keeping the .gpx and .pos overlays on the map after closing then opening the program.  A year or so ago, I thought it did keep them, but I don't remember what may have changed as I had to manually delete the overlays then. 
Bob


Re: Keeping .gpx and .pos upon closing

Bob KE6GYD
 

And no, they are not listed under Configure/Overlays.  There are some grayed out overlay files listed, but those are not the ones I'm trying to use.
I'll let you know how the development version goes.
Thanks
Bob


Re: Keeping .gpx and .pos upon closing

Bob KE6GYD
 

It's the 2012 version.  I'll try the latest and see how that works.
Thanks
Bob


Re: Keeping .gpx and .pos upon closing

Lynn Deffenbaugh
 

APRSIS32 should be saving the GPX settings when you close the program.  Are the overlays still defined, but just not enabled?  Or are there definitions completely gone?  In other words, are they listed under Configure / Overlays after the restart?

Also, what version are you running.  I cannot state firmly what the behavior is in the 2012 General release, but only the 2019 Development version.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/7/2020 3:12 PM, Bob KE6GYD wrote:
Is there a setting I'm missing?  I have configured .gpx and .pos overlays to show a course and checkpoints. 
When I close APRSIS32, the overlays disappear when I open the program again. I'd like them to show.

Thanks & 73
Bob
KE6GYD


Keeping .gpx and .pos upon closing

Bob KE6GYD
 

Is there a setting I'm missing?  I have configured .gpx and .pos overlays to show a course and checkpoints. 
When I close APRSIS32, the overlays disappear when I open the program again. I'd like them to show.

Thanks & 73
Bob
KE6GYD


Re: Kenwood THD-7

Lynn Deffenbaugh
 

It's ok to keep the conversation here.  I'm sure there are others with D7s that could benefit or contribute.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/7/2020 9:55 AM, Steve Bunting M0BPQ wrote:
Thanks Lynn!

I didn't get the radio to respond to PuTTY so have work to do. I'll save this list from non-APRSIS32 related chatter though.

73
Steve


Re: Kenwood THD-7

Steve Bunting M0BPQ
 

Thanks Lynn!

I didn't get the radio to respond to PuTTY so have work to do. I'll save this list from non-APRSIS32 related chatter though.

73
Steve


Re: Kenwood THD-7

Lynn Deffenbaugh
 

Yes, that should be correct.  I haven't personally tested the D7, but I suspect there are some out there using one with APRSIS32.

One key would be to connect the cabling to the radio and bring up a terminal emulator.  When you switch the radio's TNC between the various modes, you should see text coming through on the terminal emulator.  Once that is verified, close the terminal emulator, put the radio into Packet (or Packet96), and fire up APRSIS32 with a KISS (not Simply(KISS)) type port configured with the same serial port and baud rate that worked in the terminal emulator.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/6/2020 7:52 AM, Steve Bunting M0BPQ wrote:

Hi everyone,

I am looking to experiment with 9K6 APRS with a local friend of mine. As I have an unused Kenwood THD-7 this becomes the obvious choice for my (70cm) I-gate. (Im aware of its limitations - but this is a bit of no cost fun)

After reading old posts on the forum, it seems that "just" setting up a new KISS port in APRSIS32 should kick the radio into KISS mode (when it is in Packet mode not APRS mode). Is that still correct? If so I need to look more closely at the provided cables etc.

Any other tips on using the radio/TNC will be gratefully accepted.

73

Steve M0BPQ


Kenwood THD-7

Steve Bunting M0BPQ
 

Hi everyone,

I am looking to experiment with 9K6 APRS with a local friend of mine. As I have an unused Kenwood THD-7 this becomes the obvious choice for my (70cm) I-gate. (Im aware of its limitations - but this is a bit of no cost fun)

After reading old posts on the forum, it seems that "just" setting up a new KISS port in APRSIS32 should kick the radio into KISS mode (when it is in Packet mode not APRS mode). Is that still correct? If so I need to look more closely at the provided cables etc.

Any other tips on using the radio/TNC will be gratefully accepted.

73

Steve M0BPQ


Re: A Question about Digipeating

KD7YZ Bob <kd7yz@...>
 

OK.
I guess I should moderate the “likelihood “ of putting it in my Farm P/U truck.
I wouldn’t say “never “..
Just that (A) no one cares where I am driving.
And (B) there are usually two working dogs in the compartment behind the driver/passenger seats where I removed the former full seats. They, fwiw, weigh 175#

They’re both curious as well as suspicious of things that don’t belong. I have had driver seats chewed to the springs when they needed to go see some threat. Some accidentally left ham gear has been marked, drugged thru mud and otherwise told to go away.

All I want to do is try to report and or work thru PSAT,S ISS and USNAP1

Since ur here. Are there any UHF APRS types of birds up there I can set my D710GA CH-B to and have meaningful packets magically appear?

Thanks for answering


--
--
KD7YZ Bob EM88LL


Re: A Question about Digipeating

Robert Bruninga
 

First of all, I can never seeing myself driving along anywhere whilst
using my D710 in any vehicle.
Not what my initial intended purpose was.
Just in case, the callsign of the mobile MUST be different from the callsign
of the receiving station because APRS ignores its own call.

Bob


Re: A Question about Digipeating

KD7YZ Bob <kd7yz@...>
 

You’d mentioned this before. However I see it differently now that I have used the Com port output of my D710.

And here is a quote from there too:

By having APRSISCE/32 monitoring the COM port, it is possible to decode and display all of the information received by the TM-D710.

I never saw a way to have APRSIS32 see the D710 port directly.
So I connected my SignaLInk to the D710 data port.
SignaLInk outputs as an Rx/Tx Soundcard.

I had to use AGWPE to make a Port of the Soundcard type. As you already knew..

And THEN I had APRSIS32 make a Soundcard Port reading the AGWPE PORT.

Is this what the wiki page is alluding to? Have APRSIS32 grab the D710GA COM port through an intermediary program?

Because those few paragraphs led me to believe I must create an APRSIS32 Kenwood D710 APRS port.

Am I getting reduced functionality?

First of all, I can never seeing myself driving along anywhere whilst using my D710 in any vehicle.
Not what my initial intended purpose was.


--
--
KD7YZ Bob EM88LL


Re: A Question about Digipeating

Rob Giuliano
 

This should explain it better:



Quoted from that page:
"APRSISCE/32 makes use of these internal commands (TC 0, TC 1) in order to assume control of the radio so it can send packets. In doing so, APRSISCE/32 sends a number of commands to the radio, including a command to set the source callsign (MYCALL). If the TM-D710 is left in control, and APRSISCE/32 is attempting to assert control, you can end up with some interesting effects. Note that APRSISCE/32 cannot provide digipeater support in this mode because the UNPROTO … VIA … command does not support used (*) path components."

Robert Giuliano
KB8RCO



On Saturday, January 4, 2020, 9:03:45 AM EST, KD7YZ Bob <kd7yz@...> wrote:


1:Fm N4PWH-10 To APDW15 Via KD7YZ-15,WIDE1*,WIDE2-1 <UI pid=F0 Len=57 >[08:40:46]
!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY  [UISS/AGWPE]

or
( and I'd asked about this "not supported stuff earlier]

WinMain:2020-01-04T13:40:46.127 Digipeating N4PWH-10 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2020-01-04T13:40:46.127 Original(N4PWH-10>APDW15,WIDE1-1,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 Transmit(N4PWH-10>APDW15,KD7YZ-15*,WIDE1*,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

The question is, why don't I see the next station that heard me DigiPeat N4PWH ?
I see a thick brownish line connection N4PWH and "ME" on the APRSIS32 map everytime he Beacons that message.
However I never see a line from "ME" to someone else who received my repeat of PWH.

There are actually two or three guys out here in Rural Appalachia, over 100 miles, on ridgelines like me, who DO include my call in their Beacon path. I have seen the brown lines and seen AGWPE-UISS Digipeat them.

I realise that technically, AGWPE->UISS caught the decode through the Signalink off the D710 Data-Port. And that UISS did the DigiPeat. So maybe no seeing I make in APRSIS32 or the D710 would make any difference.

But I thought I'd ask anyway. Any D710 users feel free to email me at mycall from ARRL.  DOT argghhhh matey.

that should be obfuscated enough to belay the spam-bots, hi hi

Thanks es HNY
--
KD7YZ Bob EM88LL


1361 - 1380 of 35335