开云体育

Hello all. You guys have been a ton of help in the past so thanks for that. I'm hoping you can help me get find the root of this "Unsupported Packet Format" issue. Strangely enough it digipeats other stations jsut fine, but doesnt show up itself on maps and has this error. Some messages weren't showing that way, but most are here is a copy and paste: (Station is K2CZH-1) 2023-09-25 13:06:47 EDT: K2CZH-1>TPUR0W,WIDE1-1,WIDE2-1,qAR,W2KB-15:`fAYl &>/"6@}Mobile Digipeater 2023-09-25 13:13:49 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:23:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:28:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,W2KB-15:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:33:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:36:47 EDT: K2CZH-1>TPUR0W,WIDE1-1,WIDE2-1,qAR,N2WH-10:`fAYl!S>/"6;}Mobile Digipeater 2023-09-25 13:38:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,W2KB-15:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:43:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 13:53:50 EDT: K2CZH-1>APTT4,W2LV-3,WIDE1*,WIDE2-1,qAR,W2KB-15:Monitoring 146.52 [Unsupported packet format] 2023-09-25 14:03:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 14:06:47 EDT: K2CZH-1>TPUR0W,WIDE1-1,WIDE2-1,qAR,N2WH-10:`fAYl!S>/"6>}Mobile Digipeater 2023-09-25 14:13:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 14:33:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 14:38:50 EDT: K2CZH-1>APTT4,W2LV-3,WIDE1*,WIDE2-1,qAR,W2KB-15:Monitoring 146.52 [Unsupported packet format] 2023-09-25 14:43:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 15:03:50 EDT: K2CZH-1>APTT4,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] (here was where I changed the apptt4 setting - no dice) 2023-09-25 16:05:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 16:10:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 16:30:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 16:40:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 16:45:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] 2023-09-25 16:50:54 EDT: K2CZH-1>K2CZH,WIDE1-1,WIDE2-1,qAR,N2WH-10:Monitoring 146.52 [Unsupported packet format] And in case its my settings, which I suspect but can't find) (I changed the APPT4 to my callsign thinking that was the problem but it didnt fix the problem just changed the callsign field of the problem lol) BANK is 0 P300 is FALSE TXTDISP is FALSE NODISP is TRUE PPATHING is FALSE DMSDISP is FALSE MICETMV is FALSE ENTS is FALSE TELHIRES is FALSE TELVOLT is TRUE TELTEMP is TRUE PREEMPT is TRUE DIGIID is TRUE WXPOS is FALSE 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 TRUE TOSV is TRUE TALT is TRUE TSPEED is TRUE TIMESTAMP is TRUE TIMEHMS is TRUE SBEN is TRUE TSWPT is TRUE AMODE is GPS BMODE is TEXT ABAUD is 4800 BBAUD is 19200 BNKMODE is 0 SSIDROUTE is 0 ALTNET is K2CZH MYCALL is K2CZH-1 PATH1 is WIDE1-1 PATH2 is WIDE2-1 PATH3 is TSTAT is Mobile Digipeater BTEXT is Monitoring 146.52 BPERIOD is 300 TXD is 40 MTXD is 10 PERSIST is 65 SLOTTIME is 15 QUIET is 10 TRNKMODE is 0 CDMODE is TONES CDLEVEL is 20 TXLE

How can I turn off beaconing on my TT4 but still allow APRSIS32 program to beacon so that my station shows up only once on APRSIS32 and APRS.FI. Currently on APRSIS my iGate from TT4 is shwoing up on APRSIS32 as AB9NN and my beacon from APRSIS32 is shwoing up on APRSIS32 as AB9NN-48. On APRS.FI I only showup as AB9NN-48. THanks! I would like AB9NN-48 to be an RF beacon on APRS. I am running a Windows 11 PC and a Yeasu FTM400XDR radio. APRS on my radio is defined as AB9NN-9.

