Date   

Re: N1MM/K3/Remoterig/Win10 comm problem

SM0MDG
 

Maybe I should have mentioned this right away; My connection is pretty stable, DSL at the station and cable in the remote end. Ping times 25-30 ms with very few dropouts. Nothing changed in the connection over the past years. 

Yes, I had the occasional drop ut once in a while. What I am seeing now is something completely different. It happens several times per hour, and if N1MM+ is sitting idle it just freeze up. The biggest change I made was moving to N1MM+.

Since yesterday I have Win-Test running on the computer and it has a stable connection with the K3/Remoterig combo. No drop outs except when Windows decided to automatically update and reboot (have to turn that “feature” off!).

73 de Björn,
SM0MDG
SE0X


Re: N1MM/K3/Remoterig/Win10 comm problem

jpescatore@...
 

At the K4VV/W4AAW remote operation, we've invariably found this type of problem to be bandwidth/traffic driven.

If you are hearing any audio dropouts, you are having packet loss and may have N1MM connectivity problems just as you're having audio problems. If you are doing PTT keying, you'll hear scrambled CW. If you are doing Winkey, you will usually hear speed varying CW. (I tested this out over the air with Shin JA1NUT, as the ultimate CW tester, and he would say "John - you are having brainstorms again" when Winkey sending would go from dead air to really fast...

I'm sure the N1MM+ internal networking capabilities/robustness will continue to evolve but the RRC can't re-insert lost packets so there is no reason to expect the N1MM+ software will either.

Obviously, the ideal solution is  enough bandwidth so that you don't have latency problems and/or dropouts. However, what you really care about is how much bandwidth the RemoteRig and audio gets - you don't necessarily need a larger/faster Internet pipe.

Many routers have Quality of Service functions where you can reserve bandwidth for certain ports/services. This allows you to starve web browsing or video streaming when bandwidth is tight, and preserve bandwidth for the RRC ports/services. It may piss off the rest of your family or whoever shares the radio-side Internet connectivity, but they can go read a book...

At W4AAW (where K4VV remote operations were moved after K4VV shut down) we are using an ASUS router and Rick N1RM configured the QOS parameters to give the SIP and UDP ports 200 Kbs guaranteed bandwidth, about twice what our peak usage is with 3 stations running. Has been working great - no more audio blippies, much less popping up of the N1MM window "Lost Connection With the Radio"

However, that window does still occasionally pop-up and have to retry/re-establish occasionally.

Also, there are still issues over the RRC connection using N1MM FKeys that mix messages and macros. I brought this issue up to Microbit last  year, but I don't think enough people were hitting that so hasn't been fixed on their end, which is where the issue appears to be.

73 John K3TN


Re: Why am I getting Telnet cluster "Connection error occurred"?

Vytenis LY5T
 

Hi Thomas,

Most often this happens due to firewall preventing to pass traffic to/from telnet clusters. Built in windows firewall or user installed as a separate or integrated with antivirus. I would recommend temporary to disable all firewalls for 5 minutes and test dx cluster connectivity again.

Vytenis
ly5t


Re: Printed Dupe Sheets

Dave Hachadorian
 

Jim,
 
Can you hit the printscreen button on the keyboard (copies what’s on the screen to the clipboard), then open Microsoft  Paint and paste the clipboard contents in there, and print it?  What about an el cheapo inverter to run the laptop on AC?  Might cause QRN though.
 
Dave, K6LL
 

Sent: Thursday, February 18, 2016 8:18 PM
Subject: [N1MMLoggerplus] Printed Dupe Sheets
 
 

Tonight I pulled out my old, seldom used but for contests, laptop to find it dead. (It is my only one for which I have a DC--DC supply).

I'm planning to take the KX3 to salt water for the ARRL DX contest this weekend. I can send with the standalone WinKey and log on paper (not hard when doing all S&P). I would, however, be able to type in my contacts during breaks back home (other computer) and then generate a paper dupe sheet for the following operating session.

Is there a way to do this? The visible dupesheet window does not seem to lend itself to printing, copy&paste, etc.


73  -  Jim  K8MR


Re: Printed Dupe Sheets

Jim Stahl K8MR
 

I don't see anything there about generating a readily readable dupesheet (which would need to be by band) -  ??


73  -  Jim   K8MR




-----Original Message-----
From: gbyahoo@... [N1MMLoggerplus] To: N1MMLoggerplus
Sent: Thu, Feb 18, 2016 11:10 pm
Subject: [N1MMLoggerplus] Re: Printed Dupe Sheets

 
Jim,

I think this is what you are after.


>> Gerald, VE1DT



---In N1MMLoggerplus@..., wrote :

Tonight I pulled out my old, seldom used but for contests, laptop to find it dead. (It is my only one for which I have a DC--DC supply).

I'm planning to take the KX3 to salt water for the ARRL DX contest this weekend. I can send with the standalone WinKey and log on paper (not hard when doing all S&P). I would, however, be able to type in my contacts during breaks back home (other computer) and then generate a paper dupe sheet for the following operating session.

Is there a way to do this? The visible dupesheet window does not seem to lend itself to printing, copy&paste, etc.


73  -  Jim  K8MR
_


Re: N1MM/K3/Remoterig/Win10 comm problem

James Sharp
 

I have this problem as well. But find that it is the internet service provider that isn't providing a smooth connection either at the remote or control location. Having contacted them, (two different providers) and checking out their feeds, they both at some time or other had issues that caused the dropouts.  I could still do all the traditional things like downloading web pages, email, or voip phone. It also manifested itself with dropouts in voip phone conversations.

I am using a K3 Mini to a remote K3 and the remote rig twins. I also have Win 10 on both remote and control, but they are not a factor.

Good luck, 73, Jim - W5AP


Re: Printed Dupe Sheets

gbyahoo@...
 

Jim,

I think this is what you are after.


>> Gerald, VE1DT



---In N1MMLoggerplus@..., <jimk8mr@...> wrote :

Tonight I pulled out my old, seldom used but for contests, laptop to find it dead. (It is my only one for which I have a DC--DC supply).

I'm planning to take the KX3 to salt water for the ARRL DX contest this weekend. I can send with the standalone WinKey and log on paper (not hard when doing all S&P). I would, however, be able to type in my contacts during breaks back home (other computer) and then generate a paper dupe sheet for the following operating session.

Is there a way to do this? The visible dupesheet window does not seem to lend itself to printing, copy&paste, etc.


73  -  Jim  K8MR


Printed Dupe Sheets

Jim Stahl K8MR
 

Tonight I pulled out my old, seldom used but for contests, laptop to find it dead. (It is my only one for which I have a DC--DC supply).

I'm planning to take the KX3 to salt water for the ARRL DX contest this weekend. I can send with the standalone WinKey and log on paper (not hard when doing all S&P). I would, however, be able to type in my contacts during breaks back home (other computer) and then generate a paper dupe sheet for the following operating session.

Is there a way to do this? The visible dupesheet window does not seem to lend itself to printing, copy&paste, etc.


73  -  Jim  K8MR


Re: N1MM/K3/Remoterig/Win10 comm problem

Skip
 

I run RemoteRig with a K3/100 control to a K3/100-KPA500 remote radio at W7RN. The IP connection reliability varies some with occasional dropped packets on RX. N1MM+ [on Win10] at my control site seems to work OK, but it occasionally loses contact with the radio at W7RN as you describe. In practically all cases, one RETRY will restore normal operation.

I don't really *know* what is happening, but all the evidence points to IP dropouts, suggesting that N1MM+ may be a bit too demanding in it's poll/response protocol. When I experience an increase in audio dropouts in the headphones, the probability of the N1MM+ error seems to increase too.

It's not really a problem for me, just annoying. Incidentally, not all so-called "dropped packets" actually go in some unknown bit-bucket. At 30 WPM, with the RR parameters I'm running, a single dit seems to fit into a packet. Often the dit is just missing, but occasionally, it gets delivered to the CODEC out of sequence, changing an R to a D for example. :-)

