Hi Alan, Got your last and thought I had things all setup, but how could you explain this one? Have a look at the following three files in the files section please as see what you make of it. File 1 - Odd.png File 2 - Aprs Problem File 3 - Config fix 3
The problem is it shows me on the A31 when I was infact on the A3 this being which can be clearly seen on the picture APRS problem any help please. Andy Wilkinson Membership Officer South East Hampshire RAYNET --- In [email protected], "Alan" <a...@...> wrote: > > You had a lot of messed up settings, the one that caused the continuous TX > was the profile switch jumper 1 to jumper 1. this will cause a mobius loop of > TX. Uncheck all of the profile stuff. > > Other stuff: > The loooooong TX delay 465ms? set to 18ms (watch out, the CFG program will > lower this TXD number every time you look at the other profile. So set to 18 > just prior to sending config to OT2). > > the loooong path, try the recommended mobile path, this works almost > everywere. Three hops is usually not needed "wide1-1,wide2-1" I looked at > your RAW history and found that you usually need only one hop to get to an > I-gate. > > uncheck all the stuff, with that large payload, many packets will fail. Short > position reports are more successful. Send Staus only once every 15 packets, > not every time. > > Position was set to fixed, set to GPS for moving objects. > > Is your GPS 9600Baud? Set to auto baud, or to your GPS's baud rate. > > Once you get it working, then you can start playing with additional bells n > whistles. Remember that short packet burst will have a much greater success > rate. > > Please try out the 2EOBNS_FIXED config file that I posted to the folders. > Make sure your TX deviation is set to a "nice" level. It should sound as loud > as a DTMF tone, not blasting, not sub-audible. > > Cheers, > Alan > n6vud