Hi All - Sorry if this is a basic question, but I have my TT4 working well as a digipeater with the Mycall set. It seems to only retransmit my callsign, which is exactly what I wanted. I also configured the Port A as KISS and have the radio hooked up to APRSIS32 and was able to configure that to scoop up the RF from the TT4. It doesn't seem to be able to transmit beacons or messages, and I am wondering if that is because I configured it as a digipeater too. I realize that being an iGate and a Digipeater doesn't really make sense (why rebroadcast if you can get in the network), but I plan to use the unit both at home as an iGate and use the radio as a digipeater in the car when I do some SOTA hiking in the more remote parts of Maine. So I'm hoping I can use one configuration, but perhaps I need two. Anyway I am new to both the TT4 and APRSIS32 so if someone could point me in the right direction I would appreciate it. Thanks, Greg KC1RID

Hey guys, I'm looking for either an in line Bluetooth adapter or the MTT4BT radio for my truck. Let me know if anyone has one for sale they want to get rid of. Thanks, Chris

ALLCON, We had a number of PCB production issues with the prototype MT-AIO V4.1 tracker. This is improved version of our old MT-AIO tracker ( The one in the yellow Pelican case) A bunch of parts for the old AIO either became obsolete, enormously expensive, or only unpredictably available. The ubiquitous Pelican 1030 case we used for years was also dropped, and Pelican is migrating ( See what I did there?) to clear boxes with colored inserts. These are basically little solar-powered ovens. After an interim redesign, to use the Flambeau "Black Ribbon" case, Flambeau dropped these too. Something about a flu that was going around they said. After finding a new and suitable case ( the S3, T-2000 cases) we redesigned the AIO around this case. These cases are smaller, stronger and don't chip like the Pelican Cases, They are O-Ring gasketed, and I expect that the new AIO will be submersible ( Well, I guess any thing can be submerged, but the new AIO should survive the experience. It may float, depending on the battery weight, but no promises. They will fit neatly in an IFAK case. The new unit is intended to be powered by 4 X 18650, unprotected batteries. You can use protected batteries too, but you will need to turn the power down to about ten Watts or the batteries will give out too quickly. With this power source, the unit will start out with about 20 Watts output, and drop to about 17 Watts after an hour of run-time, where i levels off. With several of the 18650 batteries I have tried, the prototype seems to run for about 50 hours with two minute transmission intervals. Batteries vary dramatically, and while it may be a shocking and slanderous assertion, I believe that many of the Distributors, Dealers, and Manufacturers may not be telling the complete truth about their products specifications! Shocking. At any rate the standard antenna we used with the AIO, a Nagoya quarter wave whip, seems to handle 20 Watt transmissions. I think it would be better served to use one the AAbree "tape measure" style antennas ( Yes, they work!) to get the most out of the higher power transmitter, and to keep it away from your head. I was reluctant to make the unit dependent on LiPo batteries. Primarily because I thought that LiPo's would freeze to death in High Altitude Balloons. One of our clients disabused me of that notion, they seem to work fine in older AIO's, and clock their power up to about 12 Watts output. We will probably produce all of the new units with high-altitude ( Above 60,000 feet) GPS receivers. I will post photos as soon as I have something that is not just a mess of parts splattered on a workbench! 73, Allen AF6OF

