Date   
Re: Stew Perry Log Submission

Drew Vonada-Smith K3PA
 

I had the same issue and did the same as George...email.  The online system just did not work for me on the CAB output.

73,

Drew K3PA

Re: 7610 SO2V RTTY, VFO B not showing tuning indicator or RX text

ART W2NRA
 


Re: [N1MMLoggerPlus] New Version 1.0.7437

Thank you John, K3CT, this one was driving me nuts.  I test it this morning and VFO B is working perfectly with the IC-7610 SO2V RTTY.

I see all you guys were pretty busy this past weekend give the volume of email.  Thank you all for your efforts.

73 Art W2NRA
CWOPS 1955

On Jan 07, 2019, at 12:22 AM, ve3ki <ve3iay@...> wrote:

I don't know much about the 7610, but (a) you could check in the Windows sound card control panel app whether the codec is configured for 1 channel or 2 channels; (b) perhaps there is a menu item in the radio related to the second channel in the codec(?).

73,
Rich VE3KI


On Sun, Jan 6, 2019 at 11:31 PM, ART SEARLE wrote:
Hi Rich,
 
I’m aware of everything you wrote. I am using 2 separate incidents of MMTTY and the USB CODEC, left for VFO A and right for VFO B. 
 
My 7610 was working perfectly recently.
 
I wonder if the USB CODEC is the culprit. I also have a 7300. I’ll check this out tomorrow. 
 
73, Art, W2NRA

On Jan 6, 2019, at 10:53 PM, ve3ki <ve3iay@...> wrote:

For SO2V, you need two separate copies of MMTTY run from separate folders. Each one needs to point to a different sound card input, one for each VFO. If you were using the USB audio codec in the rig, I expect that you need to configure the VFO A copy of MMTTY to use the left channel of the codec, and the VFO B copy of MMTTY to use the right channel of the codec.

73,
Rich VE3KI


On Sun, Jan 6, 2019 at 10:33 PM, ART SEARLE wrote:
In my N1MM Logger+ set up for SO2V RTTY is working except VFO B doesn’t display tuning scope or RX text. In displays VFO A tuning scope and RX text. 
 
I do have both copies of MMTTY numbered 1 for VFO A and 2 for VFO B.  TX works properly on both VFOs. Also I can see VFO B RX on the IC-7610 Scope display.
 
I just cannot get VFO B RX into the N1MM Logger+’s VFO B RX window or the tuning scope. What am I missing. 

73, Art, W2NRA



Re: Stew Perry Log Submission

GIWagner@k5kg.com
 

I had a similar problem submitting my Stew Perry log on the WA7BNM template.  Gave up with that method, and just emailed the CAB file to tbdc@....  That worked.

73, George K5KG

Re: N1MM+ shows different frequency than transceiver's dial in RTTY FSK

ve3ki
 

In the Digital Interface window's Setup menu, uncheck the option called "Turn AutoTRXUpdate On/Off". That option is there for people doing AFSK with the rig in LSB - if your rig's dial shows the actual Mark frequency (FSK), this option should be turned off.

73,
Rich VE3KI


On Tue, Jan 8, 2019 at 05:14 AM, Adrian Sinitaru wrote:
Happy New Year to everybody in this discussion group!
 
Can somebody explain why N1MM+ logger shows  a different frequency than transceiver's dial, in RTTY FSK? The difference is -2,12 kHz.
The transceiver (FT2000) is interfaced with a MicroHam Digikeyer, which shows transceiver's dial frequency. The OS is Windows 10/32.
 
73! Adrian / YO3APJ
 

Re: N!MM+ warning message in Windows 10

Roger Cooke
 

Hi Rich and Drew.


I had to bite the bullet and start over. Renaming the old database would not work either, which was annoying. However, I still have all the information on the stick and have now installed a new clean version NOT using the ONEDRIVE. I have uninstalled and disabled that altogether. It is a real pain. I do have Dropbox anyway so have storage and backup on there. Syncing probably caused the problem in the first place I would think, but all is well once again.

Thanks for the input and help. I have already set up a new CWT contest for tomorrow, so see you in that!


73 and HNY de Roger, G3LDI

On 08/01/2019 00:06, Drew Vonada-Smith K3PA wrote:
Is it possible that the database really is bad, due to a synching problem from using the cloud?

