Date   
Re: TX audio problem and RX audio quality

Mark Weisheimer
 

Tom,

That sounds pretty frustrating.
I have a K3 using analog audio with the RigPi and you and I are having polar opposite experiences.
Mine sounds fine RX and TX and retains all of the settings through reboots.

There may be a reason for your bad audio, how old is your RigPi OS image?
RigPi and it's microSD cards shipped from MFJ after the first week in July have a newer and improved audio overlay implemented.
Older images can be easily updated and there is a document explaining that process in the files area of this forum.

https://groups.io/g/RigPi/files/RigPi%20Documentation/RigPiAudioTreeUpdate.pdf

Take a look at that and see if it helps.

I am hitting the rack now, but I can work with you tomorrow if you would like to discuss the basics of how I have configured it here.

--
73 - Mark - K8MHW
'A RigPi Enthusiast!' - I am not otherwise affiliated with MFJ or RigPi

Re: TX audio problem and RX audio quality

Howard Nurse, W6HN
 

Hi Tom,

One quirk of Mumble is that you have to click Apply, then OK, THEN restart Mumble to have the settings stick.  If you reboot without this last step, your settings will revert.

73, Howard W6HN

TX audio problem and RX audio quality

Thomas Tumino
 

After several weeks of my spare time being used up I am out of my mind here trying to get the MFJ-1234 to work, so first a few questions as I am not even sure the setup is supposed to be capable of what I thought it could do.

First, can it relay audio from my rig that I cannot distinguish from being in front of my rig at home?  Can it do this for an extended period?

Second, can it be re-booted remotely while retaining the same audio settings?


Setup is K3 connected by individual stereo cables from MFJ-1234 TX audio and RX audio jacks to mic and line out jacks on K3.  I am using a usb to serial cable for rig control.  I must run a ground wire between the rig and MFJ-1234 for even barely acceptable audio.

Sometimes I can get TX audio to go after reebooting and tweaking all sorts of settings again and again in alsamixer, the rigppi desktop and mumble server.  When I do get tx audio working, if for example I am running WSJT-x , the tx audio will work until I reboot.  Once re-booted it all goes to heck and then some combination of tweaking settings and unplugging and replugging the audio cables brings back my tx audio.  Typically this takes a few days to get the right combination.  Sometimes it is as easy as plugging earbuds into the tx audio jack, then unplugging them and then replugging them.  Earbuds are fine and audio cables are fine.   Why does my system go out of wack when rebooted?  What can I do to get it working permanently?  Why does replugging the cables change the audio settings in the rigpi?  This is not a rig problem as confirmed by the buds.  Also my pigremote has no such problems.

RX audio works pretty much all the time, but always in the same poor fashion.  I get a few seconds or sometimes minutes of what I expect, good quality audio as if I were at the rig, then it gets muffled and almost sounds like a speaker underwater or something.  I can cure this by going into tx on the rig for an instant.  The RX problem will just pop up again and again though.   The problem is most evident when listening to static.  I have tried every combination of mumble settings I can come up with and all recommended settings in the rigpi manual. The problem occurs when connected on the same network, to the same router as the MFJ-1234 and it happens remotely as well.  Is this the best I can hope for from an MFJ-1234?  Its a far cry from my old pigremote.

Thanks in advance.  I am going to throw in the towel after this despite how I feel so tantalizingly close to getting things to work reliably.

Tom, N2YTF 

Re: DB Error after my pi disk space filled up

Howard Nurse, W6HN
 

Hi Adam,

Do you have a backup of the RigPi image?  That would be the simplest way to recover.

It looks like the User database may be corrupt of missing.  Other problems could exist beyond that.  You can use phpmyadmin to take a look.

  1. Start PHPMyAdmin from the Raspberry Pi application menu in the Programming item.
  2. Use username root and password 7388.
  3. Click station in the list to the left to expand all databases.
  4. Do you see User?  Can you open it?
--Howard

Re: TS 2000 no PTT

Howard Nurse, W6HN
 

Hi Don,

Here are drawings showing the pin layouts:  https://groups.io/g/RigPi/files/RigPi%20Documentation/audiodipconnections.pdf

Yes, you will see the pin designations marked on the "top" (facing down) of the audio daughter jumper board.  PTT is pin 6.  Ground is pins 1, 2, and 3.



--Howard

Re: TX Keying delay

K7UL@...
 

Thank you Howard for the reply.  

My PTT off time is about a 7 Mississippi count currently.  Some times as short as 3, but not often.
I look forward to the update.

73-Andy

Re: Toggle the big PTT switch?

Janne Blomquist / SM5SUH
 

For some reason it seems that my answer from my mobile phone didn’t get trough but here is my answer regarding what happens if I 'choke'.

 

I guess that the deadman switch doing the job and kill the TX after the time I have set (6 minutes). If this should be a problem, why is there a TX/RX button already?

Jan  / SM5SUH

Re: TS 2000 no PTT

Don Domina
 

Howard,

By RigPi header jumper, you mean the jumper module that is on the small board that the audio cable plugs into?  According to the information I have on that jumper, PTT is on PIN 3 and Ground is on PIN 7, 8 or 9.  Please confirm this is correct and I will check it.

Thanks.

Cheers

Don KC0DE

