Thanks for the tips. I found a later version of the MT AIO config that allows changing the TX Delay and the T2 seems to be repeating it with greater regularity. (Look for K7RBW-14).
RE adjusting the AIO's Deviation: I actually tuned it using the audio spectrum analyzer using the individual tones. First I turned on the low tone and tweaked the Dev pot to find where the low tone was "purest." Tweaking the Dev. Pot would cause a high tone to come in and out of the spectrum while sending a low tone so I adjusted the pot such that the low tone didn't send out any high tone. Then I checked the high tone and it was slightly lower than the low tone so I figured that was as good as I could get without any other instrumentation. I've also used digipan's waterfall to tweak and test the output. (One of these days I'll get some real test equipment :) It still sounds a bit strong, but at least it's cleaner. Thanks again for the tips! --bob K7RBW --- In [email protected], "Alan" <a...@...> wrote: > > I don't think I've ever heard a MT AIO that didn't sound like the TX dev was > flat topping on the limiter (WAY too loud). They always have TX delay waaaay > too long, at least half a second. My OT2's have a hard time decoding them too. > > The advanced AIO config (download from byonics) will let you turn TX delay to > a sane delay, like 120MS to 180MS max. The TX level is controlled with a pot. > > If you are routing "speaker" audio into the sound card the tones should be > about the same level. If the low tone is at a higher level than the high tone > many digis will have trouble decoding it. The tones should be a smooth round > shape, no flat tops, or buzz saw. That was a good idea using AGWE to look at > your wave form;-) > > The link below is a MT AIO that wandered into my area. The user had cranked > the TX dev pot up. He did turn it down after I contacted him, but it still > sounds too loud. > http://www.youtube.com/watch?v=StLHPvVUX5c > > Short packets win, long packets get clobbered. Your AIO looks good with MicE > and status only sent about once every 10 beacons. > > You can also test how well digis decode you by programming your path to a > nearby digis call sign. Make adjustments until it starts to receive you well. > Remove WIDE1-1,WIDE2-1 and put a nearby digis call in (N7JEX-10) Test if it > digis your problem Tracker. > > Good luck, > Alan > > > > --- In [email protected], "k7rbw" <flyboy_pa34@> wrote: > > > > I tuned in the deviation using the sound card tuner of AGWPE until I got a > > clean tone on each frequency. That seems to help a bunch. At least I'm > > getting about 3/5 of the packets now. Some of the lost packets could be > > attributed to collisions, but some are still coming in clear on the AGWPE > > monitor while not showing up in the Tracker 2. > > > > Adding the EQ jumper to the T2 (which I believe removes the EQ) seems to > > help. > > > > As far as the TXDelay goes, configuration of that value is disabled in my > > MTAIOConfig program. > > > > I'm still stumbling around... > > -- bob > > K7RBW > > > > --- In [email protected], "Keith VE7GDH" <ve7gdh@> wrote: > > > > > > Bob K7RBW wrote... > > > > > > > 5) Beacon 2 - Byonics AIO beacon. These packets get digipeated > > > > intermitently. Maybe 1/10 of the time but not with any obvious pattern. > > > > > > How is the deviation and TXdelay on the AIO? If you don't have > > > a deviation meter, an experienced ear should be able to tell if it > > > was very high or very low. Long and short transmit delays are > > > also easy to tell by ear. > > > > > > 73 es cul - Keith VE7GDH > > > -- > > > "I may be lost, but I know exactly where I am!" > > > > > >