73,

Fred K6DGW
- Northern California Contest Club
- CU in the Cal QSO Party 1-2 Oct 2016
- www.cqp.org

On 2/18/2016 1:08 PM, bjorn@sm0mdg.com [N1MMLoggerplus] wrote:
I have a problem that showed up a few months ago. I am not really sure
which party to blame. I am using a K3/0 to K3 connection via Remoterig.
Everything is running under Windows 10. Logging is done in the remote
control end and serial speed is set to 9600. My problem is that the
serial connection between the K3 and N1MM is extremely unstable. If I
leave the computer sitting idle N1MM crashes after 5-10 minutes. Every time!


Another strange effect is that N1MM+ sometimes confuse the A/B VFO
frequencies when polling the K3. Sometimes N1MM+ also seems to get a
plain wrong frequency adjusting itself after this and being totally out
of sync with the K3.

For the past years I have used the same setup with N1MM and XP, even
running in a virtual machine under parallels. It was always flawless!
The two new parameters are Win10 and N1MM+. This week I installed a
fresh Windows 7 copy on a Mac Mini running under Bootcamp and I still
have this problem. So the only new parameter is N1MM+ and whatever
updates been done to the firmware in Remtoterig.

Because this seems to be a communications problem I have tried reducing
the polling rate in N1MM and many other things too, but nothing really
helps.

