Date   
Re: Dummy Not Disconnecting

Frank Wroblewski
 

Howard,

Thanks for your help.  I wasn't clicking the cloud.  I didn't know about clicking the cloud, but that;s no one's fault but my own as I see that info is published in the manual and I missed reading it.  Everything working fine now, thanks for the great product and the phenomenal support your provide.

Frank

Re: mumble server

Howard Nurse, W6HN
 

Hi Robert,

Here are some things to check.

1. Check that the audio settings are correct on the Raspberry Pi desktop by right-clicking the Speaker icon.
2. Check that the audio settings are correct in Mumble>Configure>Settings>Audio In and Audio Out.
3. Are the lips red for the Pi user and your phone user?
4. If not, make sure Mumble in both places is set to Transmission>Continuous.
5. In Mumble on the RPi desktop, go to Configure>Settings>Audio in and temporarily change Transmission to Audio Level, then click Applu.
6.  Dose the bar graph bounce around showing radio noise?

—Howard

Re: Dummy Not Disconnecting

Howard Nurse, W6HN
 

Hi Frank,

After entering the correct data for your radio, try clicking the Cloud icon at the top to save the settings.  Then when you try Test Radio, does it continue to connect to the Dummy radio?

—Howard

Re: How to program or even look at macros

Howard Nurse, W6HN
 

Hi Ken,

You should be able to tap a box in the Macro settings window to set the focus, then use arrow keys/type to change the contents.

—Howard

Re: Yaesu vx-8dr

Howard Nurse, W6HN
 

Hi James,

Welcome to the RigPi forum!

It is possible to use a VX-8dr in a limited way.  The radio does not have the ability to change frequency, etc, via CAT commands.  For single channel operation, you can use the Hamlib Dummy radio with hardware PTT.  Audio in/out and PTT are available on the radio through the Packet connector on the top.  You can use Mumble for audio via those connections.  Enable the Keyer for use with the Dummy radio so you will get PTT switching via the Keyer PTT connector.

73, Howard W6HN

Re: IC-706MIIG SETUP

Andy
 

Hi Dennis, 
Agreed on the CI-V port needs to be correct on RPORT. 
Your next challenge will be transmit control. If you have a solution please pass it on. 
Unless something has changed, using the PTT from the GPI/O 17 was found to be unstable
on my system, If you can get it to transmit, it is hard to get it back to RX. In most cases, you cannot 
rely on the PTT button red (TX) status because that is set by a command status read from the IC706mk2 which 
is not supported by the radio. if you have your manual, check the CIV command set you won't find a TX command or TX status READ command.  Be careful and use a dummy load, it could get stuck in TX. I have a post somewhere on the group discussing the above from sometime ago. 

