开云体育

I believe the Blue LED is power. Red - TX Yellow - Carrier Detect Green - GPS Robert Giuliano KB8RCO On Wednesday, April 24, 2024 at 07:32:03 PM EDT, AB9NN - Jon Kreski <jkreski@...> wrote: This while at rest. My iGate is not processing APRS packets. Is the blue light a problem indicator?

Is there anything on the market that is a rough equivalent to the MTT4B? Alternatively, any idea if the MTT4B will be coming back? I am currently using one coupled with a Raspberry PI as an igate, and I'm considering setting up another igate at a different site. The MTT4B and Rpi makes for a nice small package with minimal cables. Thanks, -Dj

I am trying to connect to my TT4 with TeraTerm (latest version). It shows me three options to connect to. One seems to be a RT Systems Cable. That can't be the right one, can it? I connect to it but only get a black screen. I seem to remember from several years ago that I had to put TeraTerm into a special command mode by quickly pressing escape three times or something but for the life of me I can't seem to get that right. There are two other options offered when I go to connect. One is Com 5 and one is Com 6. Sometimes it will connect and sometimes it won't. I am trying to connect at 1200 baud which is what the radio is set at. Is that the correct baud rate? Can someone walk me through how to do this. I am trying to tune the RX AMP on the TT4 for an iGate installation on a new radio. The radio is a Yeasu FTM400 XDR and the PC is a newish Windows 11 PC. Maybe two years old. Latest Windows updates installed. Connection to the radio is through the MIC and SPKR jacks as the data jack won't transmit on APRS and there is no cable manufactured for the data jack by the TT4 folks. Thanks!

Hello can I increase this to 60 sec?

new to the group just bought an TT4 .

I’m working with an older version of the micro trak AIO (version 1.4.4 on circuit board) trying to change the callsign in its program using “Real Term,” and I have a failure to communicate. I’ve been using the stereo plug to USB adaptor that came with unit. I’ve identified the proper com port, set the baud rate at 19,200, and turned flow control off. When I turn on the unit, and hit ESC thrice, no joy. I’ve not had this problem with either TT3s or TT4s. What am I doing wrong?

Hal, you seem to be jumping to other threads and re-asking the same questions. This makes it VERY difficult for users to find the information when they have the same question. Your question is about using the TT4 to do both DIGI and Wx (from Peet station). What firmware version are you running on the TT4? Looks like the latest is still 0.72. Have you recently upgraded it? You don't say the radio type you are connected or how much power you are using with it. When the radio locks in TX, does the TT4 LED stay on as well? There are 2 main causes of the radio remaining in TX: 1. The TT4 locks in TX mode and the TT4 TX LED stays ON. This is typically a setting problem, which may be caused by a corrupt EEPROM. A possible fix is to reset the settings to default, then reload the settings file you attached on the other thread 2. The TT4 stops the TX (LED goes out), but the radio remains in TX. Many possibilities here. a) Incorrect JP8 setting may cause this, but often stays in TX right from power up. b) RF may cause this. Try moving the TT4 further away form the radio / antenna c) Failed MPS2222A (not real common but happens) d) A friend had an issue when they used PTT_In "instead of" PTT_Out. I only connect PTT_Out (Pin 3). I have never connected both. Having both may be a factor. BTW, You have ALIAS1 as your Callsign-SSID. You can set DIGIMY TRUE and get the same affect. This is PREFERRED to ensure you don't change the CALLSIGN-SSID and forget to change the ALIAS1 setting. They are always tied together. I would also comment that PPERIOD and BPERIOD set to 120 is pretty often for what appears to be a stationary implementation. ------- Rob Giuliano KB8RCO >>> Quoted part below <<< Robert, The CDMODE is "Level" and the CDLEVEL is 20. I tried adjusting the transmit audio level and it didn't change anything. It currently cycles through, like a normal startup, the radio keys and locks in transmit when it finishes the startup sequence. It looks like it works, but the radio sticks in transmit. This is exactly whet my old TT4 (2013) does and I hd thought I had broke it. I have attached the config file. I set it to K4PAR-2 so I could see it on SAR Trak. Out WX station is K4PAR-1 and runs a TT3 WX Tracker. Like I said the cable works fine with another TT3 I have, so it has to be in the TT4. Thanks for your response, I sure hope I didn't break it. Old Hal, K6DPL Hide quoted text Since the big difference between TT3 vs. TT4 is receive capability. First question would be"What are the settings for CDMODE?" Although if it "keys" the radio, it typically isn't CDMODE. Next questions would be: a) Are you sure it "keys" the radio? or just turns on the TX LED on the TT4 (radio doesn't actually get keyed)? b) Did you adjust the TXLEVEL? Robert Giuliano KB8RCO On Wednesday, January 31, 2024 at 08:08:57 PM EST, halgreid@... <halgreid@...> wrote: Troops. I got my new TT4 yesterday and found the configuration files I had used with the old one. Set up to do Peet Bros WX and digipeat. Everything was working fine and I just needed to get the right lat/long numbers for our antenna site. . somehow, it quit transmitting packets although it would key the radio. Now, it looks normal without a radio connected, with the radio connected, it cycles then the transmit stays on. When it does the power on transmit, I don't hear any packets, The cable and radio works fine with my TT3, JP8 is right. Did I break it or do I have a setting wrong? I see Byon is on vacation until February 15th, so I can't ask him. Tnx, Old Hal, K6DPL