I am now at the point where I will have to try Win-Test to see if the
problem persists with another software package.

I wonder if anyone else have experienced this and found a solution?

73 de Björn,
*SM0MDG*
SE0X


N1MM/K3/Remoterig/Win10 comm problem

SM0MDG
 

I have a problem that showed up a few months ago. I am not really sure which party to blame. I am using a K3/0 to K3 connection via Remoterig. Everything is running under Windows 10. Logging is done in the remote control end and serial speed is set to 9600. My problem is that the serial connection between the K3 and N1MM is extremely unstable. If I leave the computer sitting idle N1MM crashes after 5-10 minutes. Every time!


Another strange effect is that N1MM+ sometimes confuse the A/B VFO frequencies when polling the K3. Sometimes N1MM+ also seems to get a plain wrong frequency adjusting itself after this and being totally out of sync with the K3.

For the past years I have used the same setup with N1MM and XP, even running in a virtual machine under parallels. It was always flawless! The two new parameters are Win10 and N1MM+. This week I installed a fresh Windows 7 copy on a Mac Mini running under Bootcamp and I still have this problem. So the only new parameter is N1MM+ and whatever updates been done to the firmware in Remtoterig.

Because this seems to be a communications problem I have tried reducing the polling rate in N1MM and many other things too, but nothing really helps.

I am now at the point where I will have to try Win-Test to see if the problem persists with another software package.

I wonder if anyone else have experienced this and found a solution?

73 de Björn,
SM0MDG
SE0X



Re: Orion 565 UCW vs LCW?

Peter Alterman W2CDO
 

Gerald, that's certainly possible. It's been a long time.
Yes John, that's the way my Mark V has been working for ~15 years (see Gerald's suggestion). 
Got the memo now, thanks. 
Peter


To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 15:33:32 -0500
Subject: Re: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 


On Feb 18, 2016, at 15:22, Peter Alterman w2cdo@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

Yes Rich, that's how it works.
The conventions about sidebands apply to CW as well as SSB.

Where is that written?

That's why my transceiver switches from one to the other when I  change bands manually.

The whim of the developer. What transceiver? Are you saying that in your rig, for CW the receiver listens in USB for the upper bands and LSB for the lower bands? (It will not affect your transmitted CW signal at all.)

73,

John K8AJS





Re: Orion 565 UCW vs LCW?

John E Bastin <bastinj@...>
 


On Feb 18, 2016, at 15:22, Peter Alterman w2cdo@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

Yes Rich, that's how it works.
The conventions about sidebands apply to CW as well as SSB.

Where is that written?

That's why my transceiver switches from one to the other when I  change bands manually.

The whim of the developer. What transceiver? Are you saying that in your rig, for CW the receiver listens in USB for the upper bands and LSB for the lower bands? (It will not affect your transmitted CW signal at all.)

73,

John K8AJS




Re: Orion 565 UCW vs LCW?

gbyahoo@...
 

Peter,

Are you sure you haven't just configured the settings on your radio that way and the radio remembers them that way for you?

Also, as far as I know, there is no such thing as the "guy calling on the other sideband". Changing between CW and CW-Reverse or ucw vs lcw only applies to receiving.

>> Gerald, VE1DT


---In N1MMLoggerplus@..., <w2cdo@...> wrote :

Yes Rich, that's how it works.
The conventions about sidebands apply to CW as well as SSB. That's why my transceiver switches from one to the other when I  change bands manually. That distinction may have changed but I didn't get the memo.
73, 
Peter W2CDO 



