I don’t have a FT450D or a RigBlaster Plug&Play but let me take a stab at this.

 

There are usually 3 different items when working digital modes, that work more or less independent:

1. Sound. The RigBlaster should create an external soundcard for Win10.  I guess this is working fine, assuming FLDigi is working OK. This also means that you should be receiving OK with WSJT-X but you may have to tune manually.
2. CAT control. This is for setting the frequency, mostly, with WSJT-X. The FT450D is not in the list of radios in WSJT-X. My FTDX3000 isn’t either but the FTDX5000 selection works fine. I think the CAT commands for general things like setting the frequency are pretty much the same between the Yaesu radios so try another model that is closest to yours. Maybe try the FT991 or FT950 or FT857.  Another part of the CAT control is the baud rate of the serial link. Look at the setting in FLDigi, again assuming FLDigi is working fine. My FTDX3000 defaults to 38400. Usually, when there is something wrong with the serial link, WSJT-X will complain.
3. PTT.  You have 4 choices for PTT: VOX, CAT, DTR or RTS. In case of VOX, the radio itself detects an audio signal and starts transmitting on its own. I have seen cable hookups with the SignaLink interface where the soundcard in the SignaLink detects the audio and then clicks a relay on a connector that plugs into the “key” input on the radio. In this case you’d select VOX in the software. Maybe the RigBlaster does that too. CAT may also work. I use “RTS” myself with a different digital interface. When FLDigi is working fine, check how FLDigi is controlling PTT and do the same with WSJT-X.

 

Maybe there is somebody here that also has a FT450D and that can provide some more specific info.

 

Best regards,

Eddy, W6EDY

 

Sent from Mail for Windows 10

 

From: Chuck Roth via Groups.Io
Sent: Monday, September 11, 2017 1:59 PM
To: WSJTX@groups.io
Subject: [WSJTX] Help Settings help #WSJTX_config #WSJTX_config

 

Well lets try this request for help again. 

I cannot get Wsjtx rc2 to control the radio or to transmit with PTT.

My Equipment is as follows:

Rig: Yaesu FT 450D
OS: Windows 10
Soft: fldigi v4.0.8

On other programs I use
Com5 Rigblaster Plug and Play for PTT And Sound
Com 7  RS232 to DB9 on the back of the radio for rig control. No matter
what combination of com settings will provide rig control and PTT

Can anyone out there let me know what settings I need to alow me to use
this program?

Thanks
Chuck
KB7OGE

 

Well lets try this request for help again. 

I cannot get Wsjtx rc2 to control the radio or to transmit with PTT.

My Equipment is as follows:

Rig: Yaesu FT 450D
OS: Windows 10
Soft: fldigi v4.0.8

On other programs I use
Com5 Rigblaster Plug and Play for PTT And Sound
Com 7  RS232 to DB9 on the back of the radio for rig control. No matter
what combination of com settings will provide rig control and PTT

Can anyone out there let me know what settings I need to alow me to use
this program?

Thanks
Chuck
KB7OGE

Been trying FT8 for a while now and posted questions on the 'digitalradio' forum but got no responses, so will try here:  

1) Running FT-8, when I double-click on a station calling CQ, WSJT-X frequently starts transmitting immediately instead of waiting for the next transmit window.  Is this normal?  Is it because there's still enough time left for a possible decode on the receiving side?  I also notice it often takes multiple answers to a CQ to get a response.

2) How much power are folks running.  I sometimes see a very large difference between sent/received signals, especially from stations working Europe.  A post on the Flex forum said some are running 100's of watts, up to the full 1500W at times!  

3) In the Message section, what is the ~U.S.A. and !Italy etc?  Are these DXCC entities and is there any documentation on the use of "~" and "!"?  I scanned the most User Guide including FT8 and didn't see it. 

Thanks,
Dick
KF5SA

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Richard Berry
Sent: Monday, August 14, 2017 9:43 AM
To: WSJTX@groups.io
Subject: [WSJTX] FT8 Questions #new #FT8

Been trying FT8 for a while now and posted questions on the 'digitalradio' forum but got no responses, so will try here:  

1) Running FT-8, when I double-click on a station calling CQ, WSJT-X frequently starts transmitting immediately instead of waiting for the next transmit window.  Is this normal?  Is it because there's still enough time left for a possible decode on the receiving side?  I also notice it often takes multiple answers to a CQ to get a response.  I have found the same thing.  This is probably due to the fact that FT-8 only is a 15 second cycle.  So, if you double click toward the end of the CQ-ing station's transmission, your station will appear to start transmitting immediately.  This would also answer the rest of your question, in that if your station doesn't get a chance to get a full return message out, the CQ-ing station wouldn't be able to decode it, hence he/she will send another CQ.

2) How much power are folks running.  I sometimes see a very large difference between sent/received signals, especially from stations working Europe.  A post on the Flex forum said some are running 100's of watts, up to the full 1500W at times!  With my station, I try to keep my output power to 30 watts for domestic (US) stations, but never exceeding 50 watts for DX stations.  Typically, when a station is transmitting using excessive power, it will tend to "desense" a good portion of the window, but there's not much we can do about that, I guess….