Might be best to start with a fresh database and make sure that works before doing anything else.

73,
Drew K3PA

Virus-free. www.avast.com

Re: Stew Perry Log Submission

Jamie WW3S
 

You must be using a old copy of n1mm...I think Cabrillo is now 3.0.....I would update to the latest version of mm, restart the contest, remove 599 from the exchange in contest setup and export to cabrillo again....


On Jan 7, 2019, at 11:57 PM, Jim W7RY <jimw7ry@...> wrote:

I would guess there is somthing missing (or added into) in your Cabrillo file.

Can you copy and paste the first of your Cabrillo file to the list? Make sure it paginates correctly in your email or it will be useless.

Or take a picture of it and put it on a picture sharing location so we can look at it?

What logging program did you use? I don't see it listed in the Cabrillo...


Thanks
73
Jim W7RY
On 1/7/2019 12:13 PM, Michael Marx wrote:
Hey Guys,

I'm at my wits end.  I have been trying to submit my Stew Perry log data on the WA7BNM page and it just isn't working.  Every line indicates there is missing data.

Here is a sample line submitted:

QSO:  1803 CW 2018-12-29 2215 WB0SND        599 EM48   K3MD          599 FN10     


Here is what is reported back:

ERROR--> Following line had too many items:
QSO:  1803 CW 2018-12-29 2215 WB0SND        599 EM48   K3MD          599 FN10


Here is the header (all screwed up):

<-Enter your QSO data starting on the next line. Do not erase this line.->
ERROR--> Following line had too few items:
START-OF-LOG: 2.0
ERROR--> Following line had too few items:
ARRL-SECTION: MO
ERROR--> Following line had too few items:
CALLSIGN: WB0SND
ERROR--> Following line had too few items:
CLUB: SMC
ERROR--> Following line had too few items:
CONTEST: STEW-PERRY
ERROR--> Following line had too many items:
CATEGORY: SINGLE-OP ALL HIGH CW
ERROR--> Following line had too few items:
CLAIMED-SCORE: 1630
ERROR--> Following line had too few items:
OPERATORS: WB0SND
ERROR--> Unrecognized date: NAME:
ERROR--> Time is not numeric or out of range: Michael
ERROR--> Invalid call-copied: C.
NAME: Michael C. Marx
ERROR--> Unrecognized date: ADDRESS:
ERROR--> Time is not numeric or out of range: 14401
ERROR--> Invalid call-copied: ROWE
ADDRESS: 14401 Rowe Lane
ERROR--> Following line had too many items:
ADDRESS: De Soto, MO 63020
ERROR--> Following line had too few items:
ADDRESS: UNITED STATES
ERROR--> Unrecognized date: CREATED/BY:
ERROR--> Time is not numeric or out of range: N1MM
ERROR--> Invalid call-copied: LOGGER+
ERROR--> Unrecognized grid-copied: 1.0.7403.0


All of the data at the header is also rejected for various reasons.   All I have done is generated the Cabrillo file as I have for countless contests.  But, this one is exploding.  Any ideas of what I should try?

73
Mike WB0SND




Re: N1MM+ shows different frequency than transceiver's dial in RTTY FSK

Jamie WW3S
 

Yes, you have an offset configured (usually used for afsk ).... I’m not in front of the software right now, but I believe it’s under setup in the digi window....


On Jan 8, 2019, at 2:52 AM, Adrian Sinitaru via Groups.Io <yo3apj@...> wrote:

Happy New Year to everybody in this discussion group!

Can somebody explain why N1MM+ logger shows  a different frequency than transceiver's dial, in RTTY FSK? The difference is -2,12 kHz.
The transceiver (FT2000) is interfaced with a MicroHam Digikeyer, which shows transceiver's dial frequency. The OS is Windows 10/32.

73! Adrian / YO3APJ

locked Re: New Version

Tom - N1MM
 

