Greg, It appears that you've hijacked the thread "Driving GPIO pins," and created a lot of confusion for those following the thread. Don't know why you'd do that without any mention why. As far as I can tell, the TC2004A-03R "20 character x 4 line LCD Display" that you bought (as did I years ago), other than being an accessory for the TT4, has nothing much to do with the original post in the "Driving GPIO pins" thread as posted by Steven Heimann on April 3. If I'm mistaken, please forgive me. I suppose the pins that the ribbon cable, supplied with the Display/Keyboard interface board, might be a good way to access what the OP Steven H. called "GPIO Pins," although I don't believe I've ever previously heard that usage. Now to address what you've asked about, there is a manual and a wiring diagram/chart for the display board that totally explains how to use the board, how to wire it up to the kit TT4 or plug it into the built TT4. These documents do a far better job of explaining all this than I could do, although I could probably address some specific issues. It's been years since I bought my KB/Disp adapter board and 20x4 LCD, but at the time I bought the kit, I read the manual and had no problems whatsoever. Did you also buy the add-on keyboard/display interface board? If I remember correctly, you don't have to buy the board, which might be a good option if you don't intend to use a PS/2 keyboard with your TT4. I'm not sure if new PS/2 keyboards are still for sale, but used ones are probably not difficult to find. I bought one very cheap (<$10) at an ancient electronics/cellphone store called "Radio Shack" ages ago. Did you download and read the manual? If not, you might want to do so. Here are some links: About halfway down is the description of the display interface board (with docs links). This is the manual that provides info about the Display/Keyboard interface board AND the whole setup with the 20x4 LCD board. A more concise document defining the wiring with various options, with & without the DKB adapter board, with the Kit TT4 or the Built TT4. Barry N4MSJ On 5/18/2021 1:29 PM, Gregory Lane via groups.io wrote: Bob,
I think I bought a TC2004A-03R board to interface with my TT4.
Have you or anyone in groups.io have the hookup and command settings for this board?
Thanks, Greg
-----Original Message-----
From: Robert Bruninga <bruninga@...>
To: [email protected]
Sent: Sat, Apr 3, 2021 5:54 pm
Subject: Re: [TinyTrak] Driving GPIO pins
You?set up these commands: (they may not be exact since htis is from memory) but similar:
NODISP on
MSGCOMMAND?ON
etc
THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
Bob
On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann <vk2bos.lists@... <mailto:vk2bos.lists@...>> wrote:
Evening all
I have a memory that it is possible to drive a gpio pin in a
Tinytrak 4 high or low based on the receipt of an over the air
command in an APRS packet.? I have looked at the manuals and this
mailing list but can't find anything. I am looking to drive a relay
to switch a repeater on and off at a remote mountain site which is
battery powered.? Is my memory more faulty than usual?? Could
someone point me to some doco on this.
Thanks and regards
Steven VK2BOS
|
Tnx,? I forgot the hookup, thanks for the info!
On Tue, May 18, 2021 at 4:17 PM, vhsproducts via groups.io <vhsproducts@...> wrote: It strikes me as a lot of work to replicate a product ( Well, hopefully) that you can have in your hands from Byonics in two days, but a Ham's quest for knowledge ( And getting stuff done less expensively) is inexhaustible! Let us know how it works out, I would love to see what you come up with.
Allen AF6OF
-----Original Message-----
From: Don Woodward <dbwoodw@...>
To: [email protected] <TinyTrak@...
Sent: Tue, May 18, 2021 4:06 pm
Subject: Re: [TinyTrak] Driving GPIO pins
Looks similar to this one?
Byonics makes a display and interface for the TT4??
I don¡¯t have either.
73¡¯²õ
Don W.
KD4APP?
?
Get
I sent you these pics. LCD with some I/O connections I thought to display APRS data?
Greg
On Tue, May 18, 2021 at 2:42 PM, Greg
<k7sdw@...> wrote:
On Tue, May 18, 2021 at 2:05 PM, Robert Bruninga
<bruninga@...> wrote:
I need more info.? What is that board?
thanks
Bob (in chemo fog)
On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io
<k7sdw= [email protected]> wrote:
>
> Bob,
> I think I bought a TC2004A-03R board to interface with my TT4.
> Have you or anyone in groups.io have the hookup and command settings for this board?
>
> Thanks, Greg
> -----Original Message-----
> From: Robert Bruninga < bruninga@...>
> To:
[email protected]
> Sent: Sat, Apr 3, 2021 5:54 pm
> Subject: Re: [TinyTrak] Driving GPIO pins
>
> You set up these commands: (they may not be exact since htis is from memory) but similar:
>
> NODISP on
> MSGCOMMAND ON
> etc
>
> THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
>
> Bob
>
>
> On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann < vk2bos.lists@...> wrote:
>
> Evening all
>
> I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay
to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this.
>
> Thanks and regards
> Steven VK2BOS
>
>
|
It strikes me as a lot of work to replicate a product ( Well, hopefully) that you can have in your hands from Byonics in two days, but a Ham's quest for knowledge ( And getting stuff done less expensively) is inexhaustible! Let us know how it works out, I would love to see what you come up with.
Allen AF6OF
-----Original Message-----
From: Don Woodward <dbwoodw@...>
To: [email protected] <TinyTrak@...
Sent: Tue, May 18, 2021 4:06 pm
Subject: Re: [TinyTrak] Driving GPIO pins
Looks similar to this one?
Byonics makes a display and interface for the TT4??
I don¡¯t have either.
73¡¯²õ
Don W.
KD4APP?
?
Get
I sent you these pics. LCD with some I/O connections I thought to display APRS data?
Greg
On Tue, May 18, 2021 at 2:42 PM, Greg
<k7sdw@...> wrote:
On Tue, May 18, 2021 at 2:05 PM, Robert Bruninga
<bruninga@...> wrote:
I need more info.? What is that board?
thanks
Bob (in chemo fog)
On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io
<k7sdw= [email protected]> wrote:
>
> Bob,
> I think I bought a TC2004A-03R board to interface with my TT4.
> Have you or anyone in groups.io have the hookup and command settings for this board?
>
> Thanks, Greg
> -----Original Message-----
> From: Robert Bruninga < bruninga@...>
> To:
[email protected]
> Sent: Sat, Apr 3, 2021 5:54 pm
> Subject: Re: [TinyTrak] Driving GPIO pins
>
> You set up these commands: (they may not be exact since htis is from memory) but similar:
>
> NODISP on
> MSGCOMMAND ON
> etc
>
> THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
>
> Bob
>
>
> On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann < vk2bos.lists@...> wrote:
>
> Evening all
>
> I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay
to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this.
>
> Thanks and regards
> Steven VK2BOS
>
>
|
Looks similar to this one?
Byonics makes a display and interface for the TT4??
I don¡¯t have either.
73¡¯²õ
Don W.
KD4APP?
?
Get
toggle quoted message
Show quoted text
I sent you these pics. LCD with some I/O connections I thought to display APRS data?
Greg
On Tue, May 18, 2021 at 2:42 PM, Greg
<k7sdw@...> wrote:
On Tue, May 18, 2021 at 2:05 PM, Robert Bruninga
<bruninga@...> wrote:
I need more info.? What is that board?
thanks
Bob (in chemo fog)
On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io
<k7sdw= [email protected]> wrote:
>
> Bob,
> I think I bought a TC2004A-03R board to interface with my TT4.
> Have you or anyone in groups.io have the hookup and command settings for this board?
>
> Thanks, Greg
> -----Original Message-----
> From: Robert Bruninga < bruninga@...>
> To:
[email protected]
> Sent: Sat, Apr 3, 2021 5:54 pm
> Subject: Re: [TinyTrak] Driving GPIO pins
>
> You set up these commands: (they may not be exact since htis is from memory) but similar:
>
> NODISP on
> MSGCOMMAND ON
> etc
>
> THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
>
> Bob
>
>
> On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann < vk2bos.lists@...> wrote:
>
> Evening all
>
> I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay
to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this.
>
> Thanks and regards
> Steven VK2BOS
>
>
|
I sent you these pics. LCD with some I/O connections I thought to display APRS data?
On Tue, May 18, 2021 at 2:42 PM, Greg <k7sdw@...> wrote:    On Tue, May 18, 2021 at 2:05 PM, Robert Bruninga <bruninga@...> wrote: I need more info.? What is that board? thanks Bob (in chemo fog) On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io <k7sdw= [email protected]> wrote: > > Bob, > I think I bought a TC2004A-03R board to interface with my TT4. > Have you or anyone in groups.io have the hookup and command settings for this board? > > Thanks, Greg > -----Original Message----- > From: Robert Bruninga < bruninga@...> > To: [email protected]> Sent: Sat, Apr 3, 2021 5:54 pm > Subject: Re: [TinyTrak] Driving GPIO pins > > You set up these commands: (they may not be exact since htis is from memory) but similar: > > NODISP on > MSGCOMMAND ON > etc > > THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits > > Bob > > > On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann < vk2bos.lists@...> wrote: > > Evening all > > I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this. > > Thanks and regards > Steven VK2BOS > >
|
toggle quoted message
Show quoted text
On Tue, May 18, 2021 at 2:05 PM, Robert Bruninga <bruninga@...> wrote: I need more info.? What is that board? thanks Bob (in chemo fog) On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io <k7sdw= [email protected]> wrote: > > Bob, > I think I bought a TC2004A-03R board to interface with my TT4. > Have you or anyone in groups.io have the hookup and command settings for this board? > > Thanks, Greg > -----Original Message----- > From: Robert Bruninga < bruninga@...> > To: [email protected]> Sent: Sat, Apr 3, 2021 5:54 pm > Subject: Re: [TinyTrak] Driving GPIO pins > > You set up these commands: (they may not be exact since htis is from memory) but similar: > > NODISP on > MSGCOMMAND ON > etc > > THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits > > Bob > > > On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann < vk2bos.lists@...> wrote: > > Evening all > > I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this. > > Thanks and regards > Steven VK2BOS > >
|
I need more info. What is that board? thanks Bob (in chemo fog) On Tue, May 18, 2021 at 3:11 PM Gregory Lane via groups.io <k7sdw@...> wrote:
Bob,
I think I bought a TC2004A-03R board to interface with my TT4.
Have you or anyone in groups.io have the hookup and command settings for this board?
Thanks, Greg
-----Original Message-----
From: Robert Bruninga <bruninga@...>
To: [email protected]
Sent: Sat, Apr 3, 2021 5:54 pm
Subject: Re: [TinyTrak] Driving GPIO pins
You set up these commands: (they may not be exact since htis is from memory) but similar:
NODISP on
MSGCOMMAND ON
etc
THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
Bob
On Sat, Apr 3, 2021 at 1:32 PM Steven Heimann <vk2bos.lists@...> wrote:
Evening all
I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet. I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay to switch a repeater on and off at a remote mountain site which is battery powered. Is my memory more faulty than usual? Could someone point me to some doco on this.
Thanks and regards
Steven VK2BOS
|
Bob,
I think I bought a TC2004A-03R board to interface with my TT4.
Have you or anyone in groups.io have the hookup and command settings for this board?
Thanks, Greg
-----Original Message-----
From: Robert Bruninga <bruninga@...>
To: [email protected]
Sent: Sat, Apr 3, 2021 5:54 pm
Subject: Re: [TinyTrak] Driving GPIO pins
You?set up these commands: (they may not be exact since htis is from memory) but similar:
NODISP on
MSGCOMMAND?ON
etc
THen, over the air, you send a message to the devices callsign "!OUT=$FF" where $FF is the state you want for the port bits
Bob
Evening all
I have a memory that it is possible to drive a gpio pin in a Tinytrak 4 high or low based on the receipt of an over the air command in an APRS packet.? I have looked at the manuals and this mailing list but can't find anything. I am looking to drive a relay to switch a repeater on and off at a remote mountain site which is battery powered.? Is my memory more faulty than usual?? Could someone point me to some doco on this.
Thanks and regards
Steven VK2BOS
|
Re: setting up a digi with tt4 need some config advice
Thanks for that, Rob.? Here is what I often tell people about digi setup:
To configure the stationary TT4 as a digipeater,
Connect the TT USB cable to the computer and install drivers if needed
Run a terminal program such as TeraTerm Pro and set it for 19200 baud
Connect the TT USB cable to the TT4 J2 DB-9
When prompted to press ESC 3 times, do it quickly to enter the command menu
Enter the following commands
RESTORE < this puts everything back to DEFAUT >
MYCALL <your callsign>
ALIAS1 WIDE1 (or WIDE2, or WIDE)
and set the audio levels to match your radio (TXLEVEL, TXTWIST, RXA, CALIBRATE, and MONITOR commands, plus the R1 pot.)
If you also want the unit to transmit its location, then set:
TSYMC #
PPER ?3600
LOCATION <your location> (Must match format exactly)
TOSV N
PATH1 WIDE2-2
PATH2 %
To convert your lat/long from decimal degrees like DD.dddddd just use the 2 digits (for the first number, 3 for the second) before the decimal, then multiply the .dddddd by 60, and put that after the DD with 2 digits, decimal, then 4 digits after the decimal.
To use calibrate, enter CALIBRATE and press enter. Use this command to adjust and test the transmit audio levels. While calibrating, PTT is activated and audio tones are sent to the radio. Use the L transmit the low tone, H to transmit the high tone, B to transmit both tones, alternating every 833us, and S to transmit both tones, alternating every 6ms (helpful to adjust twist with a scope). Use 1 & 2 to change overall tone levels, 3 & 4 to adjust twist (high tone vs. low tone), and Q to quit calibration.
I hope that helps.?
Byon
I believe this is typically the very first part of TSTAT PHG5360/WIDE because that is appended to the position TX. ?? According to the protocol, TSPEED should be FALSE
?? I am not sure about BText as that typically doesn't include a position report.?
?? This information should be included with a position report.
On Thursday, May 13, 2021, 1:53:38 PM EDT, steve potter < spotterotter@...> wrote:
I'm going to work on it some more when I get home from work today, i'm not planning on having a gps attached to it, its probably left over from when I used to run this in my truck. I'm trying to make it as legitimate and standard as the rest of the Digi's in the area granted it will have a lot less power. So if I'm understanding this right I can put the PHG5360/wide in the tstat and btext fields with the proper identifiers?
Thanks for the help so far!
Steve Potter
K7HAK
|
Re: setting up a digi with tt4 need some config advice
I believe this is typically the very first part of TSTAT PHG5360/WIDE because that is appended to the position TX. ?? According to the protocol, TSPEED should be FALSE
?? I am not sure about BText as that typically doesn't include a position report.?
?? This information should be included with a position report.
On Thursday, May 13, 2021, 1:53:38 PM EDT, steve potter <spotterotter@...> wrote:
I'm going to work on it some more when I get home from work today, i'm not planning on having a gps attached to it, its probably left over from when I used to run this in my truck. I'm trying to make it as legitimate and standard as the rest of the Digi's in the area granted it will have a lot less power. So if I'm understanding this right I can put the PHG5360/wide in the tstat and btext fields with the proper identifiers?
Thanks for the help so far!
Steve Potter
K7HAK
|
Re: setting up a digi with tt4 need some config advice
uidigi is an eprom that you burn after you did a files with your specs and there you go.
you can enter in command mode via rf so it is no1.
anyhow if you find your way with the tt4,good
73 and great week end
Gef
I guess I don't find the TT4 any more difficult to program than other TNCs I've used.
Comparing command summaries, I really see that the1270C had many fewer.? About the only difference I see is that you need to catch the bootloader on power up with the TT4 to make changes, where the 1270C had a cmd: interface.?
The older TNCs were made for CONV mode (keyboard-to-keyboard) and had options for APRS (trackers) or KISS mode (attached computer clients).? The TT4 is kind of the opposite.? It is designed as a tracker/client with an option to be used in CONV
mode.
The other tricky part (IMHO) is the setting of the decode parameters.? Most other TNCs use a chip (Bell 202 modem IC like the MX614).? These are easy to implement, but DSP (Digital Signal Processing) has come a long way since their design.? Software
modems like Direwolf, UZ7HO, and AGW all use this newer DSP capability in a PC.? Byon put it into a Sanguino (yes just a higher power Arduino chip).
Of course, in doing so, you have a little more to configure.? Some of those options went into the menu to replace or supplement resistors.? Where R4 &R5 are supplemented by RXAMP and R1 supplements TXLEVEL.? This gives you more control over the
encode and decode tones.
So did you get things setup the way you want?
On Thursday, May 13, 2021, 8:19:10 AM EDT, Gervais Fillion <ve2ckn2@...> wrote:
Robert
i understand you very clearly,
they are not easy to ^rpgramm at all .
no offence but i prefer my UIDigi with my old 1270C ,not that the TT4 is not good it is just complicated to programm
73 and good luck
gervais ve2ckn
I am not sure what you are asking when it comes to "fixed".
Fixed means not moving and so if your location doesn't change, you are fixed.
If you are concerned over the mic-E status being a bit untrue, then change TPROTOCOL
? TPROTOCOL MIC-E????????????????? compressed data which inclues a status like "Off Duty", "En Route", ...
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ?????????????? you have it set to 2 "In Service"
??TPROTOCOL APRS ????????????????? readable text data which does NOT inclues a status
??TPROTOCOL COMPRESSED ? compressed data which does NOT inclues a status
As for PHG details, you would add them manually to the beacon or status message.
Info:?
It appears you will have a GPS attached to a fixed station, but if it is fixed,
SBEN really isn't the method to time your TX.? No need to continually report you aren't moving (TSPEED)
Other items:
* I always set both PKTICOM and
PKTOCOM true, even if no computer is attached.? Then, if you do attach a computer, you will already have the infomration turned on.
* If it is remote and on battery/solar, you could set
LEDS FALSE
* If it is going to be remote, you might look into
MSGCMD
?? Some people use a PORT C as a reset (reboot).? So connect it through a relay to ground the reset pin of the micro, and you will be able to reboot the TT4 remotely using the !OUT command.
?? You should read up on that before implementing.
At a quick glance, those would be my comments.
On Wednesday, May 12, 2021, 10:24:24 PM EDT, steve potter <spotterotter@...> wrote:
I'm wondering what is the command to have it say that its fixed? Currently it says mic-e where a normal digi says fixed, unsure if i can put details on the power and the antenna direction also my
station says s instead of p when receiving packets on my ft2dr. I want to get this right since its going to be solar up in no mans land without access for months at a time. Current config as of now. the bperiod will change before it goes up the mtn. Any help
is greatly appreciated!
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 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 FALSE
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 APTT4
MYCALL is TMPFIL
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Digi Test
BTEXT is >K7HAK test digi Current voltage is ^V int temp ^T
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 126
TXTWIST is 50
RXAMP is 10
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 4632.8527N 12041.5691W
GALT is 450
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 3
PPERIOD is 300
MPPERIOD is 0
SBSSPEED is 6
SBFSPEED is 90
SBSPERIOD is 720
SBFPERIOD is 48
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 2
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
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
?
|
Re: setting up a digi with tt4 need some config advice
I'm going to work on it some more when I get home from work today, i'm not planning on having a gps attached to it, its probably left over from when I used to run this in my truck. I'm trying to make it as legitimate and standard as the rest of the Digi's in the area granted it will have a lot less power. So if I'm understanding this right I can put the PHG5360/wide in the tstat and btext fields with the proper identifiers?
Thanks for the help so far!
Steve Potter
K7HAK
|
Re: setting up a digi with tt4 need some config advice
I guess I don't find the TT4 any more difficult to program than other TNCs I've used.
Comparing
command summaries, I really see that the1270C had many fewer.? About
the only difference I see is that you need to catch the bootloader on
power up with the TT4 to make changes, where the 1270C had a cmd:
interface.?
The older TNCs were made for CONV mode (keyboard-to-keyboard) and had options for APRS (trackers) or KISS mode (attached computer clients).? The TT4 is kind of the opposite.? It is designed as a tracker/client with an option to be used in CONV mode.
The other tricky part (IMHO) is the setting of the decode parameters.? Most other TNCs use a chip (Bell 202 modem IC like the MX614).? These are easy to implement, but DSP (Digital Signal Processing) has come a long way since their design.? Software modems like Direwolf, UZ7HO, and AGW all use this newer DSP capability in a PC.? Byon put it into a Sanguino (yes just a higher power Arduino chip).
Of course, in doing so, you have a little more to configure.? Some of those options went into the menu to replace or supplement resistors.? Where R4 &R5 are supplemented by RXAMP and R1 supplements TXLEVEL.? This gives you more control over the encode and decode tones.
So did you get things setup the way you want?
On Thursday, May 13, 2021, 8:19:10 AM EDT, Gervais Fillion <ve2ckn2@...> wrote:
Robert
i understand you very clearly,
they are not easy to ^rpgramm at all .
no offence but i prefer my UIDigi with my old 1270C ,not that the TT4 is not good it is just complicated to programm
73 and good luck
gervais ve2ckn
I am not sure what you are asking when it comes to "fixed".
Fixed means not moving and so if your location doesn't change, you are fixed.
If you are concerned over the mic-E status being a bit untrue, then change TPROTOCOL
? TPROTOCOL MIC-E????????????????? compressed data which inclues a status like "Off Duty", "En Route", ...
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ?????????????? you have it set to 2 "In Service"
??TPROTOCOL APRS ????????????????? readable text data which does NOT inclues a status
??TPROTOCOL COMPRESSED ? compressed data which does NOT inclues a status
As for PHG details, you would add them manually to the beacon or status message.
Info:?
It appears you will have a GPS attached to a fixed station, but if it is fixed,
SBEN really isn't the method to time your TX.? No need to continually report you aren't moving (TSPEED)
Other items:
* I always set both PKTICOM and
PKTOCOM true, even if no computer is attached.? Then, if you do attach a computer, you will already have the infomration turned on.
* If it is remote and on battery/solar, you could set
LEDS FALSE
* If it is going to be remote, you might look into
MSGCMD
?? Some people use a PORT C as a reset (reboot).? So connect it through a relay to ground the reset pin of the micro, and you will be able to reboot the TT4 remotely using the !OUT command.
?? You should read up on that before implementing.
At a quick glance, those would be my comments.
On Wednesday, May 12, 2021, 10:24:24 PM EDT, steve potter <spotterotter@...> wrote:
I'm wondering what is the command to have it say that its fixed? Currently it says mic-e where a normal digi says fixed, unsure if i can put details on the power and the antenna direction also my station says s instead of
p when receiving packets on my ft2dr. I want to get this right since its going to be solar up in no mans land without access for months at a time. Current config as of now. the bperiod will change before it goes up the mtn. Any help is greatly appreciated!
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 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 FALSE
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 APTT4
MYCALL is TMPFIL
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Digi Test
BTEXT is >K7HAK test digi Current voltage is ^V int temp ^T
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 126
TXTWIST is 50
RXAMP is 10
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 4632.8527N 12041.5691W
GALT is 450
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 3
PPERIOD is 300
MPPERIOD is 0
SBSSPEED is 6
SBFSPEED is 90
SBSPERIOD is 720
SBFPERIOD is 48
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 2
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
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
?
|
Re: setting up a digi with tt4 need some config advice
Robert
i understand you very clearly,
they are not easy to ^rpgramm at all .
no offence but i prefer my UIDigi with my old 1270C ,not that the TT4 is not good it is just complicated to programm
73 and good luck
gervais ve2ckn
I am not sure what you are asking when it comes to "fixed".
Fixed means not moving and so if your location doesn't change, you are fixed.
If you are concerned over the mic-E status being a bit untrue, then change TPROTOCOL
? TPROTOCOL MIC-E????????????????? compressed data which inclues a status like "Off Duty", "En Route", ...
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ?????????????? you have it set to 2 "In Service"
??TPROTOCOL APRS ????????????????? readable text data which does NOT inclues a status
??TPROTOCOL COMPRESSED ? compressed data which does NOT inclues a status
As for PHG details, you would add them manually to the beacon or status message.
Info:?
It appears you will have a GPS attached to a fixed station, but if it is fixed,
SBEN really isn't the method to time your TX.? No need to continually report you aren't moving (TSPEED)
Other items:
* I always set both PKTICOM and
PKTOCOM true, even if no computer is attached.? Then, if you do attach a computer, you will already have the infomration turned on.
* If it is remote and on battery/solar, you could set
LEDS FALSE
* If it is going to be remote, you might look into
MSGCMD
?? Some people use a PORT C as a reset (reboot).? So connect it through a relay to ground the reset pin of the micro, and you will be able to reboot the TT4 remotely using the !OUT command.
?? You should read up on that before implementing.
At a quick glance, those would be my comments.
On Wednesday, May 12, 2021, 10:24:24 PM EDT, steve potter <spotterotter@...> wrote:
I'm wondering what is the command to have it say that its fixed? Currently it says mic-e where a normal digi says fixed, unsure if i can put details on the power and the antenna direction also my station says s instead of
p when receiving packets on my ft2dr. I want to get this right since its going to be solar up in no mans land without access for months at a time. Current config as of now. the bperiod will change before it goes up the mtn. Any help is greatly appreciated!
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 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 FALSE
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 APTT4
MYCALL is TMPFIL
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Digi Test
BTEXT is >K7HAK test digi Current voltage is ^V int temp ^T
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 126
TXTWIST is 50
RXAMP is 10
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 4632.8527N 12041.5691W
GALT is 450
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 3
PPERIOD is 300
MPPERIOD is 0
SBSSPEED is 6
SBFSPEED is 90
SBSPERIOD is 720
SBFPERIOD is 48
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 2
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
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
?
|
Re: setting up a digi with tt4 need some config advice
I am not sure what you are asking when it comes to "fixed". Fixed means not moving and so if your location doesn't change, you are fixed.
If you are concerned over the mic-E status being a bit untrue, then change TPROTOCOL
? TPROTOCOL MIC-E????????????????? compressed data which inclues a status like "Off Duty", "En Route", ... ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ?????????????? you have it set to 2 "In Service"
??TPROTOCOL APRS ????????????????? readable text data which does NOT inclues a status
??TPROTOCOL COMPRESSED ? compressed data which does NOT inclues a status
As for PHG details, you would add them manually to the beacon or status message. Info:?
It appears you will have a GPS attached to a fixed station, but if it is fixed, SBEN really isn't the method to time your TX.? No need to continually report you aren't moving (TSPEED)
Other items: * I always set both PKTICOM and PKTOCOM true, even if no computer is attached.? Then, if you do attach a computer, you will already have the infomration turned on. * If it is remote and on battery/solar, you could set LEDS FALSE
* If it is going to be remote, you might look into MSGCMD ?? Some people use a PORT C as a reset (reboot).? So connect it through a relay to ground the reset pin of the micro, and you will be able to reboot the TT4 remotely using the !OUT command. ?? You should read up on that before implementing.
At a quick glance, those would be my comments.
On Wednesday, May 12, 2021, 10:24:24 PM EDT, steve potter <spotterotter@...> wrote:
I'm wondering what is the command to have it say that its fixed? Currently it says mic-e where a normal digi says fixed, unsure if i can put details on the power and the antenna direction also my station says s instead of p when receiving packets on my ft2dr. I want to get this right since its going to be solar up in no mans land without access for months at a time. Current config as of now. the bperiod will change before it goes up the mtn. Any help is greatly appreciated!
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 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 FALSE
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 APTT4
MYCALL is TMPFIL
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Digi Test
BTEXT is >K7HAK test digi Current voltage is ^V int temp ^T
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 126
TXTWIST is 50
RXAMP is 10
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 4632.8527N 12041.5691W
GALT is 450
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 3
PPERIOD is 300
MPPERIOD is 0
SBSSPEED is 6
SBFSPEED is 90
SBSPERIOD is 720
SBFPERIOD is 48
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 2
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
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
?
|
setting up a digi with tt4 need some config advice
I'm wondering what is the command to have it say that its fixed? Currently it says mic-e where a normal digi says fixed, unsure if i can put details on the power and the antenna direction also my station says s instead of p when receiving packets on my ft2dr. I want to get this right since its going to be solar up in no mans land without access for months at a time. Current config as of now. the bperiod will change before it goes up the mtn. Any help is greatly appreciated!
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 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 FALSE
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 APTT4
MYCALL is TMPFIL
PATH1 is WIDE1-1
PATH2 is WIDE2-1
PATH3 is
TSTAT is >Digi Test
BTEXT is >K7HAK test digi Current voltage is ^V int temp ^T
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 126
TXTWIST is 50
RXAMP is 10
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 4632.8527N 12041.5691W
GALT is 450
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 3
PPERIOD is 300
MPPERIOD is 0
SBSSPEED is 6
SBFSPEED is 90
SBSPERIOD is 720
SBFPERIOD is 48
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 2
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
ALIAS3 is
DUPETIME is 30
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
?
|
Re: My overly-complicated TT3+ install
Hello Bill,
Thanks for sharing with us your tricks for your install. You have given us a few ideas for our future installs.
toggle quoted message
Show quoted text
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: My overly-complicated TT3+ install
Yes, it's an active antenna with 28dB gain also.?
I've been using several mag mount GPS antennas but just didn't like the coax across the roof and in through the doorframe. I much prefer the small antenna permanently mounted in the center of the roof.
|
Re: My overly-complicated TT3+ install
Is that a passive or active antenna?? Many gps boards feed dc antenna power up the center conductor (through an smt choke and then capacitively couple the signal into the module).
This is a nice active antenna that also has the wire exit on the side and a magnet to stick it to a vehicle roof.? 28dB of gain gets you locked faster and pulls in more of the constellation for better positioning.
gil
----- Original message -----
Subject: Re: [TinyTrak] My overly-complicated TT3+ install
Date: Thursday, May 06, 2021 11:16 PM
Last stop is a $13 GPS antenna with SMA connector  from Amazon. I popped some of the plastic off around the windows and was able to pull the headliner down enough to safely drill a hole for the antenna. My truck is black, as is the antenna so I had to point out the newly installed antenna to my wife, I guess that's a good thing.
Attachments:
|
Re: My overly-complicated TT3+ install
Last stop is a $13 GPS antenna with SMA connector  from Amazon. I popped some of the plastic off around the windows and was able to pull the headliner down enough to safely drill a hole for the antenna. My truck is black, as is the antenna so I had to point out the newly installed antenna to my wife, I guess that's a good thing.
|
Barry L. Lankford
Gregory Lane
Doug J
Bill WA4OPQ