Date   
Re: TS 2000 no PTT

Mark Weisheimer
 

Don,
 
When you ground the PTT line with a jumper, the TS-2000 would be expected to go into transmit and turn it's LED red, but the RED keying light in the RigPi will not illuminate.
 
So CAT PTT is working, albeit sluggishly, which you proved by removing the audio cable and then operating PTT on the RigPi.
 
One part that is puzzling is that the TS2000 phantom keys when you plug the audio cable back in and won't quit unless you power the TS2000 off and then on.
Yet it will not go into transmit when you ground the PTT line.
I am wondering if the TS2000 has VOX enabled for the data port and that is where the transmit is coming from.
 
I think you have already said this, but please enlighten me again, the radio will not go into transmit mode when the audio cable is plugged in.

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

Re: TX audio problem and RX audio quality

Thomas Tumino
 

I have discovered yet another frustrating issue.

Although the RigPi manual explains the need for, and gives basic guidance for setting up port forwarding, it makes no mention of the fact that the port forwarding will only work temporarily until your RigPi gets itself a new IP from your router UNLESS you perform a software mod on the RigPi to get it to keep a specific IP.

So now I have found references to a thread somewhere here that details the mod to the RigPi's software to get it to stick to an internal network IP, but I can't find a good step by step guide.  Guides found online don't match what I find when I start editing the dhccpd.

So I have two requests. 
-Can someone post step by step directions here on getting the RigPi to keep to an IP number once assigned by the router and marked by the router to be static.
-Can someone edit the RigPi manual to explain that port forwarding will only work temporarily for you unless you get your router and RigPi to cooperate on keeping a single, static IP on the internal network

It would also be great if the RigPi software simply was designed by default to keep an IP once assigned unless specifically reset. This would seem to be what the default should be-not the other way around.

Thanks again,
Tom

Re: TS 2000 no PTT

Don Domina
 

Mark,

Thanks for responding so quickly.  First, I want to say that Howard and others on this forum have been great in helping me troubleshoot this installation.  I addressed my note to Howard because I was responding to his comments.   I know how hard he is working on all RSS issues.

To your points:  I have verified the jumper is "notch to notch".  I tried it the other way as well.  With the TS2000, the jumpers are symmetrical so the position does not really matter.  All "wires" cross directly across the jumper to the corresponding socket.  In other words, pin 1 goes directly across to the first socket, as does Pin 2 and Pin 3.  Pins 4 and 5 are not connected and Pins 6, 7 and 8 are also wired directly across to their corresponding socket.  As you can see, the pattern is symmetrical so it should work in either direction.  Again, it is installed notch to notch.  The pattern is the same as the pattern I use in a Signalink that works fine with the TS2000.  That pattern was verified to me in an earlier post in this chain.  The jumper block is a Signalink "hard wired" block specifically for the TS2000.   I did not get a new jumper block with the MFJ cable.

I understand the methods of "keying".  I am going by my Signalink installation which I think uses the "grounding" technique to key the TS2000.

My comment regarding the RSS "keying' is in error.  I should have said the TS2000.  I was referring to the RSS "keying the TS2000" but I understand how that might be misunderstood.  The TS2000 has a GREEN receive light and a RED transmit light.  Even though the RSS (software and RED light on the RSS) show PTT, the TS2000 remains in the GREEN receive mode.  I have assumed that with the "grounding test" if it is successful the RED PTT light on the RSS would also illuminate.  Is that correct?

With regards to the cable keying the RSS:  In one of the troubleshooting notes, I think it was Howard that asked me to start the RSS and pull the "Audio" cable.  I was then asked to test PTT on the screen and with the space bar.  In that mode, the TS2000 would change from GREEN receive to RED transmit.  It was very sluggish and not particularly responsive to either the GUI PTT or the spacebar.  At the end of that test, I reinserted the "Audio" cable.  At that point, the TS2000 went into RED transmit mode.  It would not release.  If I pulled the "audio" cable it would release, but as soon as I reinserted it, the radio when into RED transmit mode.  The only way to reset the condition was to power off the radio.  When the radio was powered back on with the "audio" cable installed, it would be in the GREEN receive mode and would behave as noted earlier.

I hope this clarifies what I said in the earlier notes.  Thanks for taking time to give me your perspective.  I have found it helpful to go through the various steps in my mind and in writing to make sure I am not missing anything.

Cheers

Don KC0DE

Re: TS 2000 no PTT

Mark Weisheimer
 

Hi Don,

Howard might be online in a bit (he is on Pacific time) but I'll offer a couple of thoughts.

First, the SignaLink jumper block needs to be inserted with it's notch opposite the notch of the 16 pin socket in the RigPi.
That may be why you do not get keying when you short the PTT line to ground.
Either reverse the SignaLink jumper block or install the one that came with the new cable and try again.
The RSS should not key when you short that PTT to ground, the TS2000 should be the only thing that is keyed.

Howard is hard at work on the code to improve the PTT function and it should fix up the sluggishness you are experiencing.

