Date   

KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

KD7YZ Bob <kd7yz@...>
 

I have the D710 APRS port config box set with every box checked (on) except No-Gate-ME is unchecked.

Something I do notice, and keep seeing from port to port, is that when I just checked that D710 APRS port, the SSID name is missing (KD7YZ-15) and the comment line is now also blank/greyed-out.

yet the status at the top of the scroll column rotates through KWD710(APRS) OK


so is it or isn't it?

-------------------------------------------------------------------
WinMain:2019-11-07T19:40:19.771 Restore Saved ALWAYS Enable
WinMain:2019-11-07T20:00:35.436 Digipeating N4TNA-9 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2019-11-07T20:00:35.436 Original(N4TNA-9>SX2Y0P,WIDE1-1,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 Transmit(N4TNA-9>SX2Y0P,KD7YZ-15*,WIDE1*,WIDE2-1:`nCYlfyv/`"5w}Monitoring the KG4DVE Repeater_%)
WinMain:2019-11-07T20:00:35.436 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
----------------------------------------------------------------------------

Not sure where to look for this as UIDIG is "ON".

--
73
Bob KD7YZ
AMSAT LM #901


Re: Trying to understand the Log from "Port(KWD710(Pkt)"-- Solved

KD7YZ Bob <kd7yz@...>
 

I discovered that the setup did not like me using VSPE Virtual Serial Port Emulator. I'd made COM4:, the D710GA Port virtual to COM12: (for sundry reasons.


now I see a brief listing which ended quite a while ao)

WinMain:2019-11-07T19:40:20.070 Starting Port(KWD710(APRS))
Port(KWD710(APRS)):2019-11-07T19:40:20.070 CpReader Running on COM4:9600,N,8,1 (31 OpenCmds, 6 CloseCmds)
Port(KWD710(APRS)):2019-11-07T19:40:20.070 Opening COM4:9600,N,8,1
Port(KWD710(APRS)):2019-11-07T19:40:20.071 Opening COM4 with 4 Args
Port(KWD710(APRS)):2019-11-07T19:40:20.075 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 31 OpenCmds

------------------------------------------------------------------------------


now I see the next problem which I shall open in another thread.

Bob KD7YZ


Re: Download and install

Lynn Deffenbaugh
 

You need to delete the APRSIS32.XML file that is in the directory where you execute APRSIS32 from.  That way it will recreate all settings.

The bar you describe though, appears when you're executing APRSIS32 from within the downloaded .ZIP file.  You need to UNZIP the download into a newly created empty directory and then double-click APRSIS32.EXE from within that directory, not from within a zip file viewer.

You might want to check out the Initial Startup video at:

http://aprsisce.wikidot.com/initial-startup


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

On 11/6/2019 11:39 AM, Gurdon Wolfe via Groups.Io wrote:
I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW






Re: Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob <kd7yz@...>
 

So I just deleted most "Ports" ... leaving the ore-configured NMEA and APRs-IS

I made a new port from the Drop-Down ...

Port(KWD710(APRS)

checked ALL the boxes just in case I might leave one un-checked that was supposed to be "ON".

APRSIS32 (min) has beaconing ON, fwiw

Enable Ports "ALL", Log All
RX... -- unchecked

and here is what I see, again


------------------------------------------------------
Port(KWD710(APRS)):2019-11-07T12:20:23.456 Missed Expected Response(cmd:) From Command(^M~!cmd:!1)
WinMain:2019-11-07T12:23:11.155 Stopping Port(KWD710(APRS))
WinMain:2019-11-07T12:23:11.155 Waiting at line 742
WinMain:2019-11-07T12:23:11.256 Waiting at line 742
WinMain:2019-11-07T12:23:11.357 Waiting at line 742
Port(KWD710(APRS)):2019-11-07T12:23:11.426 Terminating after 331330 msec vs 0 Quiet
Port(KWD710(APRS)):2019-11-07T12:23:11.426 Closing COM12:9600,N,8,1
WinMain:2019-11-07T12:23:11.457 Waiting at line 2877
---------------------------------------------------------

I need some serious assistance here.


Bob KD7YZ with a month old TM D710GA and APRSIS32 which are way smarter than me.


Re: Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob <kd7yz@...>
 

Well, I spoke too soon.
With cable in the COM port on the D710 Display, lookie what I see, again:

-------------------------------------------------------------------
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Terminating after 240279 msec vs 240000 Quiet
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Closing COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Command[2]:^M
Port(KWD710(Pkt)):2019-11-07T11:55:57.384 Output[2]:<0D 0D>
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Missed Expected Response(cmd:) From Command(^M!cmd:!1)
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Command[5]:LTM 0
Port(KWD710(Pkt)):2019-11-07T11:55:59.386 Output[6]:LTM 0<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Missed Expected Response(cmd:) From Command(LTM 0)
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Command[4]:TC 1
Port(KWD710(Pkt)):2019-11-07T11:56:01.386 Output[5]:TC 1<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Missed Expected Response(TS 1) From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Command[6]:TN 0,0
Port(KWD710(Pkt)):2019-11-07T11:56:03.387 Output[7]:TN 0,0<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Missed Expected Response(TN 0,0) From Command(TN 0,0!TN 0,0)
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Restarting Reader...
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 CpReader Running on COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Packet Length 64 Version 2
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:ServiceMask 0x1 Reserved1 0x0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:MaxQueue Tx 0 Rx 0 Baud 268435456
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Provider SubType 1 Capabilities 0xFF
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Settable Params 127 Baud 0x10000FFF Data 0xF StopParity 0x1F07
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Current Queue Tx 0 Rx 0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 COM12:Provider Specifics 0x0 0x0
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 CpOpen:Port COM12 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(0) !InXoff(0) DTR_ENABLE !DSRSense RTS_ENABLE
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Opened COM12:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Command[7]:^C^C^C~
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Output[3]:<03 03 03>
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Command[4]:TC 1
Port(KWD710(Pkt)):2019-11-07T11:56:05.388 Output[5]:TC 1<0D>
Port(KWD710(Pkt)):2019-11-07T11:56:06.389 CmdResp[12]:?<0D>?<0D>?<0D>?<0D>?<0D>?<0D>
---------------------------------------------------------------------------

Bob KD7YZ


Re: Trying to understand the Log from "Port(KWD710(Pkt)"

Randy Love
 

Yeah, those RT systems cables are pretty solid... 
They used the FTDI chip set, so they aren't nearly as flakey as cheaper USB dongles.
I had a Keyspan once... key word being HAD... it was never reliable for me, so I give it to someone that swore by them.. 
I'm sure he swore AT that one tho...

73,
Randy
WF5X


On Wed, Nov 6, 2019 at 6:06 PM KD7YZ Bob <kd7yz@...> wrote:
On 11/6/2019 11:19, Randy Love wrote:
> Just a quick check, the cable is into the back of the control head, correct?
>
> Randy
> WF5X

Crikey!
So today I used the programing from RT Systems ... THEN never unplugged
from the back to put it back on the Control display box.

Thanks. And before I ask the next in a line of "How do I do this"
questions, I will pull the list and see if they exist when the cables go
to the right places.

I am using the USB-K5G Radio Cable that came with theTM-D710G Programmer.

Previously I was using a Keyspan which converted the Rig's RS232 to USB
...HOWEVER, I had a lot of trouble with the Keyspan "going missing" on
my Dell ....I tried activating (did) the COM1: and jut plugging in the
serial cable as designed ....Dev Man showed COM1: at 9600b but the
computer never saw the rig on COM1 ..... thus I decided to use the RT
systems' already programmed cable.

But it would help if I plugged it back onto the "COM" socket instead of
leaving it on "PC" .

thanks for the help.

--
73
Bob KD7YZ
AMSAT LM #901




Re: Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob <kd7yz@...>
 

On 11/6/2019 11:19, Randy Love wrote:
Just a quick check, the cable is into the back of the control head, correct?
Randy
WF5X
Crikey!
So today I used the programing from RT Systems ... THEN never unplugged from the back to put it back on the Control display box.

Thanks. And before I ask the next in a line of "How do I do this" questions, I will pull the list and see if they exist when the cables go to the right places.

I am using the USB-K5G Radio Cable that came with theTM-D710G Programmer.

Previously I was using a Keyspan which converted the Rig's RS232 to USB ...HOWEVER, I had a lot of trouble with the Keyspan "going missing" on my Dell ....I tried activating (did) the COM1: and jut plugging in the serial cable as designed ....Dev Man showed COM1: at 9600b but the computer never saw the rig on COM1 ..... thus I decided to use the RT systems' already programmed cable.

But it would help if I plugged it back onto the "COM" socket instead of leaving it on "PC" .

thanks for the help.

--
73
Bob KD7YZ
AMSAT LM #901


Download and install

Gurdon Wolfe
 

I changed a setting on the installed APRSIS32 and was unable to get it corrected. I thought I'll just delete it
and start over, however when I downloaded it from the website things went bad from there. After downloading 
it and tried to run it, a screen came up with this warning:  Downloading from 2012/08/30 09:19 to  2012/08/29 
21:31 is NOT recommenced, continue anyway? (NOTE: some settings may be lost.). I answered yes and the
program began to load but after a second or two a bar appeared across the screen and began to pulse and
continued to pulse indefinitely. To the best of my knowledge I've deleted all of the old files associated with
APRSIS32. I have attempted this procedure many times all with no success. Any help would be greatly
appreciated.


 73, Don
 W4GCW


Where am I? Click link below.
https://aprs.fi/#!call=a%2FW4GCW-9&timerange=3600&tail=3600







Re: Trying to understand the Log from "Port(KWD710(Pkt)"

Randy Love
 

Just a quick check, the cable is into the back of the control head, correct?

Randy
WF5X

On Wed, Nov 6, 2019 at 10:52 AM KD7YZ Bob <kd7yz@...> wrote:
when I look at Configure- Port and Port(KWD710(Pkt), the box seems complete.

Enables Port Port(KWD710(Pkt) is checked.

Yet if I view the log I see a repeating :
-------------------------------------------
WinMain:2019-11-06T15:45:02.082 Starting Port(KWD710(Pkt))
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 CpReader Running on
COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-06T15:45:02.083 Opened COM12:9600,N,8,1,
Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-06T15:45:04.084 Missed Expected Response(?)
 From Command(TC 1!?)
Port(KWD710(Pkt)):2019-11-06T15:45:06.084 Missed Expected Response(TS 1)
 From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:45:08.085 Missed Expected Response(TN
2,0) From Command(TN 2,0!TN 2,0)
Port(KWD710(Pkt)):2019-11-06T15:45:13.087 Missed Expected Response(cmd:)
 From Command(^M!cmd:!5)
Port(KWD710(Pkt)):2019-11-06T15:45:15.087 Missed Expected Response(cmd:)
 From Command(DIG OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:17.088 Missed Expected Response(cmd:)
 From Command(GB 4800)
Port(KWD710(Pkt)):2019-11-06T15:45:19.089 Missed Expected Response(cmd:)
 From Command(HB 1200)
Port(KWD710(Pkt)):2019-11-06T15:45:21.089 Missed Expected Response(cmd:)
 From Command(GPST $GPRMC)
Port(KWD710(Pkt)):2019-11-06T15:45:23.090 Missed Expected Response(cmd:)
 From Command(LTM 10)
Port(KWD710(Pkt)):2019-11-06T15:45:24.091 Missed Expected Response(cmd:)
 From Command(LTMH OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:26.091 Missed Expected Response(cmd:)
 From Command(LOC E 0)
Port(KWD710(Pkt)):2019-11-06T15:45:28.092 Missed Expected Response(cmd:)
 From Command(M ON)
Port(KWD710(Pkt)):2019-11-06T15:45:30.093 Missed Expected Response(cmd:)
 From Command(MCOM ON)
Port(KWD710(Pkt)):2019-11-06T15:45:32.094 Missed Expected Response(cmd:)
 From Command(MS OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:34.094 Missed Expected Response(cmd:)
 From Command(CONO OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:36.095 Missed Expected Response(cmd:)
 From Command(P 250)
Port(KWD710(Pkt)):2019-11-06T15:45:38.095 Missed Expected Response(cmd:)
 From Command(UI OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:40.097 Missed Expected Response(cmd:)
 From Command(UIF NOID)
Port(KWD710(Pkt)):2019-11-06T15:45:42.098 Missed Expected Response(cmd:)
 From Command(UIT %)
Port(KWD710(Pkt)):2019-11-06T15:45:44.099 Missed Expected Response(cmd:)
 From Command(X OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:46.099 Missed Expected Response(cmd:)
 From Command(HEADER OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:48.099 Missed Expected Response(cmd:)
 From Command(NE ON)
Port(KWD710(Pkt)):2019-11-06T15:45:50.100 Missed Expected Response(cmd:)
 From Command(NO OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:52.101 Missed Expected Response(cmd:)
 From Command(ECHO OFF!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:45:54.102 Missed Expected Response(cmd:)
 From Command(BEACON EVERY 0!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:45:56.103 Missed Expected Response(cmd:)
 From Command(ECHO OFF!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:45:58.103 Missed Expected Response(cmd:)
 From Command(BEACON EVERY 0!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:49:02.239 Terminating after 240156 msec
vs 240000 Quiet
Port(KWD710(Pkt)):2019-11-06T15:49:02.239 Closing COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:49:04.240 Missed Expected Response(cmd:)
 From Command(^M!cmd:!1)
Port(KWD710(Pkt)):2019-11-06T15:49:06.241 Missed Expected Response(cmd:)
 From Command(LTM 0)
Port(KWD710(Pkt)):2019-11-06T15:49:08.241 Missed Expected Response(TS 1)
 From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Missed Expected Response(TN
0,0) From Command(TN 0,0!TN 0,0)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Restarting Reader...
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 CpReader Running on
COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opened COM12:9600,N,8,1,
Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-06T15:49:12.244 Missed Expected Response(?)
 From Command(TC 1!?)
Port(KWD710(Pkt)):2019-11-06T15:49:14.244 Missed Expected Response(TS 1)
 From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:49:15.244 Missed Expected Response(TN
2,0) From Command(TN 2,0!TN 2,0)
Port(KWD710(Pkt)):2019-11-06T15:49:20.245 Missed Expected Response(cmd:)
 From Command(^M!cmd:!5)
Port(KWD710(Pkt)):2019-11-06T15:49:22.246 Missed Expected Response(cmd:)
 From Command(DIG OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:23.246 Missed Expected Response(cmd:)
 From Command(GB 4800)
Port(KWD710(Pkt)):2019-11-06T15:49:25.247 Missed Expected Response(cmd:)
 From Command(HB 1200)
Port(KWD710(Pkt)):2019-11-06T15:49:27.247 Missed Expected Response(cmd:)
 From Command(GPST $GPRMC)
Port(KWD710(Pkt)):2019-11-06T15:49:29.248 Missed Expected Response(cmd:)
 From Command(LTM 10)
Port(KWD710(Pkt)):2019-11-06T15:49:31.249 Missed Expected Response(cmd:)
 From Command(LTMH OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:33.250 Missed Expected Response(cmd:)
 From Command(LOC E 0)
Port(KWD710(Pkt)):2019-11-06T15:49:35.250 Missed Expected Response(cmd:)
 From Command(M ON)
Port(KWD710(Pkt)):2019-11-06T15:49:37.251 Missed Expected Response(cmd:)
 From Command(MCOM ON)
Port(KWD710(Pkt)):2019-11-06T15:49:38.252 Missed Expected Response(cmd:)
 From Command(MS OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:40.253 Missed Expected Response(cmd:)
 From Command(CONO OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:41.253 Missed Expected Response(cmd:)
 From Command(P 250)
Port(KWD710(Pkt)):2019-11-06T15:49:43.254 Missed Expected Response(cmd:)
 From Command(UI OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:45.255 Missed Expected Response(cmd:)
 From Command(UIF NOID)
Port(KWD710(Pkt)):2019-11-06T15:49:46.255 Missed Expected Response(cmd:)
 From Command(UIT %)
Port(KWD710(Pkt)):2019-11-06T15:49:48.256 Missed Expected Response(cmd:)
 From Command(X OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:49.256 Missed Expected Response(cmd:)
 From Command(HEADER OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:51.257 Missed Expected Response(cmd:)
 From Command(NE ON)
Port(KWD710(Pkt)):2019-11-06T15:49:53.258 Missed Expected Response(cmd:)
 From Command(NO OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:54.259 Missed Expected Response(cmd:)
 From Command(ECHO OFF!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:49:55.259 Missed Expected Response(cmd:)
 From Command(BEACON EVERY 0!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:49:57.260 Missed Expected Response(cmd:)
 From Command(ECHO OFF!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:49:59.261 Missed Expected Response(cmd:)
 From Command(BEACON EVERY 0!cmd:!1.00)
---------------------------------------------------------------------------


why is that ?

thanks





--
--
73
Bob KD7YZ
AMSAT LM #901




Trying to understand the Log from "Port(KWD710(Pkt)"

KD7YZ Bob <kd7yz@...>
 

when I look at Configure- Port and Port(KWD710(Pkt), the box seems complete.

Enables Port Port(KWD710(Pkt) is checked.

Yet if I view the log I see a repeating :
-------------------------------------------
WinMain:2019-11-06T15:45:02.082 Starting Port(KWD710(Pkt))
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 CpReader Running on COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:45:02.082 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-06T15:45:02.083 Opened COM12:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-06T15:45:04.084 Missed Expected Response(?) From Command(TC 1!?)
Port(KWD710(Pkt)):2019-11-06T15:45:06.084 Missed Expected Response(TS 1) From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:45:08.085 Missed Expected Response(TN 2,0) From Command(TN 2,0!TN 2,0)
Port(KWD710(Pkt)):2019-11-06T15:45:13.087 Missed Expected Response(cmd:) From Command(^M!cmd:!5)
Port(KWD710(Pkt)):2019-11-06T15:45:15.087 Missed Expected Response(cmd:) From Command(DIG OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:17.088 Missed Expected Response(cmd:) From Command(GB 4800)
Port(KWD710(Pkt)):2019-11-06T15:45:19.089 Missed Expected Response(cmd:) From Command(HB 1200)
Port(KWD710(Pkt)):2019-11-06T15:45:21.089 Missed Expected Response(cmd:) From Command(GPST $GPRMC)
Port(KWD710(Pkt)):2019-11-06T15:45:23.090 Missed Expected Response(cmd:) From Command(LTM 10)
Port(KWD710(Pkt)):2019-11-06T15:45:24.091 Missed Expected Response(cmd:) From Command(LTMH OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:26.091 Missed Expected Response(cmd:) From Command(LOC E 0)
Port(KWD710(Pkt)):2019-11-06T15:45:28.092 Missed Expected Response(cmd:) From Command(M ON)
Port(KWD710(Pkt)):2019-11-06T15:45:30.093 Missed Expected Response(cmd:) From Command(MCOM ON)
Port(KWD710(Pkt)):2019-11-06T15:45:32.094 Missed Expected Response(cmd:) From Command(MS OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:34.094 Missed Expected Response(cmd:) From Command(CONO OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:36.095 Missed Expected Response(cmd:) From Command(P 250)
Port(KWD710(Pkt)):2019-11-06T15:45:38.095 Missed Expected Response(cmd:) From Command(UI OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:40.097 Missed Expected Response(cmd:) From Command(UIF NOID)
Port(KWD710(Pkt)):2019-11-06T15:45:42.098 Missed Expected Response(cmd:) From Command(UIT %)
Port(KWD710(Pkt)):2019-11-06T15:45:44.099 Missed Expected Response(cmd:) From Command(X OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:46.099 Missed Expected Response(cmd:) From Command(HEADER OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:48.099 Missed Expected Response(cmd:) From Command(NE ON)
Port(KWD710(Pkt)):2019-11-06T15:45:50.100 Missed Expected Response(cmd:) From Command(NO OFF)
Port(KWD710(Pkt)):2019-11-06T15:45:52.101 Missed Expected Response(cmd:) From Command(ECHO OFF!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:45:54.102 Missed Expected Response(cmd:) From Command(BEACON EVERY 0!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:45:56.103 Missed Expected Response(cmd:) From Command(ECHO OFF!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:45:58.103 Missed Expected Response(cmd:) From Command(BEACON EVERY 0!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:49:02.239 Terminating after 240156 msec vs 240000 Quiet
Port(KWD710(Pkt)):2019-11-06T15:49:02.239 Closing COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:49:04.240 Missed Expected Response(cmd:) From Command(^M!cmd:!1)
Port(KWD710(Pkt)):2019-11-06T15:49:06.241 Missed Expected Response(cmd:) From Command(LTM 0)
Port(KWD710(Pkt)):2019-11-06T15:49:08.241 Missed Expected Response(TS 1) From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Missed Expected Response(TN 0,0) From Command(TN 0,0!TN 0,0)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Restarting Reader...
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 CpReader Running on COM12:9600,N,8,1 (29 OpenCmds, 4 CloseCmds)
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opening COM12:9600,N,8,1
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opening COM12 with 4 Args
Port(KWD710(Pkt)):2019-11-06T15:49:10.242 Opened COM12:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 29 OpenCmds
Port(KWD710(Pkt)):2019-11-06T15:49:12.244 Missed Expected Response(?) From Command(TC 1!?)
Port(KWD710(Pkt)):2019-11-06T15:49:14.244 Missed Expected Response(TS 1) From Command(TC 1!TS 1)
Port(KWD710(Pkt)):2019-11-06T15:49:15.244 Missed Expected Response(TN 2,0) From Command(TN 2,0!TN 2,0)
Port(KWD710(Pkt)):2019-11-06T15:49:20.245 Missed Expected Response(cmd:) From Command(^M!cmd:!5)
Port(KWD710(Pkt)):2019-11-06T15:49:22.246 Missed Expected Response(cmd:) From Command(DIG OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:23.246 Missed Expected Response(cmd:) From Command(GB 4800)
Port(KWD710(Pkt)):2019-11-06T15:49:25.247 Missed Expected Response(cmd:) From Command(HB 1200)
Port(KWD710(Pkt)):2019-11-06T15:49:27.247 Missed Expected Response(cmd:) From Command(GPST $GPRMC)
Port(KWD710(Pkt)):2019-11-06T15:49:29.248 Missed Expected Response(cmd:) From Command(LTM 10)
Port(KWD710(Pkt)):2019-11-06T15:49:31.249 Missed Expected Response(cmd:) From Command(LTMH OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:33.250 Missed Expected Response(cmd:) From Command(LOC E 0)
Port(KWD710(Pkt)):2019-11-06T15:49:35.250 Missed Expected Response(cmd:) From Command(M ON)
Port(KWD710(Pkt)):2019-11-06T15:49:37.251 Missed Expected Response(cmd:) From Command(MCOM ON)
Port(KWD710(Pkt)):2019-11-06T15:49:38.252 Missed Expected Response(cmd:) From Command(MS OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:40.253 Missed Expected Response(cmd:) From Command(CONO OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:41.253 Missed Expected Response(cmd:) From Command(P 250)
Port(KWD710(Pkt)):2019-11-06T15:49:43.254 Missed Expected Response(cmd:) From Command(UI OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:45.255 Missed Expected Response(cmd:) From Command(UIF NOID)
Port(KWD710(Pkt)):2019-11-06T15:49:46.255 Missed Expected Response(cmd:) From Command(UIT %)
Port(KWD710(Pkt)):2019-11-06T15:49:48.256 Missed Expected Response(cmd:) From Command(X OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:49.256 Missed Expected Response(cmd:) From Command(HEADER OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:51.257 Missed Expected Response(cmd:) From Command(NE ON)
Port(KWD710(Pkt)):2019-11-06T15:49:53.258 Missed Expected Response(cmd:) From Command(NO OFF)
Port(KWD710(Pkt)):2019-11-06T15:49:54.259 Missed Expected Response(cmd:) From Command(ECHO OFF!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:49:55.259 Missed Expected Response(cmd:) From Command(BEACON EVERY 0!cmd:!1.0)
Port(KWD710(Pkt)):2019-11-06T15:49:57.260 Missed Expected Response(cmd:) From Command(ECHO OFF!cmd:!1.00)
Port(KWD710(Pkt)):2019-11-06T15:49:59.261 Missed Expected Response(cmd:) From Command(BEACON EVERY 0!cmd:!1.00)
---------------------------------------------------------------------------


why is that ?

thanks





--
--
73
Bob KD7YZ
AMSAT LM #901


Re: MultiTrack window sizing problem

Lynn Deffenbaugh
 

Make sure you do not have the main window maximized when APRSIS32 is closed.  With a maximized window, some settings are not saved.

On the MultiTrack, get one set up the way you want it and then hit each of the Preferred options: Percent, Size, and Zoom.  If you want MultiTracks to open in View / None, you can hit that one also.

If that doesn't do what you're after, post here again.

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

On 11/5/2019 7:58 PM, Arnold Harding. - KQ6DI wrote:
Why doesn't the MultiTrack window ever come up in the last window size that was used, or ANY useful window size I've previously used?????  This is very annoying.  EVERY time I use a MultiTrack window is is a larger size than my screen, so it must be manually reduced, AND the display is almost completely dark so I ALWAYS need to press the keys to lighten the screen.
The main window for APRSISCE/32 is just fine.  It's just the MultiTrack window.
HELP !
Arnold, KQ6DI


MultiTrack window sizing problem

Arnold Harding - KQ6DI
 

Why doesn't the MultiTrack window ever come up in the last window size that was used, or ANY useful window size I've previously used?????  This is very annoying.  EVERY time I use a MultiTrack window is is a larger size than my screen, so it must be manually reduced, AND the display is almost completely dark so I ALWAYS need to press the keys to lighten the screen.
The main window for APRSISCE/32 is just fine.  It's just the MultiTrack window.
HELP !
Arnold, KQ6DI


Re: GPS problem

Lynn Deffenbaugh
 

Roy,

You found the thing I saw immediately, so all is good.  You probably just need to make sure the device is in full view of the sky, at least to get the initial fix and the almanac to get updated.  After that it might be able to hang onto a fix for longer.

You can turn off the red dot by unchecking Configure / Screen RedDot if you want.  And if you want to know what it's about, see:

http://aprsisce.wikidot.com/doc:red-dothttp://aprsisce.wikidot.com/doc:red-dot


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

On 11/4/2019 10:54 AM, Roy Schulz wrote:
Lynn, I appear to have found the answer. Looking at the data file I attached I noticed one of the sentences mentioned only a single satellite was in view, Of course this is not enough for a fix.

I tried a few computer reboots and finally when I left your program running for awhile it started showing satellites. Though watching the red dot bounce around can be distracting, hi.

Still not got soliid gps performance, but it looks like the cause is outside your program so I'll stop bothering you. Tthanks for your help and the fine software.

regards, Roy


Re: GPS problem

Roy VE7DH
 

Lynn, I appear to have found the answer. Looking at the data file I attached I noticed one of the sentences mentioned only a single satellite was in view, Of course this is not enough for a fix.

I tried a few computer reboots and finally when I left your program running for awhile it started showing satellites. Though watching the red dot bounce around can be distracting, hi.

Still not got soliid gps performance, but it looks like the cause is outside your program so I'll stop bothering you. Tthanks for your help and the fine software.

regards, Roy


Re: GPS problem

Roy VE7DH
 

Thanks, Lynn

GPS data attached.

regards, Roy


Re: GPS problem

Lynn Deffenbaugh
 

Please open and enable the NMEA trace log and capture some of the sentences from it.  I can compare them to the code and figure out which one is saying there is no fix.

And it may be that your internal GPS doesn't provide the sentences that give the satellite information.


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

On 11/3/2019 9:22 PM, Roy Schulz wrote:
Using Win 10/64 on a Panasonic Toughbook with built-in gps. Windows sees the gps on Com3, 4800b and other programs have no problems using the gps.

The NMEA port is set to Com3, 4800b and the GPS is enabled.

Enabling the NMEA log shows the expected data string scrolling from the gps.

The main screen tells me that NMEA is OK, however it also tells me there is no fix. There is no gps satellite info at all.

Thoughts?

regards, Roy


GPS problem

Roy VE7DH
 

Using Win 10/64 on a Panasonic Toughbook with built-in gps. Windows sees the gps on Com3, 4800b and other programs have no problems using the gps.

The NMEA port is set to Com3, 4800b and the GPS is enabled.

Enabling the NMEA log shows the expected data string scrolling from the gps.

The main screen tells me that NMEA is OK, however it also tells me there is no fix. There is no gps satellite info at all.

Thoughts?

regards, Roy


Re: Triggers

Julian
 

Hi Lynn. Only to let you know I have tried APRSISMO on my Samsung phone with Mobilinkd + HT. It works great. Many thanks, 73, de J, M0IPU YO3FCA


Re: Blocking a digipeater from digi'ing my beacon

Robert Bruninga
 

There is also a problem of not using WIDE1-1.  In Northern California, a majority of the digipeaters do not respond to anything more than WIDE1-1,  So if your mobile has a path of WIDE2-1, you will get very few of your position reports ever being heard.

 

That is an improperly configured digipeater.  Yes, in areas with mountain digis and large populations, those digis can greatly reduce congestion by being configured to 1 hop only.  But they shoud do that by simply adding WIDE1-1, WIDE2-1, WIDE2-2 as unique calls in the UIDIGI list.  In that list  each of those is not ttreated as a WIDEn-N process, but simply as a unique call.  There fore it is digipeated once, and marked as use.  Thus they all go one hop and one hop only.  Not repeated again by any lower more local digis.

 

If the digis are not properly configured, then fix the digis.  There is a section on 1-hop digis on the main APRS guidance page http://aprs.org/fix14439.html

 

Bob, WB4APR

 

On October 24, 2019 at 12:39 PM James Ewen <ve6srv@...> wrote:

And to clarify another point, no fixed station should be using WIDE1-1 as a hop request. 

 

WIDE1-1 is intended to be used as a request from low powered stations for an extra helping hand from home stations to get heard by the main digipeaters (if required). 

 

Improper use of WIDE1-1 as a first hop request by high powered stations such as mobiles and home stations causes excessive local digipeats by home stations, and possible dupes by main digipeaters. 

 

People using WIDE1-1 improperly can make others attempting to act on WIDE1-1 to improve the digipeater network shut down their home WIDE1-1 digipeaters because of abuse and interference, thereby ruining the network for all. 

All digipeaters *should* respond to their assigned callsign/alias if implemented properly. 

Furthermore, if you are attempting to observe whether the RF network is working properly, you should observe the activity of the RF network directly by looking at what you can hear/see on the RF network. 

 

Don’t attempt to observe the RF network by looking at what you can see on APRS-IS connected sites like APRS.fi or other online sites. The data available there is heavily filtered, and provides only a minor portion of the information available. 

 

Listen to and observe the packets being delivered by the RF network. If you are trying to observe operation of a digipeater outside of your local reception range, you can set a path that will go out to the far digipeater and back. If you hear the packet come back, then it was successfully handled by the digipeaters in the used portion of the digi path segment of the packet. 

 

Note that the APRS network is unconnected, and may not always deliver your packets successfully. Also most APRS networks are heavily overloaded and cannot reliably handle the normal day to day traffic on them. Also long paths are not recommended for normal use as it causes heavy network loads, leading to that heavy network load that makes the networks unreliable. 

 

Having said all that, yes, you can do things to test and observe exactly what you want to do. 


 


Re: Blocking a digipeater from digi'ing my beacon

Robert Bruninga
 

Your first sentence is correct.  Beginning a path with WIDE1-1, is only for mobiles and not for fixed stations.  Fixed stations can more efficiently just use WIDE2-2 and it makes every packet 7 bytes shorter, thus improving capacity and lso avoiding bringing up neighboring home WIDE1-1’s.

 

The second sentence is simply wrong.  A misguided approach due to a failure to address the “problem” which is a well placed fixed station, improperly beginning his path with WIDE1-1.

 

Bob, WB4APR

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of KP3FT via Groups.Io
Sent: Friday, October 25, 2019 4:50 AM
To: aprsisce@groups.io
Subject: Re: [APRSISCE] Blocking a digipeater from digi'ing my beacon

 

"If however high powered stations use WIDE1-1, there’s a potential for many home stations to hear the request and act upon it, causing lots of potential noise on the channel. The solution then is to shut down the home WIDE1-1 digipeaters, thereby removing the ability for low powered stations to get help from a nearby home station."

 

"I sent an email to Bob Bruninga asking him if what I was seeing was what was to be expected. His response was 'I don’t know, I’ve never seen a properly implemented APRS network at work.'"

 

It sounds like a "proper" APRS network is actually just theoretical; not possible in reality?  Or is it possible but needs the perfect geography with the perfect number and spacing of digipeaters with associated perfect paths?  Is that what you have in Alberta?  If so, what are the "proper" settings you use?

 

I'm not being flippant, just genuinely curious.  There's an abundance of conflicting information on the internet.  WIDE1-1 is good... WIDE1-1 is bad.  Never use WIDE2-2... it's good to use WIDE2-2.  Use WIDE3-3... never, ever, ever use WIDE3-3.  Never use RX-only iGates... RX-only iGates are wonderful.  And so on.

 

Also, is part of the problem too much internet integration?

 

 

1521 - 1540 of 35335