Bill and Karza -- you are great!  Got added to the dialout group (what a secret!), upgraded something from 18.10 from 18.04, selected the correct port (pure trial and error, mostly error), then played with levels, and presto (as if it was actually easy, which it is not, but we move on..haha!).  In the screen cap below, you will notice a complete QSO!  That means that the entire value change (I love that business talk) was integrated and operational functional. Meaning the while thing...ubitx radio, antenna, ubuntu, sound dongle, rig control, atomicPi, usb hub, mouse, keyboard, wifi, all worked as one...I feel like my head is going to explode from all the new stuff ubuntu (is that how you spell it? haha) I've had to jam into my bean. But here we are. 

true story: I had to lookup how to log out.  I just wanted to confess that and get it off my chest. hahah

Thank you!!!!

Now flush with this success...I'm moving on to getting Fldigi working for the rest of the digital modes..Can I ask you guys questions on Fldigi, or should I find another group? Now that sounds weird...but you know what I mean...

The Odroid X4U (2 GB RAM / 8 cores) is faster than the Raspberry Pi.  The eMMC board option makes it even faster.  

I have both.  I also have an Awow windows 10 tiny PC that fits in the palm of my hand.  I ran my station with it for about 1 month just for the fun of it.  It is more expensive than the Odroid or the Pi.

73.
Carl - WC4H

Hello Kari!  I did the following (trying to flow your guidnace).

I was holding off 2.0.1 but I guess I should take the jump. AFAIK it happened just once for me. Not as active as I’d like to be. Life got in the way these last few months, hihi.

Thanks
Mike
G7TWC

thanks for all the suggestions everyone, much appreciated!

On 30/05/2019 18:52, Mike Ruttenberg G7TWC wrote:

TLDR: this is not just you seeing this.

Mike
G7TWC

Mike,

that is correct for those who have not upgraded from WSJT-X v2.0.0 to the currently supported GA version v2.0.1.

73
Bill
G4WJS.

On 30/05/2019 05:52, Dennis Vandeveer wrote:

Hello all. A new guy to the group but not to WSJT-X I have the latest updates for WSJT-X, JT-Alert and ACLog. All was working well until during a FT8 QSO with K6ZH reported he was not WW8Q. I have never contacted WW8Q but that's what he was seeing. On my end all looked fine and I never saw WW8Q the whole time. Very strange and thought I'd better report it.
73-Dennis
DU3/KB7DV

HI Dennis,

WW8Q is probably running an out of date WSJT-X version. There were several defects related to decoding hashed non-standard calls that were fixed in the v2.0.1 release. If he is running v2.0.0 then he need to upgrade.

73
Bill
G4WJS.

Sounds like a hash mixup. I once had a QSO where I saw something different on screen to what a friend watching my QSO saw at his QTH. I was waiting for RR73. I got RR73 from someone completely different but my friend saw it as my callsign and their callsign RR73. All timestamps were correct and his screenshot was the only way I know it had been completed. Lucky for me I guess but something definitely wasn’t right there.

TLDR: this is not just you seeing this.

Mike
G7TWC

Hello all. A new guy to the group but not to WSJT-X I have the latest updates for WSJT-X, JT-Alert and ACLog. All was working well until during a FT8 QSO with K6ZH reported he was not WW8Q. I have never contacted WW8Q but that's what he was seeing. On my end all looked fine and I never saw WW8Q the whole time. Very strange and thought I'd better report it.
73-Dennis
DU3/KB7DV

Raspberry pi works fine. Jack freq to 1000MHz.
--
Bo W4GHV - since '54

Skip XP. Skip the $99 RCA Windows laptop.

--
Bo W4GHV - since '54

Hello!  Trying to get WSJTX cat control working with my uBITX radio on my new AtomicPi (like a RaspberryPi but not as friendly, haha.). 

The audio from the uBITX via a sound card dongle via a USB hub into the AtomicPi to WSJT-X works great.  I get decodes!!  So audio input/decodes/etc. is all good there.

The issue is cat control for TX and freq changing, etc.   I've tried very option, of five, in the Serial Port dropdown. None of them enabled  cat control. The error is the std msg


The same uBITX radio works GREAT under WSJTX/Fldigi/etc. cat control on my win10 laptop using the trusted Yaesu FT-817 Rig setting.  I just copied the other parameters for baud, bits, etc. from the Win10 to the Ubunto.  But still no love.  See screen cap below.

Hi Don,

I suspect you are not selecting the correct serial port device for CAT in WSJT-X. Your screen capture shows "USB", that is definitely incorrect. I would guess that /dev/ttyUSB0 is the right one, that would be a USB to serial interface.

You also need to add your user to the 'dialout' group to be able to access serial devices:

sudo adduser $USER dialout

You must log out your desktop session and log back in for that to take effect, or simply reboot.