There are multiple ways to "key" a radio with the RigPi.
1. Via the serial CAT port.
2. Grounding the PTT line (via the 13 pin DIN and its interface cable on your TS2000)
3. Grounding the CW key line and this requires that a cable be connected from the 1/8" Key jack of the RigPi to the radios CW key port.

I am just a tad confused about the phantom keying that you describe.
You say that the RSS keys when you install the audio cable, do you see the red keying light on the RSS turn on when that happens?
Does the TS2000 key too?
And turning the TS2000 off, then on will release it?

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

Re: Kenwood TS-480HX and RigPi

George Miller W3GWM
 

That’s good to know. I haven’t tried to connect it yet, but I’ll watch for that.


--
George W3GWM

Re: Rigpi ptt led stop lighting up. Kenwood TS 590s

Loic SM5VFE
 
Edited

Kenwood TS 590s working very well now with RigPi. 
For me was to change some audio settings in Mumble both on remote computer and in RigPi. 
Here you can find more info.
https://www.mumble.com/support/mumble-server-robotic-distorted-voice.php

Regards from Loic, SM5VFE

Re: TS 2000 no PTT

Don Domina
 

Howard,

The "official" new cable from MFJ arrived yesterday.  Installed and tested today.  I get the exact same result.  No radio key, very sluggish reaction to PTT GUI or spacebar.............
Since the RSS did not "key" when I shorted the PTT to GND does that indicate an issue with the RSS?  With the Jumper?  I  have the TS2000 Jumper module from Signaling installed.  With the 13 Pin to RJ45 cable removed, the RSS did key the TS2000.  It is still intermittent and sluggish.  When I reinstall the audio cable, the RSS keys and will not release the key until I shutdown and restart the TS2000.
I think i have the original image of the SD card and can try to load a new image.  I did this once before with the same results.  I am out of ideas.  Can I send the sd card to you to check?  Can I send the RSS?  I am hoping for some resolution soon.

Thanks for the help 

Cheers.

Don KC0DE

Re: TS 2000 no PTT

Don Domina
 

Bruce,

Thanks.  I will give that a try.

Cheers.

Don KC0DE

Re: Micro SDHC card performance question

tmeys@...
 
Edited

Thanks, Mark.  Good to know.  Maybe I just had a card that functioned, but has some performance defect.  Still seems what is recommended as a card and what MFJ ships are different.  I'm also thinking some may see this and some not based on what radio you use (I'm using the FT-991) and the load Mumble + RSS + other apps put on the SD card given the CAT requirements of the specific radio.

'73 - Tony - AE0AU

Re: TS 2000 no PTT

Don Domina
 

Howard,

It did not key the radio.  Nothing happened when I shorted between the two.  My "official" cable from MFJ now arrives on Monday.  I will test again when it is here.  I am thinking more and more it is the cable or the device.  I should be able to rule out the cable on Monday.

Appreciate your persistence.

Cheers.

Don KC0DE

Re: Kenwood TS-480HX and RigPi

Mark Weisheimer
 

Herb,

That is very interesting. I completely missed that the notches are 180 degrees apart between the 2 companies.
The numbers are the same, but the notch of the jumper block is opposite between MFJ and Tigertronics.
Just as you say, when using a Tigertronics jumper block, the Tigertronics notch will need to point towards the MFJ end that has 1 and SPK marked on the board.

Thank you for pointing that out!

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

Re: Kenwood TS-480HX and RigPi

HERB KEATON N2GEW
 

George:
I don't know if your experience with the Tigertronics jumper block will be the same as mine but I have checked
both the 6-pin DIN cable and the 8-pin DIN cable and the optional "pre-wired" blocks that Tigertronics sells
as options for the SignaLink USB.
In both cases, those blocks work inserted "opposite" from the markings on the block receiver. 
There is a "notch" etched into both the block and the receiver and I noted those at opposite 
ends in order complete the correct circuit.

Seems like quite a coincidence but confirmed.

N2GEW / herbk@...

Re: Micro SDHC card performance question

Mark Weisheimer
 

My Sandisk Ultra from MFJ is white and gray and I don't see that issue.

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

Re: So, I got an SSD...

Mark Weisheimer
 

Hi Mike,

No need to format the microSD as it gets overwritten with ALL of the data that is on the source image, including formatting.
It is a cloning process, so it makes a duplicate of what the source has.
It sounds more like an issue with the card or USB reader/writer.
If your RigPi version is 1.05, (it shows at the log on screen or in "system") you are up to date.
RigPi offers to update whenever an update is available so nothing special needed there.

If it is any help, here are some of what I use successfully:

https://www.microcenter.com/product/486146/16gb-microsdhc-class-10-flash-memory-card
https://www.microcenter.com/product/485030/usb-card-reader

and if you have amazon prime, here is a deal for 5 cards and a reader/writer combo.

https://www.amazon.com/PACK-SanDisk-MicroSDHC-SDSQUNB-016G-MicroSD/dp/B015IYSDVU/ref=sr_1_16?keywords=sandick+microsd+16gb&qid=1569063662&s=gateway&sr=8-16


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

Re: TX audio problem and RX audio quality

Mark Weisheimer
 

Tom,