3) In the Message section, what is the ~U.S.A. and !Italy etc?  Are these DXCC entities and is there any documentation on the use of "~" and "!"?  I scanned the most User Guide including FT8 and didn't see it  These are DXCC entities, but I'm not sure what the other characters represent.

Thanks,
Dick
KF5SA

Laurie said he wasn't going to go in to details or even discuss this again.

There was some bad blood going on when HRD blocked JTAlert without warning.

A lot of people switched away from HRD for that and other reasons.  

Purportedly HRD has changed their ways (involving people getting replaced) but it's hard to repair a broken relationship.

de Mike W9MDB

---

From: Eddy van Keulen via Groups.Io <eddyvk@...>
To: WSJTX@groups.io
Sent: Monday, May 8, 2017 9:36 AM
Subject: Re: [WSJTX] QSO Relay Software - JTAlertX 2.9.x link to Ham Radio Deluxe 6.x Logbook #new

I am curious, do we know why the JTAlert people dropped this feature?  They must have had their reasons.

HRD is my master local LOG and the automatic logging of JTAlert to HRD is one of the reasons I use it. I am not sure if I want to run yet another layer of support for WSJT-X so I will probably stick with JTAlert 2.8.7 for a while.

Eddy, W6EDY

--------------------------------------------

On Thu, 5/4/17, Bruce VK2RT <bruce@...> wrote:

Subject: [WSJTX] QSO Relay Software - JTAlertX 2.9.x link to Ham Radio Deluxe 6.x Logbook #new

To: WSJTX@groups.io

Date: Thursday, May 4, 2017, 5:58 PM

Since support for Ham Radio

Deluxe (HRD) Logbook v6.x is no longer be available from

JTAlertX version 2.9.x., a group of amateurs who wanted to

maintain this link between the latest versions of JTAlertX

and HRD, decided to develop an application to achieve this

end. The software was designed and developed by Chris VK2BYI

who some of you may know, developed and designed FTRestore

for managing menus and memories for the FT-991, FT991A,

FTdx1200 and FTdx3000 radios. JTAlertX adds

significant functionality with audio and visual alerts for

WSJT-X (and JT65-HF etc) and now with QSO Relay we are able

to keep using the latest JTAlertX application (2.9+) in

conjunction with the latest Ham Radio Deluxe software

(6.4+).

QSO Relay is a Windows desktop application that runs

as a System Tray application that listens for contacts being

forwarded from WSJT-X and JTAlertX via the User Datagram

Protocol (UDP). As datagrams are received, they are logged

locally in a SQLite database and then relayed via

Transmission Control Protocol (TCP) to a Ham Radio Deluxe

Logbook v6.x database.

QSO Relay was developed as a proxy application that

interacts with JTAlertX the same way as one of the alternate

logging applications supported by JTAlertX – Log4OM. This

allows JTAlertX to verify that that QSO has been logged by

querying the SQLite database, before the contact is relayed

to the HRD Logbook database.

As confirmations of contacts are subsequently

received from various sources such as LoTW, eQSL.cc and QSL

Cards, the corresponding rows in the HRD Logbook database

are updated. QSO Relay has a feature whereby contact

confirmations in the HRD Logbook database can be made to the

QSO relay database as well. This synchronisation process is

requested by selecting a QSO Relay menu item.

This in turn should be followed by a ‘Scan Log and

Update…’ in JTAlertX to update its Wanted Alert

requirements.

Features

Runs as a minimised application with an icon in

the System Tray.Works with HRD Logbook v6.x with

full support for logbooks hosted on the following database

platforms:Microsoft Access (Standard Jet

Database *.mdb files);Microsoft SQL

Server;Oracle MySQL

Server.Synchronisation between the HRD Logbook

database and the QSO Relay database can be triggered when

desired to ensure updates are replicated back to QSO

Relay. 

I have been part of the testing team and have

been using this application for some time now with complete

success. I recommend this application to those who wish to

keep using the latest Ham Radio Deluxe with the latest

JTAlertX.The software is available at

http://www.vk2byi.com.au/qsorelay/.  As well as

downloading the software, please ensure that you download

and read the associated documentation.The following

link will take you to the VK2BYI-QSO Relay Forum where

support will be available:

https://groups.io/g/vk2byi-qsorelay/I recommend that

you join this Forum in order to keep up to date with any

software changes and maybe provide constructive feedback,

this will be the sole source for software update information

and software support.

ISSUEThere is currently an issue

with Windows Regional

Settings where a comma "," is being

used as the Mhz separator as shown in the WSJT-X/JTDX etc.

frequency window.Quick FIx - if

your Windows Regional

Setting is a comma "," change it

to is a dot "."A new release of QSO Relay will be

available shortly that fixes this issue.

DE BruceVK2RT