I followed all the settings in both the "firmware" documentation and posts on here and yet to get my TT4 to digi. I can see beacons on a handheld but it does not appear to be making it anywhere else. Here is settings. Thoughts ? :disp 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 TRUE RPATHDISP is FALSE LEDS is TRUE PAVPEN is FALSE DEC96 is FALSE DDIST is FALSE HEADERLN is FALSE DMETRIC is FALSE SOFTRST is FALSE 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 9600 BBAUD is 4800 BNKMODE is 0 SSIDROUTE is 0 ALTNET is APTT4 MYCALL is KD4MOT-3 PATH1 is WIDE1-1 PATH2 is WIDE2-1 PATH3 is TSTAT is /KD4MOT-3 BTEXT is kd4mot-3 BPERIOD is 900 TXD is 100 MTXD is 10 PERSIST is 65 SLOTTIME is 15 QUIET is 10 TRNKMODE is 0 CDMODE is PIN2 CDLEVEL is 10 TXLEVEL is 128 TXTWIST is 50 RXAMP is 14 GWAYLEN is 9 GWAYMODE is NMEA GRELAYBITS is 1 GRELAYRATE is 0 GKRELAY is 0 LOCATION is 3657.0138N 07989.5980W GALT is 1000 TSYMCODE is # TSYMTABLE is / STATUSRATE is 1 PPERIOD is 900 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 APRS TPSWITCH is 0 TPERIOD is 0 TVOLTTWK is 128 TTEMPTWK is 128 WPERIOD is 0 ALIAS1 is WIDE1 ALIAS2 is ALIAS3 is DUPETIME is 30 FILTERCALL is : Jeff / KD4MOT

Hello. I am part of a school amateur radio club that is launching a weather balloon soon, and we are using the MicroTrak 1000 to track it. We are able to receive the MicroTrak on our station's i-gate, but not our handhelds. We are using a couple of Anytone AT878UVII, and they can receive other APRS packets. However, they can't pick up the ones from the MicroTrak. Can anyone help, solve, or replicate this problem?

I recently changed a setting in my TinyTrak4 and don't understand why I'm having a problem. Setting was: PATH1 W4XXX Setting now PATH1 WIDE1-1 I've changed the setting to WIDE1-1, reinstalled the TT4 and still it's using PATH1 W4XXX. After doing a DISPLAY I see the new setting and don't understand why the TT4 doesn't see it. Any suggestions? 73, Don W4GCW

The topic message pretty much tells all: Byonics now has the RTG-30 ( 30-40 Watt tracker) back in stock. 73, Allen AF6OF

I inadvertently over-wrote a customer's RTG-50 that had been set up as a tracker for SkyWarn. Does anyone have any idea what Symbol/Table or other special settings these guys use? 73, Allen AF6OF

Hi I have a Tiny Trak That works correctly but every month or so it locks up. When it locks up the yellow led is on steady, which would indicate that the squelch was open. But it is not open, in fact i disconnect the radio from the Tiny Trak and the led stays on no change. In this mode it will not transmit any data, and the red led is off. I have to power cycle the Tiny Trak to reset it and then it works fine for a month or so. Any suggestions. Thanks Byron NJ7J

Hi, I have three TT3 transmit devices and peet cables for serial to TT3 and from TT3 to radio. I have never gotten success transmit out to 144.39 net so never see my station and wx information on aprs.fi my oldest TT3 I flashed successfully and set up as NL7TK-13. I have never been successful using windows 10 and Tera term while following read me file to the letter. (On newer TT3) Questions: do you have any suggestions. And is there a terminal program compatible with windows 11? I’m assuming peet 2100 keyboard is working as I saw it out put wx strings normally at Hamvention this year while at peet booth. Was hoping to see Byronic booth but either missed it or no show. Thanks in advance, Dean NL7TK

