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

Pages: 1 2 3 [4] 5
46
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

47
Is there some reason the RRC software/protocol would handle those commands differently than anything else?

That command string works in a directly connected setup, doesn't work when the RRCs are between N1MM and the K3. The {END} and {CATDELAY} macros should not really travel over the RRC connection - the {END} tells the N1MM software to wait until CW is done before executing any following commands. {CATDELAY" tells the N1MM software to wait x milliseconds before doing anything following.

So, the CAT1ASC value of SWT11; is really the only thing that gets sent over the RRC "wire".  But it appears to rarely get to the K3. I've tried very long delay values, doesn't seem to change the problem.

I have F9 as a dedicated VFO swap key that sends the CAT1ASC SWT11; command by itself - that works fine.

It appears that sending Winkey CW and then trying to send an ASCII command does NOT work, yet I have K3 commands like CLEARRIT after CW strings and that works.

Is there something about the ; that might honk things up in the RRC handling?

48
It shouldn't be the dynamic vs. electret thing, as the same headset works FB directly connected to the K3 and also works FB now when connected to the Control RRC vs the Mini!

How do you connect the CM500 to your Mini? Are you using the front panel circular connector and headphone jack?

49
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

50
I ran the latest beta firmware in the 4 hour NA CW Sprint this past Saturday night. That contest hardware and software the most of any contest (although only over 4 hours) as there is constant QSYing and calling and speeds are 30+ wpm. I made 290 QSOs in my first remote effort, down a bit from when I am physically at the station but i think the speed of the Sprint does penalize  you for any delays.

I had one N1MM+ crash - a bad one, related to moving between entry window boxes when hitting enter - that I don't think had anything to do with RemoteRig.

The CW sending worked flawlessly - type ahead worked, hitting F1 or Enter multiple times never failed, etc. - fantastic.

One possible small thing: it seems when I first start N1MM+,nothing happens the first time I hit an Fkey. The second time it works and then works continuously there after.

On the END, CATDELAY and CAT1ASC issues - I left those in and during the 4  hours there were perhaps 3-5 times when those commands worked! So, sometimes they are getting passed on to the K3 but very rarely.

Once again, thanks for all the effort on the WinKey sending with N1MM+ - if I couldn't break it during the CW Sprint, it is pretty hard to break!

73 John K3TN

51
I am not seeing the crashing after a few characters of sending, but tonight will get a major test in the 4 hour NA Sprint!

52
Jan - very quick test here at lunch time: that build seems to have fixed the WinKey pot issue. I can choose to ignore the pot, or only use it for paddle and keyboard and use N1MM for Fkey speed!

It also seems to have fixed the "need to send a dit" issue in my last post! Tried that several times, seems to be working. Will pound on it more since the CW Sprint is tomorrow night and want to be rock solid.

It did *not* however solve the {END}{CAT1ASC} issue in my other post :(

Thanks for all these rapid fixes!

73 John K3TN

53
Thanks, Jan - i will load that version and try. I think I have also found another CW keying problem, perhaps this is related:

In N1MM+, in S&P mode in a Sprint contest I answer a CQ by hitting enter and it sends my call. The other station sends their info, I enter it and hit enter - N1MM+ sends my info by sending the F2 exchange message. I wait for the other station to acknowledge, he does and I hit enter which should send CQ - nothing happens. No Fkeys work - unless I hit a dit on the paddle and then the CQ starts.

The F2 message ends in the {RUN} macro, which tells N1MM+ to go to RUN mode - it does that. But that seems to then prevent Fkeys from sending unless I hit the paddle. I also found if a put a spurious character (like an e for a single dit) after the {RUN} command, it would send that dit and then the F Keys *would* work - just as if I hit the paddle!

Or this might be related to my other posted problem, where using the {END} and {CAT1ASC} macros seem to prevent cw from being sent.

54
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

55
Yes, agree - that crash was probably an N1MM crash.

Been playing with it a lot - I have hit a WinKey issue: N1MM has CW speed control and WinKey has a potentiometer for speed control. There seems to be some interaction happening - change speed on N1MM and it starts a message at the N1MM speed but then starts sending at the RRC CW potentiometer setting, or just ignores one of the other.

N1MM has a "ignore WinKey speed control" setting. Tried turning that on but doesn't seem to cure the problem.

Is there a RRC setting to essentially disable the hardware speed control? Or have programmatic control take precedence cleanly?

56
The "all of a sudden" I mentioned really meant "the first time I used N1MM+ in a contest where I called CQ, the problem happened..."!

I loaded the latest 2.85 beta and it seems to have fixed the problem - if I am calling CQ and K4RUM calls me,  I can type in K4RU hit enter. N1MM will start to send and I can enter the last letter M and N1MM+ will send K4RUM - all is good.

I tested it out a bit last night in the CWT test it worked fine, but I was able to cause one bad crash. Not quite sure, I couldn't seem to repeat it, but it crashed N1MM and trashed my Com Ports, had to restart PC.

I *think* the actions that caused the crash: I called CQ (hitting F1), W3ABC answers. I start typing W3AB and then hit SPACEBAR by mistake, which advances cursor to next entry box (in this case that is the NAME field). Hitting SPACEBAR doesn't not initiate response, so I hit ENTER key - kerplooey. The ability to keep entering a callsign while CW is being sent I think should only happen after the ENTER key or LOG command is given - the cursor is still in the callsign entry box. If the cursor has been advanced, should not be going back to callsign  buffer unless cursor was moved back there.

I dunno if that makes sense - tonight will try it again in the NS Sprint and see what happens.

Thanks for all the updates on this.

73 John K3TN

57
The "all of a sudden" I mentioned really meant "the first time I used N1MM+ in a contest where I called CQ, the problem happened..."!

I loaded the latest 2.85 beta and it seems to have fixed the problem - if I am calling CQ and K4RUM calls me,  I can type in K4RU hit enter. N1MM will start to send and I can enter the last letter M and N1MM+ will send K4RUM - all is good.

I tested it out a bit last night in the CWT test it worked fine, but I was able to cause one bad crash. Not quite sure, I couldn't seem to repeat it, but it crashed N1MM and trashed my Com Ports, had to restart PC.

I *think* the actions that caused the crash: I called CQ (hitting F1), W3ABC answers. I start typing W3AB and then hit SPACEBAR by mistake, which advances cursor to next entry box (in this case that is the NAME field). Hitting SPACEBAR doesn't not initiate response, so I hit ENTER key - kerplooey. The ability to keep entering a callsign while CW is being sent I think should only happen after the ENTER key or LOG command is given - the cursor is still in the callsign entry box. If the cursor has been advanced, should not be going back to callsign  buffer unless cursor was moved back there.

I dunno if that makes sense - tonight will try it again in the NS Sprint and see what happens.

Thanks for all the updates on this.

73 John K3TN

58
I am going to load this beta, as just ran into the problem today in the CWT contest. All of a sudden N1MM CW send would not work the way it used to  - if I hit Enter to start sending and kept typing in remainder of the call, it would not send the additional characters. I will try this beta tonight.
73 John K3TN

59
Hi, Mitch - I'd like a copy of that checklist as well. I'd be glad to download if it is online somewhere, or you can email to jpescatore at aol dot com.

I'm in the final stages of getting a K3/Mini to control my K3 at a remote site. it is a 120 mile round trip, so the checklist may help me from yet another oops return trip!

73 John K3TN

60
Thanks! Will load here today.

73 John K3TN

Pages: 1 2 3 [4] 5