RigBlaster Pro Mic Wiring

I promised more detail, so here it is.

I have ripped the setup apart to make room for dinner on the kitchen table, so now I am cleaning this blog up by finishing the setup details. Brad N1JIF shot some closeups of the equipment as we ripped it all down, and I will compile the details in seperate posts.

I am getting ready to record the audio exchanges and put the finishing touches on the laptop setup and while all of this is fresh in my memory I have decided to document as much as I can to not only help me, but others who may have questions and are brave enough to navigate this blog for answers. The following info is direct from the RigBlaster Pro User Manual:

YAESU with 8 Pin Screw on Microphone Connectors
(This jumpering is for newer Yaesu radios that have Microphones with isolated PTT & audio grounds.)

INPUT SIDE
Pin #
1 Blue Shunt Jumper to Pin 1 OUTPUT Side
2 Blue Shunt Jumper to Pin 2 OUTPUT Side
3 Blue Shunt Jumper to Pin 3 OUTPUT Side
4 Blue Shunt Jumper to Pin 4 OUTPUT Side
5 White Jumper to PTT GND – INPUT Side
6 White Jumper to PTT – INPUT Side
7 White Jumper to MIC GND – INPUT Side
8 White Jumper to MIC – INPUT Side



OUTPUT SIDE
Pin #
5 White Jumper to PTT GND – OUTPUT Side
6 White Jumper to PTT – OUTPUT Side
7 White Jumper to MIC GND – OUTPUT Side
8 White Jumper to MIC – OUTPUT Side

Here is the diagram as published in the RigBlaster Pro manual:

Here is the actual photo of the jumpers as I have them configured inside the RigBlaster Pro:

The 2 jumpers to the right of the block are not connected to anything, they are for jumpering receive audio at the mic connector. Neither is the GNDTIE jumper on the block, the actual jumper sits on a single pin. Jumpering this introduces a horrible ground loop that gets passed on thru to the transmitter.

This wiring is for the Yaesu MD-100 mic, which is screwed into the front of the RigBlaster Pro via its 8-pin cable (8-pin RJ-45 modular to circular screw-on 8-pin). Output to the rig is accomplished out the back of the RigBlaster Pro through the 8-pin cable (8-pin modular RJ-45 to circular screw-on 8-pin) to a Yaesu CT-69 connector, which adapts an 8-pin to the modular 6-pin RJ-11 that is required by the FT-100D. The CT-69 contains a 27K resistor as well as a small capacitor (i dunno what the capacitor is for, but Randy N1GWL will explain it to me, as he as well as Chuck WA1NBU are the kings of capacitors) built into the 8-pin circular screw-on shell.

I will forego the MD-100 wiring for now, but I have successfully interfaced the MD-100 to the FT-100, the UP/DOWN buttons work and the audio is outstanding. Problem is, I haven't built the cable for the RigBlaster Pro yet... That requires yet another cable... If anyone wants the details, it is easy to email me for more info, or leave a comment.

Complete 40M-75M Field Day Setup

OK, here is my contribution, listed as best I can.
I hope KT1Q and N1GWL can list their contributions here as comments...
(note you can click on many items and view either the manufacturers site or the actual product itself)

Yaesu FT-100D HF-440 rig
Yaesu MD-100 Microphone
West Mountain RigBlaster Pro
Dell Latitude D630 running Win 7
Astron RS-50M Power Supply
West Mountain RigRunner 4010S
LDG Z-11 Pro Auto Tuner
Daiwa CN-101 SWR/Power Meter
Heil HC-4 ProSet headset
Bird Model 43 ThruLine Wattmeter
Decibel DB4303G Dummy Load
West Mountain PwrGate Controller

Another important piece of equipment often overlooked is the User Manuals. I cannot say how many times I have been told to RTFM (Read The Fine Manual), and equally as many times it has saved my ass. I do have to confess that my book-reading for pleasure was replaced long ago by reference materials and technical bulletins. One of the easiest things to do is to compile all the manuals in .PDF format and put them in your My Documents folder. If you have the ambition, write the manuals to a CD or DVD (depending on size) and if you have a duplex (print on both sides) printer, print them out and place them in a 3-ring binder. Personally my 3-ring binders tend to come out more like a 3-ring circus, but you get the drift of what I am trying to say.

