Andy, Looks like James called right. Your second profile has a different SSID.
This link shows both SSID's and -4 never updated coordinates. http://aprs.fi/?call=a%2F2E0BNS-4%2C2E0BNS-9&mt=roadmap&z=10&timerange=86400 It looks like your GPS might not be locking, and it's sending the coordinates that are stored in the OT2. Both profiles show up in the same location on A31 http://aprs.fi/?c=raw&call=2E0BNS-9 What GPS do you have? What port, and baud rate? I remember something about port B having a problem with some GPS's. Make sure the "act" led flickers once the GPS locks. Check both profiles. The config file looks good. The only things I would change is "comment" to "Status" every 15 positions. That is a lot of text to pile on top of every position report. Then you will have a much greater packet success rate. You might consider changing Comment to "Status" with an occasional text report of something sent between every 5 and 15max position reports. Also, the TX Delay bug in the config program lowers the TX Delay to 0. It lowers every time you look at the other profile. Just make sure to set it to about 18MS just before saving the config. Cheers, Alan --- In [email protected], "Andy W in Waterlooville" <adw...@...> wrote: > > 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" <alan@> 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 >
