The T2 RETRIES occurs for EACH retransmission of the Nuvi. I don't recall exactly how many of those there are, but that's probably where 6*4 (or whatever it is) came from.
Lynn (D) - KJ4ERJ - Nuvi/T2-135 as KJ4ERJ-9 and KJ4ERJ-14 Keith VE7GDH wrote: > > > Adrian KD5HTZ wrote... > > > If you get a chance have a look at > > http://aprs.fi/?c=raw&call=KD5HTZ-9 > <http://aprs.fi/?c=raw&call=KD5HTZ-9> > > > > because there is no ack it keeps sending the same message > > 2009-07-16 01:45:44 UTC: > KD5HTZ-9>APOT2A,WIDE1-1,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{af > > 2009-07-16 01:45:58 UTC: > KD5HTZ-9>APOT2A,SANDIA*,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{ag > > 2009-07-16 01:46:03 UTC: > > > KD5HTZ-9>APOT2A,WIDE1-1,WIDE2-1,qAS,MELODY:/014616h3511.85N/10642.88W>147/000/A=005347 > > 14.0V 81F > > 2009-07-16 01:47:07 UTC: > KD5HTZ-9>APOT2A,SANDIA,RAVEN*,WIDE2,qAR,KM5VY-10::KD5HTZ-9 :test nuvl{ag > > [Duplicate message ID] > > 2009-07-16 01:47:42 UTC: > KD5HTZ-9>APOT2A,WIDE1-1,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{ag > > [Duplicate message ID] > > 2009-07-16 01:47:59 UTC: > KD5HTZ-9>APOT2A,SANDIA*,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{ah > > 2009-07-16 01:48:09 UTC: > > > KD5HTZ-9>APOT2A,SANDIA*,WIDE2-1,qAS,MELODY:/014821h3511.85N/10642.88W>295/000/A=005374 > > 14.0V 81F > > 2009-07-16 01:48:41 UTC: > KD5HTZ-9>APOT2A,SANDIA,CEDRO*,WIDE2,qAR,KM5VY-10::KD5HTZ-9 :test nuvl{ah > > [Duplicate message ID] > > 2009-07-16 01:49:58 UTC: > KD5HTZ-9>APOT2A,WIDE1-1,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{ai > > 2009-07-16 01:50:37 UTC: > KD5HTZ-9>APOT2A,WIDE1-1,WIDE2-1,qAS,MELODY::KD5HTZ-9 :test nuvl{ai > > [Duplicate message ID] > > > > Do you think this is a setting I'm totally stumped > > You said earlier that you had RETRIES set for 6. It shouldn't send a > message more than 6 times. However, what I see above are multiple > messages. Look at the message identifiers... {af, {ag, {ah and {ai. They > aren't the same message. They just happen to be 4 messages to the same > station and contain the same text. {af was sent once (just going by what > made it to an IGate. {ag was sent 3 times. {ah was sent twice. {ai was > sent 2 times. You have since also sent further messages with the same > content. Just because the text contained in the message is the same as > what you sent earlier, they aren't all the same message. > > So... you are sending messages to yourself. You aren't going receive > any of them unless you hear them coming back from a digi. In 5 of the > instances above, you were digi'd. The other times, you may or may not > have been digi'd but because they were heard directly by an IGate, there's > no way of knowing if they were also digi'd. Do a RESET and it should > stop sending un-acked messages. > > While you should be able to send messages to yourself for a test, try > shortening your path temporarily e.g. WIDE2-1 and send to another nearby > station instead of yourself. Turn MON ON and watch for <Digi Echo>s to > confirm that you are being digipeated. Of course, if the other station > is in direct earshot, you could set it to no path at all... PATH % > temporarily. To get an ACK, the other station must hear you and actually > send an ACK, and you must hear it. > > Which firmware version are you using? Scott - were there any issues with > sending or ACKing messages with older versions? > > 73 es cul - Keith VE7GDH > -- > "I may be lost, but I know exactly where I am!" > >