73
Bill
G4WJS.

Adam,

I used a Dell 9360, KX3 and JTDX.  The software has a better layout to be used on a laptop.

Pictures and details can be found here: http://bit.do/8Q7WK-2018 (click on the picture for full size)

73's de OE1MWW

Hi Don,

On 05/30/2019 04:40 AM, Don - KM4UDX wrote:

Hello! Trying to get WSJTX cat control working with my uBITX radio on my new AtomicPi (like a RaspberryPi but not as friendly, haha.).

...

Make sure your user-id is a member of the 'dialout' group.

To check:

* open terminal
* type command "id | grep dialout" ( without the quotemarks )
This command should return a string with groupnumbers and -names
one of which is 'dialout'.

If nothing is returned by the command then you need to add your username
to the 'dialout' group with command "sudo usermod -aG dialout km4udx".
Then log out and log in again ( or even reboot if you are used to do things like in Windows ;).

HTH & 73 de Kari oh2gqc

Hello!  Trying to get WSJTX cat control working with my uBITX radio on my new AtomicPi (like a RaspberryPi but not as friendly, haha.). 

The audio from the uBITX via a sound card dongle via a USB hub into the AtomicPi to WSJT-X works great.  I get decodes!!  So audio input/decodes/etc. is all good there.

The issue is cat control for TX and freq changing, etc.   I've tried very option, of five, in the Serial Port dropdown. None of them enabled  cat control. The error is the std msg


The same uBITX radio works GREAT under WSJTX/Fldigi/etc. cat control on my win10 laptop using the trusted Yaesu FT-817 Rig setting.  I just copied the other parameters for baud, bits, etc. from the Win10 to the Ubunto.  But still no love.  See screen cap below.

I'm sure the problem is I don't know anything about linux/ubuntu. Like zero.  I'm thrilled that I got ubuntu up and working on the AtomicPi, and the ubunto desktop is great. (yes, this is my FIRST non-windows experience..hahah)  All on a $38 little board computer. But anyway, the ubuntu seems to run just fine on the board. But, while wsjt-x hears the uBITX USB audio just fine, it will not control and do the TX thing. ..so...help!   I'm sure I've done something simple and stupid (my specialty, haha).

WSJTX version 2.0.1

--

On 29/05/2019 22:40, vbifyz wrote:

My observations about different mobile CPUs decoding FT8:
Raspberry Pi 3+ is not fast enough for QSO. OK for SWL on a moderately busy band. Choke on a very busy band - skip entire decoding cycles because the previous cycle decoding hasn't finished in 15s.
Cheap tablets/laptops based on Atom Z3735F - good for SWL, can keep up with 1 or even 2 busy bands. Especially when using JTDX software, because it efficiently utilizes all 4 cores. Barely OK for QSO on a moderately busy band.
Cheap laptops based on N3050/N3060 or newer low-end Celeron CPU - usable for QSO, great for SWL on multiple bands.. Acer Cloudbook, HP Stream, many Chromebooks use these CPUs.
For real fast paced QSO, i5 or equivalent AMD CPU is needed. Older generations (2nd and 3rd, like i5-2350M) have comparable speed, but consume more power than newer ones (5th gen and newer).
JTDX multi-threaded decoding gives a definite advantage when using cheaper slower CPUs.

73, Mike AF7KR

Hi Mike,

you do not state what decoding depth you used for the timing you quote.

73
Bill
G4WJS.

My observations about different mobile CPUs decoding FT8:
Raspberry Pi 3+ is not fast enough for QSO. OK for SWL on a moderately busy band. Choke on a very busy band - skip entire decoding cycles because the previous cycle decoding hasn't finished in 15s.
Cheap tablets/laptops based on Atom Z3735F - good for SWL, can keep up with 1 or even 2 busy bands. Especially when using JTDX software, because it efficiently utilizes all 4 cores. Barely OK for QSO on a moderately busy band.
Cheap laptops based on N3050/N3060 or newer low-end Celeron CPU - usable for QSO, great for SWL on multiple bands.. Acer Cloudbook, HP Stream, many Chromebooks use these CPUs.
For real fast paced QSO, i5 or equivalent AMD CPU is needed. Older generations (2nd and 3rd, like i5-2350M) have comparable speed, but consume more power than newer ones (5th gen and newer).
JTDX multi-threaded decoding gives a definite advantage when using cheaper slower CPUs.

73, Mike AF7KR

Bill,

Thanks for the details.  Clearly, I'm in over my head, so will give up on this!  ;)  I'm not a programmer...  Hopefully someone who is capable can use the information you gave to write a Linux application to pull the data from gpsd and make the grid square available to WSJTX.  I use a ruby script to do this with JS8call, and thought I could do the same with WSJTX due to the similarity, but apparently there is a difference in the port I/O.

73,
-Joe-
K0OG