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

Pages: [1]
1
General discussion / Re: No audio packets
« on: 2024-04-02, 03:47:43 »
I finally have audio from the remote K3 to the laptop at the control site but while I have audio with a headset using through the jacks in the dongle and via a USB headset, I cannot figure how to get that audio to computers speakers on this Windows 11 computer.  I have it working fine on the Windows 10 pc.  Any ideas as to how set up the Sound Settings in Windows 11 to do that? 

Thanks,

Joe

2
General discussion / No audio packets
« on: 2024-03-03, 02:53:31 »
I am using the 1274A dongle attached to a Windows 11 PC with the 1258MKII at the radio site (Elecraft K3).  I have no audio packets arriving at the PC - the green bar is blank.  I am at my home on the same LAN. 

I also have a Windows 10 PC using the same configuration for both in the RRC and the 1274A and it has audio packets without any problems.  It functions normally within the local LAN or outside.

Does anyone have any ideas as to how I can fix this problem?  Here is a copy of the RRC Status when HRD is connected via the 1274A Com port:

Status

Name   Value
P5.2   OFF
Connection status   OK
SIP status   Connected/transfering
Last SIP error   None
RTP status   Excellent(60)
UDP cmd status   OK(45)
SIP command timeout   0
Rx Jitter buffer size   12
Rx Jitter delay   10
Dual Rx   0
Current audio packet size   20
Current audio quality   0 - alaw 8 kHz
External IP   72.93.241.136
SIP Out port   51200
SIP In port   51200
Audio Out port   51201
Audio In port   51201
Command Out port   51202
Command In port   51202
External SIP In port   51200
External Audio In port   51201
External Cmd In port   51202
Other party   192.168.1.152
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
Dynamic DNS status   OK
Ping status (watchdog)   Off
DNS status   OK, remoterig.com = 86.107.103.218
Active profile   Default
PTT status   OFF
Antenna-Switch (IP)   not connected
Common network settings   No

Thanks,

Joe
AJ1Y

3
General discussion / Re: RRC Micro 1274A
« on: 2020-01-11, 15:46:14 »
I now see how to restart the RRC at the QTH remotely.  That solved my "Busy Here" issue.

I can connect and when I do, there is no green bar under the connect buttons.  The message that comes up when I hover over that bar is that if it is not green then packets are not coming fast enough.  What adjustments can I make to the audio settings so as to get the packets coming in fast enough?

Thanks,

Joe

4
General discussion / Re: RRC Micro 1274A
« on: 2020-01-11, 11:45:10 »
Thanks for the suggestion, Mike. 

How do I do that?  If I were at the QTH, I would know exactly what to.  While I am remote, I  am not sure exactly how to access and login to the RRC  at my home QTH so as to be able to restart. 

Thanks for the help!

Joe

5
General discussion / Re: RRC Micro 1274A
« on: 2020-01-11, 08:11:17 »
Mitch,

I was not very clear about what I experienced.  Let me elaborate a bit.

By way of backgroud, before ileft my QTH I made several  contacts on my wifi. After I left home, I connected once from my remote location and everything appeared to be normal while receiving.

This morning when I went to connect,  I opened the Microclient software just as I did 2 days ago.  After I click on the connect button, on the first line of the client software window next to the buttons where it usually shows the remoterig server name it displays the server name for several seconds.  After that it shows the message "Busy Here" and never connects to the radio. 

The setup is K3 with RRC at the QTH.  At my current location, I am using the RRC micro dongle (1274A).  The computer is a PC running Windows 10.

Does any of that help to diagnose the problem.

Thanks,

Joe

6
General discussion / RRC Micro 1274A
« on: 2020-01-11, 03:19:01 »
When I try to connect to my rig using the Remoterig PC Client and the 1274A, it does not connect and I get a message in the line where I see the DNS server name that says "Busy Here."

1. What does that tell me?

2. How do I fix the problem?

Thanks,

Joe

7
Hi Mike,

Set to mode 1 and made one change to HRD (had set the stops wrong - should have been none).  Works great!!  Thanks very much!!

73 Joe AJ1Y

8
Mike,

Thanks.  Since I am connecting the RRC to the rotor and the rotor has an RS 232 port, I will try the cable where 2 and 3 pins are crossed.

Another question I have is the mode to set at the RRC and at the RRC Micro on the PC end?  There are several different choices.  From what I understand, I just want everything from the PC to Rotor to be transparent BUT I am not sure what settings to make that happen? 

Thanks,
Joe
AJ1Y


9
We are using Mk1258 RRC at the radio end and the RRC-Micro PC-Client with a K3 and HRD.  The system works fine with the radio. 

The last remaining issue is the connection to the rotor.  The RC2800PXAZ is connected to COM 1 on the Mk1258 RRC at the radio site.  The cable between the RRC and the RS232 port on the rotor is a straight pin to pin cable.  The rotor manual says that the port settings should be

baud rate 9600
bits 8
stop bits 1
parity none
handshake present, but not used

Those are the settings that I applied to the RRC Mk1258 COM 1 in Serial Setup.  Also the rts/cts is 0 and the terminator is 00.  I have tried multiple COM 1 Modes (all unsuccessfully).

On the RRC-Micro PC-Client I set the RRC COM 1 setup to be a variety of modes (none of which have worked) along with aligning it to PC COM 1 (while having radio control on PC COM 2).  I have left the terminator block blank and the timeout at 40 ms.

I then set HRD to connect via PC COM 1 and attempt to connect.  No luck.  I have tried various COM modes on both ends and nothing works.

Since the remainder of the remote setup is working like a champ, I assume that am doing something wrong in the interfaces from the PC thru to the rotor.

Can someone provide some suggestions?

Thanks,
 

10
Mitch was kind enough to try to help me out by posting this request.  Mitch's correctly states the situation and the problem. 

In the end, based upon information provided from another OM quite familiar with Apple OS and the difficulties associated with port opening running Windows in a virtual machine, I reloaded Windows using Apple's bootcamp process and software.  It works fine as, instead of running in a Virtual Machine, you are really running Windows in a partition on the hardware.  It works fine and is, for the purposes of remote rig, easy.

Since doing this, I have solved not only the audio problem with audio on my own LAN but have also been able to connect to my rig via the web.

73
Joe AJ1Y

Pages: [1]