Version 2.3.0

A couple weeks ago I had freq control over the FT450 .. as in, if I selected FT-8 then my FT450 switched to 50.313

dunno what went wrong since I usewd that rig last.

But now the only program that I can get to actually change the frequency on the FT450 is their own PCC_450 GUI.

Wsjtx barfs with a HamLib error as seen in the screenshot.

I can't get DXLab's 'Commander' to change freq on the FT450 either.
Switch modes or TX/RX I can do via WSJTx or others.

So what's the HamLib error mean? (see screenshot)

many thanks ...
BOB KD7YZ

[Edited Message Follows]

OK let me clarify. Since I am almost color blind, I never cared much for JTALERT since I find it useless (I can't detect the colors....).

Yes I have recently added GridTracker but I am not yet very familiar with it. I need to investigate more. You might be correct Carl and I will find out. This might just be the answer to my problem.

When using JTDX I always play a short bursty sound lasting about 100msec to warn me someone is either calling me if I am not watching the screen. Sometimes stations call you after 2 or 3 minutes. This short wav file is also played anyone is using my callsign. Yes during a QSO as well. I have edited that nice bursty sound using Acoustica and it is really nice and catchy.

You also have the choice of playing that wav file on any decoded activity. This is really usefull when a band is closed or you are waiting for a band to open, waiting for a sporadic E event or some other tropo/meteor scatter occurence. There are no stations there and you spend endless minutes/hours "scope-watching a boring screen" until someone shows up. In JTDX, just leave it "listening for a band opening" and then you hear the secret wav file that catches your attention while you are cooking in the kitchen. This is really a usefull idea someone has coded JTDX. It is a menu choice.

Yes I know third party can do this maybe but it just thought the WSJT team had only one copy-paste operation to do ("stealing the code") from open source JTDX. That was only a suggestion box idea.

Richard,

Are you using an IC-7300 and ubuntu 20.04 I am here also if so

If I power off the radio only nothing happens but if I power off the power supply for the radio the rig's UB audio port drops from the ububntu repertoire and it auto switches audio assignments. When I power it back on (ie the PS only) the USB audio is detected on ubuntu and it recinfigures sound assigments again. What I found was had to get coomand off google search to enter in terminal to stop the autoconfiguring of USB audio devices then use the pavu volume control to configure devices inputs/outputs/recording /playback etc to what was needed  manually.

Then start WSJT-X  JTDX and FLDigi and tweek them all to get the right combination to work properly for each of the programs and then it seemed to stabilize. the spec you showed alsa-input and alsa-output is correct one I use for wsjtx and jtdx but if I recall correctly it is different on FLDigi. I had to enable realtime kernel and run jack audio connection kit app to get the flexibility to find the correct ones. Now it is set and all three programs come up OK with jack audio being needed.

Hope this helps

73 Gud Dx Andy ve4per

On 2021-02-18 4:44 p.m., Pa3gcu wrote:

Hello all, and Bill.

Bill, i have finally got the microkeyer 3 working with ubuntu but not with 20.04, i installed 18.04

on another computer installed everything in the same way as on 20.04. Installed wsjtx 2.2.2 (had depenency problems but they were easy to solve).

Now the funny thing was when i started wsjtx and configured the rig etc, went to the audio tab and found the devices were there automaticly defined as:

alsa_input.usb-microHAM_MKIII_xxxxxxxxxxxxxxxxxxxxxxxxx.mono-fallback

alsa_output.usb-microHAM_MKIII_xxxxxxxxxxxxxxxxxxxxxxxxx.analog-sterio

the xx was a combination of letters and numbers.

Now after a reboot wsjtx did not work properly, rig control was ok but sound errors came up, when i opened the audio tab there was a complete different set of devices which did not work.

After some experimenting with different devices i found that the following worked;

plughw:CARD=MKIII,DEV=1

plughw:CARD=MKIII,DEV=0

There were 30 devices to choose from.

I only hope it keeps working after the next reboot:-)

If anyone can explane why the first set of devices dissapiered after a reboot i would be interested

to hear what he or she has to say.

Anyway it works, i wonder how many mkIII's there are out there running on linux.

Again thanks to all who helpt especially Bill.

73 Richard PA3GCU.