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.

Messages - K7FL

Pages: [1] 2
Configuration, RRC 1258 / Re: No receive audio
« on: 2017-01-15, 00:27:50 »
More info: receive audio is heard at the station (RF) end of link  ... nothing from the K3/0 through speaker or headsets.

Configuration, RRC 1258 / Re: No receive audio
« on: 2017-01-14, 23:41:11 »
BTW, version 2.87

Configuration, RRC 1258 / No receive audio
« on: 2017-01-14, 23:33:36 »
I have my two RRC's and the K3/K30 mini communicating over the Internet using cellular data. Rig control works fine and I can see the s-meter fluctuating at the remote site, but there is no receive audio. Tried the obvious like the K3/0  rf and af gain, but still no audio. Any ideas from the learned masses?

General discussion / Boot sequence for remote
« on: 2016-12-28, 19:10:34 »
I am successfully using a K3/0 Mini plus the K3, KAT & KPA 500's via the RRC boxes. I also have a PC connected via Team Viewer which talks to the configuration via serial ports. I'm connecting an IP power strip, and curious as to the best boot sequence to program so everything is 'awake' when hardware and software are trying to communicate. I'm thinking the following order, but would welcome suggestions:
1. Web router/hub
2. RRC at remote site
3. PC
4. 12VDC bus that powers radio and radio accessories
Dennis, K7FL

Configuration, RRC 1258 / Multilevel passwords for WiFi
« on: 2016-03-21, 18:52:14 »
I'm in Mexico and trying to access my home station in Washington state. The ISP here requires two entries to sign in. I can see the local wifi on the RRC, but the RRC firmware allows only has one field for the password.  The wifi network asks for a room number and a last name (2 separate items in two different fields).

Any ideas how I might get around this login issue?


General discussion forum / Acceptable jitter
« on: 2016-02-17, 00:03:10 »
I have identified a potential host QTH for my remote with great bandwidth, but the jitter is 13ms. Jitter on my current remote site is 1ms and I've been successful with running CW on the RRC with the default jitter settings. As there are no antennas or power at the new site, its difficult to test the significance of 13ms jitter on my operations, and if the 13ms of jitter can be mitigated by RRC settings.

How bad does line jitter need to be before causing issues on CW? I understand there may be other variables, but I am trying to determine some rule of thumb about levels of jitter found to be problematic for users. The archives have lots of info on addressing jitter, but few reports of the measured jitter users are trying to mitigate.

Remote: K3 line
Control: K3/0
RRC's current rev
Windows 7

Configuration, RRC 1258 / Re: Congestion tone on first setup
« on: 2016-02-13, 01:40:25 »
Solved! I had forgotten to enter the SIP password. So obvious !!!  :o
Dennis, K7FL

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.

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.

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
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

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

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

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.
Dennis, K7FL

Configuration, RRC 1258 / Re: Control RRC is confused :-)
« on: 2016-01-11, 16:47:27 »
Sent serial number info to SM2O.
Dennis, K7FL

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 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 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

Pages: [1] 2