LATER EDIT: You can use the same settings for the Kenwood TH-72 because the TNC chipset is the same. Tested and work OK!
Last days I was confronted with a big problem!
How to establish a APRS local gateway from Internet to Radio with a TM-D710 and UI-View, the well known software from G4IDE!
First time, I started the Kenwood TM-D710 in Packet mode and I made the necessary settings for 9k6 but when it connects to UI-View, the baudrate reverted to 1k2!
The main issue is that this software have more than 7 years of no-upgrade due to the SK of the author and the INIT file for the Kenwood TM-D710 radio is not included within the CMD files.
Therefore I start to look around how the software sent the commands to the radio.
It seems that in the CMD folder within the installation directory is the key.
Inside this folder, there are some files that define the initialisation commands for every TNC listed in UI-View menu and that initialisation occured everytime I tried to setup the communications with the radio.
The solution is here:But how we find the TM-D710-9k6 TNC-type?
Very simple!
We search in the CMD folder for a file named "TM-D700.ORG".
Open it with Notepad. You should see something like this:
;This is a copy of the default version of TM-D700.CMD. ;This is a sample TNC initialisation file for use with ;the Kenwood TM-D700.[SETUP] ;DON'T alter anything in this section unless you are ;sure you know what you are doing! COMMAND_PROMPT=cmd: COMMAND_CHARACTER_CODE=3 ESCAPE_CHARACTER_CODE=CONV_COMMAND=CONVMYCALL_COMMAND="MYCALL "UNPROTO_COMMAND="UNPROTO " NO_BEACON_COMMAND= BEACON EVERY 0 [INIT_COMMANDS]^CAI 1!AI 1 etcNow, open a new file in the Notepad and paste the following code: [SETUP] ;DON'T alter anything in this section unless you are ;sure you know what you are doing! COMMAND_PROMPT=cmd: COMMAND_CHARACTER_CODE=3 ESCAPE_CHARACTER_CODE= CONV_COMMAND=CONV MYCALL_COMMAND="MYCALL " UNPROTO_COMMAND="UNPROTO " NO_BEACON_COMMAND=BEACON EVERY 0
[INIT_COMMANDS] ^C^C^C ;Control mode on. TC 1!TS 1 ;Select TNC PKT mode on A band. TN 2,0!TN 2,0 ;Waiting for command prompt. ^M!cmd:!5 ;Repeating the first two commands is not an error! ECHO OFF ; Below we can set the beacon in 10*N seconds. 60 means 600 seconds BEACON EVERY 60 ; You can set the beacon text with BTEXT ... ECHO OFF ; You can set the Digipeating function but have to add some other commands DIGI OFF ;Below we setup the RF TNC baudrate ;If you want 1k2 baud, simply replace "9600" with "1200" HBAUD 9600 GPSTEXT $GPRMC LTMON 5 LTMHEAD ON LOC E 0 MON ON MCOM ON MSTAMP OFF CONOK OFF PACLEN 250 UIDIGI OFF UIFLOOD % UITRACE % XFLOW OFF HEADER OFF NEWMODE ON NOMODE OFF
[EXIT_COMMANDS] LTMON 0 MON OFF TC 1 TN 0,0
After that, rename the .txt file into "TM-D710-9k6.CMD" and save it in the same CMD folder.
Open UI-View, go to SETUP menu, click on COMMS SETUP and, BINGO, you will have the new TNC option enabled!
Watch the first picture again, make the same settings and go for 9k6 APRS with the Kenwood TM-D710! Beware: you have to keep the radio with no menu-enabled TNC! The TNC will "revive" once you hit the "OK" button (first image) and the LCD on the radio will show "PACKET96"!
73 de YO3HJV
LATER EDIT
I was asked by Jack, G4AMF to tell him how to setup the radio for 1200 baud APRS operation.
If you look on the code above, you will see a "commented" line (with ; in the beggining) whic tells you how to do it. You simply replace
HBAUD 9600 with HBAUD 1200
and, Voila! you got the 1k2 APRS working with TMD 710 as KISS TNC!
Don't forget to put the radio in TNC mode and not in APRS mode!
The same 73 from Romania! Another Later edit: You can find the files on Github: https://github.com/yo3hjv/TM-D710-Ui-View32-TNC-files
Download them, put them into the CMD folder of the programm installation folder, restart UI-View.
A lot of people told me that the instructions for Sky Command found on the user manuals are somehow too complicated and not so easy to follow. Some of them complaint about not succeeding to setup the link.
So, I prepared a step-by-step procedure for the Sky Command II.
I used a TS2000 and a TM-D710. Both are "K-Type" versions. Of course, they were "E" type before the mod was applied...
First of all:
The TS2000x is the TRANSPORTER and the TM-D710 is the COMMANDER.
We assume that both Transporter and Commander radios are Sky Command II capable. Mine was modified to do Sky Comm as they was European version. I applied the “K type mod”.
Before anything, go on MAIN receiver and select a convenient HF frequency. TUNE THE HF ANTENNA!
Very important step (from Marco, a italian HAM): RESET FIRST THE TNC ON BOTH RADIOS!!!
Setup the TRANSPORTER (TS2000):
Select on main channel VHF 144.750. This will be the Transporter to Commander channel.
Select on aux channel UHF 438.500. Select CTCSS on aux channel on 100,0 Hz.
Return to the MAIN section of the radio.
Press MENU and scroll to the Menu #62. Press SUB. After pressing the SUB key, the LCD will show something like “MENU 62A-COMMANDER CALLSIGN”.
Here you input the callsign which will be used by the TS2000, in my case, “YO3HJV-1”. {Yes, the callsign is followed by a number! (Explanation: The COMMANDER and the TRANSPORTER use Packet radio to communicate and they need different SSID’s.)}
The input is made as follows: Scroll the letters with MULTI/CH and advance the position of the letter with MAIN(Back) or SUB (Forward).
Store the callsign with M.IN key.
Scroll to “MENU 62B-TRANSPORTER CALLSIGN” and enter your TRANSPORTER CALLSIGN, in my case, “YO3HJV-2”. Follow the previous #8 and #9 step above.
Select MENU 62C. Here you will select the CTCSS code used for UHF data and voice comm with MULTI/CH. In my case, 100 Hz.
Select MENU 62D and choose with MULTI/CH 1200bd. This is the data speed for Packet comm.
Select MENU 62E and choose “T-PORTER”. This tells the TS2000 that is acting as a Transporter.
Press MENU. The panel control in TS2000 will not work because it is set to work remote only (Sky Command II).
Setup the COMMANDER (TM-D710):
Check if you have MENU 7xx enabled. If not, apply the “K Type” mod.
On the “A” receiver (left) dial 144.500 MHz. On the “B” receiver (right), dial 438.500 MHz.
On the “B” receiver set the CTCSS to 100 Hz.
Go to Menu nr. 700(COMMANDER callsign) and set the callsign as per step #8 (In my case, YO3HJV-1). Press the DIAL button to store the callsign.
Go to Menu nr.701 (TRANSPORTER callsign) and set the callsign as per step #11 (in my case, YO3HJV-2). Press the DIAL button to store the callsign.
Go to Menu nr.702 and set the same CTCSS as per step #12 (100 Hz).
Go to Menu nr.703 and choose the “role” of the TM-D710. In our case, choose “COMMANDER”. Press Dial.
Now, you should be in COMMANDER MODE.
Press “0” to start the link between Transporter and Commander.
To activate the TRANSPORTER, press “1”. The TRANSPORTER should transmit the callsign (in my case, YO3HJV) on the 2m band, and after that, should retransmit the audio feed from HF frequency set as per step #3.
For the rest of the “game”, read the Sky Command section in the user manual of the TM-D710. Is very explicit.
I also tried (and succedeed) to use the Sky Commander with a TH-D7, but this is another story...
73!
PS
Bob Bruniga has the following ideeas:
IDEAS For SKY-COMMAND III for CLUB ops 22 Feb 07
----------------------------------------------------------------------
SkyCommand II was designed for an individual to have remote control of
his own rig on a one-for-one basis. But there are many applicaitons
for clubs that may want to have a group with access to the SkyCommand
HF transceiver and for all to be able to participate in the group
monitoring while one is transmitting. Here is my WEB page that tries
to optimize this type of operations.
Although we can do Group operations with SkyCommand II, there are some
ideas that could make this better, for new users while being fully
backwards compatible with SkyCommand II systems. An overview of the
required changes for group operations for what I call SkyCommand III
are as follows:
1) Use default Generic COMMANDER and TRASNSPORTER calls so that
everyone can set their radio once, and then be able to use any Sky
Command system that is made public with these same generic calls.
2) Use two PL's on the UHF audio link, so that only one PL keys the
remote SkyCommand transmitter, but the other PL (or none) lets all
members of the group chat on the UHF channel for coordination.
Enable a front panel button for selection of CHAT or PTT choice of
PL while operating Sky Command.
3) Have provisions for the multiple COMMANDER radios to BEACON an
APRS status packet periodically that contains their FCC call so that
they can be identified and so that other SKY-III transceivers can
also see who else is sharing the UHF command channel and operations.
4) Have the TRANSPORTER auto-QSY periodically to the APRS channel
and put out a Sky Command status packet to put the HF asset on the
APRS system map showing the current operating frequency.
5) Some provision for additioanl commands for antenna selections.
6) Allow the D700 to operate UHF COMMANDER link on band A UHF so
that band B can be used for 220, 902 or 1296 reception of Sky
Command Audio.
DETAILS FOLLOW: Each of these concepts is further expanded below.
GENERIC CALLS:
Let the default COMMANDER call be CMDR and the default TRANSPORTER
call be TRPTR, and default TRANSPORTER skycommand PL be 123. while
the default USER or CMDR PL is 88. This makes any user able to
monitor a SkyCommand system out of the box, or to go from one public
skycommand station to another. And he can chat with other skycommand
users on the UHF channel without bringing up the HF TX, unless he
selects the special 123 TX PL.
Another advantage of generic callsign operation is that multiple
COMMANDERS can all be in SkyCommand mode and can see the same front
panel HF radio status at the same time.
ALTERNATIVE (a): Another option may be to have the OPTION for public
systems to allow the TRANSPORTER to be GENERIC on receipt and accept
Sky Commands from ANY callsign in this mode. This way, every
existing COMMANDER can control the radio without having to use a
generci call. This keeps the COMMANDER operator legal, since his
call will be in every packet.
ALTERNATIVE (b): Another option for COMANDERS is to allow for
GENERIC receipt and display of Sky Command data independent of the
TRANSPORTER call. This way, each COMMANDER does not have to change
his transporter callsign for each different GENERIC system that
he wants to control.
UHF PL CONSIDERATIONS:
1) While in Sky-Command mode, the COMMANDERS need a front panel
button to turn on and off sky command PL. This way, all the
group COMMANDERS can turn off special PL and talk/coordinate
back and forth on the UHF simplex channel without keying up the
sky-command radio. This allows very powerful use of HF radio in
local groups, and very simple to implement. I suggest naming
this soft button toggle between "PTT" and "CHAT" as it toggles
between the SkyCommand PL and the non-skycommand PL or off.
SKYCOMMAND COMMANDER OBJECT BEACON PACKETS:
While a COMMANDER is in SkyCommand III mode, it should include some
periodic OBJECT packets to tell others on the UHF frequency who it
is and where it is. This should beacon once every 10 minutes or
each time after the skycommand RX is activated.
FORMAT: THe format for the status packet (in APRS OBJECT format)
would include the MYCALL as the object name and TIME/position, etc.
This is because the actual packet will be originated by the generic
"CMDR" callsign and so without the OBEJCT packet, we cannot tell
who is doing what. Here is a suggeted format:
THe TX is transmitted if the SkyCommand PL is set, and an "RX" will
show if the SkyCommand PL is not set.
LIST: On receipt, these objects can go to the normal APRS list or
to the DX list? While in SkyCommand III mode, there should be a
"LIST" hot key on the D7 or D700 radio that will call up this list,
and display only other SkyCommand stations.
PACKET MUTE:??? New COMMANDER radios need to have a 20 dB mute when
monitoring the UHF channel so that VOICE can be heard but packets
are muted. Or is CTCSS Set in Skycommand mode? If so, then it needs
to recognize BOTH the PL's for PTT and for CHAT mode only.
CROSSBAND???? While Sky Commander with TX PL is transmitting on HF,
does the VHF audio link remain up and provide a copy of the transmitted
voice so that all monitoring stations can hear it? This can help in
CHAT mode with PL's and muting packets? More thought here...
SKYCOMAND III TRANSPORTER APRS ANNOUNCEMENT PACKETS:
SkyCommand III needs an APRS Station packet from the Transponder
radio periodically that goes out on the APRS (144.39 in the USA)
channel to beacon the HF radio (IF) status for all surrounding
APRS mobiles (on 144.39). This beacon packet will put the public
SkyComand III station on the MAP, and alert all drivers of its
presence and operating frequency. In most cases, this packet
will go only DIRECT.
Notice the Frequency is inlcuded. But the inclusion of the
UHF is optional and if not used, then the HF channel can show.
The Transporter needs to auto-qsy for one-second periodically to
put this out on the APRS frequency and not the SkyCommand channel.
My guess would be once every 10 minutes if no-change in frequency
and within one minute of each frequency CHANGE. THis results in
no transmissions while fine-tuning, but an update within a minute
after a change is made.
Also, the SkyCommand Transporter needs to INITIATE a radio status
packet (in IF... format) once every minute on the UHF command
frequency to update all monitoring COMMANDERS that may begin
monitoring.
Note: Backwards compatibility. For SkyCOmmand II, a BT and BEACON
can be set in packet mode and it will continue to work in SKyComand
mode, but it is not on the APRS channel, only the SkyCOmmand
channel.
ANTENNA SELECTION:
SkyCommand III needs to be able to select ANTENNA on the TS-2000.
ALthough MEMORY channel on TS-2000 can remember ANTENNA 1/2, an
external antenna selection is needed for selecting fixed beams or
othere options on the same band. More later on this subject?
SEMI-PUBLIC OPERATION:
Provision needs to be made in Sky Command III for the uplink command
channel to be on 900 or 1296 MHz and private, while the VHF or
User Listening channel can be on VHF or UHF. In otherewords, the
Sky Command III should be able to operate in RECEIVE-ONLY mode and
give the user the full status of the SkyCommand Radio display, even
if he is not commanding and even if he cannnot press [0] to start
the link.
CONVERSLY, provision needs to be made for Sky Command to use 220, 900
or 1296 bands in place of the VHF audio link. This reduces the demand
on the 2m band for these links. The Remote controlled site may have
to add one of these 220, 902, or 1296 band transmitters just for the
audio, but the D700 should be able to receive this audio in place of
2 meter audio link and still operate in Sky Command COMMANDER mode.
It is very easy to BUILD a skycommand III system TRANSPORTER with a
D700 radio's internal TNC and some external software. So this investment
in SkyCommand III can multiply more than just the new radios sold.
SkyCommand III also willbe fully backwards compatible to II's.
SOFTWARE TRANSPORTER: My next document will describe tha backwards
compatible SkyCommand II+ system that can run on a PC between a D700
TNC and a TS-2000. This PC software can implement many of the advantages
of SkyCOmmand III and be compatible with existing D700's.
Acum aproape un an, scriam aici un post despre cum am adaptat un GPS Holux pentru utilizarea pe TM D-710 cu un minim de conectica. Am cautat un modul convenabil din punct de vedere al dimensiunilor dar si al pretului. Un alt criteriu a fost acela al sensibilitatii de receptie, intrucat antena urma sa fie obturata de capacul de plastic al panoului frontal.
Am achizitionat de la Farnell un GPS Leadtek LR9552, cu antena incorporata. Dimensiunile sunt de 25x25 mm cu o grosime de aproximativ 7 mm! Am fost impresionat de cat de mic este modulul; practic, antena acestuia este mai mare decat montajul propriu-zis...
Asadar, aveam in cutia cu "maimute" un modul GPS. (De fapt, mai am unul, HI). Multa vreme am incercat sa gasesc si conectorul mama, corespondent conectorului existent pe modulul GPS. Nu am reusit sa il gasesc iar astazi, am avut ideea salvatoare, asa ca am trecut la fapte! Am taiat partea de sus a conectorului si am capatat astfel acces la pini, urmand sa lipesc direct pe ei alimentarea si iesirea de semnal NMEA. Conectorul este foarte mic, astfel incat operatiunea se recomanda celor cu vedere buna si mana sigura.
Pentru lipirea firelor am folosit un letcon de 25W caruia i-am subtiat varful astfel incat sa nu lipesc mai multi pini deodata. Conform fisei tehnice, modulul GPS are doua iesiri! TxDA si TxDB.
Intrucat nu stiam care dintre ele este cea care furnizeaza semnalul necesar, am lipit pe toti pinii cate un fir. De fapt, nu imi trebuiau si intrarile la modul, dar, pentru ca mi-a iesit prima lipitura, am continuat, asa, din inertie... Ulterior, dupa identificarea pinului corect, am dezlipit celelalte fire, ca nefiind necesare. Proba de functionare am facut-o folosind conectorul lateral al panoului de control si o sursa de alimentare exterioara (o baterie 6F22 de 9V si un stabilizator LDO de 5V). Pinul 2 de la GPS este cel care furnizeaza semnalul necesar (TxDA).
Am desfacut panoul capacul panoului frontal si am desfacut saibele de fixare de la potentiometrii de volum/squelch si de la optical encoder.
Cele doua blocuri potentiometrice sunt conectate pe doua bucatele de cablaj si, desi sunt codificate diferit, in realitate sunt identice ca valori si schema electronica, deci nici o grija ca le-ati putea incurca intre ele la montaj. Pe placa cu componente exista o folie profilata destinata protejarii cablajulu iin zona decupata a capacului din spate. O puteti ridica fara grija, nu este prinsa nici de cablaj si nici de capac. Sub aceasta folie exista un conector flexibil si este bina sa aveti mare grija cu el!
Desfacem cele doua suruburi care fixeaza cablajul de masca si ridicam montajul. Conectorul de 2,5mm se gaseste in stanga afisajului LCD si se observa ca este vorba de o mufa care are si circuit de autodeconectare. In figura de mai jos se vede clar pe care dintre pini conectam firul de semnal de la GPS.
Dupa ce lipim firul de semnal de la GPS, asezam cablajul la loc in panou si folosim o degajare in PCB pentru a trece firul in spatele carcasei. In stanga conectorului RJ45 ce foloseste la conectarea panoului frontal la unitatea centrala observam un regulator LDO. Acesta este regulatorul care furnizeaza 5V montajului. Intre regulator si conector, pe cablaj este marcat traseul de 10V. Acest marcaj este facut exact pe traseul de GND, unde ne vom conecta cu pinul 1 de la GPS. Pinul 7, de +5V de la GPS se va lipi direct pe pinul regulatorului LDO.
Dupa lipirea firelor de la GPS, putem face o proba: Conectam panoul de comanda si pornim statia. In meniul APRS selectam la INPUT: GPS. Pornim TNC-ul in regim APRS12 si apasam butonul PMON pentru a observa informatiile furnizate de modulul GPS. Dupa aproximativ 2 minute, la mine a inceput sa dea informatiile de pozitie. Cu ESC ne intoarcem in regimul de afisare a frecventei si apasam POS. Pe afisaj ar trebui sa observam deja coordonatele locului in care ne aflam, inclusiv cu afisarea careului (KN34BK in cazul meu). In partea din stanga sus a afisajului, va clipi "GPS"; semnificatia este aceea de semnal NMEA coerent.
Oprim statia si deconectam panoul de comanda pentru etapa urmatoare. Dupa ce am verificat functionarea corecta, eliminam de pe capacul din spate ghidajul destinat unui beeper (nu stiu care era rostul HI). Aplicam o bucata de folie dublu adeziva pe care vom lipi modulul GPS, chiar pe partea cu antena de receptie. Am observat ca nu influenteaza cu nimic performanta receptorului GPS.
Fixam modulul dupa cum se observa din imagine si inchidem capacul de la panoul de comanda.
Din acest moment, avem un TM D-710 cu GPS incorporat in panoul frontal!
Imi cer scuze pentru calitatea imaginilor dar am folosit ce aveam la indemana, adica un telefon mobil.
Mai jos sunt cateva informatii despre modulul GPS folosit:
{Some time ago I made a GPS unit for TM D-710. Now, with a little help from Leadtek, I manage to embedd a GPS OEM unit inside the TM D-710 Control panel! Yes, I just put a GPS inside the "box". }
20-channel, miniaturized single chipset module GPS with integrated ceramic antenna
The Leadtek GPS 9952 module (LR9552) is a high sensitivity and very compact smart antenna module, with built in GPS receiver circuit. This 20-channel global positioning system (GPS) receiver is designed for a wide range of OEM applications and is based on the fast and deep GPS signal search capabilities of SiRFStarIII architecture.
Features:
Based on the high performance features of the SiRFstarIII single chip set
20 channels with All-In-View tracking
Compact module size for easy integration: 25x25x8.4 mm
Hardware compatible with SiRF GSW3 v 3. 2.2 software
Multiple I/O pins reserved for customizing special user applications
Low power consumption: up to 70 mA, and extra high sensitivity: -158dBm
RoHS compliance
Cold/Warm/Hot Start Time: 4 2 /38/ 1 sec . at open sky and stationary environments.
Reacquisition Time: 0.1 second
RF Metal Shield for best performance in noisy environments
Multi-path Mitigation Hardware
RS232 level for GPS communications interface
Operating temperature: -20 ℃ to +60
Protocol: NMEA-0183/SiRF Binary (default NMEA)
Baud Rate: 4800, 19200, or 57600 baud (default 4800)
Ideal for high volume mass production (Taping reel package)
Cost saving through elimination of RF and board to board digital connectors
TECHNICAL SPECIFICATIONS:
Chipset SiRFstarIII single chipset (GSC 3f ) General Frequency L1, 1575.42 MHz (C/A code 1.023 MHz chip rate) Channels 20 Sensitivity -159 dBm
Accuracy
Position 10 meters, 2D RMS 5 meters 2D RMS, WAAS corrected <5meters(50%)>Velocity 0.1 meters/second Time 1 microsecond synchronized to GPS time Datum Default WGS-84 Other selectable for other Datum
Time to First Fix (TTFF) (Open Sky & Stationary Requirements) Reacquisition 0.1 sec., average Snap start 1 sec., average Hot start 1 sec., average typical TTFF Warm start 38 sec., average typical TTFF Cold start 42 sec., average typical TTFF
Main power input 5 +- 10% VDC input Power consumption ≈350 mW (continuous mode) Supply Current ≈70 mA Backup Power 1.5 +- 10% VDC input.
Serial Port
Electrical interface Two full duplex serial TTL interface. Protocol messages NMEA-0183/4800 bps (Default)
Time-1PPS Pulse
Level RS232 orTTL Pulse duration The 1PPS pulse width is 1 μs, this 1PPS is NOT suited to steer various oscillators (timing receivers, telecommunications system, etc). Time reference At the pulse positive edge. Measurement Aligned to GPS second, ? 1 microsecond
Environmental Characteristics
Operating temperature range -20 deg. C to +60 deg. C Storage temperature range -20 deg. C to +65 deg. C
Physical Characteristics
Length 25 mm Width 25 mm Height 8.9 mm (with 4mm antenna)
6.9 mm (with 4mm antenna) Weight 13.0/8.0g
WARNING!
The Leadtek 9552 OEM GPS comes in two "flavours": RS232 and TTL I/O. Be sure to choose and order the RS-232 version! They both share the same user manual/leaflet! Only the RS-232 works with the TM-D710!!!
I was looking for a compact solution for APRS mobile operation. First, I was started with a HOLUX GM210 "mouse" GPS.
The GPS unit was powered from a little homebrew stabilizer from the 12V socket. The same case was hosting the connection between the radio and the GPS unit. But, this solution was to messy for my auto because involved a lot of wires and boxes. So, I started to look for a more compact solution. And this is what I made: a little box with the GPS module inside among a double RJ45 connector. The connector is needed to have the +5V supplied directly by the radio. At the time of making the project, I had to choose from where to have the 5V: from the remote head or directly from the radio. The remote head of the radio is powered at 10V and has some LP stabilisers inside. The LP stabs was evaluated and the conclusion was that they must not be stressed with the supplementary current surged by the GPS unit. Instead, I choose the main 10V from the radio, available directly from the RJ45 cable. So, I used 2 RJ45 female couplers, already with straight connections between pins. The result is in the pictures. The case is a half of the initial housing which host the first stabilizer. In the box is the Holux GM210 module, a LM7805 stabilizer and the conections.
But how we find the TM-D710-9k6 TNC-type?