Here is a shot of the setup on the kitchen table:

There isn't a lot of detail you can see in this shot but I will post more about the specific setup. I know a lot of you are thinking 'Jeez, just bring your rig and set it up, no need for all this extra crap...' and at times I tend to agree. But that is what eventually makes the difference between an average station and a top-scoring station. Field Day isn't just an exercise, it is a contest.

EnableInputMonitor = 01

Here is installment #5 of the continuing Field Day Setup Progress Report (no longer named FIASCO!)

No longer a fiasco because I was able to get full-duplex audio working on the Dell D630 Laptop!

For those of you with a Dell Latitude D630 running Microstink Vista (or any computer that uses Sigmatel audio for that matter...) who want to enable full-duplex audio, you will need to edit the registry.

Here is the fix:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0000\Settings\filter\SpeakerHp\

Change the Binary Value for EnableIntSpkrMute to 00

Add the Binary Value EnableInputMonitor and set the value to 01

Reboot

Right Click the Volume Speaker Icon by the clock on the taskbar, Select Playback Devices, Double-click Speakers/Headphones, Click the Levels tab, then unmute the Input Monitor option.

LET ME MAKE THIS DISCLAIMER - Editing the registry can be dangerous to your computer and your sanity. I cannot be held liable for anything you do while editing the registry of your computer. If you have never edited the registry, or if you feel uncomfortable even thinking about editing the registry, give your laptop to some geek who has done it before, and let them do it for you.

Works like a charm. I now have inserted a REAL laptop into the main slot, let's see how this one reacts...

Anyway, busy day today, spent all day at a conference in South Burlington at the High School. I used to think our school and network were screwed up. Turns out Woodstock is miles ahead as far as technology is concerned, and we are doing things in a small school that bigger schools can only hope to implement some day. Go figure. It appears as though they have plenty of money though, their auditorium was one of the nicest I have ever seen. Really cool audio and lighting boards. Wish we had that.

Testing will continue with the Dell D630 this weekend. I hope to setup some .wav files, but I have to remember to start Sound Recorder from the command line, as by default it wants to record .wma files. Damned Vista... Yet another ill-behaved Microscam product. At least the D630 has a REAL 9-pin com port. No serial to USB adapter to worry about. Besides, I have always thought the delay introduced by the USB stuff was a problem, I will use the ThinkPad with the USB to serial as a backup now. Mike KT1Q won't need to scrape up a backup laptop after all...