Version 1.0.7437 (January 8, 2019)
  1. RFC (Cup of the Russian Federation): contest time (night and day sessions) updated per new rules (UA9PM) (Coded by NA3M)
  2. WJST List: Corrects an issue that could cause a error where WSJT-X will stop coloring callsigns.(Coded by N2AMG)
  3. WSJT List: Only colors the Callsign in the list. (Coded by N2AMG)
  4. WSJTList: Stops alot of flicker while list is updating. (Coded by N2AMG)
  5. Saved packet spots were being read with incorrect timestamp (K3CT) (Coded by N1MM)
  6. ARRLRTTY (ARRL RTTY Roundup): all Qs in PSK modes were "RY" in Cabrillo, now "DG" (UC4I) (Coded by NA3M)
  7. Catch serial port UnauthorizedAccessException and suggest remedial action. (Coded by N2IC)
  8. Improved responsiveness of deleting spots. (Coded by N1MM)
  9. Available Window: Redesigned to always display the selected spot in the middle of the display. Implement several efficiency improvements and bug fixes. When spots are sorted by time stamp, initially unselect the selected row and disable auto-centering and auto-scrolling. If a spot is selected when sorted by time stamp, re-enable display auto-centering. Also, when sorted by time stamp, double clicking to the left or right of the summary table clears the selected spot and scrolls the list to the top. When the mouse is used to scroll the display, start a timer that will reset the display if a new spot is not selected. Alt+A and Alt+Shift+A can be used to select the next/previous spot. Alt+A can be used to grab the first spot when none are selected. (Coded by K3CT)

N1MM+ shows different frequency than transceiver's dial in RTTY FSK

Adrian Sinitaru
 

Happy New Year to everybody in this discussion group!

Can somebody explain why N1MM+ logger shows  a different frequency than transceiver's dial, in RTTY FSK? The difference is -2,12 kHz.
The transceiver (FT2000) is interfaced with a MicroHam Digikeyer, which shows transceiver's dial frequency. The OS is Windows 10/32.

73! Adrian / YO3APJ

Re: Stew Perry Log Submission

Jim W7RY
 

I would guess there is somthing missing (or added into) in your Cabrillo file.

Can you copy and paste the first of your Cabrillo file to the list? Make sure it paginates correctly in your email or it will be useless.

Or take a picture of it and put it on a picture sharing location so we can look at it?

What logging program did you use? I don't see it listed in the Cabrillo...


Thanks
73
Jim W7RY
On 1/7/2019 12:13 PM, Michael Marx wrote:

Hey Guys,

I'm at my wits end.  I have been trying to submit my Stew Perry log data on the WA7BNM page and it just isn't working.  Every line indicates there is missing data.

Here is a sample line submitted:

QSO:  1803 CW 2018-12-29 2215 WB0SND        599 EM48   K3MD          599 FN10     


Here is what is reported back:

ERROR--> Following line had too many items:
QSO:  1803 CW 2018-12-29 2215 WB0SND        599 EM48   K3MD          599 FN10


Here is the header (all screwed up):

<-Enter your QSO data starting on the next line. Do not erase this line.->
ERROR--> Following line had too few items:
START-OF-LOG: 2.0
ERROR--> Following line had too few items:
ARRL-SECTION: MO
ERROR--> Following line had too few items:
CALLSIGN: WB0SND
ERROR--> Following line had too few items:
CLUB: SMC
ERROR--> Following line had too few items:
CONTEST: STEW-PERRY
ERROR--> Following line had too many items:
CATEGORY: SINGLE-OP ALL HIGH CW
ERROR--> Following line had too few items:
CLAIMED-SCORE: 1630
ERROR--> Following line had too few items:
OPERATORS: WB0SND
ERROR--> Unrecognized date: NAME:
ERROR--> Time is not numeric or out of range: Michael
ERROR--> Invalid call-copied: C.
NAME: Michael C. Marx
ERROR--> Unrecognized date: ADDRESS:
ERROR--> Time is not numeric or out of range: 14401
ERROR--> Invalid call-copied: ROWE
ADDRESS: 14401 Rowe Lane
ERROR--> Following line had too many items:
ADDRESS: De Soto, MO 63020
ERROR--> Following line had too few items:
ADDRESS: UNITED STATES
ERROR--> Unrecognized date: CREATED/BY:
ERROR--> Time is not numeric or out of range: N1MM
ERROR--> Invalid call-copied: LOGGER+
ERROR--> Unrecognized grid-copied: 1.0.7403.0


All of the data at the header is also rejected for various reasons.   All I have done is generated the Cabrillo file as I have for countless contests.  But, this one is exploding.  Any ideas of what I should try?

