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

Fwd: Re: [aprsisce] Re: Kiss Mode for RF

Expand Messages
  • Colin Catlin
    Sorry I did of course mean Mobile not Portable . I think I have something sorted (in my mind at least) for Portable subject to my testing working out
    Message 1 of 1 , Jun 3, 2010

      Sorry I did of course mean 'Mobile' not 'Portable'. I think I have something sorted (in my mind at least) for Portable subject to my testing working out (hopefully next week).

      73,
      Colin.


      On 03/06/2010 16:28, Colin Catlin wrote:
      Hi Lynn,

      I would be very interested in what you are planning in your car (KJ4ERJ-9), it sounds similar to what I have in mind for my portable setup but that won't be for a while yet. I haven't even decided on what hardware yet.


      73,
      Colin.

      On 03/06/2010 14:27, Lynn W. Deffenbaugh wrote:
       

      With the right splitter cable and PKTOCOM configured in the TT4 coupled
      with a Bluetooth to Serial adapter, you can use APRSISCE on a
      Bluetooth-capable phone and be able to do APRS over RF via the TT4 as
      well as be able to use messaging and mapping of the received stations.
      I'm doing a similar thing soon in my car (KJ4ERJ-9) with an OT2m as soon
      as I get the right cables fabricated.

      Lynn (D) - KJ4ERJ

      Rick wrote:
      > I can't use aprsis on mobile cause only have gps 2 from Byon and no rs232 port on laptop.
      >
      > --- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> wrote:
      >
      >> I checked your raw packets at http://aprs.fi/?c=raw&call=KD4DRA-9 and
      >> I'm not seeing a change in path. The only packets there came from the
      >> TT4 directly, not from APRSISCE. Or did you do the test with a
      >> different -SSID than -9?
      >>
      >> Lynn (D) - KJ4ERJ
      >>
      >> kd4dra@... wrote:
      >>
      >>> Thanks lynn I did that last night and he still show in the path.
      >>> Thanks again
      >>> Rick
      >>>
      >>> Sent from my Verizon Wireless BlackBerry
      >>>
      >>> ----------------------------------------------------------
      >>> *From: * "Lynn W. Deffenbaugh" <kj4erj@...>
      >>> *Date: *Thu, 03 Jun 2010 08:29:19 -0400
      >>> *To: *<aprsisce@yahoogroups.com>
      >>> *Subject: *Re: [aprsisce] Re: Kiss Mode for RF
      >>>
      >>>
      >>>
      >>> Unfortunately, no. There's no provision in APRS to tell a digi to
      >>> ignore you if you're using one of it's aliases. The only option would
      >>> be to replace the WIDE1-1 with a specific digi's call, but that would
      >>> only work while you were within simplex range of that digi and would
      >>> hurt big-time when you left the area.
      >>>
      >>> I did some inquiring about what the digi was doing and it's a known
      >>> configuration issue of a certain type of hardware. I'll see if I can
      >>> find that response and post it back here later.
      >>>
      >>> Lynn (D) - KJ4ERJ - Our abilities are only as good as our infrastructure
      >>>
      >>> Rick wrote:
      >>>
      >>>> Hey Lynn
      >>>> I sent this digi owner a letter, I copy and pasted your comment
      >>>>
      >>> about the Wide1 and copy and pasted some of the raw data from aprs.fi
      >>> and its still not fixed. Can I block a digi from my path?
      >>>
      >>>> Thanks
      >>>> Rick
      >>>>
      >>>>
      >>>> --- In aprsisce@yahoogroups.com <mailto:aprsisce%40yahoogroups.com>,
      >>>>
      >>> "Lynn W. Deffenbaugh" <kj4erj@> wrote:
      >>>
      >>>>> Rick,
      >>>>>
      >>>>> I checked your raw packets this morning and noticed that you have both
      >>>>> APRSIS32 and the TT4 both configured for KD4DRA-9. It is best to give
      >>>>> each and every device and program its own -SSID
      >>>>> (http://aprsisce.wikidot.com/ssids) to avoid confusion and provide
      >>>>> better problem detection by knowing where various packets are
      >>>>>
      >>> coming from.
      >>>
      >>>>> Also, it appears that you've got a split-personality Digi in the area.
      >>>>> Consider the following packets:
      >>>>>
      >>>>> 2010-05-22 20:37:51 UTC:
      >>>>> KD4DRA-9>3TTR9S,KE4CJA-4*,WIDE1,WIDE2-1,qAR,N2VUZ-1:'n,]l
      >>>>> <0x1c>v/"6q}TinyTrak4 / 110F 13.5V
      >>>>> 2010-05-22 20:38:48 UTC:
      >>>>> KD4DRA-9>3TTR9S,KE4CJA-4*,WIDE1,WIDE2-1,qAR,WA4SAS-11:'n,]l
      >>>>> <0x1c>v/"6q}TinyTrak4 / 110F 13.5V
      >>>>>
      >>>>> KE4CJA-4 apparently changed your WIDE1-1 to WIDE1 and insert a used
      >>>>> callsign for itself. However, it should have marked the WIDE1 as used
      >>>>> (WIDE1*). With what it did, that packet will only be picked up by an
      >>>>> obsolete WIDE digi and until that gets used, the WIDE2-1 will be
      >>>>> ignored. Your path of WIDE1-1,WIDE2-1 is correct.
      >>>>>
      >>>>> I then checked the packets directly from KE4CJA-4 and found that its
      >>>>> comments claims that it is a WIDEN-N digi, but yet its own path
      >>>>>
      >>> betrays
      >>>
      >>>>> it's true obsolescence as it tries to go out via WIDE,WIDE. I don't
      >>>>> know if you have contact info for that digi operator, but it would
      >>>>>
      >>> help
      >>>
      >>>>> the area if it would get fully WIDEn-N compliant.
      >>>>>
      >>>>> 2010-05-23 09:46:20 UTC:
      >>>>> KE4CJA-4>BEACON,WIDE,WIDE,qAR,AL0I:!3510.93NN08240.93W#PHG6830 EM85
      >>>>> W-R-T-NC WIDEN-N RICH MTN TRN CNTY
      >>>>>
      >>>>> Let me know if you can use any more help getting the TT4 working in
      >>>>>
      >>> KISS
      >>>
      >>>>> mode. Your raw packets (http://aprs.fi/?c=raw&call=KD4DRA-9
      >>>>>
      >>> <http://aprs.fi/?c=raw&call=KD4DRA-9>) appear
      >>>
      >>>>> that you had it working on 05-22 16:3x, but it had reverted to Text by
      >>>>> 05-22 20:12 through 20:14. The packets from 05-23 02:4x don't count as
      >>>>> they went direct to APRS-IS.
      >>>>>
      >>>>> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
      >>>>>
      >>>>>
      >>>>>
      >>>>> Rick wrote:
      >>>>>
      >>>>>
      >>>>>> Thanks all for your help !
      >>>>>> Rick
      >>>>>>
      >>>>>>
      >>>>>> --- In aprsisce@yahoogroups.com
      >>>>>>
      >>> <mailto:aprsisce%40yahoogroups.com>, "Lynn W. Deffenbaugh" <kj4erj@>
      >>> wrote:
      >>>
      >>>>>>
      >>>>>>> Rick,
      >>>>>>>
      >>>>>>> Fred is correct, you'll want to wipe out all of the OpenCmd and
      >>>>>>>
      >>> CloseCmd
      >>>
      >>>>>>> and have the single pair of:
      >>>>>>>
      >>>>>>> <OpenCmd>~!!0</OpenCmd>
      >>>>>>> <CloseCmd~!!0</CloseCmd>
      >>>>>>>
      >>>>>>> And according to what I see in the log below, you do not have the
      >>>>>>>
      >>> TT4 in
      >>>
      >>>>>>> KISS mode already. You'll need to do that first as APRSISCE/32
      >>>>>>>
      >>> expects
      >>>
      >>>>>>> the device to already be KISS, although that's what the Open and
      >>>>>>>
      >>> Close
      >>>
      >>>>>>> Cmd tags are going to become. Because the TT4 isn't speaking
      >>>>>>>
      >>> KISS, the
      >>>
      >>>>>>> quiet time expires so it closes and re-opens the port.
      >>>>>>>
      >>>>>>> <RFtoISEnabled>0</RFtoISEnabled>
      >>>>>>>
      >>>>>>> RFtoIS controls the gating of RF-received APRS packets to the
      >>>>>>>
      >>> APRS-IS connection. If it is set to 1 (the upcoming default, but not
      >>> in the development version), all packets will be forwarded on.
      >>>
      >>>>>>> <IStoRFEnabled>0</IStoRFEnabled>
      >>>>>>>
      >>>>>>> IStoRF controls the gating of messages from the APRS-IS to the RF
      >>>>>>>
      >>> interface if the target station has been heard "recently" "local",
      >>> currently defined as max 2 hops in the past 30 minutes. "Hops" are
      >>> counted as path components marked "used" in the path.
      >>>
      >>>>>>> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
      >>>>>>>
      >>>>>>>
      >>>>>>> Rick wrote:
      >>>>>>>
      >>>>>>>
      >>>>>>>
      >>>>>>>> Hi Lynn
      >>>>>>>> I'm trying to setup running in kiss mode with the TT4
      >>>>>>>> I noticed at the top of screen where it shows the status
      >>>>>>>> of your modes, it keeps cycleing, (open kiss rf, kiss rf ok,
      >>>>>>>> and then close kiss rf.) Please help, have I got something set
      >>>>>>>>
      >>> wrong?
      >>>
      >>>>>>>> And also does telementry have to be enabled for postion reporting.
      >>>>>>>> See my captures below:
      >>>>>>>>
      >>>>>>>> Thanks Rick / kd4dra
      >>>>>>>>
      >>>>>>>>
      >>>>>>>> <!--RFPort[1]-->
      >>>>>>>> <RFPort Name="Kiss RF">
      >>>>>>>> <Protocol>KISS</Protocol>
      >>>>>>>> <Device>COM3:19200,N,8,1</Device>
      >>>>>>>> <RfBaud>1200</RfBaud>
      >>>>>>>> <OpenCmd>^M~</OpenCmd>
      >>>>>>>> <OpenCmd>XFLOW OFF</OpenCmd>
      >>>>>>>> <OpenCmd>FULLDUP ON</OpenCmd>
      >>>>>>>> <OpenCmd>KISS ON</OpenCmd>
      >>>>>>>> <OpenCmd>RESTART!!0</OpenCmd>
      >>>>>>>> <CloseCmd>^192^255^192~!!0</CloseCmd>
      >>>>>>>> <CloseCmd>^C^C^C~!!0</CloseCmd>
      >>>>>>>> <CloseCmd>TC 1!TS 1</CloseCmd>
      >>>>>>>> <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
      >>>>>>>> <QuietTime>8</QuietTime>
      >>>>>>>> <Enabled>1</Enabled>
      >>>>>>>> <XmitEnabled>1</XmitEnabled>
      >>>>>>>> <RFtoISEnabled>0</RFtoISEnabled>
      >>>>>>>> <IStoRFEnabled>0</IStoRFEnabled>
      >>>>>>>> <MyCallNot3rd>0</MyCallNot3rd>
      >>>>>>>> <BeaconingEnabled>1</BeaconingEnabled>
      >>>>>>>> <BeaconPath>wide1-1,wide2-1</BeaconPath>
      >>>>>>>> <TelemetryEnabled>0</TelemetryEnabled>
      >>>>>>>> <TelemetryPath>wide1-1,wide2-1</TelemetryPath>
      >>>>>>>> <!--DigiXform-->
      >>>>>>>> </RFPort>
      >>>>>>>>
      >>>>>>>> Here is my captured text...
      >>>>>>>> WinMain:2010-05-22T13:10:24 Starting Kiss RF
      >>>>>>>> Kiss RF:2010-05-22T13:10:24 Opening COM3 with 4 Args
      >>>>>>>> Kiss RF:2010-05-22T13:10:26 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(^M~)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:27 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(XFLOW OFF)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:28 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(FULLDUP ON)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:30 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(KISS ON)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:30 Have 63 Bytes to write
      >>>>>>>> Kiss RF:2010-05-22T13:10:30 Writing 63 Bytes from 0/63
      >>>>>>>> WinMain:2010-05-22T13:10:53 Logging Enabled
      >>>>>>>> WinMain:2010-05-22T13:10:54 Queueing
      >>>>>>>>
      >>> KD4DRA-9>APWW02,WIDE1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:54 KISS:Got 18 Bytes ending in 0x84
      >>>>>>>> Kiss RF:2010-05-22T13:10:54
      >>>>>>>>
      >>> KISS:KD4YDC>APU25N,AB4KN-2*,KE4CJA-4*,WIDE2:;New
      >>> 444.6*261913z3328.45N/08426.24WmNew site for 444.600 (77hz) (41)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:54
      >>>>>>>>
      >>> KISS:Payload(<IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4
      >>>
      >>>>>>>> )
      >>>>>>>> Kiss RF:2010-05-22T13:10:54 KISS:Sending[79]:<C0 00 82 A0 AE
      >>>>>>>>
      >>> AE>`d<E0 96 88>h<88 A4 82>r<AE 92 88 8A>b@b<AE 92 88 8A>d@c<03
      >>> F0><IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4<0A C0>
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:54 Have 79 Bytes to write
      >>>>>>>> Kiss RF:2010-05-22T13:10:54 Writing 79 Bytes from 0/79
      >>>>>>>> Kiss RF:2010-05-22T13:10:54 Sent[79]:<C0 00 82 A0 AE AE>`d<E0 96
      >>>>>>>>
      >>> 88>h<88 A4 82>r<AE 92 88 8A>b@b<AE 92 88 8A>d@c<03
      >>> F0><IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4<0A C0>
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:10:57
      >>>>>>>>
      >>> KISS:KD4DRA-9>APWW02,N4VDE-3*,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4
      >>> (52)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:03 KISS:Got 80 Bytes ending in 0x43
      >>>>>>>> Kiss RF:2010-05-22T13:11:03 Residual[80]:<C0 00 82 A0 AE
      >>>>>>>>
      >>> AE>`d<E0 96 88>h<88 A4 82>r<96 8A>h<86 94 82 E8 AE 92 88 8A>b@`<AE 92
      >>> 88 8A>d@c<03 F0><IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_C
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:03
      >>>>>>>>
      >>> KISS:KD4DRA-9>APWW02,KE4CJA-4*,WIDE1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=4,DIR_CNT=0,RF_CNT=4
      >>> (52)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:05
      >>>>>>>>
      >>> KISS:N3MCZ-2>S5SU6U,KE4CJA-4*,N4VDE-3*,WIDE2:`n==lKT</`";A}_ (32)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Terminating after 8112 msec vs 8000
      >>>>>>>>
      >>> Quiet
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Closing COM3:19200,N,8,1
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Command[13]:^192^255^192~
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Output[3]:<C0 FF C0>
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Command[7]:^C^C^C~
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Output[3]:<03 03 03>
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Command[4]:TC 1
      >>>>>>>> Kiss RF:2010-05-22T13:11:13 Output[5]:TC 1<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:15 Missed Expected Response(TS 1) From
      >>>>>>>>
      >>> Command(TC 1!TS 1)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:15 Command[6]:TN 2,0
      >>>>>>>> Kiss RF:2010-05-22T13:11:15 Output[7]:TN 2,0<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:16 Missed Expected Response(TN 2,0)
      >>>>>>>>
      >>> From Command(TN 2,0!TN 2,0)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:16 Restarting Reader...
      >>>>>>>> Kiss RF:2010-05-22T13:11:16 Reader Running on COM3:19200,N,8,1
      >>>>>>>>
      >>> (5 OpenCmds, 4 CloseCmds)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:16 Opening COM3:19200,N,8,1
      >>>>>>>> Kiss RF:2010-05-22T13:11:16 Opening COM3 with 4 Args
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:Packet Length 64 Version 2
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:ServiceMask 0x1 Reserved1 0x0
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:MaxQueue Tx 0 Rx 0 Baud 268435456
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:Provider SubType 1 Capabilities
      >>>>>>>>
      >>> 0xFF
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:Settable Params 127 Baud
      >>>>>>>>
      >>> 0x1007FFFF Data 0xF StopParity 0x1F07
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:Current Queue Tx 0 Rx 4096
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 COM3:Provider Specifics 0x0 0x0
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 CpOpen:Port COM3 19200,N,8,1
      >>>>>>>>
      >>> !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense
      >>> RTS_ENABLE
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 Opened COM3:19200,N,8,1, Flushing 0
      >>>>>>>>
      >>> in TransmitQueue, Sending 5 OpenCmds
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 Command[3]:^M~
      >>>>>>>> Kiss RF:2010-05-22T13:11:17 Output[1]:<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:18 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(^M~)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:18 Command[9]:XFLOW OFF
      >>>>>>>> Kiss RF:2010-05-22T13:11:18 Output[10]:XFLOW OFF<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:19 CmdResp[99]:<C0 00 82 A0 A4
      >>>>>>>>
      >>> A6>@@`<96 82>h<8E 9C B2>f<96 82>h<8E 9C B2 EE 96 8A>h<86 94 82 E8 AE
      >>> 92 88 8A>d@`<8E 82>b@@@c<03
      >>> F0>!!0000007E02A5096027E702AA03AA----008D0224096A0000<0D 0A C0>
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:19 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(XFLOW OFF)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:19 Command[10]:FULLDUP ON
      >>>>>>>> Kiss RF:2010-05-22T13:11:19 Output[11]:FULLDUP ON<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:20 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(FULLDUP ON)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:20 Command[7]:KISS ON
      >>>>>>>> Kiss RF:2010-05-22T13:11:20 Output[8]:KISS ON<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:22 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(KISS ON)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:22 Command[7]:RESTART
      >>>>>>>> Kiss RF:2010-05-22T13:11:22 Output[8]:RESTART<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Terminating after 8594 msec vs 8000
      >>>>>>>>
      >>> Quiet
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Closing COM3:19200,N,8,1
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Command[13]:^192^255^192~
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Output[3]:<C0 FF C0>
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Command[7]:^C^C^C~
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Output[3]:<03 03 03>
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Command[4]:TC 1
      >>>>>>>> Kiss RF:2010-05-22T13:11:25 Output[5]:TC 1<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:26 Missed Expected Response(TS 1) From
      >>>>>>>>
      >>> Command(TC 1!TS 1)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:26 Command[6]:TN 2,0
      >>>>>>>> Kiss RF:2010-05-22T13:11:26 Output[7]:TN 2,0<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:27 Missed Expected Response(TN 2,0)
      >>>>>>>>
      >>> From Command(TN 2,0!TN 2,0)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:27 Restarting Reader...
      >>>>>>>> Kiss RF:2010-05-22T13:11:27 Reader Running on COM3:19200,N,8,1
      >>>>>>>>
      >>> (5 OpenCmds, 4 CloseCmds)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:27 Opening COM3:19200,N,8,1
      >>>>>>>> Kiss RF:2010-05-22T13:11:27 Opening COM3 with 4 Args
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:Packet Length 64 Version 2
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:ServiceMask 0x1 Reserved1 0x0
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:MaxQueue Tx 0 Rx 0 Baud 268435456
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:Provider SubType 1 Capabilities
      >>>>>>>>
      >>> 0xFF
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:Settable Params 127 Baud
      >>>>>>>>
      >>> 0x1007FFFF Data 0xF StopParity 0x1F07
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:Current Queue Tx 0 Rx 4096
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 COM3:Provider Specifics 0x0 0x0
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 CpOpen:Port COM3 19200,N,8,1
      >>>>>>>>
      >>> !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense
      >>> RTS_ENABLE
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 Opened COM3:19200,N,8,1, Flushing 0
      >>>>>>>>
      >>> in TransmitQueue, Sending 5 OpenCmds
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 Command[3]:^M~
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 Output[1]:<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:28 CmdResp[81]:<C0 00 82 A0
      >>>>>>>>
      >>> A8>fbb`<9C>l<86 9C 8E>@b<96>h<9E B4 A6>@<F4 AE 92 88 8A>b@<E0 9C>h<AC
      >>> 88 8A>@<E6 AE 92 88 8A>d@a<03 F0>/221311z2848.56N/08133.12Wu123/000<C0>
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:29 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(^M~)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:29 Command[9]:XFLOW OFF
      >>>>>>>> Kiss RF:2010-05-22T13:11:29 Output[10]:XFLOW OFF<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:30 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(XFLOW OFF)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:30 Command[10]:FULLDUP ON
      >>>>>>>> Kiss RF:2010-05-22T13:11:30 Output[11]:FULLDUP ON<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:32 Missed Expected Response(cmd:) From
      >>>>>>>>
      >>> Command(FULLDUP ON)
      >>>
      >>>>>>>> Kiss RF:2010-05-22T13:11:32 Command[7]:KISS ON
      >>>>>>>> Kiss RF:2010-05-22T13:11:32 Output[8]:KISS ON<0D>
      >>>>>>>> Kiss RF:2010-05-22T13:11:32 CmdResp[57]:<C0 00 A6>j<A6
      >>>>>>>>
      >>> AA>l<AA>`<9C>f<9A 86 B4>@<E4 96 8A>h<86 94 82 E8 AE 92 88 8A>b@`<AE 92
      >>> 88 8A>d@e<03 F0>`n==l#T</`";?}_ <0D C0>
      >>>
      >>>>>>>>
      >>>
      >>>
      >>>
      >
      >
      >
      >
      > ------------------------------------
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >




    Your message has been successfully submitted and would be delivered to recipients shortly.