To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 11:45:31 -0800
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 
"Follow the conventions"? I don't follow. The convention about sidebands above and below 10 MHz applies to SSB. AFAIK it has nothing to do with CW (or digital modes).

If you are tuned in exactly to a CW signal, it will sound the same in both sidebands. The difference is only heard in signals that are not on exactly the same frequency as yours. If you are CQing, if an off-frequency signal is higher in frequency than yours is, it will sound higher in pitch than your sidetone in UCW, whereas it will sound lower in pitch than your sidetone in LCW. On the other hand, if it is lower in frequency than yours is, it will be the opposite (lower in pitch in UCW and higher in pitch in LCW). Assuming errors are equally likely to be in both directions, it doesn't matter which sideband you pick, half the off-frequency signals will sound higher than your sidetone and half will sound lower. The only difference is in which signals will be in which half.

Seems to me that the place where the difference is most likely to be noticed is when you are S&Ping and tuning across the band. In UCW, if you tune upwards, signals first appear at high pitch and drop in pitch as you tune. If you tune downwards, signals first appear at low pitch and climb in pitch as you tune. In LCW, it's the opposite. If you always tune in the same direction and the direction of the change in pitch matters to you, you might prefer one sideband over the other, but if so, your preference should be the same on all bands. I can't think of a good reason why you would want it to be different on different bands, unless you use the direction of pitch change as a mnemonic to remind you which band you are S&Ping on.

I can more easily see wanting to switch sidebands whenever you change from tuning upwards to tuning downwards, as Eric suggested, but that is independent of which band you are on.

73,
Rich VE3KI




---In N1MMLoggerplus@..., <w2cdo@...> wrote :

I'm the other op so let me answer both questions. First, the reason to change from lcw to ucw is to follow the conventions. Not so important during S&P but when running on a crowded band with the filters screwed down to 200 Hz the guy calling on the other sideband is, at best, harder to copy.  Second, yes, John, I reconfig for reverse CW but that needs to be done whenever you go from 20 to 40 or 40 to 20 *if you follow the conventions* and that's not a really convenient thing to do in the heat of battle.  All that said, I know a lot of contesters simply stay in ucw regardless of band but I'd prefer my software to follow the conventions.

regards,  Peter W2CDO


To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 12:40:51 -0500
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 




Eric,
Use the Config, Other tab option for reverse CW.

John, K3CT 

-------- Original message --------
From: "Eric Rosenberg ericrosenberg.dc@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
Date: 2/18/2016 11:55 AM (GMT-05:00)
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 

One of our ops passed along this problem with N1MM+ and my Orion 565. The Orion lets you choose UCW (upper cw) or LCW (lower cw) as your mode. While I tend to leave it in one position or the other for all bands, many choose to the follow the phone band conventions (160-40 = LCW; 20-10 = UCW).

"I noticed the Orion was in UCW instead of LCW.  I would change the mode manually but N1MM+ would switch it back to UCW every time I pressed a button." 

"I have the same problem with MM+ on my Mark V and the developers haven't addressed the need for radios to shift from Lower to Upper sideband when moving up the bands and vice versa when moving down the bands."
Is there a solution to this or should i just leave it one way or the other?
73,

Eric W3DQ





Re: Orion 565 UCW vs LCW?

Peter Alterman W2CDO
 

Yes Rich, that's how it works.
The conventions about sidebands apply to CW as well as SSB. That's why my transceiver switches from one to the other when I  change bands manually. That distinction may have changed but I didn't get the memo.
73, 
Peter W2CDO 



To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 11:45:31 -0800
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 
"Follow the conventions"? I don't follow. The convention about sidebands above and below 10 MHz applies to SSB. AFAIK it has nothing to do with CW (or digital modes).

If you are tuned in exactly to a CW signal, it will sound the same in both sidebands. The difference is only heard in signals that are not on exactly the same frequency as yours. If you are CQing, if an off-frequency signal is higher in frequency than yours is, it will sound higher in pitch than your sidetone in UCW, whereas it will sound lower in pitch than your sidetone in LCW. On the other hand, if it is lower in frequency than yours is, it will be the opposite (lower in pitch in UCW and higher in pitch in LCW). Assuming errors are equally likely to be in both directions, it doesn't matter which sideband you pick, half the off-frequency signals will sound higher than your sidetone and half will sound lower. The only difference is in which signals will be in which half.

