More likely than not the ack is now getting through where when it was set to 6, the ack was not. The only time I've had messages "stuck" in the outbox and still sending is when the receiver was either not running or their ack was decidedly not gating back out to me.
I just open the outbox after sending a message and kill it if it doesn't change to a timestamp in what I consider to be a reasonable amount of time. Lynn (D) - KJ4ERJ Brad wrote: > Thanks. "--RETRIES" returned a value of 6 which I guess is the default. I > changed the setting to 1 and now both units are sending and receiving > messages from each other only one time. This appears to do the trick. > > So basically, with a setting of 1, I'm guessing the sending unit doesn't > require an acknowledgement from the receiving unit in order to consider the > job complete. > > Now, to experiment with that theory, I will change the "--RETRIES" setting to > 30 and see if I get the message 30 times or if there is in fact an > acknowledgement at some point..... > > Wow! Interesting result... The message went through on the first try and an > acknowledgement was received. The message ended up being sent only one time. > I tried this on both units with the same result. I didn't expect that > happen. > > I'm a bit puzzled and can't figure out why I would get that result on > "--RETRIES 30" when I had such a different result at the point "--RETRIES" > was at the default setting of 6. > > .... hmmm my working theory now is that maybe changing the "--RETRIES" > setting somehow reset something in the system or maybe forced it to recognize > that parameter setting where it maybe wasn't seeing it before. Or perhaps > there is some sort of logical connection within the programming where > "--RETRIES" and the message acknowledgement loop have some sort of dependency > or inter-relationship in the coding. If that is the case, maybe changing > the Retries setting caused the acknowledgement loop to reset somehow. > > Anyway, that's all speculation and probably irrelevant. The good news is we > got it to work! I really appreciate your suggestion. It seems to have > cleared up whatever was causing the problem. > > Have a great day! > > Thanks again! > Brad (KE4YOV) > > --- In [email protected], "CatzMeow" <ironki...@...> wrote: > >> Brad, >> >> I had a similar issue when I first set up my Nuvi 350, try this: >> >> If I interpret things correctly, the OT2m will try to send a message >> once, and then again if you have it set to do so. The default number of >> retries is like "1" or something. It seems that it would be enough >> since you're really going car to car, but try increasing the number of >> retries anyway (you'll probably need more than one out in the field). >> >> From the Nuvi, send the command "--RETRIES" (no quotes). You should get >> a response message back with the current value. If it is anything less >> than 5 or 10, send a command "--RETRIES 30" (again, no quotes), This >> will tell the OT2m to try and send a message 30 times until it gets a >> confirmation. >> >> Let us know how that goes. >> >> -Ed- >> >> >> --- In [email protected], "Brad" <bcansler@> wrote: >> >>> I read through other posts and see that some users have had a similar >>> >> problem to mine but updating their Nuvi & OT2m firmware solved their >> problems. >> >>> In my case, I'm running two brand new Nuvi 350 / OT2m stations (one >>> >> for my car and one for my wife's car) and both stations have been >> updated to the latest versions. For the Nuvi - that is version 6.20 and >> for the OT2m I'm on firmware version 55076. >> >>> Unfortunately, the updates haven't solved my problem. I can send a >>> >> message from Nuvi 1 to Nuvi 2 just fine but then Nuvi 1 says "Sending" >> and eventually, I receive the message on Nuvi 2 again, and again until I >> delete the message from the outbox on Nuvi 1. >> >>> I have also noticed when I try to send a message from Nuvi 2 to Nuvi >>> >> 1, I never receive the message on Nuvi 1. >> >>> This may be a clue that this problem has something to do with >>> >> acknowledgement perhaps. >> >>> I have checked through the config settings on both OT2m units several >>> >> times each but can't seem to find anything wrong with either unit's >> configuration. >> >>> Both sets of radio cables I'm using came from Byonics and they all >>> >> seem to be transmitting / receiving just fine because the two different >> call signs are showing up on both Nuvi's as stations heard. There are no >> other APRS stations within radio communications range of my home so I >> know that the only way the callsigns show up in the list is if the two >> stations digipeat each other. >> >>> Transmit on both radios is set to Extra Low as they are in the same >>> >> room with each other and the receive volume is set to about 50% of max >> volume on both radios. >> >>> I've spent about 4 hours or more trouble-shooting this evening but >>> >> I've tried everything I can think to try. I'm hoping that someone has >> come across this problem on updated equipment and found a solution. I'm >> sure it is probably some sort of user error but I don't seem to be able >> to figure out what I've done wrong. >> >>> Any help or thoughts on this are appreciated. >>> >>>
