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.


Topics - K3TN

Pages: 1 [2]
16
I've read the RemoteRig section on RTTY and W1UE's writeup. Nowhere did I actually see anything about getting the audio to the PC/software on the  Control side.

I'm guessing I need to run a cable from the SPKR jack on the front of the Control RRC to the PC microphone input to the sound card? That would mean disconnecting the headphones.

Configuration: K3/Mini to laptop running N1MM/MMTTY.

73 John K3TN

17
I've got a K3/Mini running, remotely operating a K3 - but I have two major audio problems if I use the K3 Mini cable to connect the Mini to the RRC, and then plug my Heil headset into the mini:

1. Headphone audio is down 20 db compared to plugging headphone into the RRC.
2. On xmit, horrendous hum on the xmit audio - which goes away if I plug the mic directly into the RRC.

Elecraft has sent me a new I/O board for the Mini, I will see if that fixes the problem - but others have had the problem and the I/O board did not fix.

Is anyone out there seeing success plugging a headset into the Mini, either using the 8 pin circular connector and the 1/4 phone jack on the front panel, or using the side min phonos?

73 John K3TN

18
With a local K3 connected to N1MM, I can use the following Function Key string:

F3 TU,{CLEARRIT}<<r>>{END}{CATDELAY 3}{CAT1ASC SWT11;}

This Clears the RIT setting, sends the letter r. The {END} macro tells the N1MM software "wait until the message is sent before executing anything to the right"

After the r is sent, the CAT1ASC command tells the K3 to swap VFOs. The CATDELAY command says wait 3 ms before sending the CAT1ASC SWT11; string - I needed that to make it work since stopping sending took a few ms.

Trying this over RemoteRig results in the R being sent but no VFO swap. Upping the CATDELAY to 3000 (3 seconds) didn't make it work.

Without the END macro, the VFO swap happens (after the CATDELAY) but the R never gets sent.  That is to be expected. But, the END macro should work - but it doesn't seem to.

I'm guessing that the interleaving of data comms between the RRCs is causing this issue - but not sure how/why.

Is there some reason this shouldn't work? Or some setting for one of those mysterious Serial Settings that would enable it work?

Thanks, John K3TN

19
Configuration, RRC 1258 / Popping noise when CW send ends
« on: 2015-01-12, 00:16:34 »
Using RemoteRigs to remote control a FT1000 - when I send CW and my headphone audio switches from the CW sidetone to the receiver audio, there is a loud popping/clicking/chirping sound, at least 90% of the time.  It is many dB louder than the rx audio, so very fatiguing to listen to.

Seems to happen more with software (such as N1MM function key) sending, not so much with sending CW with the paddle that is connected to the Control RRC.

On the Control RRC, I see under Advanced Settings PTT-off mute delay. But changing that from the default setting of 0 all the way up to 900 does not make much, if any, difference.

Is there some other parameter to set?

Thanks, John K3TN

20
Remotely controlling an FT1000MP, using N1MM contest logging software. The FT1000 is one of three at the station (K4VV) and N1MM software is used for multi-op efforts to both network the computers together and to support rotator control without having each PC have a hard wired connection to every rotor.

That is done using N1MM feature that allows each PC to talk to each other over the shack LAN - each copy of N1MM has a .ini file with the local IP addresses to make this work.

Example: N1MM on control end wants to send packets to PC on radio LAN  to turn rotor. If I just put the radio LAN IP addresses in the N1MM .ini file now, the control side PC running N1MM will just send on the control side LAN, not the radio side LAN.

So, the question: if there a configuration of RemoteRig that enable software on the control side (N1MM) talk on the radio-side LAN? I know that works with Com ports, but can it handle this scenario? Or, anyone doing this with N1MM configuration?

Thanks, John K3TN

21
On a clean Windows 7 laptop I installed the Microbit Setup Manager and had it install virtual ports. I also installed the N1MM logging program.

I am running my K3 in terminal mode to connect to a remote K3. I have that working, with one slight audio issue I'll chase later.

