Loading ...
Sorry, an error occurred while loading the content.

Re: Settings Changing By Themselves!

Expand Messages
  • kb1vcz
    I have a new serial port card coming so I ll try that and see if that solves this problem. I am using a USB to serial converter, but I have never had any
    Message 1 of 9 , Oct 11, 2011
    • 0 Attachment
      I have a new serial port card coming so I'll try that and see if that solves this problem.

      I am using a USB to serial converter, but I have never had any issues with this particular model (and that was after going through several).

      I also tried reducing the buffer values, but that didn't seem to solve it either.





      --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)" <ldeffenb@...> wrote:
      >
      > If COM4 is a USB to serial or Bluetooth port, it appears that Windows is
      > losing the device. The errors shown there are being returned by the
      > Windows API and indicate a hardware-type error on the port.
      >
      > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
      >
      > PS. Error 995 is "ERROR_OPERATION_ABORTED" which Windows usually does
      > to all pending I/O operations when the device is being disconnected.
      >
      > On 10/7/2011 11:06 PM, kb1vcz wrote:
      > > Well, it looks like I spoke to soon.
      > >
      > > I made the changes and everything was working fine, but after a day or so I started losing connection to the tracker 2 when using it with the software.
      > >
      > > It looks like the KISS changing by itself was fixed, but now the connection drops
      > >
      > > Here is the log for the Tracker:
      > >
      > > WinMain:2011-10-07T21:05:26.826 Starting OT2M
      > > OT2M:2011-10-07T21:05:26.826 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
      > > OT2M:2011-10-07T21:05:26.826 Opening COM4:9600,N,8,1
      > > OT2M:2011-10-07T21:05:26.826 Opening COM4 with 4 Args
      > > OT2M:2011-10-07T21:05:26.826 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
      > > OT2M:2011-10-07T22:24:07.201 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-07T22:24:07.201 Error Reading Port, CpReadBytesWithTimeout FAILED!
      > > OT2M:2011-10-07T22:24:07.201 Error Reading Port, PortReadCommPort FAILED!
      > > OT2M:2011-10-07T22:24:07.201 Terminating after 10220 msec vs 0 Quiet
      > > OT2M:2011-10-07T22:24:07.201 Closing COM4:9600,N,8,1
      > > OT2M:2011-10-07T22:24:07.201 Restarting Reader...
      > > OT2M:2011-10-07T22:24:07.201 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
      > > OT2M:2011-10-07T22:24:07.201 Opening COM4:9600,N,8,1
      > > OT2M:2011-10-07T22:24:07.201 Opening COM4 with 4 Args
      > > OT2M:2011-10-07T22:24:07.201 CpOpen:SetCommState failed!
      > > OT2M:2011-10-07T22:24:07.201 SetParameters(4 pieces) Failed
      > > OT2M:2011-10-07T22:24:07.201 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
      > > OT2M:2011-10-07T23:54:46.151 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-08T01:33:18.992 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-08T01:33:19.022 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-08T01:33:19.091 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-08T01:33:19.091 Error Reading Port, CpReadBytesWithTimeout FAILED!
      > > OT2M:2011-10-08T01:33:19.091 Error Reading Port, PortReadCommPort FAILED!
      > > OT2M:2011-10-08T01:33:19.091 Terminating after 11594618 msec vs 0 Quiet
      > > OT2M:2011-10-08T01:33:19.091 Closing COM4:9600,N,8,1
      > > OT2M:2011-10-08T01:33:19.596 Restarting Reader...
      > > OT2M:2011-10-08T01:33:19.596 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
      > > OT2M:2011-10-08T01:33:19.596 Opening COM4:9600,N,8,1
      > > OT2M:2011-10-08T01:33:19.597 Opening COM4 with 4 Args
      > > OT2M:2011-10-08T01:33:19.604 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
      > > OT2M:2011-10-08T02:17:22.250 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
      > > OT2M:2011-10-08T02:17:22.250 Error Reading Port, CpReadBytesWithTimeout FAILED!
      > > OT2M:2011-10-08T02:17:22.250 Error Reading Port, PortReadCommPort FAILED!
      > > OT2M:2011-10-08T02:17:22.250 Terminating after 2642655 msec vs 0 Quiet
      > >
      > > Any ideas?
      > >
      > >
      > > --- In tracker2@yahoogroups.com, "kb1vcz"<kb1vcz@> wrote:
      > >> Thanks Lynn, that has solved the problem completely.
      > >>
      > >>
      > >>
      > >> --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"<ldeffenb@> wrote:
      > >>> Double-check your<CloseCmd>s on the port in APRSIS32. The default KISS
      > >>> port commands are designed for Kenwood radios and include things to take
      > >>> it out of KISS mode. Please read and apply the following Wiki pages and
      > >>> see if the situation improves:
      > >>>
      > >>> http://aprsisce.wikidot.com/tt4-via-kiss (I know it's TT4, but it's
      > >>> actually anything that locks in KISS)
      > >>>
      > >>> http://aprsisce.wikidot.com/editing-xml-configuration - You MUST have
      > >>> the client closed when editing!
      > >>>
      > >>> Lynn (D) - KJ4ERJ - OT2m w/Bluetooth on A and Nuvi350 on B as KJ4ERJ-9
      > >
      > > ------------------------------------
      > >
      > > Yahoo! Groups Links
      > >
      > >
      > >
      > >
      >
    • kb1vcz
      Hi Lynn, It looks like I had the PC in sleep mode, so every 20 minutes or so it was causing the com port connection to drop. I turned this off and have not had
      Message 2 of 9 , Oct 12, 2011
      • 0 Attachment
        Hi Lynn,

        It looks like I had the PC in sleep mode, so every 20 minutes or so it was causing the com port connection to drop.

        I turned this off and have not had any serial port issues since.

        And as I stated before the fix for the KISS mode changing also works as you suggested.

        Thanks for the help!

        --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)" <ldeffenb@...> wrote:
        >
        > If COM4 is a USB to serial or Bluetooth port, it appears that Windows is
        > losing the device. The errors shown there are being returned by the
        > Windows API and indicate a hardware-type error on the port.
        >
        > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
        >
        > PS. Error 995 is "ERROR_OPERATION_ABORTED" which Windows usually does
        > to all pending I/O operations when the device is being disconnected.
        >
        > On 10/7/2011 11:06 PM, kb1vcz wrote:
        > > Well, it looks like I spoke to soon.
        > >
        > > I made the changes and everything was working fine, but after a day or so I started losing connection to the tracker 2 when using it with the software.
        > >
        > > It looks like the KISS changing by itself was fixed, but now the connection drops
        > >
        > > Here is the log for the Tracker:
        > >
        > > WinMain:2011-10-07T21:05:26.826 Starting OT2M
        > > OT2M:2011-10-07T21:05:26.826 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
        > > OT2M:2011-10-07T21:05:26.826 Opening COM4:9600,N,8,1
        > > OT2M:2011-10-07T21:05:26.826 Opening COM4 with 4 Args
        > > OT2M:2011-10-07T21:05:26.826 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
        > > OT2M:2011-10-07T22:24:07.201 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-07T22:24:07.201 Error Reading Port, CpReadBytesWithTimeout FAILED!
        > > OT2M:2011-10-07T22:24:07.201 Error Reading Port, PortReadCommPort FAILED!
        > > OT2M:2011-10-07T22:24:07.201 Terminating after 10220 msec vs 0 Quiet
        > > OT2M:2011-10-07T22:24:07.201 Closing COM4:9600,N,8,1
        > > OT2M:2011-10-07T22:24:07.201 Restarting Reader...
        > > OT2M:2011-10-07T22:24:07.201 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
        > > OT2M:2011-10-07T22:24:07.201 Opening COM4:9600,N,8,1
        > > OT2M:2011-10-07T22:24:07.201 Opening COM4 with 4 Args
        > > OT2M:2011-10-07T22:24:07.201 CpOpen:SetCommState failed!
        > > OT2M:2011-10-07T22:24:07.201 SetParameters(4 pieces) Failed
        > > OT2M:2011-10-07T22:24:07.201 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
        > > OT2M:2011-10-07T23:54:46.151 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-08T01:33:18.992 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-08T01:33:19.022 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-08T01:33:19.091 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-08T01:33:19.091 Error Reading Port, CpReadBytesWithTimeout FAILED!
        > > OT2M:2011-10-08T01:33:19.091 Error Reading Port, PortReadCommPort FAILED!
        > > OT2M:2011-10-08T01:33:19.091 Terminating after 11594618 msec vs 0 Quiet
        > > OT2M:2011-10-08T01:33:19.091 Closing COM4:9600,N,8,1
        > > OT2M:2011-10-08T01:33:19.596 Restarting Reader...
        > > OT2M:2011-10-08T01:33:19.596 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
        > > OT2M:2011-10-08T01:33:19.596 Opening COM4:9600,N,8,1
        > > OT2M:2011-10-08T01:33:19.597 Opening COM4 with 4 Args
        > > OT2M:2011-10-08T01:33:19.604 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
        > > OT2M:2011-10-08T02:17:22.250 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
        > > OT2M:2011-10-08T02:17:22.250 Error Reading Port, CpReadBytesWithTimeout FAILED!
        > > OT2M:2011-10-08T02:17:22.250 Error Reading Port, PortReadCommPort FAILED!
        > > OT2M:2011-10-08T02:17:22.250 Terminating after 2642655 msec vs 0 Quiet
        > >
        > > Any ideas?
        > >
        > >
        > > --- In tracker2@yahoogroups.com, "kb1vcz"<kb1vcz@> wrote:
        > >> Thanks Lynn, that has solved the problem completely.
        > >>
        > >>
        > >>
        > >> --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"<ldeffenb@> wrote:
        > >>> Double-check your<CloseCmd>s on the port in APRSIS32. The default KISS
        > >>> port commands are designed for Kenwood radios and include things to take
        > >>> it out of KISS mode. Please read and apply the following Wiki pages and
        > >>> see if the situation improves:
        > >>>
        > >>> http://aprsisce.wikidot.com/tt4-via-kiss (I know it's TT4, but it's
        > >>> actually anything that locks in KISS)
        > >>>
        > >>> http://aprsisce.wikidot.com/editing-xml-configuration - You MUST have
        > >>> the client closed when editing!
        > >>>
        > >>> Lynn (D) - KJ4ERJ - OT2m w/Bluetooth on A and Nuvi350 on B as KJ4ERJ-9
        > >
        > > ------------------------------------
        > >
        > > Yahoo! Groups Links
        > >
        > >
        > >
        > >
        >
      • Lynn W. Deffenbaugh (Mr)
        Good to know on both counts. Software is so often trapped by the hardware on which it runs. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
        Message 3 of 9 , Oct 12, 2011
        • 0 Attachment
          Good to know on both counts. Software is so often trapped by the
          hardware on which it runs.

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

          On 10/12/2011 10:36 PM, kb1vcz wrote:
          > Hi Lynn,
          >
          > It looks like I had the PC in sleep mode, so every 20 minutes or so it was causing the com port connection to drop.
          >
          > I turned this off and have not had any serial port issues since.
          >
          > And as I stated before the fix for the KISS mode changing also works as you suggested.
          >
          > Thanks for the help!
          >
          > --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"<ldeffenb@...> wrote:
          >> If COM4 is a USB to serial or Bluetooth port, it appears that Windows is
          >> losing the device. The errors shown there are being returned by the
          >> Windows API and indicate a hardware-type error on the port.
          >>
          >> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
          >>
          >> PS. Error 995 is "ERROR_OPERATION_ABORTED" which Windows usually does
          >> to all pending I/O operations when the device is being disconnected.
          >>
          >> On 10/7/2011 11:06 PM, kb1vcz wrote:
          >>> Well, it looks like I spoke to soon.
          >>>
          >>> I made the changes and everything was working fine, but after a day or so I started losing connection to the tracker 2 when using it with the software.
          >>>
          >>> It looks like the KISS changing by itself was fixed, but now the connection drops
          >>>
          >>> Here is the log for the Tracker:
          >>>
          >>> WinMain:2011-10-07T21:05:26.826 Starting OT2M
          >>> OT2M:2011-10-07T21:05:26.826 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
          >>> OT2M:2011-10-07T21:05:26.826 Opening COM4:9600,N,8,1
          >>> OT2M:2011-10-07T21:05:26.826 Opening COM4 with 4 Args
          >>> OT2M:2011-10-07T21:05:26.826 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
          >>> OT2M:2011-10-07T22:24:07.201 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-07T22:24:07.201 Error Reading Port, CpReadBytesWithTimeout FAILED!
          >>> OT2M:2011-10-07T22:24:07.201 Error Reading Port, PortReadCommPort FAILED!
          >>> OT2M:2011-10-07T22:24:07.201 Terminating after 10220 msec vs 0 Quiet
          >>> OT2M:2011-10-07T22:24:07.201 Closing COM4:9600,N,8,1
          >>> OT2M:2011-10-07T22:24:07.201 Restarting Reader...
          >>> OT2M:2011-10-07T22:24:07.201 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
          >>> OT2M:2011-10-07T22:24:07.201 Opening COM4:9600,N,8,1
          >>> OT2M:2011-10-07T22:24:07.201 Opening COM4 with 4 Args
          >>> OT2M:2011-10-07T22:24:07.201 CpOpen:SetCommState failed!
          >>> OT2M:2011-10-07T22:24:07.201 SetParameters(4 pieces) Failed
          >>> OT2M:2011-10-07T22:24:07.201 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
          >>> OT2M:2011-10-07T23:54:46.151 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-08T01:33:18.992 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-08T01:33:19.022 Status -1 Error 31 At 581 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-08T01:33:19.091 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-08T01:33:19.091 Error Reading Port, CpReadBytesWithTimeout FAILED!
          >>> OT2M:2011-10-08T01:33:19.091 Error Reading Port, PortReadCommPort FAILED!
          >>> OT2M:2011-10-08T01:33:19.091 Terminating after 11594618 msec vs 0 Quiet
          >>> OT2M:2011-10-08T01:33:19.091 Closing COM4:9600,N,8,1
          >>> OT2M:2011-10-08T01:33:19.596 Restarting Reader...
          >>> OT2M:2011-10-08T01:33:19.596 CpReader Running on COM4:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
          >>> OT2M:2011-10-08T01:33:19.596 Opening COM4:9600,N,8,1
          >>> OT2M:2011-10-08T01:33:19.597 Opening COM4 with 4 Args
          >>> OT2M:2011-10-08T01:33:19.604 Opened COM4:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
          >>> OT2M:2011-10-08T02:17:22.250 Status -1 Error 995 At 533 in c:\cvstest\code\aprs\aprsisce\cprtns.c
          >>> OT2M:2011-10-08T02:17:22.250 Error Reading Port, CpReadBytesWithTimeout FAILED!
          >>> OT2M:2011-10-08T02:17:22.250 Error Reading Port, PortReadCommPort FAILED!
          >>> OT2M:2011-10-08T02:17:22.250 Terminating after 2642655 msec vs 0 Quiet
          >>>
          >>> Any ideas?
          >>>
          >>>
          >>> --- In tracker2@yahoogroups.com, "kb1vcz"<kb1vcz@> wrote:
          >>>> Thanks Lynn, that has solved the problem completely.
          >>>>
          >>>>
          >>>>
          >>>> --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"<ldeffenb@> wrote:
          >>>>> Double-check your<CloseCmd>s on the port in APRSIS32. The default KISS
          >>>>> port commands are designed for Kenwood radios and include things to take
          >>>>> it out of KISS mode. Please read and apply the following Wiki pages and
          >>>>> see if the situation improves:
          >>>>>
          >>>>> http://aprsisce.wikidot.com/tt4-via-kiss (I know it's TT4, but it's
          >>>>> actually anything that locks in KISS)
          >>>>>
          >>>>> http://aprsisce.wikidot.com/editing-xml-configuration - You MUST have
          >>>>> the client closed when editing!
          >>>>>
          >>>>> Lynn (D) - KJ4ERJ - OT2m w/Bluetooth on A and Nuvi350 on B as KJ4ERJ-9
          >>> ------------------------------------
          >>>
          >>> Yahoo! Groups Links
          >>>
          >>>
          >>>
          >>>
          >
          >
          >
          > ------------------------------------
          >
          > Yahoo! Groups Links
          >
          >
          >
          >
        Your message has been successfully submitted and would be delivered to recipients shortly.