Re: Somthing looks wrong in this log. Any clues what I might have set wrong? I can report positions ok as is tho.


charles leahy
 

Yes Lynn
Mostly you guest correctly. I'm using an SCS Tracker in kiss mode 300bd. Yes it is transmitting fine and sending info to APRS. When I closed and opened the program I needed to reboot the TNC so I put the 3 at the end of close Cmd. That fixed the problem getting in and out of kiss but the program seem to close much slower and the log looks like a train wreck.
73
Charles
Vk2syd
^027~!!1
^064^075!!1
^192^255^192~!!13
^027~!!1


Sent from Yahoo Mail for iPad

At 24 Mar 2015 10:59:24 pm, 'Lynn W Deffenbaugh (Mr)' kj4erj@... [aprsisce]<'aprsisce@...'> wrote:

(Brace yourself for a lot of questions and maybe an answer or two. Please respond to all of them if possible)

Well, first, what TNC are you using? If I had to guess, it would be an SCS of some type?

Second, what port type are you using? If I had to guess, it would be KISS or Simply(KISS)?

Third, what s are you using? If I had to guess, they would be:

^027~:* (Send Escape, suppress , wait up to 1 second for *)
^064^075::0 (Send @K, include default , wait zero seconds for response)

If this is a correct guess, why bother with the ^064^075? You could just put the @K since they're printable. Also, I suspect you really wanted the trailing ~ to suppress the default on that command? And apparently it doesn't give a response, or maybe it does...

The message you're probably concerned about is the "Read Zero bytes too often with 4 in buffer", right? That means just what it says. 4 bytes of data have been read from the TNC, but the data doesn't look like a KISS packet yet, and it's taking too long for the final characters to arrive.

Based on the final log of "Flushed[4]:@K<0D 0A>", I suspect the @K was actually echoed as @K as the response from the final . If the TNC always provides that response, you could put it in the as:

@K:@K^015^012 (Send @K with default , wait for @K in response)

With that command, the 4 bytes of TNC response would be read and wouldn't cause the complaints about the non-KISS stuff in the buffer.

Finally, did the TNC actually work after that? I mean, did you receive any true KISS packets from RF? If my assumption about the SCS is correct, you're likely on HF and may have to wait a LONG time before seeing a packet.

Also, did the transmitted packet actually go out over the air? Did you see the transmit light on the radio and/or hear tones by monitoring with another radio on the same frequency.

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

On 3/24/2015 7:31 AM, vk2syd@... [aprsisce] wrote:

WinMain:2015-03-24T10:51:52.218 Restore Saved ALWAYS Enable
WinMain:2015-03-24T10:51:52.437 Starting Port(scs)
Port(scs):2015-03-24T10:51:52.437 CpReader Running on COM7:38400,N,8,1 (2 OpenCmds, 2 CloseCmds)
Port(scs):2015-03-24T10:51:52.437 Opening COM7:38400,N,8,1
Port(scs):2015-03-24T10:51:52.437 Opening COM7 with 4 Args
Port(scs):2015-03-24T10:51:52.483 COM7:Packet Length 64 Version 2
Port(scs):2015-03-24T10:51:52.483 COM7:ServiceMask 0x1 Reserved1 0x0
Port(scs):2015-03-24T10:51:52.483 COM7:MaxQueue Tx 0 Rx 0 Baud 268435456
Port(scs):2015-03-24T10:51:52.483 COM7:Provider SubType 1 Capabilities 0xFF
Port(scs):2015-03-24T10:51:52.483 COM7:Settable Params 127 Baud 0x10066B70 Data 0xC StopParity 0x1F05
Port(scs):2015-03-24T10:51:52.483 COM7:Current Queue Tx 0 Rx 4096
Port(scs):2015-03-24T10:51:52.483 COM7:Provider Specifics 0x0 0x0
Port(scs):2015-03-24T10:51:52.499 CpOpen:Port COM7 38400,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE
Port(scs):2015-03-24T10:51:52.499 Opened COM7:38400,N,8,1, Flushing 0 in TransmitQueue, Sending 2 OpenCmds
Port(scs):2015-03-24T10:51:52.499 Command[5]:^027~
Port(scs):2015-03-24T10:51:52.499 Output[1]:<1B>
Port(scs):2015-03-24T10:51:52.530 CmdResp[2]:*
Port(scs):2015-03-24T10:51:53.536 Command[8]:^064^075
Port(scs):2015-03-24T10:51:53.536 Output[3]:@K<0D>
Port(scs):2015-03-24T10:51:53.888 Sent[77]:b`d`<8E 82 A8 8A>@@`d@c<03 F0>@105153h3349.36S/15108.28EjAPRS-IS for Win32
Port(scs):2015-03-24T10:51:55.731 [1] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:56.043 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:56.355 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:56.667 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:56.979 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:57.291 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:57.603 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:57.915 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:58.227 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:58.539 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:58.851 [0] Read Zero bytes too often with 4 in buffer
Port(scs):2015-03-24T10:51:58.851 Flushed[4]:@K<0D 0A>


Join APRSISCE@groups.io to automatically receive all group messages.