I promised quite a number of people that I would let them know about the status of a couple of products in the Micro-Trak Line. Many of the Micro-Trak products had to be redesigned due to parts becoming extinct. Apparently there was a flu or something going around, and certain parts manufacturers went belly-up, made undocumented changes to the their parts, or just raised the prices. In the case of some amplifiers the parts increased by 500%! This caused us to pull a number of our products until we could obtain new parts, or acquire the current parts inexpensively enough to build the products at a price point that is not awful. The RTG-50 ( Originally called the "BFT"-50) is in production, but with somewhat reduced power. The new version, identical in almost all other respects to the old version, uses a different amplifier module, and has an output power of between 30-40 Watts, depending on your power supply voltage. With an alternator running at 14 Volts, it will typically produce 40 Watts, but we are calling it the RTG-30 so as to not appear like the CHICOM Walkie-Talkie people who claim handhelds with 25 Watts output. I have already sent Byon a number of these, and I expect he will put it back on the Byonics webstore shortly. The firmware and the configuration software are the same as before. Like the last generation of RTG-50's, these RTG-30's have thermostats that will shut off the amplifier if they reach 50C. ( Still, try to remember to turn off the tracker when you remove your antenna) The reboot of the MT-AIO is in the works too. One of the reasons that it disappeared was that Pelican, after about a hundred yeas making the same stuff, decided to drop the Yellow case we have used for the last decade. We redesigned the unit fit in another manufacturers case, whereupon they dropped the whole family of cases from production ( Flambeau, "Black Ribbon" cases) I found a case that I liked a few months ago, and have been quietly working on a next-gen version of the MT-AIO. The prototype is smaller and lighter, and works well. Since a whole new generations of Hams has come on to the scene, I decided to rethink a lot of the design elements. Like Neanderthal Man, we had built the unit around running on alkaline batteries. With Alkaline batteries, the output voltage decays with operating time. I decided to plan this unit around operating with four, 18650 LiPo batteries. With protected 18650 batteries (These have a built-in little circuit to protect the batteries from going up like Hiroshima, and not catch fire when charging) the limitations on supply current cap the unit at about 12 Watts output. With unprotected batteries, the unit runs at about 20 Watts initially, tapering to about 16 Watts before the batteries run out. LiPO's run more or less flat until they are discharged completely, and then just stop working. In bench testing, where I have the limitation of no view of the sky, the unit ran about four days, with the standard two minute transmission interval, and "sleeping" the GPS between transmissions. It will do better of course if its outside and has a view of the sky. Like most of the Micro-Trak APRS transmitters, the output power is trimmer-pot adjustable. At any rate, I have the first run of boards being run now, and hope to have saleable products in Byon's capable hands soon. I will put up photos of the new production units as soon as I put one together. 73, Allen AF6OF VHS/BYONICS

Greetings from Columbus, I am currently using my TT4 to transmit Peet weather station data into the APRS network on 144.390 using port B of the "Y" adapter. That was the easy part.... Now, I would like to receive local APRS traffic from the same radio and TT4 and send it into port A of the "Y" adapter, in KISS mode, so I can show the RF reports on a mapping application. Stated differently, I need to route radio receive data to tty port A (AMODE=KISS), and sensor output data from the weather station to tty port B (BMODE=PEET). Like this: Peet Mode ----> TT4 ----> Transmitter Receiver ----> TT4 -----> KISS Mode APRS map computer Is this possible, using the same TT4 and radio? Some specifics: The Peet weather station data is actually coming from a Java app I wrote for a Raspberry Pi, that converts Ecowitt hub data into Peet weather station data, so I can use the PEET mode of the TT4 to put APRS weather station reports over RF. My Java app also displays my local weather station data, as well as super cool, but very scary, real time, NASA Space Weather reports from the NASA API on a 7" display. I am trying to display the incoming APRS reports on a map that is included in John Wisemann's LinBPQ package that I have running on a different Raspberry Pi. I am hoping I can do this on two separate ports, just to make it more universal - one port for Peet data and another port for APRS data. Otherwise, it turns into a serious kludge, whereby I will have to try and do it all one one port. Thanks for reading! John, N1CTF Columbus, Ohio

Hello, I have an MT-1000 which I'm planning to use on a high altitude balloon. I was wondering if it was possible to configure it to keep the transceiver on at all times. That way, I can tap the audio from the unit and run it through a demodulator, so that I can use APRS packets to control the balloon from the ground. I would use a second transceiver for reception only, but I'm worried about blowing its frontend with it so close to the MT-1000. Thanks!