I just downloaded the Quick Start Guide 0.7 and it still references the old Yahoo Group. I wonder how much of the other documentation still references the old group? ------- Rob Giuliano KB8RCO

Hijacked Topic now a separate thread. The TT4 is capable of both DIGI and Wx functions - you even acknowledge you had one doing that at your home station. The only question is that is Wx Trax? Is it a computer software package or a Wx station device? I did an internet search and only "Wax Trax" or WxTrack showed up. The next question would be whether the club station would have a computer attached - or stand alone. I would guess stand alone as there is no need for a computer for the functions you are working with - UNLESS Wx Trax is a computer app. ------- Rob Giuliano KB8RCO On Tue, Jan 23, 2024 at 06:54 PM, <halgreid@...> wrote: Guys, I have a simple question. Our Club has had a Peet Bros 100 and a WX Trax running for several years (K4PAR-1). I believe that several years ago I also had a TT4 running as a WX station (Peet Model 100) and as a digipeater at the same time on my home station. Recently, some of our Club members have asked about a digipeater. Can I use a TT4 for both, replacing the TT3 WX Trax? Tnx, Old Hal, K6DPL

Hello, I have a MicroTrak 2001 and am using TinyTrak3Config v1.4.6 to configure it. However, when I "read version" or "read config", I get a "TinyTrak3 not found ()" error. The MicroTrak is connected to my Windows 10 laptop via USB. I did successfully configure it once, but have not been able to a second time. Any ideas on how to get connected again? 73, --Michael WZ0C

If there were a way to add a momentary (Normally Closed) switch on the 5V pin 4 of the TT-USB inside the DE9 case, that would make this device ideal. Pressing the switch would allow the user to momentarily interrupt power to the TinyTrak device and allow it to go to the boot loader. Just a thought if future changes are made to this device ------- Rob KB8RCO

I've been using an Aprsworld APO3 battery cutoff for several years now and during that time i've had several TinyTrak units go bad and stop working. Do I just have a bad one or has anybody else had this problem? I like the idea of not having to run an on/off switch up to the front but not at the cost of replacing a TT3 or even worse a TT4. Has anybody found a battery cut off that works better? This could be the reason why Byonics doesn't sell them? -- 73, Don W4GCW

Howdy; I am trying to make some changes to my settings in TinyTrak4. I want to send the temp and voltage values when it beacons. I saw earlier using ^ T and ^ V would do what I wanted. But I cannot get this to the system. I am using Hyperterm to do this with, but no luck. Just blinks at me. Suggestions? I had issues changing some settings earlier. Appreciate the help. 73 Mike - N7ZEF

In case any of you were wondering, some of the parts for our MF-15 transmitters became extinct, and when we ran dry, so did the old MF-15. It was very much based on the TT3 encoder, and in fact, could be loaded with APRS firmware for anyone who had the urge to have a 15 mW APRS transmitter. ( 15 Milliwatts works surprisingly well as an APRS transmitter at the edge of space...on the ground, not so much) At any rate, we have replacement for the MF-15, the MF-50. The MF-50 follows the same name scheme, and has an output of between 0db and 50 mW's. (Strangely, one of the chief complaints about the MF-15 was that the fixed, 15 mW power output was too high for typical park-style fox hunts!) You can set the output of the new unit anywhere from 1-50, which kinda-sorta reflects the power output settings. Its a whole new RF section and a whole new processor. The unit uses the ubiquitous CH340 USB Drivers, which probably already live in your computer, even, presumably, with Windows 11. You probably already have the programming cable! It can be programmed using pretty much any terminal program or an online configurator, and a GUI will no doubt be along in due course. The MF-50 is NOT backwards compatible with Micro-For Config or any of the APRS firmware versions, but an APRS version is not out of the question. The transmitter has a Micro USB connector through which you can operate the transmitter or charge an internal LiPo battery. Here is the manual for any FOX people who may be interested: https://byonics.com/downloads/MicroFox-50_Manual_v0.1.pdf I went out in the rain a couple of days ago, just to see what kind of range to expect, and a had a fairly solid signal at 5 miles, roof-to-hill top, using a Baofeng UV-50 and an Arrow 3 element yagi, which exceeded my expectations!

No, No, No, No! Keep in mind that for every digipeater you put on the air you HALVE the channel capacity! That's right you 1/2 the number of packets the channel can pass. Digipeating is a store and forward system, so as it repeats it duplicates the time needed, and reduces the time available to hear new packets. You need to consider the RF environment before you start digipeating. If you look at the large metropolitan areas, you actually see the performance of the 'system' decline when random additional digipeaters are put in place. Yes, there are large portions of rural America that could benefit from additional digipeaters, and Igates. But you need to consider the environs around your area to provide the best service. I get concerned when general statements about adding digipeaters get thrown out there without qualification. If people don't understand the implications of placing a device on the air, they risk adding to congestion and decreasing the capacity of the system. Chuck - n0nhj On 11/21/2023 06:17, vhsproducts via groups.io wrote: Virus-free.www.avg.com