Seems to me that the place where the difference is most likely to be noticed is when you are S&Ping and tuning across the band. In UCW, if you tune upwards, signals first appear at high pitch and drop in pitch as you tune. If you tune downwards, signals first appear at low pitch and climb in pitch as you tune. In LCW, it's the opposite. If you always tune in the same direction and the direction of the change in pitch matters to you, you might prefer one sideband over the other, but if so, your preference should be the same on all bands. I can't think of a good reason why you would want it to be different on different bands, unless you use the direction of pitch change as a mnemonic to remind you which band you are S&Ping on.

I can more easily see wanting to switch sidebands whenever you change from tuning upwards to tuning downwards, as Eric suggested, but that is independent of which band you are on.

73,
Rich VE3KI




---In N1MMLoggerplus@..., wrote :

I'm the other op so let me answer both questions. First, the reason to change from lcw to ucw is to follow the conventions. Not so important during S&P but when running on a crowded band with the filters screwed down to 200 Hz the guy calling on the other sideband is, at best, harder to copy.  Second, yes, John, I reconfig for reverse CW but that needs to be done whenever you go from 20 to 40 or 40 to 20 *if you follow the conventions* and that's not a really convenient thing to do in the heat of battle.  All that said, I know a lot of contesters simply stay in ucw regardless of band but I'd prefer my software to follow the conventions.

regards,  Peter W2CDO


To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 12:40:51 -0500
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 




Eric,
Use the Config, Other tab option for reverse CW.

John, K3CT 

-------- Original message --------
From: "Eric Rosenberg ericrosenberg.dc@... [N1MMLoggerplus]"
Date: 2/18/2016 11:55 AM (GMT-05:00)
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 

One of our ops passed along this problem with N1MM+ and my Orion 565. The Orion lets you choose UCW (upper cw) or LCW (lower cw) as your mode. While I tend to leave it in one position or the other for all bands, many choose to the follow the phone band conventions (160-40 = LCW; 20-10 = UCW).

"I noticed the Orion was in UCW instead of LCW.  I would change the mode manually but N1MM+ would switch it back to UCW every time I pressed a button." 

"I have the same problem with MM+ on my Mark V and the developers haven't addressed the need for radios to shift from Lower to Upper sideband when moving up the bands and vice versa when moving down the bands."
Is there a solution to this or should i just leave it one way or the other?
73,

Eric W3DQ





Using the computer's proxy

Kevin Timm
 

I have installed N1MM+ but the machine is behind a proxy so I cannot get to the telnet servers.  Is there a way to set N1MM+ to utilize my system/default Internet proxy server?

73 de K5KDT



Re: Orion 565 UCW vs LCW?

ve3ki@...
 

"Follow the conventions"? I don't follow. The convention about sidebands above and below 10 MHz applies to SSB. AFAIK it has nothing to do with CW (or digital modes).

If you are tuned in exactly to a CW signal, it will sound the same in both sidebands. The difference is only heard in signals that are not on exactly the same frequency as yours. If you are CQing, if an off-frequency signal is higher in frequency than yours is, it will sound higher in pitch than your sidetone in UCW, whereas it will sound lower in pitch than your sidetone in LCW. On the other hand, if it is lower in frequency than yours is, it will be the opposite (lower in pitch in UCW and higher in pitch in LCW). Assuming errors are equally likely to be in both directions, it doesn't matter which sideband you pick, half the off-frequency signals will sound higher than your sidetone and half will sound lower. The only difference is in which signals will be in which half.

Seems to me that the place where the difference is most likely to be noticed is when you are S&Ping and tuning across the band. In UCW, if you tune upwards, signals first appear at high pitch and drop in pitch as you tune. If you tune downwards, signals first appear at low pitch and climb in pitch as you tune. In LCW, it's the opposite. If you always tune in the same direction and the direction of the change in pitch matters to you, you might prefer one sideband over the other, but if so, your preference should be the same on all bands. I can't think of a good reason why you would want it to be different on different bands, unless you use the direction of pitch change as a mnemonic to remind you which band you are S&Ping on.

I can more easily see wanting to switch sidebands whenever you change from tuning upwards to tuning downwards, as Eric suggested, but that is independent of which band you are on.

73,
Rich VE3KI




---In N1MMLoggerplus@..., <w2cdo@...> wrote :

