Date   
Re: Port Forwarding by Cox Communications

Jeffrey Wolf
 

Doing it the way I'm doing it, I'm running into the problem that I can't get to the port setting stage. The problem is what to use for the IP address. I've used the IP address for the RigPi to get to RigPi, but I can't use it twice. So what is the IP address to access Mumble? It must have another IP address. If there's actually no way to do this by this method, I'll try to use PiVPN. Not quite sure I understand how to use it, but I'll try to figure it out.
Thanks.
--Jeff, K6JW


On 9/24/2019 4:59 PM, Aaron Jones wrote:
Jeff,

It sounds like you are using a separate port forward for each application?  If so Mumble uses port: 64738 TCP AND UDP, in some routers that would be two separate entries, or others you'd be able to select tcp/udp  for the port forward.

So for a separate port forward you'd need to do the following:

MUMBLE = External Port: UDP and TCP 64738 = Internal IP UDP and TCP 64738
HTTP (for rigpi UI over browser = External Port TCP XXXX (8000)  = Internal IP 80
VNC = External port 5900 = INTERNAL PORT 5900 (OR A MAPPING OF YOUR CHOOSING)

However, if you move to using the PiVPN / openvpn configuratoin you would only open one port:
External port 443 (or of your choosing) UDP = Internal port 443 (or whatever port you define when isntalling PiVPN)

Then you use your phone and connect to the "openvpn" which connnext to your external IP to your RigPI then mumble, VNC, and HTTP all go over the standard ports with no router mapping.

Just my two cents and experience.  I still have some external mappings for VNC so I can connect over my external IP to the RigPI vnc session without using VPN.

Good luck.

Re: So, I got an SSD...

Art Olson
 

Mike

Can you provide steps or point to your source you used to run rigpi on a ssd. I have done a few with vanilla pi software. But stuck  on this one

Art N2AJO 


On Sep 22, 2019, at 9:39 PM, Mike K0JTA <mike@...> wrote:

I believe I have found the resolution!  I restarted the Raspberry PI, and I am now able to copy the SD card to the new external USB-based SSD.  It is now under way; Copy of partition one is done, and partition two is under way, as I type.

73 from Mike, K0JTA

Re: Kenwood TS-480HX and RigPi

George Miller W3GWM
 

I’m working on getting started one step at a time. 

I have VNC installed and I can access the Raspberry Pi Desktop from other computers on my local network. I can run RSS and make changes to the dummy radio.

I’m now trying to get pitunnel working to access raspberry pi from outside of my local network. 

After that I’ll try to get VNC to allow me to use RSS from outside my local network. 

Any help getting pitunnel running ?
--
George W3GWM

Re: TS 2000 no PTT

 

Hello all,
I found my old signalink cable and jumpers.  I did not pin out the cable but I would use the new one from MFJ.  As for the signalink jumpers, you should put them in a safe place and forget where that is. Those jumpers have embedded jumper traces that won't work with the RSS.
In other words, use the new MFJ cable and jumper block and INSTALL as called for in the original instructions.
I checked my jumper block and it is in fact notch to notch and has no other embedded trace jumpers.
If it doesn't work then, I still think it is a hardware problem and not software.
That's all I have for now.
Don
N3BMT

Re: Port Forwarding by Cox Communications

Aaron Jones
 

Jeff,

It sounds like you are using a separate port forward for each application?  If so Mumble uses port: 64738 TCP AND UDP, in some routers that would be two separate entries, or others you'd be able to select tcp/udp  for the port forward.

So for a separate port forward you'd need to do the following:

MUMBLE = External Port: UDP and TCP 64738 = Internal IP UDP and TCP 64738
HTTP (for rigpi UI over browser = External Port TCP XXXX (8000)  = Internal IP 80
VNC = External port 5900 = INTERNAL PORT 5900 (OR A MAPPING OF YOUR CHOOSING)

However, if you move to using the PiVPN / openvpn configuratoin you would only open one port:
External port 443 (or of your choosing) UDP = Internal port 443 (or whatever port you define when isntalling PiVPN)

Then you use your phone and connect to the "openvpn" which connnext to your external IP to your RigPI then mumble, VNC, and HTTP all go over the standard ports with no router mapping.

Just my two cents and experience.  I still have some external mappings for VNC so I can connect over my external IP to the RigPI vnc session without using VPN.

Good luck.

Re: Macros for the Yaesu FT 991-A Help #ft-991a

Ryan Matthew Headley
 

Thanks for that info.


On Tue, 24 Sep 2019, 17:13 Mark Weisheimer, <mweisheimer@...> wrote:
I can't say why it doesn't generate any response, but 3B hex is a semi-colon which is the "end of command" delimiter for many CAT radios.
Kind of like RETURN key.


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

Re: TS 2000 no PTT

Bruce N7XGR
 

Howard,  This is why I advised him to do the Ohm meter test directly
from the DIP socket on the number side to the 13 pin DIN plug.
This will test for continuity and correct wiring to the DIP socket
with respect to the jumper module wiring being correct also.

Bruce  N7XGR


On Tue, Sep 24, 2019 at 6:45 PM Howard Nurse, W6HN <hlnurse@...> wrote:
Hi Don,

The Figure 1 diagram in your last message is inconsistent with the schematic and with the physical board. 

I've included an image of the board showing the callouts for JP2 (the jumper connector).  On the board the JP2 notch is at the top.  Pins 1, 2, and 3 are labelled GND.  Pin 6 is PTT. On the reverse side of the board, 1, 2, and 3 on JP2 are connected together at their P3 end.

The labels on the Figure 1 drawing numbered 1-8 are correct given the notch, but PWR, PTT, MIC and SPKR and the GND pins are not correct because they disagree with the actual board.  This wouldn't matter if there are really three jumpers on each end connected to their opposite pins.  If the jumper has one wire connecting the three G pins to 6, 7 and 8, that will cause a problem if the jumper is installed notch-to-notch.  The bottom line is that if the jumper is wired as shown in Figure 1, there should not be a problem no matter which way the jumper plug is inserted.

--Howard 

Re: TS 2000 no PTT

Howard Nurse, W6HN
 
Edited

Hi Don,

The Figure 1 diagram in your last message is inconsistent with the schematic and with the physical board. 

I've included an image of the board showing the callouts for JP2 (the jumper connector).  On the board the JP2 notch is at the top.  Pins 1, 2, and 3 are labelled GND.  Pin 6 is PTT. On the reverse side of the board, 1, 2, and 3 on JP2 are connected together at their P3 end.

The labels on the Figure 1 drawing numbered 1-8 are correct given the notch, but PWR, PTT, MIC and SPKR and the GND pins are not correct because they disagree with the actual board.  This wouldn't matter if there are really three jumpers on each end connected to their opposite pins.  If the jumper has one wire connecting the three G pins to 6, 7 and 8, that will cause a problem if the jumper is installed notch-to-notch.  The bottom line is that if the jumper is wired as shown in Figure 1, there should not be a problem no matter which way the jumper plug is inserted.

--Howard 

Re: TS 2000 no PTT

Bruce N7XGR
 

Don,  This is my advice for the next step.  Remove the cover from the RigPi,
take the screws off the RJ45/jumper board, note the pin numbering on one
side of the DIP socket.  Redo the Ohm meter test with the jumper module
removed, test directly from the DIP socket to the 13 pin DIN plug.
Inspect the soldering on the RJ jack and the DIP and the 6 flat ribbon wire.
I had to suck out the dull gray and black speckled solder from the RJ pins.
I reflowed all 8 pins, now they are bright and shiny with the correct amount
of solder.  There was waaay more than enough solder on just four pins that if
divided in half would be the right amount for the other four pins.
I did the same for the 6 wire flat ribbon.

Bruce  N7XGR


On Tue, Sep 24, 2019 at 5:26 PM Don Domina <stl_deli@...> wrote:
Howard,

I understand what you are saying.  My references numbers were for the 13 Pin ACC2 and the 8 Pin RJ45 and not the jumper module.  My module is a purchase prewired module for the TS2000.  It was "notch to notch" during the tests this morning.  I have reversed it and tested again.  I get the same results.  
I am using pattern "E1" from the website https://groups.io/g/RigPi/files/RigPi%20Documentation/audiodipconnections.pdf
The following is the information from the Signalink website showing the pattern on the jumper module.

http://www.tigertronics.com/sl_wirebm.htm

It is Figure 1 of the section beginning "13-pin DIN Accessory Port Connector (use SLUSB13K, SL1+13PK or SLCAB13K)"
Hope that clarifies the information I used and the numbering I used.

Cheers

Don KC0DE

Re: IC-7300 SETUP

Jeffrey Wolf
 

Hi again,
   I got on on 7488. Any suggestions for accessing Mumble? I know the port should be 64738, but what IP should be assigned to the program, or should it be the same as for RigPi? When I used the RigPi IP, my router said the MAC address was incorrect. Not sure why this should be.
--Jeff, K6JW

Re: Port Forwarding by Cox Communications

Jeffrey Wolf
 

Thanks, Aaron. As I learned a little while ago from Howard, I had been using the wrong IP address to get into RigPi. Instead of using my network address, I had been using the RigPi address. Once I realized my mistake, there was no problem getting in. Now, I'm just trying figure out how to start Mumble from the remote location. Mumble doesn't come up as distinct from RigPi in my list of active applications, leading me to believe that it should be included in the IP for RigPi, but that yields an incorrect MAC address. Need to puzzle this one out for awhile.
--Jeff, K6JW

Re: Port Forwarding by Cox Communications

Aaron Jones
 

Jeff,

I've configured three different cox accounts for port forwarding and had no problems.  Here's what I did to get around issues though.

  1. Instead of having each device port forwarded (Mumble, VNC, RigPI port 80) I use one port and VPN into my RigPI using OPENVPN
  2. I used Port 443 since that's a common security port - I forward that Port into my rigPI and then VPN into it, than it's as simple as directing mumble, my browser, and vnc to the core "vpn" IP defined by OPenvpn, it's 10.8.0.1 and I dont' have to worry about custom ports after that
In my personal case - I have a business IP so I can use whatever ports I want. 

One friend had a Netgear router so we used a single port on port 443 and that worked fine.

The other friend had a cox router which had Port Forwarding under the advanced settings in the cox wifi app.  I also used port 443 to the assigned IP address of the RigPI.  No problems.

Re: TS 2000 no PTT

Don Domina
 

Howard,

I understand what you are saying.  My references numbers were for the 13 Pin ACC2 and the 8 Pin RJ45 and not the jumper module.  My module is a purchase prewired module for the TS2000.  It was "notch to notch" during the tests this morning.  I have reversed it and tested again.  I get the same results.  
I am using pattern "E1" from the website https://groups.io/g/RigPi/files/RigPi%20Documentation/audiodipconnections.pdf
The following is the information from the Signalink website showing the pattern on the jumper module.

http://www.tigertronics.com/sl_wirebm.htm

It is Figure 1 of the section beginning "13-pin DIN Accessory Port Connector (use SLUSB13K, SL1+13PK or SLCAB13K)"
Hope that clarifies the information I used and the numbering I used.

Cheers

Don KC0DE

Re: New user, not computer savvy, need to understand ..... to begin

Mark Weisheimer
 

Mike,

Have you seen Clint Chrons VERY thorough document in the files section?
It has a lot of step by step instructions and is at:

https://groups.io/g/RigPi/files/Homebrew%20Information%20from%20Users/RigPi%20Installation%20For%20Icom%20USB%20Radios.pdf

It also has a section specific to the using RigPi with the IC-7300, that starts about page 10 as I recall.
See if that can help you get started.

And Welcome to the group!

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

Re: Macros for the Yaesu FT 991-A Help #ft-991a

Mark Weisheimer
 

I can't say why it doesn't generate any response, but 3B hex is a semi-colon which is the "end of command" delimiter for many CAT radios.
Kind of like RETURN key.


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

Port Forwarding by Cox Communications

Jeffrey Wolf
 

This morning I tried to set up port forwarding to the RigPi. Configuring my eero router was simple (7488 to 80) but Cox Communications (my ISP) states that it blocks port forwarding. Has anyone encountered this and managed to get around the issue? Cox has a webpage with the ports it says it blocks, but I suspect that the list is incomplete. Here is a link to that page:
https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html

New user, not computer savvy, need to understand ..... to begin

Mike <k0com@...>
 

So far Quick start has me with a lan connection to the app and connect to my 7300 controls.  It appears I need to access the rigpi desktop to set up audio, other devices.  Using an IPad or IPhone to begin with, a PC a bit later.  How does one do that specifically... steps by step.  I also want to access the radio via the web.  Looking for step by step instructions.  Are these documents available somewhere?  The threads I read are too limited or the information is in terms I’m not familiar with.  Example, what is vnc viewer and how does it work?  Thanks. 

Re: Macros for the Yaesu FT 991-A Help #ft-991a

Ryan Matthew Headley
 

I am definitely missing something here.

I entered *0w \0x56\0x4D\0x3B into an unused macros spot.  The button then appeared on the Tuner page.  When I press it, it has zero effect on anything.

On top of that, where does the '3B' come from in the hex?  VM in hex is '56 4d'.

Re: TS 2000 no PTT

Howard Nurse, W6HN
 

Hi Don,

The pin numbering on the jumper block appears to be incorrect.  Mark, in this message:

https://groups.io/g/RigPi/message/3082 

said that the jumper block needs to be inserted so that the notch is at the opposite end from normal.  If you look at the jumper block schematic here: 

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

Jumper block J2 shows 1, 2, and 3 as ground on the schematic.  Your comment above says ground is on 6, 7 and 8.  This suggests that the header block must be reversed from normal, or that the schematics are incorrect.  A test we tried earlier to short pin 6 to ground did not cause PTT to work on the radio.  A reversed jumper block would cause this.  Don, N3BMT, (who is not having a PTT problem with his TS-2000) should be able to confirm the position of his jumper block.

You said earlier that you reversed the block and it didn't help.  Please try again using the Hamlib Dummy radio.

--Howard

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

Loic SM5VFE
 

I see less delay  if I connect to cable to RigPi at radio qth and connect to cable to the mobile router on the remote side. 

Regards from Loic, SM5VFE