Hey folks! I just wanted to say thank you to everyone active here. Every day I get a new message from this group is a good day, because I know I'll learn something or see someone being really cool and working to help someone out. That's awesome. ? Hope you all have a good day! I appreciate the heck out of you all and I'm thankful to be here. 73, Vaughn W0ULF

My TT4 powers up with a constant green (power) and yellow (carrier detect) LED's lit. This is with or without a radio connected. I am unable to communicate with it via Tera Term. It has worked fine for several years. Is there any way to reset it or tell whether it is a hardware or firmware issue?

We have inventory in stock for the new Micro-Trak MT-AIO. It is a little smaller, a little more powerful, and a bit lighter than the old MT-AIO, which became a victim of Covid and supplier shortages. This new version uses 4 X 18650 LiPo batteries instead of the old version's 8 X AA batteries. With standard protected batteries, it puts out about 10 Watts; with "unprotected" 18650 batteries, it can put out 17-20 Watts. The GPS manufacturer claims it is good to 80KM altitude, but we have not been able to fly one yet to confirm this. Link for the addendum to the manual: https://byonics.com/downloads/MT-AIO_V4_Manual.pdf 73, Allen AF6OF

Hello all - Rob (KEOMIC), trying to setup a digi using the Baofeng UV-5R and a TinyTrack 4. I've perused the forum; and see the various notes about Baofeng not an optimal choice. However, I am not sure I want to spend another $$$ on a Yaesu FT60 or similar until I figure out the gremlins in this toy. Short version - it is currently a very nice receiver, not getting anything from the TinyTrak to the Baofeng. Here are some of my settings/configurations: Connected the Baofeng to the TinyTrack via the Byonics HTK2 cable. Under the 'hood' of the TT$: JP8 is 'open' JP6 is 'open' - no GPS module; entered coordinates for a 'fixed' location GPS Valid light does not illuminate. Not much on the Baofeng has been tinkered with from the default settings: VOX on the radio is set to off (I've tried on/off); squelch is set I can get a "Carrier Detect" when my Yaesu FT3D beacons position; however never any Transmit indication. Software settings below (TeraTerm for serial connection). display BANK is 0 P300 is FALSE TXTDISP is FALSE NODISP is FALSE PPATHING is FALSE DMSDISP is FALSE MICETMV is FALSE ENTS is FALSE TELHIRES is FALSE TELVOLT is TRUE TELTEMP is TRUE PREEMPT is FALSE DIGIID is TRUE WXPOS is TRUE TELREAD is TRUE FRAWDISP is FALSE HRAWDISP is FALSE WYPTXT is FALSE PKTICOM is TRUE PKTOCOM is FALSE RPATHDISP is FALSE LEDS is TRUE PAVPEN is FALSE DEC96 is FALSE DDIST is FALSE HEADERLN is FALSE DMETRIC is FALSE SOFTRST is TRUE MSGCMD is FALSE MSGCAP is FALSE LRNTPS is FALSE GPSCHK is FALSE INTCLK is FALSE DECSTAT is FALSE DIGIMY is FALSE TOSV is FALSE TALT is TRUE TSPEED is TRUE TIMESTAMP is TRUE TIMEHMS is TRUE SBEN is FALSE TSWPT is TRUE AMODE is TEXT BMODE is GPS ABAUD is 19200 BBAUD is 4800 BNKMODE is 0 SSIDROUTE is 0 ALTNET is APTT4 MYCALL is KE0MIC-1 PATH1 is WIDE1-1 PATH2 is WIDE2-1 PATH3 is TSTAT is /TinyTrak4 Alpha BTEXT is >/TinyTrak4 Alpha BPERIOD is 0 TXD is 40 MTXD is 10 PERSIST is 65 SLOTTIME is 15 QUIET is 10 TRNKMODE is 0 CDMODE is TONES CDLEVEL is 20 TXLEVEL is 128 TXTWIST is 50 RXAMP is 12 GWAYLEN is 9 GWAYMODE is NMEA GRELAYBITS is 1 GRELAYRATE is 0 GKRELAY is 0 LOCATION is 3889.9362N 10455.7013W GALT is 1000 TSYMCODE is > TSYMTABLE is / STATUSRATE is 1 PPERIOD is 3600 MPPERIOD is 0 SBSSPEED is 5 SBFSPEED is 60 SBSPERIOD is 1800 SBFPERIOD is 90 SBTANGLE is 27 SBTSLOPE is 255 SBTTIME is 5 MMSG is 0 TSOFFSET is 17 TDAO is 0 TPROTOCOL is MIC-E TPSWITCH is 0 TPERIOD is 0 TVOLTTWK is 128 TTEMPTWK is 128 WPERIOD is 0 ALIAS1 is TEMP ALIAS2 is ALIAS3 is DUPETIME is 30 FILTERCALL is TXFREQ is 144.390 RXFREQ is 144.390 RXSQUELCH is 0