Ron WR5RR wrote... > I couldn't send a message, it would hang in the outbox forever, until > I sent the "--Retries 6" from the Nuvi to the T2.
I suspect that you previously had RETRIES 0. It won't even transmit a message then. Setting it to 6 is a pretty good number. Take a look at RETRYTIME as well. RETRIES is the number of times the T2 will try and send the message. It waits RETRYTIME before trying again, and increases the time between tries by this value each time it tries. Mine is set to 7 seconds. > If there are settings in the otwincfg I overlooked them. I'll see if > any messages get an Ack, but so far from the T2 messages sent, don't > send the sending station an Ack, indicating that the message was > successful. It's all new to me. When you send a message, you don't send an ACK. It is the receiving station that sends the ACK if it hears your message. I just tried sending messages to WR5RR and to WR5RR-8 but didn't get an ACK from either one. I could retry them later. Update... I still didn't get any ACKs, but I did receive your messages saying "Received on my mobile" and "OK tnx that's what I have noticed". Obviously, a nearby IGate considers you a local station and gated my messages out to you on RF and you received them, but your ACKs to my messages didn't make it to an IGate. It could be a path issue. Are you using a one hop WIDE2-1? On the other hand, your message made it to an IGate or I wouldn't have received it. You could try a two hop WIDE1-1,WIDE2-1 to see if makes any difference. I applaud the use of shorter paths, but sometimes you do need a longer path. 73 es cul - Keith VE7GDH -- "I may be lost, but I know exactly where I am!"