Now that the laptop is working (so far) I am actually getting excited about working Field Day with the SOVARC boys (and girls... I haven't seen Mandy AI1A in ages!). The thought of loading all this crap into the truck is a but unnerving, but I survived the NEAR-Fest, so I guess this isn't too much different. I will be hauling real radio-related stuff instead of junk computer crap. It does seem a bit different to go and play radio in a different area, it would make more sense to hang out with the guys around the Upper Valley (TSRC). Ever since they ruined Field Day for myself and Mike N1MS, I have held a grudge. As past president of TSRC I am utterly appalled at what they have become and the money they waste each year. It is not as though they are rich, but they insist on maintaining a used vehicle lot in the guise of 'Emergency Service'. Best thing I ever did was dis-associate myself from those losers. Now I get to play radio with REAL hams... Or as Ed WA1MAG would say, Ham Radio Buffs...

Sometimes taking a break from things can allow you to clear your mind, look at things from a different perspective, and gain some insight that one would normally overlook. That is what happened here, I had to think about things for a bit, then figure out where to look for answers. And that brings me to the whole purpose for these recent posts, a convenient method to document the trials and tribulations of setting up a Field Day station. It really can only get worse from here...

This Dell Latitude D630 is an awesome laptop. I just can't help bragging about what this thing contains:

Intel T9500 dual-core processor @ 2.6 GHz (this may change, I may swap in a slower processor just for testing purposes, probably a T9300 @ 2.5 GHz...)
8Gb PC2 memory (all addressable, requires BIOS A15)
MS Vista SP1 64-Bit
300Gb 7200 RPM Seagate HD
Sony 16X DVD Dual-Layer optical drive
Optional 9-cell battery (approx 4-hours battery life... depending)
Optional Device Bay battery
Actual 9-pin comm port
1440X900 Display Resolution
Intel 4965 BGN Wireless (230 mps wireless connect to an N-Router)
Gigabyte ethernet

I think now you can see why I prefer to use this laptop. It is a road-warriors dream machine.

Anyway, now that it works, let's see what it can do over the next week, I will keep you all posted here. Leave a comment if you get a minute.

Not all software is created equal...

This is part 4 of the continuing Field Day Fiasco saga...

Catch up with the progress by reading the 3 previous posts below.

Anyway, it is time to move all this crap to an actual 'test' environment similar to what one could expect at Field Day. (one NEVER knows what to expect at Field Day, that is why they call it an 'exercise'...) Gotta clean off the kitchen table, Doreen is gonna be pissed as all hell when she realizes all of this complicated radio/computer/power/wiring is gonna occupy the kitchen table for a whole month. What the hell, dealing with her is GOTTA be easier than connecting all this stuff together and making it work.

Mental note - 50 amp power supplies are friggin' heavy. Try to get someone else to move it next time. So it looks like I can fit almost everything into a 4-foot square space on the table. This is good - there may be about this much room at the FD site, I will need to ask Chuck WA1NBU about where we will be and who will be there. So far I think the station will be on 40M phone. It better be, as I have no plans to bring a key or set anything up for CW.

Setting things up in the kitchen requires several trips back to the shack in order to obtain all the necessary connectors and cables, but this is why we test things in an actual test environment. At this point all is connected in a basic way, power to the radio, (and everything else) and computer to everything. Now the setup starts to break down...

Apparently not all software is created equal. At this point I have no clue that the Dell Latitude D630 running Vista 64-bit isn't going to work. Nevertheless, I plod on, installing software package after software package trying to get the rig control set just right. I can get Ham Radio Deluxe to work just as it did in the shack, it is what I use for PSK using this very setup except for the lack of a docking station and flat-panel monitor. The D630 has an actual 9-pin com port setup as COM1, and it works well to control the rig. As I have it setup, it will even key the rig and pass audio, albeit one-way. BUT WAIT! I haven't used this laptop here before! I used a different computer to run PSK with this setup! How does this even work? OK, ok... calm down, let's see what else will work. Chances are the SOVARC boys (and girls) will be using N3FJP Field Day Logger 2.8 as their main logging program. Let's run that and see what happens...

LOCK-UP... oh wait, it is just KEY-DOWN... unplug everything, and let's set this up... FD Logger is a simple program, it does one thing at a time really well. Problem is I won't find that out until later on in the process. Looks like it will do DVK, so let's set that up. Here is where I run into .wma versus .wav file difficulties. Apparently, logging programs will only recognize .wav files. The Dell D630 running Vista 64-bit will only record .wma files. What the hell!

Rip the Dell outta the setup, and place the IBM in its place on the table. WAIT - NO serial ports... Off to find some sort of adapter... YES I have 2 that actually work on XP Pro 32-bit. This is good. The Targus wants COM5, and the Belkin wants COM4. Looking in the FD Logger setup, it appears that I can use COM5, so I pick the Targus adapter, and I am off to the races. More like racing nowhere really fast...

Apparently the N3FJP FD Logger software cannot read the rig via rig control and key the rig for DVK on the same port. Took me 3 days to realize this. I had to turn off the rig interface (set to NONE) before the DVK would even begin to work. Even THEN the software keys the rig on the RTS (so it sez...) line which in all reality is the DTR line. (on the FT-100D I guess you need to key the rig via DTR and send CW via RTS...) I can tell this by looking at the front panel of the RigBlaster Pro, it has LED's for PTT & CW. Also when you activate the rig via one of these lines, it automatically switches the MIC out of the circuit and switches IN the output form the sound card in the laptop. But when I finally get it working, there is this strange buzzing being fed into the front panel mic input on the rig. What the hell! Where is this coming from?

So I pull the cover on the RigBlaster Pro, something I don't like to do because there are jumpers and wires and such inside. Besides, there are 4 screws holding the cover in place. I figure if God wanted us to play with the innards of stuff, he would have designed it with a quick-release hatch. This is a place where no normal person should ever venture. Referring to the User Manual again, I am still befuddled as to what I have configured wrong. At first I think it is something mis-wired with the rig control, after all FD Logger says I am keying the wrong lines... so I spend a day re-wiring all the serial stuff, A-to-B connections, FSK this and PSK that. All I succeeded in doing is breaking the rig control stuff, which, thank God for Ham Radio Deluxe (HRD) gave me a quick and easy way to see if everything was still working. HRD is pretty easy, and it has a fairly long development path. I have used it and its associated programs for several years, and it is to the point where I am actually considering making a donation. Just like West Mountain stuff, HRD just works.

After successfully breaking and then reconnecting all the rig control stuff, I decided to move my attention back to the mic jumpers and all that associated wiring and configuration. Referring back and forth between the User Guide and every other reference I could find, I ended up back at trial and error. What could possibly explain the wierd buzzing noise in the mic audio? Then it hit me. The FT-100D uses the same GND between the mic and the PTT line, as configured in the mic connection. In the RigBlaster Pro there is a GNDTIE configuration jumper used to tie the two grounds together. Somehow, I thought this jumper was necessary in order to get the rig to key with the PTT button on the mic. Yet again, apparently I was wrong. I pulled off the GNDTIE jumper and stored it on a single pin, and all my (well, most) audio woes went away. Mental note - Try things with ALL the software running, not with the computer turned off. I needed to have the stuff running in order to insure all was working correctly together.

Along comes N1MM Logger, my preferred software since I dumped WriteLog a few years ago. N1MM is pretty neat, it is what all the big guns use (unless they have custom proprietary software, written especially for that particular contest station) because it will allow SO2R operation as well as a host of other options such as SO2V, rotator and CW keyer control, and so many more this blog ain't big enough to list them. It is ULTRA configurable (if that is a word) and it would be real nice to have it up and running just in case the powers that be realize they can save $6.00 (that's right folks, N3FJP costs a whole $6.00) by using N1MM instead. This might be the subject for my next blog post - Why does N1MM say one thing and FD Logger say another? And why can't WriteLog use COM5?

