[hpsdr] COM Spliters

[Scott Traurig]

Mike,

I believe I know what you want, and I think I know where you are going
wrong. You are making things FAR more complex than they need to be.

I'm not familiar with log4om, but I took a quick look at the manual just
now. I believe it is the beautiful drawing of a VPSE com port splitter on
page 179 that is throwing you off.

In your case you do not need to use a splitter. And, as luck would have it,
you can have your cake and eat it, too!

For CAT control:

In PSDR, assign CAT1 to one end of the COM port pair that connects to
log4om Hamlib.
In PSDR, assign CAT2 to one end of the COM port pair that connects to
Fldigi.
In PSDR, assign CAT3 to one end of the COM port pair that connects to
WSJT-X.

For logging:

In log4om, make the appropriate TCP connection to JT-Alert/WSJT-X as shown
on page 182.
In log4om, make the appropriate TCP connection to Fldigi as shown on page
187.

That should do it, you can run ALL THREE programs at the same time, and no
splitter required! And you still have PSDR CAT4 if you need it.

For virtual COM ports you can use com0com, VSPM, or VSPE. I am 1000% with
the log4om developer's recommendation for VSPE. Yes, it costs a tiny bit of
money for the 64 bit version, but VSPE has proven, at least for me, to be
the easiest to use and most stable and reliable. And VSPE includes splitter
functionality if you ever need it. I actually use a VSPE splitter to allow
both DDUtil and the Elecraft KPA500 remote utility to both access and
control my KPA500 at the same time and it works quite well.

73,

Scott/w-u-2-o


On Mon, Jun 13, 2016 at 2:16 PM, Mike F <mikecf100 at gmail.com> wrote:

> Scott
>
> Thanks for responding.
>
> I may have been unclear about the program usages.  I want the radio,
> log4om, and EITHER fldigi or wsjt (not both) to communicate.  The setup,
> using a com splitter as shown in the log4om manual, should make this
> possible.  The desire for this is that log4om will rapidly identify the
> overall status such as country (and if it is new), beam direction, etc.
> once it has the callsign.
>
> Since I originally posted on the discussion list I have determined that I
> can get a response from the radio using putty (; results in ?;) but neither
> fldigi or wsjt recognize they are connected to the radio.
>
> Mike, K7SR
>
> On 6/13/2016 10:49 AM, Scott Traurig wrote:
>
>>     Mike,
>>
>>     Why would you want Fldigi and WSJT-X to be able to talk to each
>>     other? There is no functional support for that in either program.
>>
>>     CAT1 to program 1, CAT2 to program 2 and so on. You have the ability
>>     for 4 programs to access PSDR information and control PSDR at the
>>     same time.
>>
>>     73,
>>
>>     Scott/w-u-2-o
>>
>>
>>     On Fri, Jun 10, 2016 at 4:32 PM, Mike F <mikecf100 at gmail.com
>>     <mailto:mikecf100 at gmail.com>> wrote:
>>
>>         ***** High Performance Software Defined Radio Discussion List
>> *****
>>
>>         I use com0com to connect from powersdr to my logging program
>>         (log4om). I use psdr cat2 to connect to other applications such
>>         as fldigi and wsjt.  However I would like to be able to have all
>>         of the programs talk to each other, and this is suppose to be
>>         doable using a com spliter program.  I have chosen to do this
>>         using hub4com, the companion program to com0com.  I set this up
>>         following the process that should produce three bidirectionally
>>         enabled com ports.  Using three instances of putty I have
>>         verified that this is working as planned.  However if I connect
>>         powersdr in place of one of the puttys.  The two remaining
>>         puttys still communicate fine, but psdr does not join them.
>>         Without changing psdr cat, it works fine directly connected to
>>         an application.
>>
>>         PSDR is v3.3.6.
>>
>>         Mike, K7SR
>>
>>         _______________________________________________
>>         HPSDR Discussion List
>>         To post msg: hpsdr at openhpsdr.org <mailto:hpsdr at openhpsdr.org>
>>         Subscription help:
>>         http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>>         HPSDR web page: http://openhpsdr.org
>>         Archives:
>> http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20160614/91768b6e/attachment.htm>