31
Configuration, RRC 1258 / Re: Congestion tone on first setup
« on: 2016-02-12, 18:58:35 »
We used the actual IP address.
More suggestions welcomed.
Thanks
More suggestions welcomed.
Thanks
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
32
Configuration, RRC 1258 / Re: Congestion tone on first setup
« on: 2016-02-12, 05:26:55 »
Yes, we changed to the external IP address. The control RRC is not using DHCP but we did change the IP address to the correct subnet so it is visible on the local network.
33
Configuration, RRC 1258 / Congestion tone on first setup
« on: 2016-02-12, 02:23:51 »
I have my Elecraft K3s communicating effectively over the LAN and am now attempting to connect over the Internet. I have enabled port forwarding on my firewall for 13000, 13001, 13002, and 80 and the RRC shows "Idle" status (see below). However, the K3s still gives a congestion tone when turned on. Everything is physically connected as normal but the AUX/MIC shows no link or activity lights.
Any pointers would be appreciated.
Here is the status from my control RRC:
Name Value
Control panel ON
Radio OFF
Connection status Disconnected
SIP status Idle
Last SIP error None
RTP/UDP audio status Disconnected
UDP cmd status Disconnected
SIP command timeout 0
Rx Jitter buffer size 4
Rx Jitter delay 3
Dual Rx 0
SIP Out port 13000
SIP In port 13000
Audio Out port 0
Audio In port 0
Command Out port 0
Command In port 13002
External SIP In port 13000
External Audio In port 13001
External Cmd In port 13002
Other party 0.0.0.0
Input 0 High
Input 1 High
Input 2 High
Output 0 Low
Output 1 Low
Output 2 Low
DNS status Unknown
Active profile Profile 2
PTT status OFF
Common network settings Yes
Any pointers would be appreciated.
Here is the status from my control RRC:
Name Value
Control panel ON
Radio OFF
Connection status Disconnected
SIP status Idle
Last SIP error None
RTP/UDP audio status Disconnected
UDP cmd status Disconnected
SIP command timeout 0
Rx Jitter buffer size 4
Rx Jitter delay 3
Dual Rx 0
SIP Out port 13000
SIP In port 13000
Audio Out port 0
Audio In port 0
Command Out port 0
Command In port 13002
External SIP In port 13000
External Audio In port 13001
External Cmd In port 13002
Other party 0.0.0.0
Input 0 High
Input 1 High
Input 2 High
Output 0 Low
Output 1 Low
Output 2 Low
DNS status Unknown
Active profile Profile 2
PTT status OFF
Common network settings Yes
34
General discussion / Re: Typical data usage?
« on: 2016-01-29, 21:47:12 »
Thanks Mitch. My apologies. I did a search but must not have selected the correct key words.
I'll go to the link you suggested and research.
Best Regards,
Dennis, K7FL
I'll go to the link you suggested and research.
Best Regards,
Dennis, K7FL
35
General discussion / Typical data usage?
« on: 2016-01-29, 21:07:44 »
I have a K3, KAT500 and KPA500 with the K3/0 mini and RRC boxes. What kind of data consumption might one expect from this configuration? I suspect that's a tough question with many variables, but lets assume the radio is on and receiving for 24 hours, limited knob twisting and transmitting.
The reason I ask is that I have multiple host sites for my remote station. Some have great Internet access (Comcast high speed cable), others ADSL via WiFi, and one with a 4G Jetpack. All of these options have bandwidth, latency and cost implications. As a CW op, latency is a critical factor in my case. ADSL in my area is typically 10Mbps down, 600Kbps up ... probably acceptable from a bandwidth perspective. One of the best QTH's under consideration obtains their Internet connectivity via a Verizon 4G Jet pack. The bandwidth is probably adequate, latency is around 60ms (in their installation), but the data charges can be significant. But, it all depends on how much data I will actually consume (my question above). Any ideas?
Thoughts on these different connectivity options (cost, bandwidth, latency) are most welcome.
Kind Regards,
Dennis, K7FL
Battle Ground, WA
The reason I ask is that I have multiple host sites for my remote station. Some have great Internet access (Comcast high speed cable), others ADSL via WiFi, and one with a 4G Jetpack. All of these options have bandwidth, latency and cost implications. As a CW op, latency is a critical factor in my case. ADSL in my area is typically 10Mbps down, 600Kbps up ... probably acceptable from a bandwidth perspective. One of the best QTH's under consideration obtains their Internet connectivity via a Verizon 4G Jet pack. The bandwidth is probably adequate, latency is around 60ms (in their installation), but the data charges can be significant. But, it all depends on how much data I will actually consume (my question above). Any ideas?
Thoughts on these different connectivity options (cost, bandwidth, latency) are most welcome.
Kind Regards,
Dennis, K7FL
Battle Ground, WA
36
Configuration, RRC 1258 / Re: Control RRC is confused :-)
« on: 2016-01-12, 16:37:01 »
Thanks ... the serial number for the Control is 9777.
Hopefully I can receive the build file soon as I am unable to communicate with the Radio end until the Control is working.
73
Dennis, K7FL
Hopefully I can receive the build file soon as I am unable to communicate with the Radio end until the Control is working.
73
Dennis, K7FL
37
Configuration, RRC 1258 / Re: Control RRC is confused :-)
« on: 2016-01-11, 16:47:27 »
Sent serial number info to SM2O.
Thanks!
73
Dennis, K7FL
Thanks!
73
Dennis, K7FL
38
Configuration, RRC 1258 / Re: Control RRC is confused :-)
« on: 2016-01-11, 06:00:30 »
Let me clarify my initial post...
The RRC box initially named CONTROL 192.168.0.227 has apparently been renamed to RADIO. It appears the firmware loaded in the RRC formerly labelled CONTROL is now the RADIO RRC content (for example, going to 192.168.0.227 and selecting Radio Settings now shows no place to add the SIM Contact IP address).
As stated in my initial post, the serial number of the CONTROL (now RADIO) RRC has been set to 1.
I've reinstalled the firmware but no joy.
Dennis, K7FL
The RRC box initially named CONTROL 192.168.0.227 has apparently been renamed to RADIO. It appears the firmware loaded in the RRC formerly labelled CONTROL is now the RADIO RRC content (for example, going to 192.168.0.227 and selecting Radio Settings now shows no place to add the SIM Contact IP address).
As stated in my initial post, the serial number of the CONTROL (now RADIO) RRC has been set to 1.
I've reinstalled the firmware but no joy.
Dennis, K7FL
39
Configuration, RRC 1258 / Control RRC is confused :-)
« on: 2016-01-11, 00:45:38 »
I had to reboot the Control RRC a couple of times today. After one reboot, the rigs failed to communicate and investigating, I found the Control RRC has somehow renamed Radio. In addition, the original serial number now indicates a 1. I reloaded the firmware to no avail. No communications between the RRC's, but I can ping each IP number.
Dennis, K7FL
Dennis, K7FL
40
General discussion forum / Re: iPhone HotSpot Connection with RRC-1258 MKII
« on: 2016-01-10, 07:03:25 »
Hi Paul ... did renaming solve the problem permanently? I am having a problem connecting with the iPhone 4 hotspot with no success. As with you, I can connect other other wifi connections quite successfully.
Dennis, K7FL
Dennis, K7FL
41
General discussion forum / WSPR on K3/0 mini - RRC?
« on: 2016-01-10, 05:45:30 »
Has anyone been able to decode WSPR signals through the K3/0 mini, RRC connections?
I have been unsuccessful.
Dennis, K7FL
I have been unsuccessful.
Dennis, K7FL
42
General discussion forum / Anyone using HRD with K3/0, RRC combo?
« on: 2016-01-03, 22:32:50 »
I currently have my K3 line connected (over the LAN for now) to a K3/0 via RRC boxes. This configuration is now stable so I've begun to focus on the integration of Ham Radio Deluxe into the mix. I use HRD only for logging ... the rig control functionality is redundant with the K3/0 mini and therefore is of no interest, except for talking to the logbook (Frequency, Mode, QSY for packet spots).
Has anyone found a way to satisfy the HRD logging program data requirements from K3/0-mini/RRC feeds versus having HRD rig control active? I am assuming that running HRD rig control essentially running in the background will come at the price of data consumption.
Thoughts? Perhaps I'm worrying needlessly about the data consumption, but the concept of HRD rig control and a K3/0-mini running concurrently doesn't strike me as a good situation.
Thanks
Dennis, K7FL
Battle Ground, WA
Has anyone found a way to satisfy the HRD logging program data requirements from K3/0-mini/RRC feeds versus having HRD rig control active? I am assuming that running HRD rig control essentially running in the background will come at the price of data consumption.
Thoughts? Perhaps I'm worrying needlessly about the data consumption, but the concept of HRD rig control and a K3/0-mini running concurrently doesn't strike me as a good situation.
Thanks
Dennis, K7FL
Battle Ground, WA
43
Configuration, RRC 1258 / K3/0 and RRC's
« on: 2016-01-03, 03:52:27 »
I purchased the K3/0 mini and RRC boxes from Elecraft to remote my K3 line.
I assume the radio the Radio setting for this configuration should be 14-Elecraft Twins vs. 4, Yaesu, Kenwood and Elecraft, correct?
Dennis, K7FL
I assume the radio the Radio setting for this configuration should be 14-Elecraft Twins vs. 4, Yaesu, Kenwood and Elecraft, correct?
Dennis, K7FL
44
General discussion forum / Re: Extra dot on CW
« on: 2015-12-31, 20:47:15 »
Problem was due to the side tone setting. Once the side tone was disabled, the extra dot issue disappeared. Thanks to all who responded.
73
Dennis, K7FL
73
Dennis, K7FL
45
General discussion forum / Re: Extra dot on CW
« on: 2015-12-31, 19:26:21 »
Thanks for the reply Gus. The keyer was in iambic A. I tried both A & B and the result is the same (an extra dit on end of the transmission). I also confirmed that this occurs in the TEST mode, which indicates it is not RF related. If I switch to a voice mode (e.g. LSB) and monitor with the side tone, the problem does not occur.
Regards,
Dennis, K7FL
Regards,
Dennis, K7FL