If you want to use WJST, it works very well. You can modify the jumper board supplied with the cable assembly, 
and use a USB to RS232 serial converter cable. You will need a RS-232 connector or cut a cable to pick out 
the DTR signal on pin 4, pin 5 for ground.  DTR can be used by WSJT and FLDigi for TX control. Use a 2n222, 2n3904, general purpose transistor to pull down the PTT (actually the radio's HSEND) going to the radio, a resistor and diode are in there as well. 
Attached is a marked up schematic of the mod that I did to make it work. You will be taking the RigPi's GPIO17
PTT out of the path. 
From the old days, there was a CIV to RS232 Poor Man's converter using a couple of transistors.This might just be the method to provide the CIV command AND TX control using the RS232 DTR converter interface. I might try it out sometime.
 
The radio can be used with mumble, I am listening to the radio now, but no TX just yet. 

Rig Pi works with the RigPi CW Keyer, you just need to configure the Rig Pi Keyer as shown in the attachment 
and use a cable from the "KEY" jack in the rig pi to your 1/4" Key Jack on your 706. Just use the Tips and Shields on both. Of course, now your TX line is the Key Line. 

It took some time to get the kinks worked out and seems to be working and stable on my station, please use the information carefully and at your own risk. If anyone finds anything to enhance or correct please pass it along 

Have Fun 73 
Andy


 

Yaesu vx-8dr

jamesd.payne.forum@...
 

Is it possible to setup a Yaesu vx-8dr with the rigpi?

If yes, where do I start?

Dummy Not Disconnecting

Frank Wroblewski
 

My RigPi used to work with my Icom IC-7000, but has not stopped working.  I put all the correct values in the Advanced Settings, select CONNECT and get the result listed below.  Rebooting, updating, upgrading all had no effect.  Strangely enough, I have no problem getting FLRig to work.  WSJT-X also works, but without CAT displaying the proper frequency.  If I go to terminal mode and put in the rigctl commands, it tells me I have a communication bus error.  Any ideas anyone???
73,
Frank W2XYZ
TEST MODE Radio: 1
User: admin
Radio: 1
User: admin
Radio from settings: 1
Port from settings: None
ID from settings: 1
RigDo.php rigDoPID from settings: 4681
service_port: 4532
Hamlib Dummy radio 1 start attempt.
To see any error details, click Disconnect Radio, then start rigctld in Terminal with this line:

rigctld -m 1 -t 4532 > /dev/null 2>&1 &

rigctld processes running:

www-data 3689 0.0 0.2 5200 2364 ? S 22:34 0:00 rigctld -m 1 -t 4532

Now starting RigPi radio control link.
Congratulations, Dummy is connected!

Main frequency is 145.000.000 mHz

RigDo Processes:

www-data 3695 21.0 2.2 69616 21000 ? S 22:34 0:00 php /var/www/html/RigDo.php admin radio1 4532

RigDoPID: 3695; Radio: 1; User: admin; Keyer: rpk; CW Port: /dev/ttyS0

Now starting RigPi CW control link.
Now starting RigPi TCP remote control link on port 30001.
Now starting RigPi UDP server on port 12060.
Now starting RigPi Rotor control link on port 4533.

Now starting RigPi Rotor control link on port 4533.

Rotor: 1 (Dummy)
Rotor port: 4533
Rotor ID 1 (Dummy) start attempt.
To see any error details, click Disconnect Radio, then start rotctld in Terminal with this line:

rotctld -m 1 -T 127.0.0.1 -t 4533 > /dev/null 2>&1 &

rotctld processes running:

www-data 3707 0.0 0.2 5164 2372 ? S 22:34 0:00 rotctld -m 1 -T 127.0.0.1 -t 4533

Re: How to program or even look at macros

Kenneth A Christiansen
 

I have been in the macro window several times but can’t figure out how to change them. 
Ken W0CZ


On Mar 30, 2020, at 8:49 PM, Howard Nurse, W6HN <hlnurse@...> wrote:

way to backup and restore macros.

73, Howard W6HN
_._,_._,_

Groups

Re: How to program or even look at macros

Howard Nurse, W6HN
 

Hi Ken,

Welcome to the forum!

The Macro window in SETTINGS is currently the only way to edit and add macros.  RigPi 2, currently in Beta, has a new feature that provides a way to backup and restore macros.

73, Howard W6HN

How to program or even look at macros

Kenneth A Christiansen
 

I got my 1234 last Wednesday and have made a lot of progress so far. I may be back for other advice but for now I would like to figure out how to look at the macros and make changes or new ones. I have been doing programing for over 30 years so what I am asking is how to get to some type of editor to make the changes.

 

Thank you and I am looking forward to operating my ham radio when I am away from home camping.

 

Ken W0CZ

 

Sent from Mail for Windows 10

 

Re: LXDE-pi/run.log question (audio pop reason found)

tmeys@...
 
Edited

Hi Howard -

Running 1.3.0 on clients.  Same on RigPi (Buster) since you need to be at that level for updated Mumble.  To be very exact, the RigPi version is 1.3.0~git20190125.440b173+dfsg-2 on Buster.  A recent check for updates (a few days ago) indicated it was current on the Buster version.  (But as I mention, same issue using Stretch with 1.3.0 clients, and earlier versions of Mumble on RigPi because Stretch does not support 1.3.0.).

For those interested, I found this after I suspected the problem had to do with I/O contention on the microSD.  Used dstat to analyze what I/O was coming from where, which led me to this.  The dstat package was not installed by default, so that was a package I had to install.  

Hope this helps others if they have been seeing this problem.  I suspect if the RigPi was left running for a long period of time, this log file might fill the disk.  It gets deleted and restarted with a reboot, so that might be a lesser problem.  

'73 -- AE0AU

Re: mumble server

robert sherman
 

I mean i can log in with 7388 but no signal on my cell phone like before. No audio on receive & no transmit

mumble server

robert sherman
 

all of a sudden i am unable to log into remote mumble server. it keeps saying my server password is incorrect. I tried all i know & still cannot log in remotely. Any ideas?
--
Robert W Sherman

Re: WinKey access via external program

Howard Nurse, W6HN
 

Hi Randy,

Thanks for your nice comments about RigPi!

The new remote CW feature requires the addition of two simple jumpers in the CW boards.

Yes, RigPi 2 will be a field upgrade.   That's one of several items that has slowed down release.  The other is the current state of the Hamlib library.  The Hamlib folks have been hard at work creating a major update for the rig control libraries and I'd like to have their released version before we make RigPi 2 available.  Once these two issue are resolved we will be close to a release.

The extra time has allowed me to add some additional nifty features, including support for the Flic remote control switch for PTT.

--Howard

Re: LXDE-pi/run.log question (audio pop reason found)

Howard Nurse, W6HN
 

Good sleuthing!

Googling the error seems to point to Mumble.  In the RigPi 2 Beta I built Mumble 3.0 and do not see the error (although there are other questionable errors in that log file).  Here is one thread that seems applicable (somewhat dated):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862218

What version of Mumble are you using?

LXDE-pi/run.log question (audio pop reason found)

tmeys@...
 

Ever since I originally installed my RigPi it has had an annoying audio pop, sometimes accompanied by garbled audio before the pop.  This happens every few minutes.  Using a higher quality microSD helped, but never removed the problem. Problem only happens when RSS software is running with a user logged in. 

I have finally found that the source of this is a lot of IO to /home/pi/.cache/lxsession/LXDE-pi/run.log.  Going back to my original microSD that came with the RigPi, the problem exists from day one.  (When the RSS software started up with this constant logging, the microSD was periodically getting IO bound, slowing IO, and causing the "pop".  This is not an RSS software problem, but adding its IO load brings the problem out.)

The workaround is to redirect this error/warning log file to /dev/null to stop writing constantly to the microSD.  If you have need to see that logging, you have to remove the redirection.

The root of the problem seems to be that, after the following is logged to run.log:
ALSAAudioOutput: Initialized 1 channel, 48000 hz mixer
Warning: The VAD has been replaced by a hack pending a complete rewrite

There is constant logging of huge numbers of the following:
warning: Unknown speex_preprocess_ctl request:  2
warning: Unknown speex_preprocess_ctl request:  46
warning: Unknown speex_preprocess_ctl request:  30
..... continues constantly like this.

Questions:
- Do others see that the /home/pi/.cache/lxsession/LXDE-pi/run.log file keeps getting written to and growing on your RigPi?
- What is the "Unknown speex_preprocess_ctl" error about?  The best fix would be to find why the warning is being written.  With this warning, I see no audio or functionality problems (except for the excessive error logging).

By the way, using an FT-991 connected to RigPi using just the USB cable.  Also, I see this problem in both "stretch" and when I use a microSD that has been upgraded to "buster".

Re: WinKey access via external program

Randy Becnel
 

Thanks for quick reply Howard.. So will RigPi 2 be a field upgrade? Will any additional/new H/W be required for the upgrade or firmware/OS only? Is there  a timeline for release? And I realize I’m already utilizing Beta S/W with RigPi Hub but I hope I’ve inspired you to explore your final note on possibly adding CW keying in the future. As I was looking at the Hub dashboard I was saying to myself.. “hmmm, a CW checkbox next to that CAT box on the port configs would be nice…”, HI, HI. Since K1EL WinKeyer already exists in the RigPi and logging programs like N1MM already know how to talk to it, seems like it shouldn’t be a huge mountain to climb.

 

RigPi is everything I expected it would be as I read the info about it before buying and I see much more potential. So I will be anxiously awaiting V2, and beyond!!

 

Finally, TNX for your work with RigPi… it’s a great addition to the hobby’s remote capability.

 

73, Randy – W5UE

 

From: RigPi@groups.io [mailto:RigPi@groups.io] On Behalf Of Howard Nurse, W6HN
Sent: Sunday, March 29, 2020 12:55 PM
To: RigPi@groups.io
Subject: Re: [RigPi] WinKey access via external program

 

Hi Randy,

Looks like you are making great progress getting everything going!

RigPi Hub does not support remote CW keying, but that’s an interesting point.  RigPi 2 (in Beta) supports remote CW keying.  At the remote end you need at least a Raspberry Pi 0.  The RPi can accept keying from a RigPi Keyer board, or from an external keyer.  It seems like you should be able to use the N1MM keyer with the RPi 0 to accomplish what you want.  It might even be possible for RigPi Hub to be enhanced with a CW keying feature, so you wouldn’t need the RPi 0.

With the current RigPi, the only way to send CW is through the browser you use to access RigPi.

—Howard

Re: WinKey access via external program

Howard Nurse, W6HN
 

Hi Randy,

Looks like you are making great progress getting everything going!

RigPi Hub does not support remote CW keying, but that’s an interesting point.  RigPi 2 (in Beta) supports remote CW keying.  At the remote end you need at least a Raspberry Pi 0.  The RPi can accept keying from a RigPi Keyer board, or from an external keyer.  It seems like you should be able to use the N1MM keyer with the RPi 0 to accomplish what you want.  It might even be possible for RigPi Hub to be enhanced with a CW keying feature, so you wouldn’t need the RPi 0.

With the current RigPi, the only way to send CW is through the browser you use to access RigPi.

—Howard

WinKey access via external program

Randy Becnel
 

Hi,
I've only had my RigPi about a week now and enjoying it so far. Initial
setup controlling my K3 was easy and quick. Had no issues getting
Mumble/Pumble clients working on Windows and Chromebook and can control my
K3 from either a Win10 PC or my Chromebook via web browser. Now I've started
trying to interface N1MM Logger running on a Win10 PC using RigPi Hub. I
setup the COM port in RigPi Hub for radio communication and configured that
port as the rig port in N1MM+. Basic radio control works fine, band/mode,
etc with N1MM+. My question is whether it is possible to access the RigPi
WinKeyer using RigPi Hub or other method? Or a more basic question... what
is the recommended method for CW keying from an external program on remote
PC with the RigPi? I tried embedding the N1MM+ "CATA1ASC KY..." macros in
the CW function key files and using the CAT port to send. That "sorta" works
but keying is not smooth and N1MM+ team strongly recommends against this
method anyway... I will appreciate any guidance.

TNX/73, Randy - W5UE