OK, I now have the latest build OT-2 and the latest Nuvi load and it's still broken. See my findu (K5TAN-9). Retries set to 6. Every message sent is not getting on the web, but there are more than 6. Nuvi shows the one message and says sending. If I let it go it will do it all night. Other units are doing the same thing. Lynn D. says someone else here in the area overloads him, with multiple messages and Tim D. does the same thing to me. I've read the FMI ICD and I can't figure out how this is supposed to work. It doesn't say anything about the Nuvi (client) re-sending messages to the OT2 (server) but I think that is what is happening. Messages sent to K5TAN are the result of a single message composed in the Nuvi. Messages sent to K5TAN-1 are from the console. It looks like the OT-2 appends a designator to the message (part of APRS messaging protocol?). I sent two separate messages to K5TAN-1, test and test1. Each message retried out after 6 transmissions. First message was designator ap, second was ba. So I take from this that the Nuvi originated each of the messages sent to K5TAN that has an incremented designator. What causes it to do this? Timeout? NACK from the OT2? I can't find this in the FMI ICD. I'm guessing the Ot2 sends something to the Nuvi when it retries out and that is different from what it sends after a successful delivery. For example, what is different about -- messages from - messages? The OT-2 apparently sends something to the Nuvi when it receives a command that results in a date/time on the Nuvi display. I think it does the same when a message is successfully received by another station. Whatever it does in those cases, it should do when it retries out. If the OT-2 is sending the date/time group that gets displayed, maybe it could send all dashes or something when the message is not received. Mostly blind speculation here, but hopefully there is a relatively simple fix. Also, I can't tell any difference in output level in a monitor receiver from TXLEVEL 0 to 255. How much difference should that make? I would think that 0 would be 0 and 255 would be a different level depending on where the jumper is set. Al
--- On Tue, 2/23/10, Scott Miller <[email protected]> wrote: From: Scott Miller <[email protected]> Subject: Re: [tracker2] Re: Messaging anomalies - Nope, still sending forever...... To: [email protected] Date: Tuesday, February 23, 2010, 12:43 PM Use the 'web' button in the config program and grab the latest one. It's 55-something. Scott Al Waschka wrote: > > > I have the latest Nuvi FW. I can't relate the information on the > firmware history (just release dates) to the response I get to VER, but > my unit is Build 54746. > > Al > > > --- On *Tue, 2/23/10, Scott Miller /<[email protected]>/* wrote: > > > From: Scott Miller <[email protected]> > Subject: Re: [tracker2] Re: Messaging anomalies - Nope, still > sending forever...... > To: [email protected] > Date: Tuesday, February 23, 2010, 12:57 AM > > Hmm. And you're using the latest T2 firmware? What is RETRIES set to? > > Scott > > [email protected] > <http://us.mc1806.mail.yahoo.com/mc/[email protected]> > wrote: > > > > > > Sorry, my mistake. Go to findu and look at my messages (K5TAN-9). > > Message was retransmitted roughly every two minutes for 1.5 > hours. It > > only stopped because I powered the system down to re-run the > power and > > data cables to the Nuvi. Later tonight after finishing the > rewiring I > > tried to get a VERSION report out of the system, but I had to > delete the > > old message out of the outbox. Either RETRIES isn't working on > messages > > or the Nuvi is re-sending the message to the OT2. I still think > the Nuvi > > needs to handle a message retrying out as if it was acked by the > > receiving station to clear out the OUTBOX. > > > > Al > > > > --- In [email protected] > <http://us.mc1806.mail.yahoo.com/mc/[email protected]> > <mailto:tracker2%40yahoogroups.com>, > > "awasc...@..." <awasc...@...> wrote: > > > > > > Scott, > > > > > > With the new Nuvi firmware, RETRIES appears to limit the > > transmissions where it wasn't with the old firmware. However, when a > > message is never acked and retries out, it stays in the Nuvi > outbox and > > subsequent messages are not transmitted to the OT2. I think OT2 > is not, > > but needs to, send something to the Nuvi when a message retries > out. I > > verified this by sending a message to a station that was not on > the air. > > It retried out. I then tried a VER command and got no response > until I > > went in and manually deleted the previous message from the outbox. > > > > > > Al > > > > > > > > > --- In [email protected] > <http://us.mc1806.mail.yahoo.com/mc/[email protected]> > <mailto:tracker2%40yahoogroups.com>, > > Al Waschka <awaschka@> wrote: > > > > > > > > I did not have the latest FW. I have now upgraded and will > see how > > that works. > > > > > > > > --- On Thu, 2/18/10, Scott Miller <scott@> wrote: > > > > > > > > > > > > From: Scott Miller <scott@> > > > > Subject: Re: [tracker2] Messaging anomalies > > > > To: [email protected] > <http://us.mc1806.mail.yahoo.com/mc/[email protected]> > <mailto:tracker2%40yahoogroups.com> > > > > Date: Thursday, February 18, 2010, 11:44 AM > > > > > > > > > > > > Have you checked to make sure you're running the latest nuvi > firmware? > > > > They fixed a bug at some point that caused problems with > message ACKs. > > > > > > > > Scott > > > > > > > > awaschka@ wrote: > > > > > > > > > > > > > > > Hi - > > > > > > > > > > I purchased an OT2m in October and have it hooked up with > a Nuvi > > 350 via > > > > > the FMI cable purchased at the same time. I'm seeing some > > anomalies in > > > > > the messaging as follows: > > > > > > > > > > 1. On first few tries, I got back an indication that a sent > > message was > > > > > acknowledged. Haven't seen that lately. > > > > > > > > > > 2. A single receive message will come in and be displayed > on the > > Nuvi > > > > > multiple times. > > > > > > > > > > 3. I sent a message yesterday afternoon and today, after > over 50 > > > > > retries, the message is still being sent out. Retries is > set to 6. > > > > > > > > > > 4. When I tried to queue the retries query, it wouldn't go > out > > until I > > > > > cleared the old messag in the outbox. It looks like the > OT2 is not > > > > > acking the message to the Nuvi so the Nuvi keeps sending it. > > > > > > > > > > Any ideas? > > > > > > > > > > Thanks, > > > > > > > > > > Al K5TAN > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------ > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > ------------------------------------ > > Yahoo! Groups Links > > > (Yahoo! ID required) > > > [email protected] > ><http://us.mc1806.mail.yahoo.com/mc/[email protected]> > > > > ------------------------------------ Yahoo! Groups Links