Trying to setup N1MM was another exercise in futility, pressing F1 to start the DVK made the program spit and sputter, like a handicapped kid with a speech impediment, a lisp and a big 'ol Tootsie Pop all stuck in his mouth at the same time. Tried this with changing every configuration setting known to man, combinations and permutations numbering well into the square root of a bazillion somewhere. Better leave this for yet another day, yet another post...

So it comes time to actually feed some audio from the computer into the rig, and here is where I actually discover what the meaning of 'full-duplex' really means. Remember back when you could purchase an audio receiver that actually had jumpers where the pre-amp output was? There were actually jumpers that connected things in a bigass loop, allowing you to put whatever piece in or out you needed. Along comes the new millenium, where everything is controlled with an actual 'switch' of some sort allowing you to switch things in and out easily with the touch of a button. In today's world, buttons have been replaced with check-boxes and such that one must 'click' on in order to configure. Here is where you can turn full-duplex on or off on a Windows XP Pro 32-bit computer...

Right-click (or double-click) the audio icon in your System Tray and bring up your Audio Properties dialog box. Click Options and choose Properties. Choose the Recording Controls. To enable full-duplex, find where the mic is muted, and 'un-mute' the microphone. This is the KEY to all the RigBlaster Pro operations.

Try to do this in Vista...

My Blaster is ALIVE! Everything works! I can hear static out of my headset! HOLY SOUNDCARD, BATMAN! Why didn't they tell me this already? How come it took 2 weeks and an ungodly number of hours of trial and error to set this up? Because the words 'full duplex' are mentioned in the RigBlaster Pro manual only 1 time, under Advanced Audio Considerations. And only then it talks about the ability to process your audio properly. Nowhere does it mention that if you wanna have headphone audio, you MUST have a soundcard capable of full-duplex audio.

OK, if I sound overly excited, it is probably because I am. I now have almost everything working as I think it should. I have a base system working, with DVK setup to call CQ FD... There are many other things yet to accomplish, such as setting up all the other voice messages, and trying to get the Rig Interface working with FD Logger so that it will at least read frequency and mode. Remember, I need to make this as simple and bulletproof as possible (yeah, right...) so that when I have a 6-pack or 2 into me it will all be as clear as day how to setup and operate 40 meter phone...