73
Mike WB0SND




Re: Entry Window Band Button Misbehavior in latest version

Bob Frostholm
 

Right here
Image result for thumb up emoji
Emacs!
Bob

Ko6Lu




At 10:59 AM 1/7/2019, Jamie WW3S wrote:
Where’s the LIKE button !!!


On Jan 7, 2019, at 1:53 PM, John K3TN via Groups.Io < jpescatore@...> wrote:

Thanks, John - makes sense. I hope they end up deciding on separate contests for FT8 and RTTY, personally.

73 John K3TN

Re: Falsifying Log

NS2N_PTA@...
 

I submitted my log with the NL contact and it was accepted by Mr Roboto.

NS2N


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of Steve London <n2ic@...>
Sent: Monday, January 7, 2019 9:07:27 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Falsifying Log
 
If you are an old-timer SS or CD Party operator, you'll remember when CONN was
the abbreviation for Connecticut.

73,
Steve, N2IC

On 01/07/2019 06:49 PM, Tom Wagner (N1MM) wrote:
> "Log what is sent" is a nice simple rule with the ring of truth.  But it is wrong.
>
> Log what is meant.  If I send CONNECTIKUT as my state, will you log that, or CT?
>
>
> Tom - N1MM
>
> On 1/7/2019 8:46 PM, Joe Shuey NE3H wrote:
>>
>> Interesting, today I tried to submit my log for ARRL RU.The robot rejected it
>> because QSOs with VO1BQ showed NL as the Province.That is what was sent as
>> noted by several others. So, I changed it to the proper NF for
>> Newfoundland.Seems strange, as I always followed the rule “Report what was sent”!
>>
>> /- NE3HJoe Shuey -/
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>     Virus-free. www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
>
>



Re: Falsifying Log

Steve London
 

If you are an old-timer SS or CD Party operator, you'll remember when CONN was the abbreviation for Connecticut.

73,
Steve, N2IC

On 01/07/2019 06:49 PM, Tom Wagner (N1MM) wrote:
"Log what is sent" is a nice simple rule with the ring of truth.  But it is wrong.
Log what is meant.  If I send CONNECTIKUT as my state, will you log that, or CT?
Tom - N1MM
On 1/7/2019 8:46 PM, Joe Shuey NE3H wrote:

Interesting, today I tried to submit my log for ARRL RU.The robot rejected it because QSOs with VO1BQ showed NL as the Province.That is what was sent as noted by several others. So, I changed it to the proper NF for Newfoundland.Seems strange, as I always followed the rule “Report what was sent”!

/- NE3HJoe Shuey -/


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>     Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: Falsifying Log

Tom Wagner (N1MM)
 

"Log what is sent" is a nice simple rule with the ring of truth.  But it is wrong.

Log what is meant.  If I send CONNECTIKUT as my state, will you log that, or CT?


Tom - N1MM

On 1/7/2019 8:46 PM, Joe Shuey NE3H wrote:

Interesting, today I tried to submit my log for ARRL RU.The robot rejected it because QSOs with VO1BQ showed NL as the Province.That is what was sent as noted by several others. So, I changed it to the proper NF for Newfoundland.Seems strange, as I always followed the rule “Report what was sent”!

/- NE3HJoe Shuey -/


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Falsifying Log

Joe Shuey NE3H
 

Interesting, today I tried to submit my log for ARRL RU.  The robot rejected it because QSOs with VO1BQ showed NL as the Province.   That is what was sent as noted by several others. So, I changed it to the proper NF for Newfoundland.  Seems strange, as I always followed the rule “Report what was sent”!

 

- NE3H   Joe Shuey -


Virus-free. www.avg.com

Re: N!MM+ warning message in Windows 10

Drew Vonada-Smith K3PA
 

Is it possible that the database really is bad, due to a synching problem from using the cloud?

Might be best to start with a fresh database and make sure that works before doing anything else.

73,
Drew K3PA

Re: N!MM+ warning message in Windows 10

Roger Cooke
 

Hi Rich.