I added computer control via N1MM - a USB serial adapter shows up as COM 6 on the Win 7 laptop, I connect that to COM1 on Control RRC front panel. That works fine.

Now, I want to add CW keying. I tried following W1UEs instructions for using DTR keying, did not work.

Decided to try the Winkey approach, following DJ0QN's instructions, connecting a USB cable to the Control RRC USB connection - N1MM says Winkey not detected.

One problem may be the virtual ports. In device manager I see:

Intel Active Management Technology - SOL (COM3)
RRC1258 COM2 (COM5) - this appears when I plug in the USB to USB cable
USB Serial Port (COM6)


So, I'm telling N1MM to use COM5 for CW - but that doesn't work. However, DJ0QN's instructions seem to want me to use a virtual port COM 3, but I'm seeing that Intel COM 3, no virtual one.

In the Other Devices within Device Manager I see 3 1258 Remote Rig entries with a question mark on them, clicking on any of them brings up Device Status of "Driver not Installed"

What am I missing??

Thanks, John K3TN

22
Configuration is PC remote control of an FT1000. I can currently send CW from a paddle at the Control end and the Paddle connector at the Radio RRC connected to the FT1000 key jack.

I can start up N1MM on my PC at the Control RRC side and see the frequency of the remote FT1000, change the freq, etc - CAT is working.

But, how to I use N1MM to key the remote radio, ie use the N1MM Function Keys to send?  - does not currently work. I've tried various combinations of COM Ports in N1MM, no luck. The manual seems to hint at needed to do this via the USB connection on the Control RRC?

Thanks, John K3TN

23
Configuration, RRC 1258 / Question on Serial Settings
« on: 2014-06-20, 19:21:10 »
I've gotten a pair of RRCs working on the local LAN,  the goal is a PC-based Remote Control application. FT-1000 at the radio side, connected per the Yaeus section. On the Control side, a PC with no serial port, so USB to the Control RRC. The PC at the control end will run N1MM and/or Ham Radio Deluxe and need to control the and CW key the remote FT-1000.

To make that work, I will need to control PC to talk to the Radio CAT and to think there is Winkeyer at the radio end.

Tested all audio/CW/PTT functions on the local LAN, works fine with microphone and paddle connected to the Control RRC. Had the wrong (male to female) DB9 serial cable, so couldn't test the Radio RRC connection to the FT-1000 yet.

I'm confused about the serial settings beyond the 4800 8N2 for the Yaesu CAT. I am assuming COM 1 Mode 6 is correct, with Use USB Com Port for COM1? If so, would I then configure N1MM to use Com 1 for CAT of the remote radio?

Similar question for COM 2 serial setup: I assume I use Mode 6, and tell N1MM that Winkey is on COM2? And also set Use USB Com Port for COM@?

Any other settings needed I haven't listed?

Final question: the manual and setting mention Telnet and port 23 quite a bit, but the firewall/port forwarding section never mention putting in a rule for Telnet/port 23 - is such a rule required?

Thanks, John K3TN

24
Getting RRCs going on local LAN, with latest firmware installed. Will be used for a remote Windows XP PC operation of a FT-1000 with N1MM and maybe DXLab Commander at the Control end eventually.

I've gotten the basic functionally working locally - TX/RX audio, PTT, CW keying etc. Now want to get the computer connection running.

When I installed the Microbit Setup Manager and then connected each RRC, a number of virtual com port drivers seemed to be installed with each one, I had to click through Windows warnings of non-compliant drivers, etc). Reading W1UE's thread, I see I should see COM 0-3 in Device Manager but I don't.

I see a COM1, no COM0 and nothing that seems to say RRC or Microbit.

This PC has a MicroHam Microkeyer attached, so has a lot of Eltima virtual ports, mostly higher numbered (above 12) but does show Eltima 2, 3 which might be a conflict? Do I need to not run the Microham Router software to make this work?

What actually should I see in Device Manager if the Microbit virtual ports are installed and operating correctly?

73 John K3TN

Pages: 1 [2]