|
I'm hoping you folks can help me out here, I'm brand new to APRS and programming this TT4 is a little confusing even with the instructions (but I'm not complaining, learning new things is fun!).
I'm using a factory assembled TT4 with the factory GPS unit attached and factory radio cable (with powerpole adapter) to my Yaseu FT-8900r.? I am trying to setup a vehicular digipeater for hiking that takes me way out in the boonies, and will also report the location of the parked vehicle occasionally.? I know for sure I have the TT4 and its connected radio transmitting, my handheld Yaseu FT3D shows "DE/K2CZH-1" when it transmitts along with the correct symbol, location, and range.? Yet no hint of the TT4 and ft-8900r with its vehicle antenna on APRS.fi even when the rubber duck HT can get a beacon out on APRS.fi at the same exact location.? It seems to be a programming issue, not a signal issue if the HT makes it in, but the moble rig cant.? Below is the programming info:
?
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 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 FALSE
TOSV is TRUE
TALT is TRUE
TSPEED is TRUE
TIMESTAMP is TRUE
TIMEHMS is TRUE
SBEN is FALSE
TSWPT is TRUE
AMODE is GPS
BMODE is TEXT
ABAUD is 4800
BBAUD is 4800
BNKMODE is 0
SSIDROUTE is 0
ALTNET is APTT4
MYCALL is K2CZH-1
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Mobile Digi Test Mon 146.52
BTEXT is >Mobile Digi Test Mon 146.52
BPERIOD is 60
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 25
TXTWIST is 50
RXAMP is 80
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 1234.5678N 12345.6789W
GALT is 1000
TSYMCODE is j
TSYMTABLE is /
STATUSRATE is 1
PPERIOD is 60
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
ALIAS2 is WIDE
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
(Unrelated note if I change the baud to anything other that 4800 I lose the GPS locked LED)
If anyone can help I'd greatly appreciate it.
K2CZH - Dave
|
Hi Dave,
I first need to say that I've had my TinyTrak4 for about 10 days meaning I'm no expert but here goes! The first thing I noticed
is that you have the DIGIMY command set to false, I think it needs to be set to true. I noticed that you don't have LOCATION set
to your position. I know you're using the GPS module and if so I think?you don't need to set the LOCATION command but I'd set
that to see if it makes a difference.?
The GPS sends it's data at 4800 baud, so I think you're ok there, but I don't remember having to set the ABAUD command to 4800 baud
when the GPS is plugged in and then having to change it to 19200 baud when communicating with your computer. My TT4 isn't
handy right now for me to check but hopefully someone else can help out.
Good luck,
Larry W0SX
|
First, I'd say that 'this reply' seems to assume your issue is with the DIGI, but your issue seems bigger than that.
To set things straight, the DIGIMY is for using your callsign-SSID as an additional 'alias' to those set in ALIAS#, so no that is not required to DIGI.? Also, you are using a GPS, so LOCATION is unused
Let's try and break down the setup a bit more: ?? handheld Yaseu FT3D shows "DE/K2CZH-1"?????????? so K2CZH-1 is the TT4/FT8900 and TX is okay
?? BUT you say
?? "Yet no hint of the TT4 and ft-8900r with its vehicle antenna on APRS.fi
even when
???? the rubber duck HT can get a beacon out on APRS.fi at the same
exact location. ???? It seems to be a programming issue,"
??
This
description implies you are concerned that the TT4/FT8900 aren't
reaching an IGATE, yet the HT with a rubber duck is.
Now to look at your issues:
1. From the Byonics Website:
??? The TT4BT is a bluetooth adapter for the TinyTrak4. It connects to the
J2 serial port connector, ???? provides a bluetooth interface to Port A, and
allows the connection of a GPS to Port B. ???? . Includes free USB bluetooth dongle while they last. ??? Your settings are backward:
????????AMODE is GPS
????????BMODE is TEXT
????????ABAUD is 4800
????????BBAUD is 4800
2. Have you done the procedure for calibrating TX and RX? ??? Since your HT is decoding the TT4/FT8900 combination, you assume it is TXing okay. ??? Did you look at the path the HT used? - why didn't that same DIGI, DIGI the FT8800?
??? Your HT is very near the mobile (with power), so easier to decode, even if the signal is very weak. ??? I looked at my TXLEVEL setting when I used a TT4 with my FT8800 and it was considerably higher.
3. Your FT8900 RXAMP seems high (again compared to mine with the FT8800) and could ??? impact the decode and DIGI
I'd recommend using the Bluetooth and a computer (or phone) to monitor what the TT4 is hearing and decoding, and also adjust the RXAMP and TXLEVEL to decode and TX more clearly.
BTW my settngs were ?? TXLevel 80 ?? RXAMP 12 to use as a starting point.? Still best to check with your particular setup.?
On Wednesday, January 27, 2021, 1:22:46 AM EST, cavuobservatory via groups.io <lobo59@...> wrote:
Hi Dave,
I first need to say that I've had my TinyTrak4 for about 10 days meaning I'm no expert but here goes! The first thing I noticed
is that you have the DIGIMY command set to false, I think it needs to be set to true. I noticed that you don't have LOCATION set
to your position. I know you're using the GPS module and if so I think?you don't need to set the LOCATION command but I'd set
that to see if it makes a difference.?
The GPS sends it's data at 4800 baud, so I think you're ok there, but I don't remember having to set the ABAUD command to 4800 baud
when the GPS is plugged in and then having to change it to 19200 baud when communicating with your computer. My TT4 isn't
handy right now for me to check but hopefully someone else can help out.
Good luck,
Larry W0SX
|
Thanks for the replies!?
To clarify yes, K2CZH-1 is the TT4 and FT-8900r and K2CZH-7 is the FT3D HT.? The HT gets in the igate from the back porch, while the ft-8900 at 50w with a J-pole does not.? I can see the DE>K2CZH-1 on the FT-3D and even the correct lat-long as well as the text message and all.? EDIT:? Also to clarify I currently do not have the bluetooth but am about to buy one.
1.? To start I fixed the first item,
AMODE is GPS
BMODE is TEXT
ABAUD is 4800
BBAUD is 19200
2/3.? I substituted your TX and RX levels and it does behave alot better during calibrate/monitor checks.
TXLEVEL is 80
TXTWIST is 50
RXAMP is 13
With all of the above changes, I still dont see any -1 or digipeated -7 packets making it onto APRS.fi even when I put the TT4/FT-8900 on the moble antenna and drive the moble down the street which has the local Igate.
Below is a total rundown of my display:
DMSDISP is FALSE
MICETMV is FALSE
ENTS is FALSE
TELHIRES is FALSE
TELVOLT is FALSE
TELTEMP is FALSE
PREEMPT is FALSE
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 FALSE
TOSV is TRUE
TALT is TRUE
TSPEED is TRUE
TIMESTAMP is TRUE
TIMEHMS is TRUE
SBEN is FALSE
TSWPT is TRUE
AMODE is GPS
BMODE is TEXT
ABAUD is 4800
BBAUD is 19200
BNKMODE is 0
SSIDROUTE is 0
ALTNET is APPT4
MYCALL is K2CZH-1
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Mobile Digi Test Mon 146.52
BTEXT is >Mobile Digi Test Mon 146.52
BPERIOD is 60
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 80
TXTWIST is 50
RXAMP is 13
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 1234.5678N 12345.6789W
GALT is 1000
TSYMCODE is j
TSYMTABLE is /
STATUSRATE is 3
PPERIOD is 60
MPPERIOD is 0
SBSSPEED is 5
SBFSPEED is 60
SBSPERIOD is 1800
SBFPERIOD is 90
SBTANGLE is 0
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 WIDE1
ALIAS2 is WIDE
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
Thanks again for the help, I do feel like were getting closer.
Gratefully,
K2CZH - Dave
|
I am not seeing any 'recent posts' of either of your listed callsign-ssid combinations on aprs.fi
?? K2CZH-7 (HT)???? 2021-01-26 20:58:56 EST: >TPUP7S,WIDE1-1,WIDE2-1,qAR,:`f@Ll#)j/`"7W}Monitoring?146.52_0
?? K2CZH-1 (TT4)???2021-01-24 01:12:25 EST: >TPUR0V,WIDE1-1,WIDE2-1,qAR,:`fAYl"8j/"67}/TinyTrak4?Alpha
So if you tried both since then, neither made the trip.
So you still have the GPS on PortA because you don't have the Bluetooth adapter yet.? Makes sense now. You mentioned in a previous post that you have the GPS LED solid green, so that is working!
Going through your settings, a few non-related issues popped up: ALTNET APTT4??????????????? (to properly identify your hardware)
P300 FALSE??????????????????? (not listed, but assumed false) PPATHING FALSE?????????? (Not listed, but could influence if/when you hit another DIGI) NODISP TRUE? ????????????? (so there is no display attached)
TXTDISP FALSE???????????? (since there is no display, don't use it for TX Text)
The only other noted differences I see from my old configuration to yours are:
?? GPSCHK FALSE MANUAL: Sets the checksum to be checked on incoming GPS sentences. If the checksum is
invalid, the sentence will be ignored
?? INTCLK FALSE MANUAL: Sets the use of the internal clock for all timing. If false, the GPS time will be used for
timing when present. This should be set to true if using a GPS with a clock that doesn¡¯t
progress if not synced to the satellites.
I am not sure how your GPS is working, but if you have the "GREEN LIGHT", these shouldn't matter.
Beyond that, I can only think that the TT4 isn't really transmitting.? Have you listed to the audio from the TT4/FT8900R on the HT, or only saw that it decoded?
I pull out my TT4 and hook it to the FT8800 and check things further - at lunch.
On Thursday, January 28, 2021, 1:02:45 AM EST, dnaprstek@... <dnaprstek@...> wrote:
[Edited Message Follows]
Thanks for the replies!?
To clarify yes, K2CZH-1 is the TT4 and FT-8900r and K2CZH-7 is the FT3D HT.? The HT gets in the igate from the back porch, while the ft-8900 at 50w with a J-pole does not.? I can see the DE>K2CZH-1 on the FT-3D and even the correct lat-long as well as the text message and all.? EDIT:? Also to clarify I currently do not have the bluetooth but am about to buy one.
1.? To start I fixed the first item,
AMODE is GPS
BMODE is TEXT
ABAUD is 4800
BBAUD is 19200
2/3.? I substituted your TX and RX levels and it does behave alot better during calibrate/monitor checks.
TXLEVEL is 80
TXTWIST is 50
RXAMP is 13
With all of the above changes, I still dont see any -1 or digipeated -7 packets making it onto APRS.fi even when I put the TT4/FT-8900 on the moble antenna and drive the moble down the street which has the local Igate.
Below is a total rundown of my display:
<Snip> Thanks again for the help, I do feel like were getting closer.
Gratefully,
K2CZH - Dave
|
I checked the TT4 for the settings you mentioned, here is what I found:
ALTNET is APTT4
P300 is FALSE
PPATHING is FALSE?????????
NODISP is TRUE ????????????? (I dont have a display and this WAS listed as false so I changed it)
TXTDISP is FALSE???????????
GPSCHK is FALSE??????????? (Not sure if I should change this too?)
INTCLK is FALSE????????????? (Not sure if I should change this too?)
I had the APRS mute OFF on my HT for the last couple days of trouble shooting, and during both the config test of output, and the every 60 second packets, it sounds as loud as the local weather beacons across town.? And yes I was testing all last night, incuding driving down the local I-gates street, at midnight lol!? That first sent K2CZH-1 packet was the day I opened the box, and its never gotten though since, I even tried a restore which was unsucessfull.
Thanks again, K2CZH - Dave
|
Still investigating, but a couple more things: Your DIGI Alias:
????ALIAS1 WIDE1 ????ALIAS2 WIDE ????ALIAS3 Since the n-N algorithm is built in, WIDE variations (Wide1-N, Wide2-N, ...).? I recommend limiting this by adding the specific WIDE variance you want (WIDE1 or WIDE2 or both), but as a fill in, you really should be WIDE1.? So I suggest ALIAS2 % or ALIAS2 WIDE2 (if you plan on putting this setup on a tower or something with good coverage.)
What is the PATH you have set in the HT?
I now have my TT4 configured with your settings - but the required changes of MYCALL, etc. and my GPS is on PortB.? I will connect it to my FT8800 and see how it sounds, decodes, and what happens.
On Thursday, January 28, 2021, 12:30:33 PM EST, dnaprstek@... <dnaprstek@...> wrote:
I checked the TT4 for the settings you mentioned, here is what I found:
ALTNET is APTT4
P300 is FALSE
PPATHING is FALSE?????????
NODISP is TRUE ????????????? (I dont have a display and this WAS listed as false so I changed it)
TXTDISP is FALSE???????????
GPSCHK is FALSE??????????? (Not sure if I should change this too?)
INTCLK is FALSE????????????? (Not sure if I should change this too?)
I had the APRS mute OFF on my HT for the last couple days of trouble shooting, and during both the config test of output, and the every 60 second packets, it sounds as loud as the local weather beacons across town.? And yes I was testing all last night, incuding driving down the local I-gates street, at midnight lol!? That first sent K2CZH-1 packet was the day I opened the box, and its never gotten though since, I even tried a restore which was unsucessfull.
Thanks again, K2CZH - Dave
|
Mine seems to be working using mostly your settings. Now I am adjusting some parameters so the TX is not so often: ? BPERIOD 60??? 600??????????? (from 1 minute to 10 mintes) ? PPERIOD 60??? 300??????????? (from 1 minute to 5 minutes, but Smart Beacon is better)
Since you are using a GPS, you may consider enabling the SmartBeacon functions. The setttings in the attached file will beacon about once per mile between 5 and 75 miles per hour. A reasonable rate with the longest delay being 720 seconds (or 12 minutes) when close to stopped.
Compare these to what you had.
On Thursday, January 28, 2021, 1:41:18 PM EST, Rob Giuliano via groups.io <kb8rco@...> wrote:
Still investigating, but a couple more things: Your DIGI Alias:
????ALIAS1 WIDE1 ????ALIAS2 WIDE ????ALIAS3 Since the n-N algorithm is built in, WIDE variations (Wide1-N, Wide2-N, ...).? I recommend limiting this by adding the specific WIDE variance you want (WIDE1 or WIDE2 or both), but as a fill in, you really should be WIDE1.? So I suggest ALIAS2 % or ALIAS2 WIDE2 (if you plan on putting this setup on a tower or something with good coverage.)
What is the PATH you have set in the HT?
I now have my TT4 configured with your settings - but the required changes of MYCALL, etc. and my GPS is on PortB.? I will connect it to my FT8800 and see how it sounds, decodes, and what happens.
On Thursday, January 28, 2021, 12:30:33 PM EST, dnaprstek@... <dnaprstek@...> wrote:
I checked the TT4 for the settings you mentioned, here is what I found:
ALTNET is APTT4
P300 is FALSE
PPATHING is FALSE?????????
NODISP is TRUE ????????????? (I dont have a display and this WAS listed as false so I changed it)
TXTDISP is FALSE???????????
GPSCHK is FALSE??????????? (Not sure if I should change this too?)
INTCLK is FALSE????????????? (Not sure if I should change this too?)
I had the APRS mute OFF on my HT for the last couple days of trouble shooting, and during both the config test of output, and the every 60 second packets, it sounds as loud as the local weather beacons across town.? And yes I was testing all last night, incuding driving down the local I-gates street, at midnight lol!? That first sent K2CZH-1 packet was the day I opened the box, and its never gotten though since, I even tried a restore which was unsucessfull.
Thanks again, K2CZH - Dave
|
I looked at the HT path settings and it is on Wide1-1 and Wide2-1
I did a test just now with my HT and the FT-8900 on the same J-pole on the back porch, the HT made it in and the FT-8900 at 50w setting did not.?
The settings you posted above look identical, except for the smart beaconing which I will try.? I have a FT-817 and maybee its time to take the ft-8900 out of the equation and see if the FT-817 can tickle an I-gate.? I did change the Alias2 from wide to Wide2
Thanks,
Dave K2CZH
|
Since the Data Jack (how I am interfacing to the FT8800) specifications for the FT8800 and FT8900 are the same, I have to believe you are very close to the settings needed on the FT8900R.?
I guess there are 2 points I should double check: 1. I should verify that you are using the Data Jeck on the FT8800R? ??? I think I remember you posting that you have the Data Jack cable.
2. R1position.? I leave R1 about the middle point. ??? If it is set in the wrong position, you won't get any audio - however you said you can hear it
I am pretty confident that the FT8900R and TT4 are decoding packets.? The TX deviation is most likely the issue.? Depending on the receiving stations (DIGI and IGates), they may or may not be robust to your signal.? Without equipment (deviation meter), there is only trial-on-error.??
I should have thought of this earlier, but if you have a good way of measuring the voltage Peak-to-Peak output (J1 Pin 1 and Pin 6) you can adjust R1 such that the Vpp is between 35 and 40 mVpp (FT8800R spec for the Data Jack).? Use CALIBRATE and L and H keys to switch between the 2 tones.? The Vpp should be the same for both.? Adjust TXLevel as needed.
Otherwise:
1. Use Terra Term to or some other macro capable terminal for changing settings ??? (Assume you already are).
2. Since you already have SOFTRST TRUE, setup a Macro to reset the TT4 ; Send a reset to a Byonics TT4 or MTT4 when in text mode ; Waits for the the response and send the esc sequence to enter boot ; sendln 27 27 27 waitln '?' waitln 'Press ESC 3 times to enter TT4 Options Menu' send 27 27 27 3. Put R1 at about the center
4. Increase TXLevel by 5 and let the TT4 TX. ??? If the signal is not picked up, repeat until 128. 5. If you reach 128 without success, go back to 80 and reduce by 5 each time. 6. If you get below 50 with no success, I am guessing there is another issue and try the FT817
|
1. Yes on the Data Jack.
2. R1position.? I honestly cant tell its so small, I may have a screwdriver that small around and I'll try turning it too see what position its in, once i do ill let you know.
As far as the voltage peak to peak, I think thats within the limits of a generic radio shack volt meter? I did find the shorting pin on J6 which according to the manual should be left open for all mobiles, so I changed it to open.? I tested it off the back porch and same results as before, no Igates herd it.
|
Bummer, I was thinking the jumper was the best bet!
Yes, the voltage level is within the range of about any voltmeter - sort of.? 40 mV peak-to-peak (mVpp) is quite small and many times the leads will pick up a few mVpp, just from the lights or AC lines.? I checked my TT4 and at the settings I sent, the 'cheap meter' read 8 mV on the 'AC mV' range with just the leads.? Then 44 mVpp on TX.? Connected a scope and measurement was ~38 mVpp.
Again, you were able to hear the TX in another radio, so R1 can't be too far off.
I also changed the TPROTOCOL to APRS for testing because it has longer TX time (Then I changed to COMPRESSED as MIC-E seems more like a commercial protocol - just my opinion).
?
On Saturday, January 30, 2021, 10:44:54 AM EST, dnaprstek@... <dnaprstek@...> wrote:
1. Yes on the Data Jack.
2. R1position.? I honestly cant tell its so small, I may have a screwdriver that small around and I'll try turning it too see what position its in, once i do ill let you know.
As far as the voltage peak to peak, I think thats within the limits of a generic radio shack volt meter? I did find the shorting pin on J6 which according to the manual should be left open for all mobiles, so I changed it to open.? I tested it off the back porch and same results as before, no Igates herd it.
|
I see reports on aprs.fi !!!
So what did you find?
On Saturday, January 30, 2021, 10:44:54 AM EST, dnaprstek@... <dnaprstek@...> wrote:
1. Yes on the Data Jack.
2. R1position.? I honestly cant tell its so small, I may have a screwdriver that small around and I'll try turning it too see what position its in, once i do ill let you know.
As far as the voltage peak to peak, I think thats within the limits of a generic radio shack volt meter? I did find the shorting pin on J6 which according to the manual should be left open for all mobiles, so I changed it to open.? I tested it off the back porch and same results as before, no Igates herd it.
|
I'm not 100% sure I hooked up the FT-817 and drove east and west over some mountain tops on a highway and to my surprise got a bunch of packets onto apra.fi
I'll try again with the ft-8900 after work tonight maybee it was the shorting pin, or the txlevel settings, or my local igate in town (which didn't hear the 817) is not as sensitive as it used to be?? We have some coax addicted squirrels in my town...
|
Just re-drove the same route with the FT-8900 set to 50w on the same moble antenna and not a single packet went through.? I will ponder this more in the morning.
|
If there isn't a receiver, to pick up your packets and get them on the internet you are just sending packets into the airwaves. I've had similar things happen if there is no IGate around. My TT4 decided today to transmit every 5 seconds for some reason even with the GPS off. Gremlins in my TT4 ill need to check later.?
|
This was a direct comparison of 2 radios along the same map route.
I find it hard to believe that a number of IGATES along a route all went off the air at the same time.?
I didn't hear of a mass blackout in the area west of Newark, NJ.
On Sunday, January 31, 2021, 7:11:21 AM EST, Chuck B <brainardc@...> wrote:
If there isn't a receiver, to pick up your packets and get them on the internet you are just sending packets into the airwaves. I've had similar things happen if there is no IGate around. My TT4 decided today to transmit every 5 seconds for some reason even with the GPS off. Gremlins in my TT4 ill need to check later.?
|
I think the FT-8900 is like my FT-8800 in that it has two sides that can receive simultaneously but which side transmits when the PTT is keyed is manually selected.? Are you positive you have the side set to 144.390 selected correctly?? It'll have the "main" indicated as the side that has the path to the transmitter.?
If you're trying to use one side normally the radio can't automatically switch to the other side just for APRS transmission (like the FTM-350/400 will or a Kenwood TM-V71 does).? The radio also doesn't hold off or discriminate the PTT.? When PTT is driven the radio transmits regardless.? So if you have your TNC connected and keying but have not switched sides the repeater or simplex you're operating will get an earful of modem.?
So you may verify that you set the correct side for transmit or alternatively set both sides to 144.390 so it doesn't matter which side is selected as main.
I don't see that you've checked this, so if you have I apologize should this be redundant.
73, David, AC0VH
|
Good points that I dind't even think of.? I didn't even look at the radio side of things:
Assuming the FT8900R is the same as the FT8800R:
????Menu #27 [PKT.RXB] ????Function: Sets the receiving band for Packet operation.
????Available Values: MAIN/R-FIX/L-FIX
????Default: MAIN
????????MAIN: Packet can be operated on the ¡°Main¡± band.
????????R-FIX: Packet can be operated on the ¡°right¡± band only.
????????L-FIX: Packet can be operated on the ¡°left¡± band only.
????Note: Packet transmit band is fixed on the ¡°Main¡± band..
So you must be sure:
??? Menu #26 PKT.SPD => 1200BPS ????Menu #27 PKT.RXB => MAIN (other wise you can TX on the wrong side of the radio)
On Sunday, January 31, 2021, 1:36:10 PM EST, David A <ac0vh@...> wrote:
I think the FT-8900 is like my FT-8800 in that it has two sides that can receive simultaneously but which side transmits when the PTT is keyed is manually selected.? Are you positive you have the side set to 144.390 selected correctly?? It'll have the "main" indicated as the side that has the path to the transmitter.?
If you're trying to use one side normally the radio can't automatically switch to the other side just for APRS transmission (like the FTM-350/400 will or a Kenwood TM-V71 does).? The radio also doesn't hold off or discriminate the PTT.? When PTT is driven the radio transmits regardless.? So if you have your TNC connected and keying but have not switched sides the repeater or simplex you're operating will get an earful of modem.?
So you may verify that you set the correct side for transmit or alternatively set both sides to 144.390 so it doesn't matter which side is selected as main.
I don't see that you've checked this, so if you have I apologize should this be redundant.
73, David, AC0VH
|
Thats for receiving only, as per your bottom highlight transmit is on main only. Because of this if you are using aprs on an ft8800 you cannot use voice on the other side except for monitoring because the beacon would
go out on the voice channel.?
""Menu #27 [PKT.RXB]
????Function: Sets the receiving band for Packet operation.
????Available Values: MAIN/R-FIX/L-FIX
????Default: MAIN
????????MAIN: Packet can be operated on the ¡°Main¡± band.
????????R-FIX: Packet can be operated on the ¡°right¡± band only.
????????L-FIX: Packet can be operated on the ¡°left¡± band only.
????Note: Packet transmit band is fixed on the ¡°Main¡±
band..?""
KB3KBR Greg.
Sent from my Samsung Galaxy smartphone.
toggle quoted message
Show quoted text
-------- Original message --------
From: "Rob Giuliano via groups.io" <kb8rco@...>
Date: 1/31/21 14:10 (GMT-05:00)
Subject: Re: [TinyTrak] TInyTrak4 Digipeater Setup Problem
Good points that I dind't even think of.? I didn't even look at the radio side of things:
Assuming the FT8900R is the same as the FT8800R:
????Menu #27 [PKT.RXB]
????Function: Sets the receiving band for Packet operation.
????Available Values: MAIN/R-FIX/L-FIX
????Default: MAIN
????????MAIN: Packet can be operated on the ¡°Main¡± band.
????????R-FIX: Packet can be operated on the ¡°right¡± band only.
????????L-FIX: Packet can be operated on the ¡°left¡± band only.
????Note: Packet transmit band is fixed on the ¡°Main¡±
band..
So you must be sure:
??? Menu #26 PKT.SPD => 1200BPS
????Menu #27 PKT.RXB => MAIN (other wise you can TX on the wrong side of the radio)
On Sunday, January 31, 2021, 1:36:10 PM EST, David A <ac0vh@...> wrote:
I think the FT-8900 is like my FT-8800 in that it has two sides that can receive simultaneously but which side transmits when the PTT is keyed is manually selected.? Are you positive you have the side set to 144.390 selected correctly?? It'll have the
"main" indicated as the side that has the path to the transmitter.?
If you're trying to use one side normally the radio can't automatically switch to the other side just for APRS transmission (like the FTM-350/400 will or a Kenwood TM-V71 does).? The radio also doesn't hold off or discriminate the PTT.? When PTT is driven the
radio transmits regardless.? So if you have your TNC connected and keying but have not switched sides the repeater or simplex you're operating will get an earful of modem.?
So you may verify that you set the correct side for transmit or alternatively set both sides to 144.390 so it doesn't matter which side is selected as main.
I don't see that you've checked this, so if you have I apologize should this be redundant.
73, David, AC0VH
|
Dave K2CZH