I'm the other op so let me answer both questions. First, the reason to change from lcw to ucw is to follow the conventions. Not so important during S&P but when running on a crowded band with the filters screwed down to 200 Hz the guy calling on the other sideband is, at best, harder to copy.  Second, yes, John, I reconfig for reverse CW but that needs to be done whenever you go from 20 to 40 or 40 to 20 *if you follow the conventions* and that's not a really convenient thing to do in the heat of battle.  All that said, I know a lot of contesters simply stay in ucw regardless of band but I'd prefer my software to follow the conventions.

regards,  Peter W2CDO


To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 12:40:51 -0500
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 




Eric,
Use the Config, Other tab option for reverse CW.

John, K3CT 

-------- Original message --------
From: "Eric Rosenberg ericrosenberg.dc@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
Date: 2/18/2016 11:55 AM (GMT-05:00)
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 

One of our ops passed along this problem with N1MM+ and my Orion 565. The Orion lets you choose UCW (upper cw) or LCW (lower cw) as your mode. While I tend to leave it in one position or the other for all bands, many choose to the follow the phone band conventions (160-40 = LCW; 20-10 = UCW).

"I noticed the Orion was in UCW instead of LCW.  I would change the mode manually but N1MM+ would switch it back to UCW every time I pressed a button." 

"I have the same problem with MM+ on my Mark V and the developers haven't addressed the need for radios to shift from Lower to Upper sideband when moving up the bands and vice versa when moving down the bands."
Is there a solution to this or should i just leave it one way or the other?
73,

Eric W3DQ




Re: N1MM+ runtime error

Rick Ellison
 

Glad we were able to figure that one out..

73 Rick N2AMG

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Thursday, February 18, 2016 1:44 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] N1MM+ runtime error

 

 

Hi Rick
I'm now running  L+ as administrator and can now swap between mmtty & mmvari no problem.

Thanks for you help.

Steve /GM4OSS

On 18 Feb 2016 17:47, "Bill Woodroffe billwoodroffe@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:

 

Hi Rick,

 

Thanks. No I wasn't running  as Administrator

 

I updated the software and got the same failure, I then ran N1MM Plus in Administrator mode  and it all worked ok.

 

Apologies for any inconvenience and thanks for putting me straight,

 

73,

 

Bill

M0TDW

 

 

 

On Thu, Feb 18, 2016 at 5:30 PM, Rick Ellison rellison@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Hi Bill..

I have never been able to reproduce this as many times that it has been reported..

What are you doing just before this error message opens up?

Can you reproduce this easily?

Are you running N1MM+ as Administrator or normal?? Anything that will help me reproduce this here..

 

73 Rick N2AMG

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Thursday, February 18, 2016 11:48 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] N1MM+ runtime error

 

 

Error message I received below:-

 

73,

 

Bill

M0TDW

 

 

 

 

N1MMLogger.net - Version 1.0.5472.0

Built: 09-Feb-16 11:36:16 AM

Microsoft Windows NT 6.2.9200.0,64:1,en-US,en-US

Error occurred at: 18-Feb-16 4:41:57 PM in Thread: 

---------------------------------------------------------------------------------------

System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.

   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)

   at MMVARILib._DMMVARI.set_bActive(Boolean )

   at AxMMVARILib.AxMMVARI.set_bActive(Boolean value)

   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 791

---------------------------------------------------------------------------------------

 

 

Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

   at System.Environment.get_StackTrace()

   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 58

   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 211

   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 828

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)

   at System.Windows.Forms.Control.Show()

   at N1MMLogger.Net.DigitalInterface.InitPSKInterface() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 3261

   at N1MMLogger.Net.DigitalInterface.PSKRTTYSwap(Int32 Mode, Int16 Control) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 6174

   at N1MMLogger.Net.DigitalInterface.mnuInterfaceSelectionMMVARI_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 4856

   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ToolStrip.WndProc(Message& m)

   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82

 

On Wed, Feb 17, 2016 at 8:47 PM, GM4OSS stevegm4oss@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Hi Bill

It's Windows 10 I'm running. Appreciate any info/help you can send.

Steve/GM4OSS

 

On Wed, Feb 17, 2016 at 7:43 PM, Bill Woodroffe billwoodroffe@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

I had the same issue switching in the contest, running Windows 10, happy to send the failure if required.

73,

Bill
M0TDW

On 17 Feb 2016 15:54, "GM4OSS stevegm4oss@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:

 


Hi