I have uninstalled and installed - religiously following your instructions - over and over again. However, along the way, I did check and alter paths in the .ini file to try to take out ONEDRIVE.  I have now uninstalled that too.  I have got as far as seeing the database warning on boot-up and now have a message that says my ham.s3db file is malformed. Not seen that one before. I have emptied the databases folder and replace all the files from my USB stick, with the same result.

  I feel I am getting close, because the first screen to appear has my call on it, but just does not like my databases folder for some reason. I tried re-copying all the files from my USB stick into the main USER folder, after updating but before running the program, several times, with the same result. All references to ONEDRIVE have been removed.

 Any fresh ideas please?  You were the only one to respond!!


73 de Roger, G3LDI

On 07/01/2019 03:44, ve3ki wrote:
Did you copy all of the files from the thumb drive into the new user files area, including all of the subfolders?

You should be able to get the program working by simply deleting or renaming the n1mm logger.ini file, and then redoing the hardware configuration from scratch and (temporarily, I hope) creating a new database file. Then, if you have copied the database files from the thumb drive into the Databases folder in your new N1MM Logger+ user files area, you should be able to use the File > Open Database menu item to open your old database file.

I could be wrong, but I believe that you should be able to move all of the files in the subfolders from the old user files area in OneDrive into the corresponding subfolders in the new user files area on your local drive. The one exception I know of is the ini file, because of the references in it to file locations in the OneDrive file area.

I don't use OneDrive, so I am quite possibly missing something.

73,
Rich VE3KI


On Sun, Jan 6, 2019 at 06:16 PM, Roger Cooke wrote:

Hi Rich.

Many thanks for the reply.  I followed your steps very closely, but it still wanted to install to onedrive and I was unable to prevent it. So, I googled onedrive and found out how to disable it. I then edited the ini file to take out all references to onedrive.

However, following your installation instructions, it came up with a database error. I checked the user files on my USB stick and all the database files are there. It just does not want to look at them. I now get a very strange looking window on boot up and all sorts of error messages. It is getting late so will have to give it up for this evening and have another bash at it tomorrow.   I need to get this right by Wednesday for the CWT!!!!!

  Anyway, thanks for the help and will let you know how I get on in the morning.

 

73 de Roger, G3LDI

On 06/01/2019 15:50, ve3ki wrote:
Unfortunately, you cannot simply copy the user file area to where you want it to be. There is a setting in the Windows Registry that will point the program right back to the installed location. As far as I know, there is no way around this other than to uninstall and reinstall.

Before you start, first change some of the File Explorer options so you can see what you are doing. In File Explorer, select View > Options > Change folder and search options. This will open a Folder Options dialog window. Select the View tab, then uncheck the check box called "Hide extensions for known file types". You might want to change one or two of the other options while you are there, but this is the most important one. After exiting the Folder Options window, use View > Details to tell File Explorer to display file names in a list, with other information like the date last modified and the size of the file.

OK, once File Explorer is giving you the information you need, make a copy of your entire N1MM Logger+ user files folder (from OneDrive) in a safe place, such as on a thumb drive.

Next, use the Windows Settings > Apps window to find N1MM Logger+ and Uninstall it.

Download the Full Installer and install N1MM+ again. This time make sure that the user files location is on your local Documents folder, not in OneDrive. I believe the full installer has been changed so that it will refuse to install to OneDrive, but I would double-check anyway. Once it is installed, don't try to run the program - first, download and install the latest version. There will be a check box in the installer to run the new version; uncheck that. Instead, first copy the files from your saved copy of the old user files area (the thumb drive or whatever) into the newly-created user files area in your local Documents folder.

Before trying to run the program, I would suggest making sure that there are no references to OneDrive in your n1mm logger.ini file. You can open the file with a text editor, then search for OneDrive. If you find OneDrive in the middle of the path for a filename in the file, I would suggest removing it, i.e. changing where the path points to be on your local drive instead of on OneDrive. I don't use OneDrive, so I can't be sure of this, but I believe that if a path looks like
C:\Users\[username]\OneDrive\Documents\N1MM Logger+\filename, what you need to do is change that to read
C:\Users\[username]\Documents\N1MM Logger+\filename so that it points to your local Documents folder instead of to the one in OneDrive.

At this point, hopefully you will be able to pick up where you left off.

73,
Rich VE3KI