Although I can see the aprs packets being received and translated on the Kenwood TMD710GA mounted in the same vehicle as the mt8k, I do not see any packets being posted on aprs.fi no matter how close I drive to the digi. I’m thinking the power trimmer pot is not positioned correctly but there is no indicator that shows the physical position. I do not have a watt meter that can read 1 or 2 watts so I need to measure the Gate Voltage to get an idea of where the pot is set as per the mt8k v1.1 manual. Unfortunately the voltage between GND and the Enable Voltage Test Point reads 0 Volts. Turning the pot clockwise or counter clockwise 1/8 of a turn makes no difference - still 0 volts. I am using a 3000mAh 3S Lipo battery fully charged at 12.3 Volts and a dummy load. What am I doing wrong? 73 Steve KD9AER Begin forwarded message: From: "Stephen Grob via groups.io" <sgrob@...> Subject: Re: [TinyTrak] New TinyTrak Group Member 8000FA Questions. Date: April 29, 2023 at 6:28:14 PM CDT To: [email protected] Reply-To: [email protected] I used the diagram you speak of just to get the info on the GPS wire colors. You are right - it confused me too. So I re-soldered the GPS wires using the green wire (GPS TX) on pin 2 of the DE9F which connects to pin 2 (RX) on the mt8k DE9M. It worked! I saw the LED on the GPS puck light up and blink on and off, And the green LED on the mt8k lights up and blinks on and off too. I installed the mt8k in the test vehicle and drove my test course. I saw aprs status messages on the TMD710GA with the remark “Moving” and distance and direction info also so the GPS is working. The TMD710GA screen showed that the mt8k was transmitting position reports about every 120 secs as configured and the distance was always about a mile away and direction was behind the vehicle. Unfortunately aprs.fi only showed one position report. I’m assuming this is due to the low transmit power and lack of close by digipeaters in our area. The one position report shown on aprs.fi is at the point during my test course that is closest to the Digipeater. Next test I will circle the Digipeater and try to stay within 1 mile of it. Thanks to Allen, Rob and Rich for all the help. You guys are the best. 73 Steve KD9AER On Apr 29, 2023, at 7:31 AM, Rob Giuliano via groups.io <kb8rco@...> wrote: When I look at the website diagram, I see the explanation to be confusing. What are they telling you about the pins on which connector? The Green TX pin from the GPS will connect to the RX pin of the device. So is Green the TX pin or the TX wire with respect to the GPS? On the DE9F (female pins), pin 2 is RX, so connects to the GPS WHITE TX pin. On the DE9F (female pins), pin 3 is TX, so connects to the GPS GREEN RX pin. So the connection is made directly (no intermediate cable to swap 2 & 3. <1682771192566blob.jpg> Robert Giuliano KB8RCO On Friday, April 28, 2023 at 09:56:25 PM EDT, Stephen Grob via groups.io <sgrob@...> wrote: Thanks for the tip on non-MIC-E. I will disable that and SB. My GPS BR355 does not have a connector on it. Only wires - Green, White, Red and Black. So I soldered the wires to a DE9F accordingly. Here is where I got the pin-outs: <BR355-S4-400x400CAT_1024x1024.jpg> GlobalSat BR355-S4 Serial (PS/2) GPS Receiver gpswebshop.com In the schematic this website it shows White as TX and Green as RX - opposite from what Robs website says. I will disconnect the White wire and connect the Green wire and try again. I don’t see an LED on the GPS puck but there may be one there hiding under the “GPS” label characters. Also I will know the wiring is correct when I see the Green LED on the mt8k light up and stay on. Thanks for all the great information. 73 Steve KD9AER On Apr 28, 2023, at 6:54 PM, Rob Giuliano via groups.io <kb8rco@...> wrote: First, I agree with Allen - set a fixed TX rate (non-SmartBeaconing), non-Mic-E and decode it locally from another radio - if possible. Main website I looked at: https://www.embeddedworks.net/satl182/ HOWEVER, since you need whatever interface cable to the MT8k, you should still find a way to verify t