I entered the RSGB 80M CC data contest for first time 2016 where you can work stations on both RTTY & PSK63 on 80M band.

Set up, K3/P3, MK2, N1MM+ with MMTTY for RTTY & MMVARI for PSK63. The error pasted below happens when I swap from MMTTY to MMVARI but not the other way around. MMVARI window does open but with nothing showing in waterfall. I then close DI window then reopen DI and an odd time MMVARI will be OK (no error).

I used this setup last years run of RSGB 80M CC test with no issues so not sure if this is a N1MM problem or not. Don't think my setup has changed but would appreciate any advice to what's causing this.

Steve/GM4OSS

N1MMLogger.net - Version 1.0.5481.0
Built: 2/16/2016 8:15:10 PM
Microsoft Windows NT 6.2.9200.0,64:1,en-GB,en-GB
Error occurred at: 2/17/2016 11:05:05 AM in Thread:
---------------------------------------------------------------------------------------
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
   at MMVARILib._DMMVARI.set_bActive(Boolean )
   at AxMMVARILib.AxMMVARI.set_bActive(Boolean value)
   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 791
---------------------------------------------------------------------------------------


Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 58
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 211
   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 828
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Control.Show()
   at N1MMLogger.Net.DigitalInterface.InitPSKInterface() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 3261
   at N1MMLogger.Net.DigitalInterface.DigitalInterface_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 2050
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Control.Show()
   at N1MMLogger.Net.EntryWindow.mnu_WindowDigitalInterface1_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 16577
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82
--

73 de Steve GM4OSS




--

73 de Steve GM4OSS

 

 


Re: Sending call every (n) QSOs

DL7VOG
 

There is a way - maybe not absolutely correct after ARRL-rules but if you run a pileup since hours most of the guys know your call and if you give your call after every third QSO - like I mostly do, it seems to be enough. Of course in a contest it's another league. But in a normal pileup  you may change your F3 macro to

F3 Tu,{VARYMSG1 &TU&TU *&3&}

That will do.

73 and gl de Gerd / DL7VOG  -  In May/June I will do so as FM/DL7VOG and J68GU

www.dl7vog.de
www.qslnet.de/hk0gu
www.qslnet.de/c6aka
www.qslnet.de/zf2gu
Am 18.02.2016 um 16:07 schrieb 'Gregg W6IZT' gregg.w6izt@... [N1MMLoggerplus]:

 

Is there a way in L+ to configure sending your call after every (n) Qs in run?

 

Gregg W6IZT



Re: Orion 565 UCW vs LCW?

Peter Alterman W2CDO
 

I'm the other op so let me answer both questions. First, the reason to change from lcw to ucw is to follow the conventions. Not so important during S&P but when running on a crowded band with the filters screwed down to 200 Hz the guy calling on the other sideband is, at best, harder to copy.  Second, yes, John, I reconfig for reverse CW but that needs to be done whenever you go from 20 to 40 or 40 to 20 *if you follow the conventions* and that's not a really convenient thing to do in the heat of battle.  All that said, I know a lot of contesters simply stay in ucw regardless of band but I'd prefer my software to follow the conventions.

regards,  Peter W2CDO


To: N1MMLoggerplus@...
From: N1MMLoggerplus@...
Date: Thu, 18 Feb 2016 12:40:51 -0500
Subject: RE: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 




Eric,
Use the Config, Other tab option for reverse CW.

John, K3CT 

-------- Original message --------
From: "Eric Rosenberg ericrosenberg.dc@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
Date: 2/18/2016 11:55 AM (GMT-05:00)
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] Orion 565 UCW vs LCW?

 

One of our ops passed along this problem with N1MM+ and my Orion 565. The Orion lets you choose UCW (upper cw) or LCW (lower cw) as your mode. While I tend to leave it in one position or the other for all bands, many choose to the follow the phone band conventions (160-40 = LCW; 20-10 = UCW).

"I noticed the Orion was in UCW instead of LCW.  I would change the mode manually but N1MM+ would switch it back to UCW every time I pressed a button." 

"I have the same problem with MM+ on my Mark V and the developers haven't addressed the need for radios to shift from Lower to Upper sideband when moving up the bands and vice versa when moving down the bands."
Is there a solution to this or should i just leave it one way or the other?
73,

Eric W3DQ




Re: N1MM+ runtime error

GM4OSS
 