This is not to mention the other equipment yet to interface, such as the D630 running Vista 64-bit. I am determined to get this baby setup and working, as I have never seen a more stable OS in my life. This 64-bit stuff is incredible. Not only can I fully address 16G (that is 16 GIGABYTES) of memory, it is pretty much immune to the 32-bit puking of programs one would normally experience on XP or a Mac. Shit flies on this laptop. When you double-click an icon by mistake, the program is up, running and waiting for user input BEFORE you realize you made a mistake. I imagine this will consume the next week or so.. at least it will give me time to blog some more about software.

Stay tuned...

This should be easier than it is...

This is part 3 of the Field Day setup fiasco...

Anyway, to continue the saga, I believe I have a full station setup and working. It is not exactly how I would like it to be, but again, this is a work in progress and I finally have a good working base from which I can build.

See the two previous posts below for more info on exactly what I plan on setting up as well as the components I am trying to interface.

To summarize, I have a Yaesu FT-100D rig interfaced to a West Mountain RigBlaster Pro which is connected in many ways to an IBM ThinkPad T60 laptop running 32-bit XP Pro. Power to this system is provided by an Astron RS-50M supply thru a West Mountain RigRunner 4010S, attached to a West Mountain PwrGate and a rather large gel-cell battery as backup. In addition, there is a Diamond cross-needle power/swr meter in the mix as well as an older Panasonic speaker used for audio output. Voice input is provided by either a Yaesu MD-100 desk mic or a Heil ProSet headset (HC-5 DX element).

These are the parts I have working so far. To say I am a fan of West Mountain products is an understatement, their shit just works. Period. Now onto the things I would PREFER to get connected and working:

Dell Latitude D630 laptop running Vista 64-bit
David Clark H10-60 headset with M7 mic
Bird ThruLine wattmeter
Additional Heil headset

The next task to tackle is the D630. In order to use a laptop fully with the RigBlaster Pro interface, you need to have what is called 'full-duplex' audio through your computer. Basically this is the ability to 'un-mute' the microphone input so it can be processed and then passed through the soundcard and back out to the RigBlaster Pro. This is critical to the ability of the Blaster to provide output audio to your headphones as well as the connected rear-panel speaker output. So far I have been unable to accomplish this, but there have been a few posts where I have seen users employ full-duplex on their Vista computers using the proper drivers and settings. All hope is not lost...

On top of that will be the ability to use the David Clark headset, it is an incredible piece of work that has the ability to completely cancel all ambient noise via custom engineered gel-filled earpads. It is no wonder they use these in aircraft. Put these babys on and you are isolated in a world where silence is golden and the ONLY audio you hear is that passed thru the tiny 1/8" plug connected to something. To say these are incredible again is an understatement. Bose could learn a lesson...

The DC H10-60 is the set I have, it has an amplified M-7A microphone that I would love to be able to use while connected to radios or computers. Got these at the Hosstraders hamfest (now NEAR-Fest) years ago, but only have been able to use them as headphones because of my apparent inability to wire the microphone correctly. This shit ain't plug & play, it is more like plug & pray. Maybe I can enlist Randy N1GWL to help, he is wiz-bang at this electronics crap. It needs DC bias current at the mic, so chances are it is either gonna work slick as shit or he will destroy a $70.00 headset cable.

The specifics of the RigBlaster Pro are the neat thing here, it is ultra customizable. It will interface virtually ANY computer & soundcard to ANY radio. The problem is generally gonna be the software you use to git 'r dun. That will be the topic in Part 4 of this diatribe, the insane ramblings of an Extra class part-timer. Psychobabble as Mike KT1Q puts it...

Despite what others might tell you, the most important part of the Blaster interface is not the RS-232 stuff and TTL conversion to control the rig, that is incredibly simple according to the RigBlaster Pro User Guide. It is the Mic connection and configuration to your rig that is the heart of the matter. This took me a week to understand and configure. Thanks Yaesu, for making every rig you manufacture different from the model before.

