Posts Tagged ‘iraq’
Last summer when we were camping in the national parks, there were many campsites where we had no cell phone service. I am not complaining about that, but our work around to communicate back home to the XYL often required a trip to the pay phone (sometimes hard to find). I thought about perhaps using APRS’s capability of relaying short pieces of text as emails. Part of the problem is that there are many areas of the parks that don’t have any APRS digipeater coverage (Glacier and Yellowstone National Parks for example). How to get a message through?
Then I remembered my MARS station (AEN5AC) in Iraq. I was using an ICOM IC-7000 and an SCS PTC-IIusb modem to pass MARSGRAMS from my location north of Baghdad to another station at the US embassy in Qatar. The pairing worked quite well and I was consistently able to connect and pass traffic using PACTOR 3 at the 1400 baud rate. Could I use a similar setup to provide an HF email option while camping this summer?
I dug out my SCS PTC-IIusb modem. I had not used it since shutting down the MARS station in June of 2008. Everything was still in the box. To include the cables necessary to interface the modem with an ICOM IC-706MKIIG… the same rig I use for HF mobile.
I pulled out my spare IC-706MKIIG. Coming back to Kansas from Field Day in California back in 2009, my IC-706MKIIG quit on me. I ended up buying a second at the HRO in Denver and sent the broke one to ICOM. ICOM fixed it and returned it. I kept it in the box and it went back on the shelf. I did order a 6 pin Molex connector with powerpoles to allow for an easy power connection (#9). I connected the two cables from the modem to the rig. Once cable is for the data and plugs into the 706’s 13 pin accessory connection (#4). The other cable connects to the 706’s CI-V interface (#6) to have the radio change frequencies based on what station is being contacted.
I had the basic hardware of a HF email station, except for a computer. I would need one that would function out of the vehicle. This would probably require a laptop. I also decided for the ease of simplicity that the computer should be Windows driven (instead of Linux). Gasp! The bottom line is that the software and drivers required to send email via HF and use the SCS PTC-IIusb modem is Windows based. The answer ended up being an Dell XPS 15.
Using a Windows based computer helped me with a number of summer travel tasks that could not be accomplished by my small Linux laptop:
(1) Run the software required for HF email (more on Winlink and Airmail later)
(2) Run ARRL’s TravelPlus for Repeaters
(3) Run RT Systems radio programming software for my TM-D710A
(4) Run RT Systems radio programming software for my VX-8RGs
(5) Read the SD card from my Canon digital camera
Interestingly enough, the new laptop does not have a CD/DVD drive nor an RJ-45 connection for a LAN cable. Neither of these have been a show stopper yet.
ARRL’s TravelPlus for Repeaters
I had purchased TravelPlus for Repeaters with the intent of installing it on my existing Linux laptop and running it under a VirtualBox Windows session (similar to how I run iTunes on my Linux laptop). However the software failed to install. I tried troubleshooting and looking at suggested fixes found on the forum sites but still had no luck. I tried installing TravelPlus using WINE. It installed but would not run as well.
Dell XPS 15 to the rescue. As the laptop does not have a CD/DVD drive, I copied the drive onto network storage. I then was able to install TravelPlus over the network and it is working without issue.
RT Systems Programming Software
The RT Systems programming software works fine under a VirtualBox Windows session. As I was moving all my vehicle related radio/computer tasks to the new Windows laptop, I attempted to install the programming software for the TM-D710A (used for beaconing the location of my vehicle and talking on VHF/UHF). Following a similar procedure that worked for TravelPlus, I copied the programming software from the install disks to a network drive. The software installation for the TM-D710A worked without a hitch. The software for the VX-8RGs (HTs we use for around camp and hiking) failed to load. The error said that I must use the original disk to install. A big challenge when the laptop doesn’t have a CD/DVD drive. The work around is that you find another Windows computer with a CD drive, load the software CD, then back on the driveless laptop, map the CD drive (like you would map a network drive). That worked and I was able to install the programing software for the VX-8GR.
HF Email Software
There are two main choices for software to allow for HF email: RMS Express and Airmail. I installed both. Airmail was the same program I used in Iraq and it offered easy configuration with the IC-706MKIIG and the SCS PTC-IIusb.
I now had all my equipment for a test run setup in my basement hamshack: spare IC-706MKIIG, SCS PTC-IIusb, and the Dell XPS 15 with Airmail. I connected the IC-706MKIIG to my Elecraft tuner and used my existing G5RV antenna. Airmail configures easily. The software has a list of stations offering mailbox services that can be viewed on a propagation chart by frequency and distance. Based on time of day, I selected a station in Texas that offered a 40M PACTOR 3 connection. Airmail allows me to click on the frequency in the propagation chart which then changes the dial frequency of the radio. After listening to see if there were any ongoing connections, I initiated contact. The modem lights flashed and the rig clicked between transmit and receive. The connection was made and I was able to send a test email as well as a position report.
Success! The position reports that go into the Winlink system are copied over into APRS. Now, even if I am not able to reach a digipeater with my VHF APRS beacon, I can send a position report over HF to let the XYL know where we are.
I then thought about the steps I would have to take of transitioning my IC-706MKIIG configured for HF mobile to be ready to work with the PTC-IIusb to send email. As the remote head is located up near the drivers seat, this would present problems with being able to observe the modem, laptop, and radio control head all at the same time.
What if I just dedicated the spare IC-706MKIIG rig to the task of HF email? It would save me time and bother in pulling and plugging cables. It would also give the camping option of being able to operate HF from outside the vehicle.
Using an additional iPortable box, I rack mounted the spare IC-706MKIIG and the SCS PTC-IIusb. Now I will have a spare HF rig with me, so if one goes out I will still be operational. I also attached the Tarheel screwdriver antenna’s rocker switch to raise and lower the antenna on the side of the box. During normal HF mobile operations, the TurboTuner (connected to the other IC-706’s tuner connection and CI-V connection) manages achieving a correct match between the operating frequency and the screwdriver antenna.
I only have the one TurboTuner. The TurboTuner requires a connection to the CI-V. So does the SCS PTC-IIusb. My solution was to leave the TurboTuner alone. Instead, using the rocker switch, I can manually tune the antenna while visually observing the 706’s SWR meter.
To transition between using the 706 dedicated to HF mobile to the 706 now dedicated to HF email, I have to do the following:
(1) disconnect the antenna feedline from the TurboTuner
(2) disconnect the control line that goes from the TurboTuner to the Tarheel screwdriver antenna
(3) connect the antenna feedline directly to the HF email 706
(4) connect the control line to the rocker switch
(5) connect the laptop to the SCS PTC-IIusb via a USB cable
(6) connect the iPortable’s powerpole connection to the junction box in the back of the vehicle
… then I am ready to go. The iPortable box rests nicely on the vehicle’s tailgate, next to the laptop. All at about lawn chair height. Not only can I use this setup to send email via HF, but I can also use it for causal National Parks On The Air contacts as well.
What’s left to do:
(1) Constant cooling fan modification for both IC-706s (see AD5X’s article)
(2) An extended control cable for the Tarheel screwdriver antenna. This will allow me to further remote away from the vehicle, but still use the antenna.
(3) A length of antenna feedline for remoting.
(4) A length of powerpole-ready powerline to attach to either the travel trailer battery or directly to the spare vehicle battery… again for remoting away from the vehicle.
(5) I have a set of Heil headsets that worked with my IC-7000. I think if I get the AD-1ICM, I should be able to use them with the 706.
(6) A Heil HS-2 hand PTT switch to use with the headset.
I’ve been attempting to get my arms around my various logs from different callsigns. Previously I have had mixed luck with LOTW. Then I pretty much abandoned it. This time I read and re-read the instructions. Today I got my TQ6 file and was off an running.
I exported my current log from fldigi as an ADIF file and then used the TQSL application to upload it. Error, error, error. What was this? I hit Google and started researching:
ARRL’s tqsl messes with fldigi saved QSO_OFF time
I learned more than I wanted to know this morning about what the ARRL¹s tqsl application for LoTW does when it signs your saved fldigi newlog.adif file. It does more than just applying your digital signature. I had a busted QSO with Jeff, N8NOE, on LoTW and spent some time trying to understand what happened. The problem was with the time of the QSO. Both of us log the time at the the end of the QSO; however for there was a disconnect because my QSO time at LoTW showed up as Time ON, rather than Time OFF. Fldigi logs both TIME_ON and TIME_OFF; however, when you ask the ARRL tqsl application to apply your digital signature, it ignores the fldigi saved Time_OFF and converts the TIME_ON to a nonstandard ADIF format called QSO_Time. If you want your fldigi logs uploaded to LoTW to reflect QSO OFF time, you have two options. You can manually edit your On and Off times in Logbook-newlog.adif panel read the same. Another workaround is to use the fldigi File/Export ADIF with the option for Time ON unchecked. Then use a text editor to search and replace TIME_OFF with TIME_ON. This will fool the ARRL tqsl application to log the correct correct QSO time. Another option for someone to think about could be a new macro command that would reset the QSO times (ON and OFF) to be the same when you click on log. If you don¹t believe tqsl changes your fldigi logged QSO TIME_OFF, open one of your last .tq8 files with text editor (I use BBEdit) and scroll down and you will note the nonstandard QSO_TIME time that matches your your ADIF TIME_ON rather than TIME_OFF. 73 Dick AA5VU
… and that is what I did. And it worked! Although the issue Dick describes and the issue I was having were different, the solution still worked.
Now I am trying to add the logs for both my YI9MI and HL9MI operations. We will see how that goes.