My overly-complicated TT3+ install
Here's how I did my TinyTrak3+ install, pretty complicated but it works well.
?
First, a couple of facts:
I'm running a Yaesu FT-7900R, which has the mini-DIN plug in back. If your radio requires connecting to the mic and speaker jacks then this will not apply.
I'm driving an older vehicle, a Ford Ranger 4X4. I've already drilled holes for VHF/UHF and HF antennas so I don't have a problem with drilling for a GPS antenna. I prefer not to have GPS coax sneaking in the door.
I retired from the radio business and I've done my share of installs back in the day. My preference is a simple looking installation without a lot of extra switches.
?
So I'll walk you through the install from +12V to antenna.?
|
Re: TinyTrak4, bank switching
When in doubt look for the simple.
It was operator error, I had missed that the GKRELAY parameters were flipped between the Banks.
Works as intended now.?
Back to this Pi Zero config as an I-Gate and fill-in digi with TT4.? AP will provided shared TNC access to DroidAPRS, YAAC on a SBC
|
Re: New TinyTrak3+ stuck in transmit.
Yes, I found a mica TO-220 insulator, which did not work.
It's the U2 mounting screw that is completing the circuit. I'll dig around for a plastic screw and nut set next.
|
Re: New TinyTrak3+ stuck in transmit.
Have you considered a piece of insulation under U2 such that it covers the trace that us being shorted?
On Mon, Apr 19, 2021 at 21:29, Bill WA4OPQ <wa4opq@...> wrote: Mystery solved...
It appears that on the latest batch of boards (mine, at least) the large hole in the center of the board has shifted so that the trace that goes from U1 pin 11 to D5 is shorted to the large plated through hole. (see arrow for location). This connects the large ground plane area on the other side to pin 11 also, so when the screw and nut are installed on U2 it grounds pin 11 and creates the stuck PTT that I experienced.
So U2 will remain floating above the board and all is good.
|
Re: New TinyTrak3+ stuck in transmit.
Mystery solved...
It appears that on the latest batch of boards (mine, at least) the large hole in the center of the board has shifted so that the trace that goes from U1 pin 11 to D5 is shorted to the large plated through hole. (see arrow for location). This connects the large ground plane area on the other side to pin 11 also, so when the screw and nut are installed on U2 it grounds pin 11 and creates the stuck PTT that I experienced.
So U2 will remain floating above the board and all is good.
|
Re: Anyone using a Tiny Trk with the Chinese 898 radios? - HOOK Squelch?
I found a couple of old-style hook switches, the ones with a microswitch inside.. Two for $10 on eBay.
This should do the trick.
|
Re: New TinyTrak3+ stuck in transmit.
Yes, I'm a bit baffled too. Yes I checked all the soldering. Orientation of D5 and D6 was correct.
With "No TX on PTT In" unchecked it caused the radio to transmit and the red LED came on. As soon as I wrote the config with "No TX on PTT in"? the red LED extinguished and the radio unkeyed. While in this mode it would not send regular messages or bulletins, but if I had it send audio tones that function worked correctly. That tells me the PTT circuit is working correctly.
With D5 removed and U1 removed pin 11 was still shorted. The only thing then connected to pin 11 was the trace going to D5, which goes under U2.
The only explanation that makes any sense is that there was a small bump on the trace that pierced the solder mask and it touched the grounded back of U2.?
I'll go back and look at that trace with a fine tooth comb; at the time I was a bit frazzled and didn't do it.
|
Re: Anyone using a Tiny Trk with the Chinese 898 radios? - HOOK Squelch?
The topic name caught my interest, I have a small fleet of 898s for APRS. And I've played with thousands of hook switches in a 40 year 2-way radio career.
I have a FT-7900 in my truck and was trying to figure the best way to control my new TinyTrak3+
So now I'll look for a hookswitch on eBay, When it's on hook it'll power the TT3+, when I pull the mike off hook it'll kill the power.
That way I'll never put out a squawk when I'm on 146.52
?
|
Re: New TinyTrak3+ stuck in transmit.
I am baffled by the voltage regulator being the issue.?
Did you double check the soldering around it?
The PPT circuit has a few connections that could cause the PTT to be active. With U2 fully in place and the radio in TX, is the PTT LED on or is the radio in TX without the LED on? (J4 must be in place). ?? If not, then verify Q1 orientation.
Moving to the pin 11, this is the feedback for PTT IN and should NOT control the PTT unless there is something
????? wrong with D5 and D6.? In this case check D5 and D6 orientation.?
???? If you remove both, does the problem go away??
Robert Giuliano KB8RCO
On Sunday, April 18, 2021, 2:34:04 AM EDT, Bill WA4OPQ <wa4opq@...> wrote:
I finished assembling my first TinyTrak3+ yesterday and the radio cable arrived today.
When I hooked it up (GPS hasn't arrived yet) it powered up OK, but it was stuck in transmit. If I checked "No Tx While PTT In" in the config, and then the stuck xmtr problem went away, but it would never transmit. It looked like U1 pin 11 was stuck low, but even removing D5 didn't help. Finally, I removed U1 and found pin 11 still low. Really? Eventually I loosened U2 and the short went away. I couldn't see exactly what caused the short, I'll chalk it up to a micro-meteorite. But until I get a TO-220 insulator it's going to remain lifted up a bit.?
This has probably been answered before on the old message board, I'm new here and had little to search. So I'm posting this for some poor soul in the future.?
|
New TinyTrak3+ stuck in transmit.
I finished assembling my first TinyTrak3+ yesterday and the radio cable arrived today.
When I hooked it up (GPS hasn't arrived yet) it powered up OK, but it was stuck in transmit. If I checked "No Tx While PTT In" in the config, and then the stuck xmtr problem went away, but it would never transmit. It looked like U1 pin 11 was stuck low, but even removing D5 didn't help. Finally, I removed U1 and found pin 11 still low. Really? Eventually I loosened U2 and the short went away. I couldn't see exactly what caused the short, I'll chalk it up to a micro-meteorite. But until I get a TO-220 insulator it's going to remain lifted up a bit.?
This has probably been answered before on the old message board, I'm new here and had little to search. So I'm posting this for some poor soul in the future.?
|
Re: kinda OT -- aprs wx station feed to internet
Glad you had fun with WeeWx.? You'd likely have to write an extension to import your data but it'll do lots of stuff once the data is in.
I used the CWOP interface just briefly, I generally export it to an APRS program and TNC.
Good luck!
|
How to work the ISS using APRS Packet Radio
How to work the ISS using APRS Packet Radio with TinyTrack4 ?
What are the settings required??
73 Corneliu?
YO4AUL?
|
Re: TinyTrak4, bank switching
If I read the schematic properly, the uP pin that is used to swap banks is using an internal pullup. Resistor R8 is a 'protector', and you place the jumper on JP1 to ground the pin, or use a switch on JP1 pin 4 to ground the pin to change banks.
So to determine the state of uP pin PA3 (pin 37) which selects the bank, you need to measure between uP pin 37 and ground.?
Kit Version:
The easiest place to do that should be from the bottom side of the PCB.? The ground would be the pins along the board edge for JP1-JP5 (any pin since they are common).? For R8, the pin closest to the uP.? I recommend the underside of the board because R8 seems to be standing on that through hole so most accessible from the bottom.?
Prebuilt:
I can't read the resistor labels on the hardware manual for the prebuilt, and I don't have one to check.
It should read close 5V for BANK 0 and close to 0V for Bank 1.
NOTE: "BNKMODE is selected selected at runtime" so you have to reset the micro after changing the pin state.
On Wednesday, April 14, 2021, 7:07:24 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:
[Edited Message Follows]
@JP1 In Kiss mode for both banks.? One bank shows gps output (? bank 0 is intended), other bank doesn't.? If I set bankmode 0, then default bank, aka 0, shows gps output in Minicom
Bank 0 Kiss --> TT4BT --> Pi Zero W --> share-tnc [provides multiple access via TCP] --> Wifi --> APRSDroid & YAAC & APRX
Will chk and report on V.? When you say chk voltage on the upside, do you mean across R8?? Or where do I ground?? Rank beginner as to electronic testing
|
Re: TinyTrak4, bank switching
@JP1
In Kiss mode for both banks.? One bank shows gps output (? bank 0 is intended), other bank doesn't.? If I set bankmode 0, then default bank, aka 0, shows gps output in Minicom
Bank 0 Kiss --> TT4BT --> Pi Zero W --> share-tnc [provides multiple access via TCP] --> Wifi --> APRSDroid & YAAC & APRX
Will chk and report on V.? When you say chk voltage on the upside, do you mean across R8?? Or where do I ground?? Rank beginner as to electronic testing
|
Re: TinyTrak4, bank switching
We need more information on your setup? ?? Are you switching banks at JP1 on the TT4 board, or using a switch on J1 pin 4?
?? If J1 pin 4, where are you getting Ground?
GKRELAY is only for KISS mode GRELAYRATE > 0 will cause GPS packets in the stream for TEXT mode
Although this wouldn't explain GPS sentences on BANK 1 in KISS mode, if you are TEXT mode on BANK 0 then the value of GKRELAY isn't important.
Are you changing modes with different banks?
Can you double check the voltage on the uP side of R8 for each state? Match these with the data flow.
On Tuesday, April 13, 2021, 9:19:00 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:
That's how the manual states it should work.? For some reason my TT4 behaves just the opposite - open is bank 1, closed is bank 0.
Bank 0 is set with GKRELAY 1, Bank 1 GKRELAY 0.? GPS sentences show when I close/ground JP1
Idea is that I want Bank 0 for APRS and Bank 1 as Kiss TNC for Winlink & Packet
|
Re: TinyTrak4, bank switching
That's how the manual states it should work.? For some reason my TT4 behaves just the opposite - open is bank 1, closed is bank 0.
Bank 0 is set with GKRELAY 1, Bank 1 GKRELAY 0.? GPS sentences show when I close/ground JP1
Idea is that I want Bank 0 for APRS and Bank 1 as Kiss TNC for Winlink & Packet
|
Re: connecting serial directly from TT4 board?
I forgot about the 3.3v <--> 5.0v.? Sounds like I'm make things more complicated rather than simplifying.
Will work within the confines of BT, serial profiles here I come
Thanks for the input
|
Re: "Limited" Fill In Digipeater Configuration
Take one of these little battery jump starters along, and see if there is enough traffic to run your battery down.? Might take a lot less power than you think.
|
Re: "Limited" Fill In Digipeater Configuration
If you set it up as a WIDE1 digi with solar power (and it gets good sun), you should be able run that for a long time. If it is at that high an elevation, I'd suggest a lower power (maybe 10 or 20 watts rather than a mobiles typical high power of 50) as it should be able to hit an IGATE or WIDE2 DIGI fairly easily.
Am extra car battery (not a fan of deep cycle, they expect to be taken down to a low charge) with CAR/RV roof solar panel (typically 20 -100 w) would last a good length of time.
On Monday, April 5, 2021, 11:09:48 AM EDT, Rick Dexter <rick@...> wrote:
Thank you for the excellent explanation.
My sole concern with digipeating other packets is running down the car battery in a remote area. ?Especially since most of these summits are up very high and I would be running the transmit at full power in many places, so I would expect it to hear a lot
of traffic and function as a high level digipeater. I figured I¡¯d be safe with only a few transmissions from us but couldn¡¯t control anything else.
Maybe I should look at using a secondary battery for the transceiver instead of running it off the main one, and/or using solar power, as your explanation makes a lot of sense.
Rick
On Apr 5, 2021, at 6:59 AM, Rob Giuliano via groups.io <kb8rco@...> wrote:
?
I don't remember seeing a response to this, so I will respond.
In general, it is polite to setup a DIGI for all to use - especially in remote areas.
If you set it up to be private, you are kinf of being a 'stingy HAM'.
The whole concept of fill-in DIGIs is that they may be temporary (moving through).
However, I believe you can set the TT4 to DIGIMY TRUE and your group MUST change their first path element to match.
Example (TT4 mycall N0NE-9)
?? PATH1 N0NE-9
?? PATH2 WIDE2-2
The catches:
?? * to this is that if the element is not used (your vehicle never hears and DIGIs the packet) that element
????? would not be used up and your packet 'may not' be DIGIed at all.? Other DIGIs that hear it would have
????? to have PREEMPT TRUE (or thier version) in order to handle the packet.
?? * You would need to change your path elements back to the default when not using the HT in this manner.
???? This would be most important for the other group members as they are NOW kind of relying on your station.
If you set ALIAS1 WIDE1, and change to
PATH1 WIDE1-1, PATH2 WIDE2-2 you get the following advantages:
?? * Your path is consistent with almost all APRS networks
????? So you never never have to change your path.
?? * It will be unlikely your other group members will need to do anything
?? * Not only do you handle your packets in earshot of the vehicle, you will also help your fellow HAMs in the area.
On Saturday, April 3, 2021, 8:43:35 PM EDT, Rick Dexter <rick@...> wrote:
Hi - new to the list and the TT4, and APRS in general.
A friend and I have been activating SOTA summits.? We are finding that APRS with our HT's is hit and miss.? Some summits have APRS coverage, some don't.? Even if we can hear a digi, it often can't hear our HT's, or can only hear them on high power and we'd
rather conserve batteries.? In general, we don't care that much about tracking/beaconing, but we want to be able to send out SOTA spots and get spots using the APRS SOTA gateway (address a text to SOTA and receive texts from the SOTA gateway).
I thought it would be nice if I could configure my higher powered mobile to digipeat our HT's while we are at the summits, assuming the HT is within simplex reach.? Most of the configurations I've tried also make it digipeat other packets as well.? I don't
really want it to do that.
I did try a configuration using a special alias that will digipeat our HT's if we set the path to include that alias, but we cannot receive any packets back from the gateway (spot acknowledgements, for example).
Maybe I am barking up the wrong tree here, but is something like this possible?? In essence, I want the mobile digi (with the TT4) to repeat packets from our two callsigns going out to the SOTA callsign, and also repeat anything it receives from the SOTA callsign
(or anything destined to our two callsigns).? I want to be able to park the car in any remote or busy area and not worry about messing up the network.
Thanks,
Rick
W5RJD
|
Re: "Limited" Fill In Digipeater Configuration
Thank you for the excellent explanation.
My sole concern with digipeating other packets is running down the car battery in a remote area. ?Especially since most of these summits are up very high and I would be running the transmit at full power in many places, so I would expect it to hear a lot
of traffic and function as a high level digipeater. I figured I¡¯d be safe with only a few transmissions from us but couldn¡¯t control anything else.
Maybe I should look at using a secondary battery for the transceiver instead of running it off the main one, and/or using solar power, as your explanation makes a lot of sense.
Rick
toggle quoted message
Show quoted text
On Apr 5, 2021, at 6:59 AM, Rob Giuliano via groups.io <kb8rco@...> wrote:
?
I don't remember seeing a response to this, so I will respond.
In general, it is polite to setup a DIGI for all to use - especially in remote areas.
If you set it up to be private, you are kinf of being a 'stingy HAM'.
The whole concept of fill-in DIGIs is that they may be temporary (moving through).
However, I believe you can set the TT4 to DIGIMY TRUE and your group MUST change their first path element to match.
Example (TT4 mycall N0NE-9)
?? PATH1 N0NE-9
?? PATH2 WIDE2-2
The catches:
?? * to this is that if the element is not used (your vehicle never hears and DIGIs the packet) that element
????? would not be used up and your packet 'may not' be DIGIed at all.? Other DIGIs that hear it would have
????? to have PREEMPT TRUE (or thier version) in order to handle the packet.
?? * You would need to change your path elements back to the default when not using the HT in this manner.
???? This would be most important for the other group members as they are NOW kind of relying on your station.
If you set ALIAS1 WIDE1, and change to
PATH1 WIDE1-1, PATH2 WIDE2-2 you get the following advantages:
?? * Your path is consistent with almost all APRS networks
????? So you never never have to change your path.
?? * It will be unlikely your other group members will need to do anything
?? * Not only do you handle your packets in earshot of the vehicle, you will also help your fellow HAMs in the area.
On Saturday, April 3, 2021, 8:43:35 PM EDT, Rick Dexter <rick@...> wrote:
Hi - new to the list and the TT4, and APRS in general.
A friend and I have been activating SOTA summits.? We are finding that APRS with our HT's is hit and miss.? Some summits have APRS coverage, some don't.? Even if we can hear a digi, it often can't hear our HT's, or can only hear them on high power and we'd
rather conserve batteries.? In general, we don't care that much about tracking/beaconing, but we want to be able to send out SOTA spots and get spots using the APRS SOTA gateway (address a text to SOTA and receive texts from the SOTA gateway).
I thought it would be nice if I could configure my higher powered mobile to digipeat our HT's while we are at the summits, assuming the HT is within simplex reach.? Most of the configurations I've tried also make it digipeat other packets as well.? I don't
really want it to do that.
I did try a configuration using a special alias that will digipeat our HT's if we set the path to include that alias, but we cannot receive any packets back from the gateway (spot acknowledgements, for example).
Maybe I am barking up the wrong tree here, but is something like this possible?? In essence, I want the mobile digi (with the TT4) to repeat packets from our two callsigns going out to the SOTA callsign, and also repeat anything it receives from the SOTA callsign
(or anything destined to our two callsigns).? I want to be able to park the car in any remote or busy area and not worry about messing up the network.
Thanks,
Rick
W5RJD
|
Bill WA4OPQ