The FT-100D is a strange beast, but it remains as a workhorse in my shack, even though it was designed to be used mobile. It has data connections on the back, as well as rig control and key/speaker connections. The strange part is the mic connector in the 'front'. You need to remove the faceplate in order to connect the mic, and only certain microphones will work. You can find a link to Yaesu's official list of supported accessories on the web, but I tend to ignore official crap like that. I figure if I have a microphone, and it has some sort of connector, that I am intelligent enough to connect it to the radio somehow. Generally this is the case, and this example is no exception.

The Yaesu MD-100 is a wonderful desk mic, with built-in audio filtering and PTT as well as up/down 'buttons' laid out on a really nice looking stand. Again I bought mine at the Hosstraders (now NEAR-Fest) hamfest a few years back at a very reasonable price. I figured because it sez Yaesu on it that it should connect easily to a Yaesu radio, right? Yeah, right...

Not only does the FT-100D use a non-standard RJ-11 6-pin connector, it apparently multiplexes all the features available on certain mics via some sort of strange resistance matrix. Just to get the PTT to work using a standard mic on the Ft-100D it requires a 27K resistor in the PTT line. When you add the up/down buttons into the mix, it adds another couple resistors in a series/paraallel arrangement. Try fitting all that crap into an 8-pin plug shell! Let's put it this way, this type of cable pushes the limit of my soldering abilities. You won't be creating one of these with a 250 watt soldering gun.

Anyway, I successfully built a cable specific to this combination, it won't work with anything else as far as I know. It might work with my broken FT-8500, but I dunno, 'cause it's broken. The up/down buttons work fine, they advance the frequency up and down just like they are supposed to when the mic is connected, holding either of the buttons will initiate scan mode in the direction of the button you are holding. So far all is good. Until you try to tailor your audio via the switches on the bottom of the mic...

The MD-100 requires voltage in order to use the 'active' filters. Oh well. The FT-100D supplies the wrong voltage, and there just isn't any more room in the 8-pin plug for a couple zener diodes to drop the voltage enough to make things work. Did I attempt to make it work? No, I read about it and decided I can run the mic in 'thru' mode without the need for active filtering. Besides, this is Field Day, and we don't need no mic filters on Field Day. Or do we? I kinda figure I can get the RigBlaster Pro to process stuff if I really need to , but I generally just crank up the mic gain and the processor (compression) in the rig and let it go at that. Real filters are made of crystal...

So with the MD-100 working, and a brief test on VHF FM with Brad N1JIF confirmed the mic actually had some output, I decided it was time to move on and plug the MD-100 into the RigBlaster Pro to see what it did. So I plugged it in. What did it do? Nothing. Seems I have to build another cable... But wait! I have this CT-69 thingy, which is an 8-pin male (mics generally have an 8-pin female...) connector to an RJ-11 6-pin connector that I got somewhere and never figured out exactly when and where to use. Taking the CT-69 thingy apart, I see it has a resistor and a small capacitor connected to the lines that an FT-100D would use for PTT! OK, so I connect this adapter to the RigBlaster Pro cable... and still nothing. Back to the User Guide...

Seems as though I need to configure the RigBlaster Pro for this particular radio/mic combination. Aha! Who would have figured! Since I had never used a mic with this setup before (PSK-31 and CW only, yes... CW. I made one contact...) there was nothing configured correctly as far as the jumpers inside the Blaster were concerned. Here is where the FD Setup Fiasco actually begins...

So you already know Yaesu doesn't do the same thing the same way twice, and when you deviate from the official accessory path you kinda can expect no support whatsoever. This is a bad place to start from. Fortunately I have a few people who will help by offering advice (I don't have any real friends...) and then again, there is the Internet. One thing to remember - Google is your friend. If you don't know something, Google it. Strange how our society will develop new verbs for doing strange shit. Anyway, between that, the Blaster manual, the rig manual and some good old fashioned trial-and-error, I got the RigBlaster Pro 'kinda' wired up to accept the MD-100 PTT. No up/down button control of frequency, but I may add that at a later date now that I know I can build a special cable for that operation. Why not use a hand mic you ask... Hand mics are for lightweights and amateurs. They are for people not adventurous enough to stray into the realm of hi-fidelity audio electronics. They are for the weenies we unfortunately call 'Appliance Operators'. Apparently they are for people who want things to work, and need to have the impedence matched properly...

