.....here's my solution. I thought it worth mentioning...as it had a bit of a twist.
Some background first - I posted this on the Ham Radio Deluxe Forum...but the DX4WIN part is pertinent here for sure: *I'm running HDSDR version 2.76 (an older version....originally, newer versions like 2.81 did NOT work with the Yaesu FTDX101D. I think it was actually an Omnirig v2 issue, and you HAD to use Omnirig vs 2 with 2.81 and above. Maybe now it does work with a 101D, but I don't care....2.76 suits me fine). I'm running SDRPlay1 on the IF output of the 101. There's never any worry of "burning up the SDR". I'm running DX4WIN 9.09. I've been running that logging program for DECADES. It's EXTREMELY reliable, and filters VERY well (and....I have some 25 years or more of daily use "vested" in it....and as a "power user", I know it inside and out}. For instance, I'm trying to not only work ALL DX 340 countries (I'm at 328 currently), but I want to work OVER 300 countries on EVERY band mode (ie 300+ countries on 10 CW and 300+ on 10 SSB, 300+ on 12 CW and 300+ on 12 SSB, etc). Well, I should clarify....every band mode I consider worth working. SSB and CW. I have ZERO interest in things like FT8.....I consider that computer to computer....like Artificial Intelligence....not Ham Radio. So I want to know from my DX cluster software and logging program....not only have I worked a particular country on say 80 meters....and not only have I worked that country on CW AND SSB (on SOME band combination, but NOT necessarily on 80)....but have I worked both modes... specifically, have I worked that country on 80 meters (in this example) on BOTH CW AND SSB. HRD can't filter with that granularity (not that I've found, please enlighten me if there is indeed a way to do that!). DX4WIN can. DX4WIN also has call sign alerts for SPECIFIC call signs....for that "real" radio I referred to....SSB and CW. You enter the call sign of a DXpedition (ie.....VU4AX).....and then it alerts you with a color coded spot for THAT country in the Spot window . HRD can do that for DIGITAL modes, but for whatever reason....apparently they chose NOT to do that call sign alert feature for SSB and CW. So the HRD Alert feature is USELESS to me...as it doesn't do SSB or CW alerts for a specific call. So for these and other similar reasons....I need DX4WIN. It has far more granularity filtering on its Cluster and Logging software features. It also has a SEPERATE Spot and Packet windows. If you want, you can clearly see ALL the spots rolling in on the website/Cluster you choose in the Packet window.....and you can quickly submit commands to the Cluster (they have shortcut tabs you can set up for things like SH/DX, SH/WWV, etc, etc). Meanwhile, only the color coded spots YOU desire that YOU set up show up in the separate and distinct Spot window. You can set time limits on spots to automatically delete old ones. You can delete particular spots manually. It's SOOOO much cleaner to look at and efficient that way. HRD has SOME filters, but again, not nearly as much granularity as DX4WIN. So that's the "why" I need DX4WIN to work. Likewise, I won't go into detail, but I've tried just about ALL the panadapter software out there, and HDSDR wins hands down for me. I won't type a bible on why......... I still have several of those others I tried (SDRUNO, SDRConsole, etc). I NEVER use them anymore after playing with them. Bottom line I get it...HRD is more a RIG CONTROL application....with logging kind of an "afterthought". DX4WIN (and other similar logging programs) ...is/are more of a LOGGING program...with almost no rig control ...kind of similarly as an afterthought as it were. Having/using BOTH....gives the best of BOTH worlds! If only HRD would incorporate a bunch of those filtering granularities I'm talking about, I could get rid of DX4WIN. Or if DX4WIN would incorporate things like controlling MULTIPLE rotator controllers, automatically uploading my logging entries to Clublog and QRZ, etc., I wouldn't want/need HRD. But I digress.........* So, HDSDR and *DX4WIN*....here's the QUICK fix(es) to work with HRD: *SETUP:* *HDSDR - * 1. In the *Options>RF Front-End configuration* - I changed the *control from "Omni-Rig*" in the drop down window...to "*by HRD (DDE)"* 2. In *Options>DDE to HDSDR *- I changed in the left column *from DDE format of "None"......to "HRD*" That's it. I changed two commands, and my HDSDR that had worked for many years using Omni-Rig and a virtual serial splitter software (called LPB2) so that I could run CWSkimmer, DX4WIN and HDSDR all at once....now I'm running the HDSDR using DDE with HRD. *Just those TWO changes* did that. I did *NOTHING in HRD* to make this work. Works perfectly...just like it did when I used LPB2 and virtual ports the "old" way...........full rig control and communication "both" directions. For *DX4WIN - * 1. *Purchased* *VSPE* serial emulation software (my LPB2 didn't have the capability to set up JUST virtual comm pairs, it wanted to be hooked up to the rig comm port...and then let things like HRD, HDSDR, DX4WIN, etc....connect via virtual ports. HRD did NOT like that and was very unstable!). I tried VSPE for free first, but to have comm pair ports AUTOMATICALLY start up with no intervention....or to have saved comm pair configurations you could load back up, you had to have a license. No problem with me on that.... 2. Set up a *virtual comm pair* - in my case....*Comm 11 and Comm 12*. I just used the default settings in VSPE. It took seconds to do this step. (Don't pick the first option from the drop down window...which sets up ONE comm port for sharing. Pick the SECOND option a comm pair...with two ports). 3. Went to *HRD* , in the Rig control side....went to *Tools>Hardware>3rd party serial port. Set the port to 11*. Set the speed to 38400 (that's what I'm using, but that's optional). I checked both the *Enable and Connect When HRD starts* boxes. Then *APPLY, and OK.* I used the defaults on all else. 4. Went to *DX4WIN*. Under *Files>Preferences>Radio*, CHANGED the* TYPE on radio 1..*..from the correct rig file for my radio (Yaesu FTDX101D)....which worked perfectly using my old software (LPB2) and other apps......to now....*KENWOOD.* I tried my correct rig file....the Yaesu file, but it didn't work. Then I read some more, and saw the HRD literature talking about it using Kenwood CAT protools. I reasoned that if DX4WIN had some kind of "default" Kenwood rig file, that should do the trick. And it DID! 5. In the same area for radio 1 configuration, *CHANGED the comm port* from the port I had been using with the old LPB2 software, to the new *VSPE port 12*...the other port of the 11/12 comm port virtual pair I had created earlier. And just like that, DX4WIN is now ALSO interfacing with the rig (via HRD). Everything is working together....HRD....HDSDR....DX4WIN....and of course, the 101D radio. I've only used it a couple of days. So far so good. But can't comment on the LONG RANGE stability. It's been stable the few days I've used it for several hours. One other thing, there's an option in VSPE to "Save as autostart config". I chose that. Now....as soon as I turn on my computer, that comm pair....11 and 12...that I created with VSPE.....IS there! No need to open VSPE/turn on the app. The pair is there for use as soon as my laptop boots up. That....is so convenient. With LPB2, I had to start that program first....let it build the virtual ports....then open the apps that would use them. With VSPE ...at least for that virtual comm pair saved with the saved autostart config, there is no need to start VSPE. In fact, if I open VSPE, I see where it loaded a file in its program folder called "autostart.vspe". That's the file I saved it to start automatically. I love that feature! In a perfect world....DX4WIN would do things like run multiple rotators (I would REALLY love that feature), upload my logging inputs to Clublog and QRZ automatically....etc. But I'm guessing the days of new features being added are probably gone? I'm ok with using my "fix"...of running BOTH HRD (and it's logging and DX Cluster functions) and running DX4WIN to get the better granularity in filtering on the cluster and the reliable things I've come to know and love about the Program. Then I can have the "best of both Worlds"....be it with having to log multiple times (just twice....once in HRD and once in DX4WIN). I like being able to do what I talked about above...that DX4WIN does....in the example of tracking band/modes like the 80 meter example I mentioned. And I FULLY trust both the Cluster and logging functions in DX4WIN. And I like having some of the rig features in HRD. But I'd HANDS DOWN.....pay for upgraded features in DX4WIN and JUST use it....if they ever did some of those things mentioned. But for now, this described how to interface HRD and DX4WIN (and HDSDR)....the best KP&W (Known Problem and Workaround....software development term) for the time being...... K4TK Tim Moore PMP ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