There are no hardware mods since day one and my main RigPi is an early unit too.
The power on/off you refer to is for the KX3 or an external relay control of a power strip.
The firmware updates online and v1.05 is the current version.
I use a dual receiver K3/P3/KPA500 with the analog audio interface and use dual stereo cables to the line in / line out jacks on the radio.
I use a USB to DB9 serial cable connected to the P3 serial port.
I do not have a ground wire connected to the RigPi and have zero hum, RF feedback or audio issues.
Since you had this ground wire issue with a Pignology interface, it sounds like there is something hinky with your audio cable or configuration.

You could use a process of elimination to isolate the audio issue by substituting other audio devices into the system.
Simple stuff like using another source of line level audio and listening to it remotely.
Or playing out the TX audio at the RigPi to a set of 1/8" headphones.
Do you have your K3 menu set to use the Line In as the source?

Network issues? I don't know but I do use gigabit ethernet in the shack, not Wifi.
That is not because of the RigPi, it is because the SDR radios choke on anything less.

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

So, I got an SSD...

Mike K0JTA
 

So, I got a nifty little SSD, complete unit that includes the needed USB cable...  Using the SD CARD COPY app that is built into the RigPI SD, I cannot make the copy of the RigPI OS, apps and so on.  (The SSD is incorrect in some way; -I am presently away from the RigPI, so cannot report accurately.)

I am assuming that the SSD needs to be formatted; -I have searched and have found a few things to try, but so far, no go.  I found a routine (procedure) that I followed, downloaded a link, which turned into (opened to?) three pieces; -I am unable to load, run or use these, even though they all (three) seemed to go through a download process.

So, what I need is a little help on this.  I got the SSD as a result of reading a posted message, which sounded very attractive. 

I have read of an UPDATE for the RigPI; -Is this all I might need..?

Thanks, and very 73 from Mike, K0JTA

Micro SDHC card performance question

tmeys@...
 
Edited

I noticed from the first time I used my MFJ-1234 (purchased about a month ago) that Mumble audio from the RigPi to any device worked, but every few minutes it would get a little garbled, crack/pop once, and then sound fine again. After elimination of configuration, network, etc. settings as the reason, I used "top" and "vmstat" to check RigPi performance in a command terminal.  What I found was system load would usually jump a bit when this "pop" happened, and vmstat looked like I/O was getting "clogged" up.  By chance, I made a backup of the original SD card.  When I tested with my backup card, the problem was gone. I also noticed that my load levels as reported by "top" dropped down.

The unit came from MFJ with a SanDisk Ultra microSD.  I replaced it with a SanDisk Ultra Plus.  Researching online, I'm seeing that the SanDisk Ultra specs are 30 to 48 MBytes per second, the Ultra Plus is 80 to 98 MBytes per second (chosen based on Howard's recommendation of 80 MB/s or better).  Am I mistaken, or are these units shipping with a microSD less than the recommended transfer rate?  Have others noticed this? 

Note:  The Ultra that came from MFJ has a white/grey packaging, not the orange/grey of current Ultra and Ultra Plus devices.  Not sure what that might mean.  Maybe an earlier version?

'73
AE0AU

Re: TX audio problem and RX audio quality

Thomas Tumino
 

Hi Mark,

I must have one of the earliest MFJ-1234 that was produced as I ordered as soon as it was available.  I did not start actually using the setup until a few weeks ago.  I had been waiting for MFJ to ship me a rig control cable  until I found that I could just use any old cable. 

Are there hardware updates/mods  for the early MFJ-1234s?

Why doesn't the MFJ-1234 have a ground lug to ground to the rig?  Is this a sign that something else is wrong as I cannot get clean audio without a ground wire to the K3 and this is atypical for the mfj-1234?    My pigremote also required a ground wire to the K3 for clean audio and also did not include a ground lug.

I have already updated everything I can figure out how to update including WSJT-x and the OS. I have not updated the mumble server on the RSS.

 I just performed the RigPi audio update you cited, and the receive audio is improved but at this moment I can't get the transmit audio to work.  I have not yet visited the shack to unplug and replug the audio cables which mysteriously cures the tx audio problem on occasion. As I am using stereo cables I wonder if this is a problem with the firmware and the "switch on the rig" provision for the KX3 that seems to function on the tx audio line from what I remember reading.

 Receive audio now has dropouts (that is new)  but a definite improvement over the watery sound that would come on with the old setup.  Unfortunately now instead of the watery sound after about 15 min the sound gets "smoothed" sort of like someone switching on a strong noise blanker. 

Can I expect dropouts on a home network where network bandwidth is not an issue?  Is this a limit of the MFJ-1234?

Howard, thanks for the tip but that doesn't account for my problem.  I always click apply and then ok.

I would imagine someone somewhere has a working setup with a K3, and I imagine all setups with a K3 with a db9 serial port all have essentially the same setup.  Is this simply a matter of one of these lucky MFJ-1234 owners providing an image of his SD card to the group and then I can copy it?  If there is no MFJ-1234 hardware problem on my end, shouldn't that work?  Of course I would have to change the passwords but I imagine in all other respects the setup would then be ready to go?

73,
Tom

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