So I key the mic, the MD-100 forces the FT-100D into life, keying the rig, activating the fancy eee-lectroniks inside the rig and making the LED on the front panel turn from green to red. All is good in the K1XH shack - so far. Until I look at the power/swr meter, which should indicate no output because I am not speaking into the mic. But yet the meter is going crazy, with some sort of strange modulation going on, being fed into the radio from the Blaster in apparently some sort of wiring mis-hap. WHAT THE HELL!

Son of a bitch, I am ripping this all apart. Enough is enough. I need to see this all in its ripped-apart glory, only to be re-assembled on the kitchen table in its planned Field Day configuration. I will work on the audio later, as I have PTT and I think that is all I need for now. Time to strip one side of the shack...

Apparently I need help...

OK, so I admit I am not a brain surgeon, but then again this is not brain surgery.

I have been trying for a week or so to get a DVK (Digital Voice Keyer) of some sort to work with the equipment I have.

I thought I had everything I needed as far as equipment goes:
Yaesu FT-100D
MD-100 Microphone
MH-42 BJ6S Hand Mic
MH-36 BJ6S DTMF Hand Mic
RigBlaster Pro
Astron RS-50M Power Supply
PwrGate & Battery Backup
RigRunner 8-Port
Various USB to Serial converters
IBM T-60 ThinkPad (no serial port) running XP 32-bit
DELL D630 Laptop (COM1 serial port) running Vista 64-bit

I thought I had all the software I needed as well…
N3FJP Field Day Logger v.2.8
N1MM Logger v.9.5
Ham Radio Deluxe v.4.01

Apparently, every piece of software that I have uses a different method of rig control and PTT keying.
All I want to do is press F1 and have it key the rig and play a .wav file, and then repeat after 4-5 seconds ‘till I press escape or key the mic.
Do any of you have any experience with this? Any tips that can help?

Anyway – I have tried 2 different laptops, and both act differently. Get this – I tried to record a .wav file with the Dell running Vista. Simple task. Except for the fact that Vista no longer records things with Sound Recorder in .wav format any longer. It now records in .wma format, which logging programs won’t play. You have to start Sound Recorder from the command line with a /recordfile .wav modifier in order for it to do this with Vista…

But on to Serial port issues… WestMountainRadio had a link (http://lists.contesting.com/pipermail/writelog/2004-April/019714.html ) to a forum article I found interesting… Anyway it is becoming apparent that all serial ports are NOT created equal. The IBM T60, with NO serial port whatsoever needs a USB to Serial converter in order to interface to the RigBlaster Pro, and seems to work well as far as rig control goes. Problem is, the IBM ThinkPad T60 is a piece of crap I lifted from school. No wonder why we were getting rid of it… Next thing I wanna do is try the DVK aspect of things, I have not explored this yet. The Dell running Vista 64 is a bit more complicated, only certain USB to Serial converters will work, because of the ‘Vista 64-bit’ thing. Still looking for drivers for one Serial to USB device, I think I have another that will work but haven’t tried it yet.

My main concentration has been on the Dell D630, really nice laptop, 8G RAM, 9-pin COM port and 64-bit OS. You would think this would be adequate for logging at Field Day… Well you thought wrong. N3FJP won’t do rig control, it won’t even read the frequency and mode from the FT-100D, and I cannot for the life of me figure out how to get the DVK to work, as it won’t even recognize the COM1 device (RigBlaster Pro / FT-100D) attached to it. Ham Radio Deluxe (HRD) works just fine, rig control is great and I can key the rig fine, except there is no DVK built into HRD. I don’t even know how the logger works, as I haven’t got to that yet… Add to that the lack (seemingly) of support for .wav files on the Dell and it appears hopeless. N1MM Logger keys the rig, and seems to read the frequency and mode, but when you push F1 to initiate the DVK the rig keys OK, but the .wav file stutters and spits and goes real slooooow thru everything. Frustrating at best…

At least when I attach one of the 3 microphones to the rig, and then attach an antenna to the output, I can press the PTT button and speak and it actually works. I worked a special event station from Ukraine on 40M like shooting fish in a barrel. I know Ukraine on 40 barefoot is no big deal, but it fuckin works!

Why can’t the rest of this crap be as easy?