Re: Toggle the big PTT switch?

Bo Barry <bobarr@...>
 

And if your PC chokes and leaves your rig on transmit forever. Or you 'choke'? 🤔

DB Error after my pi disk space filled up

Adam Hosa
 
Edited

Hi Folks,

So unknowingly my pi filled up with lots of wav files and my disk space hit its max. Once I cleaned out some space, when I went to login to my rigpi ui, after entering my creds, I'm getting the below message..it seem hozed. Any suggestions?




Thanks :)

Adam N1AH

Re: CW using a paddle

Duncan Fisken
 

Many thanks, Howard!! All clear now..

 

73,

Duncan, G3WZD

 

From: <RigPi@groups.io> on behalf of "Howard Nurse, W6HN" <hlnurse@...>
Reply to: "RigPi@groups.io" <RigPi@groups.io>
Date: Friday, 20 September 2019 at 02:03
To: "RigPi@groups.io" <RigPi@groups.io>
Subject: Re: [RigPi] CW using a paddle

 

Hi Duncan,

Yes, the CW Keyer board is the key (so to speak) for remote keying.  You can use a second RigPi, or purchase a RigPi Keyer Board separately to use with a Raspberry Pi (including the Zero).

--Howard

Re: TX Keying delay

Howard Nurse, W6HN
 

Hi Andy,

The longest the PTT OFF delay should be is under a second. The delay isn't caused by Internet dalay, but is caused mostly by polling in RigPi.  I'm working on improvements to the PTT software that will be in the next update.  The changes should provide better switching speed.

--Howard

Re: CW using a paddle

Howard Nurse, W6HN
 

Hi Duncan,

Yes, the CW Keyer board is the key (so to speak) for remote keying.  You can use a second RigPi, or purchase a RigPi Keyer Board separately to use with a Raspberry Pi (including the Zero).

--Howard

Re: Kenwood TS-480HX and RigPi

Howard Nurse, W6HN
 

Hi George,

I second Mark's welcome!  We'll look forward to updates as you proceed.

73, Howard W6HN

Re: TS 2000 no PTT

Howard Nurse, W6HN
 
Edited

Don, you can simply short the PTT line on the RigPi header jumper to ground to see if the PTT engages.

--Howard

Re: Mumble/Plumble connection for sound

Howard Nurse, W6HN
 

The Mumble server keeps track of usernames and their associated certificates.  Once the two are joined at the hip, but you are blocked, you can use a different username or sign in to Mumble on the Raspberry Pi as a Superuser where you can delete accounts.  Google Mumble superuser for details.

I just upgraded my 1.2.19 Mumble to 1.3 on a Windows computer with no issues.

73, Howard W6HN

Re: Mumble/Plumble connection for sound

Mark Weisheimer
 

It works for me on Mac, Linux and PC but I HAVE had certificate issues in the past.
It seems to me that once a certificate is done incorrectly, I can never get that username to work again.
So, what I do is to use a new username to log in from THAT client. It can be any username other than one already used and the password is always 7388
Then, when I make the first connection, I accept whatever it says about the certificate and log in anyway.
It seems to cache the certificate (or the fact that it is no good) and I have not yet figured out how to fix a failure other than using a new username.
I have also removed Mumble and re-installed it to get going in the past.

--
73 - Mark - K8MHW
'A RigPi Enthusiast!' - I am not otherwise affiliated with MFJ or RigPi

Re: Mumble/Plumble connection for sound

Hal
 

Frank,

I tried that also go the same result.  It seems to be a certificate issue and I'm sure how to solve this issue.  Can't get Mumble on Windows or Plumble on my android phone to work.

Hal
KG5LVG

Re: Mumble/Plumble connection for sound

kg9hfrank@gmail.com <kg9hfrank@...>
 

Yeah I ran into that as well.

I am a MAC guy and though it was only MAC folks that had that issue.

But.. after three days and a few (too many) hours, I deleted it and installed the older one.

All good now with 1.2.19

-73-  Frank    KG9H




On Sep 19, 2019, at 5:50 PM, Hal <hkey073@...> wrote:

Thank you for the reply.  I viewed the video and it is helpful.  However, I noticed that the Windows Mumble Client in the video is 1.2.19.  When I went to the Mumble website, the only Mumble Client is 1.3.0.  When I go into the Mumble Server Connect page to setup a server, it does not have a password window.  I fill in the other windows with the same information (Label, Address, Port, Username) in the Mumble Serve on the RigPi.  I then attempt to connect that server.  I get back it is connected but the certificate or password is wrong with a window.  I type in the password that is on the RigPi Mumble Server and still get the same error.

Hal
KG5LVG

Re: Mumble/Plumble connection for sound

Hal
 

Thank you for the reply.  I viewed the video and it is helpful.  However, I noticed that the Windows Mumble Client in the video is 1.2.19.  When I went to the Mumble website, the only Mumble Client is 1.3.0.  When I go into the Mumble Server Connect page to setup a server, it does not have a password window.  I fill in the other windows with the same information (Label, Address, Port, Username) in the Mumble Serve on the RigPi.  I then attempt to connect that server.  I get back it is connected but the certificate or password is wrong with a window.  I type in the password that is on the RigPi Mumble Server and still get the same error.

Hal
KG5LVG