On Sun, Jan 6, 2019 at 10:32 AM, Roger Cooke wrote:
I recently installed a new N1MM+ on my new Windows 10 PC. It has put the user folder in the cloud - I presume it is ONEDRIVE. I can see the folder there. There is a duplicate folder in my Documents folder in MY PC as well. I tried copying verbatim the folder from ONEDRIVE into the one in My PC, and deleted the folder in ONEDRIVE. That did not work and gave me a warning message so I undeleted it and went back to square one.
  Am I the only one suffering this or is there an easy way to rectify this situation?  I don't wish to delete my N1MM+ as I have all my old logs and personal stuff in there.  As an aside, am I the only one who abhors the direcftory structure I am presented with when invoking what used to be Windows Explorer? I could see ALL the files in there, but now I don't!

Virus-free. www.avast.com

Re: transmitter staying keyed.

ve3ki
 

The copy of MMTTY you use with N1MM+ should be a separate copy from the one you use stand-alone, stored in a separate folder. The folder it is stored in should not be in C:\Program Files. Inside that copy of MMTTY, the Radio command port must be set to None. Do not configure MMTTY to use COM8 -- N1MM+ will be using COM8. (The same is true for the copy of MMTTY you use with WInWarbler, by the way - it should not try to use COM8, because Commander needs that port for rig control, and serial ports cannot be shared.)

In N1MM+, under the Digital Modes tab in the Configurer, make sure the DI-1 MMTTY Path points to this separate copy of MMTTY.exe . In the main Hardware tab, configure COM8 for Radio control (Kenwood). If you don't have any hardware connection to the rig for PTT control (no cable from the Winkeyer's PTT output to the rig, and no other serial port controlling PTT), then also check the CW/Other check box for COM8, and in the port setup (Set button for COM8), check the check box for "PTT via Radio Command Digital Mode". You will probably need to set RTS to Always On (or maybe Handshake) on the rig control port in order to get rig control working properly.

Make sure rig control is working, i.e. check that the radio's dial frequency shows up in the title bar of the main N1MM+ Entry window, turning the radio's tuning knob makes the frequency in the title bar change, and typing 14080 into the Entry window and pressing the Enter key causes the radio to QSY to 14080 kHz. Do not try to transmit in RTTY until after you have rig control working from N1MM+.

This is not relevant for RTTY, but COM5 (with Radio type = None) should have its CW/Other check box checked. When you press the Set button for COM5, the only thing you need to do in the Port Setup window is check the Winkey check box.

The DXLab Suite Commander should also be configured to use COM8. If its radio control port is configured as None, Commander can't do anything useful. Because Commander, N1MM+ and your stand-alone copy of MMTTY all use COM8, you can only ever run one of them at a time.

What I believe is happening with your "stuck in transmit" is that your software is able to send a TX; command to the rig to put it into transmit, but that it is unable to send the RX; command to put it back into receive, possibly because of something that happened as a result of having two programs trying to use the same port at the same time. My recollection from experience with a Kenwood of similar vintage (a TS-850) is that the only way to cancel a TX; command is with an RX; command; hardware PTT, the front-panel button or even turning the rig off and back on won't do it. The upshot is this: don't ever try to use two programs connected to the same rig control port at the same time.

73,
Rich VE3KI


On Mon, Jan 7, 2019 at 02:54 PM, Anthony W. DePrato wrote:
I hope this is the correct place for this question. first my setup.

HP all in one win 7 pro. with usb to serial adapter
Com 5 in winkey control
Com 8 is rig control
Com 9 is Rotor control
radio Kenwood ts950sx

i have been running N1NN+ on this radio without any problems for ssb contests.

i run dxlab for all my rtty and for logging.i also use this suit for rtty .
i had some fun in the RU RTTY this weekend and want to get back into
rtty contesting. just a note an not new to either program just never
used N1MM for rtty.
both use MMTTY Eng.'
i have MMTTY on the computer as a standalone program also.
today i set up N1MM for RTTY and have it receiving very well . but
could not get it to key the transmitter. with into mmtty setup and
set the radio command port as com 8.
i was able to key the radio. and send rtty. BUT when i hit the
receive button the program showed it was back in receiver mode THE
Transmitter stayed Keyed. if i hit send button
it will send data again hit rx but radio stays keyed. closed out
N1MM but radio stayed keyed. after checking around i could find
nothing wrong shut computer down radio still keyed. turned radio off
and on radio still keyed.
what i have found is that if i open commander in the dxlab suit and
hit the RX button the radio will unkey. i changed the port in
commander to none closed out and opened N1MM same problem. so some
where i am getting a com conflict but the computer
is not say there is one. when i get off duty tonight i am going to
delete the standalone copy of mmtty and see if i can setup up both
dxlab and n1mm to look for just the same copy of mmtty.
Any ideals from the N1MM experts ?
thanks for any help
73 Tony WA4JQS