Hi Rick
I'm now running  L+ as administrator and can now swap between mmtty & mmvari no problem.

Thanks for you help.

Steve /GM4OSS

On 18 Feb 2016 17:47, "Bill Woodroffe billwoodroffe@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:
 

Hi Rick,

Thanks. No I wasn't running  as Administrator

I updated the software and got the same failure, I then ran N1MM Plus in Administrator mode  and it all worked ok.

Apologies for any inconvenience and thanks for putting me straight,

73,

Bill
M0TDW



On Thu, Feb 18, 2016 at 5:30 PM, Rick Ellison rellison@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:
 

Hi Bill..

I have never been able to reproduce this as many times that it has been reported..

What are you doing just before this error message opens up?

Can you reproduce this easily?

Are you running N1MM+ as Administrator or normal?? Anything that will help me reproduce this here..

 

73 Rick N2AMG

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Thursday, February 18, 2016 11:48 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] N1MM+ runtime error

 

 

Error message I received below:-

 

73,

 

Bill

M0TDW

 

 

 

 

N1MMLogger.net - Version 1.0.5472.0

Built: 09-Feb-16 11:36:16 AM

Microsoft Windows NT 6.2.9200.0,64:1,en-US,en-US

Error occurred at: 18-Feb-16 4:41:57 PM in Thread: 

---------------------------------------------------------------------------------------

System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.

   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)

   at MMVARILib._DMMVARI.set_bActive(Boolean )

   at AxMMVARILib.AxMMVARI.set_bActive(Boolean value)

   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 791

---------------------------------------------------------------------------------------

 

 

Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

   at System.Environment.get_StackTrace()

   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 58

   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 211

   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 828

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)

   at System.Windows.Forms.Control.Show()

   at N1MMLogger.Net.DigitalInterface.InitPSKInterface() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 3261

   at N1MMLogger.Net.DigitalInterface.PSKRTTYSwap(Int32 Mode, Int16 Control) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 6174

   at N1MMLogger.Net.DigitalInterface.mnuInterfaceSelectionMMVARI_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 4856

   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ToolStrip.WndProc(Message& m)

   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82

 

On Wed, Feb 17, 2016 at 8:47 PM, GM4OSS stevegm4oss@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Hi Bill

It's Windows 10 I'm running. Appreciate any info/help you can send.

Steve/GM4OSS

 

On Wed, Feb 17, 2016 at 7:43 PM, Bill Woodroffe billwoodroffe@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

I had the same issue switching in the contest, running Windows 10, happy to send the failure if required.

73,

Bill
M0TDW

On 17 Feb 2016 15:54, "GM4OSS stevegm4oss@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:

 


Hi

I entered the RSGB 80M CC data contest for first time 2016 where you can work stations on both RTTY & PSK63 on 80M band.

Set up, K3/P3, MK2, N1MM+ with MMTTY for RTTY & MMVARI for PSK63. The error pasted below happens when I swap from MMTTY to MMVARI but not the other way around. MMVARI window does open but with nothing showing in waterfall. I then close DI window then reopen DI and an odd time MMVARI will be OK (no error).

I used this setup last years run of RSGB 80M CC test with no issues so not sure if this is a N1MM problem or not. Don't think my setup has changed but would appreciate any advice to what's causing this.

Steve/GM4OSS

N1MMLogger.net - Version 1.0.5481.0
Built: 2/16/2016 8:15:10 PM
Microsoft Windows NT 6.2.9200.0,64:1,en-GB,en-GB
Error occurred at: 2/17/2016 11:05:05 AM in Thread:
---------------------------------------------------------------------------------------
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
   at MMVARILib._DMMVARI.set_bActive(Boolean )
   at AxMMVARILib.AxMMVARI.set_bActive(Boolean value)
   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 791
---------------------------------------------------------------------------------------


Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 58
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 211
   at N1MMLogger.Net.PSKEngine.PSKEngine_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\PSKEngine.vb:line 828
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Control.Show()
   at N1MMLogger.Net.DigitalInterface.InitPSKInterface() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 3261
   at N1MMLogger.Net.DigitalInterface.DigitalInterface_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 2050
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Control.Show()
   at N1MMLogger.Net.EntryWindow.mnu_WindowDigitalInterface1_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 16577
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82
--

73 de Steve GM4OSS




--

73 de Steve GM4OSS