Anthony W.DePrato WA4JQS since 1962
CQ DX HALL OF FAME # 35
DXCC HONOR ROLL
DXPEDITION OF THE YEAR 1992 VP8SSI
DXPEDITION OF THE YEAR 1993/1994 3Y0PI
VP8SSI 3Y0PI VP8BZL V31SS ZD8JQS
WA4JQS/ZS1 WA4JQS/KC4 WA4JQS/4K1

IMPORTANT: FT8 and Log Category!

jeff stai wk6i
 



---------- Forwarded message ---------
From: Jeff Stai <wk6i.jeff@...>
Date: Mon, Jan 7, 2019 at 12:35 PM
Subject: IMPORTANT: FT8 and Log Category!
To: WSJT-Group <wsjtgroup@...>, WSJT <wsjt-devel@...>, cq-contest@... <cq-contest@...>


When submitting your RTTY Roundup log, please ensure that you submit for the correct entry category!

Remember that Rule 7.4 states that all entries that made contacts in FT8 using WSJT *must* enter in one of the *Unlimited* categories (or Multiop, if you did that.) (Rules here: http://www.arrl.org/rtty-roundup)

On the ARRL's log-submission page, that means you need to check the **YES** box to the following question:

Did you use spotting assistance of any kind at any time during the contest? Yes   No    

Maybe you didn't actually use spotting assistance, but **YES** to this question is what puts you properly into the Unlimited category.

If you have already submitted a log, you can correct the problem by resubmitting it with the **YES** box checked.  Only the final log submission is used for scoring and log-checking.

Log submission page here: http://contest-log-submission.arrl.org/

**All entries must be postmarked or uploaded by 2359 UTC January 13, 2019!**

Please share this information with any appropriate groups. 73 jeff wk6i

ps: We're not going to debate the rule here. It's the rule.

--
Jeff Stai ~ WK6I ~ wk6i.jeff@...
Ask me about Green Keys Night - Jan 1, 2019 0000-2359 UTC!
RTTY op at W7RN
Twisted Oak Winery ~ http://www.twistedoak.com/


--
Jeff Stai ~ WK6I ~ wk6i.jeff@...
Ask me about Green Keys Night - Jan 1, 2019 0000-2359 UTC!
RTTY op at W7RN
Twisted Oak Winery ~ http://www.twistedoak.com/

Re: canadian mults in Roundup (and SS)

brian.moran@...
 

As a data point, we did NOT use a call history file at all during ARRL RU, yet Ontario stations that were spotted always seemed to be considered mults by N1MM.  The spot that got it into the multiplier map didn't have any special text associated with it to indicate it was anything but Ontario. I'd like to think that I like Ontario just as much as the next non-Canadian. But every VE3 a mult? that's too much.

Brian N9ADG


On Mon, Jan 7, 2019 at 10:15 AM Jamie WW3S <ww3s@...> wrote:
I know we’ve talked about this before after SS, and it was talked about mult coloring and coding of VE stations.....I had several this weekend, that failed to identify as a mult, even though they are in the call history file.....VE2FK, VE5MX, VE4EAR, VE6??, all failed to color red when spotted when they should have been a mult.....conversely, almost all the VE3, when entered in the entry window would appear RED (even though I already worked ON) until I moved to the exchange field, then they turned blue.....I’m not a programmer, and give the development team a heartfelt pat on the back, however, something seems broken with identifying VE mults in the call history file.  For example, I need LA and I need QC for mults....both AA5AU (LA) and VE2FK(QC) get spotted, both are in the call history file, AA5AU gets coded red (and appears in the mult window and available window) yet VE2FK does not.....I suspect I missed a VE mult this time (probably PEI), I was able to catch the others if I noticed them in the bandmap, but I’ve gotten into the habit of relying on the MULT window (set for sections) and the AVAILABLE window (mults only) to save screen space.