Date   
Re: MORTTY Working

Jim W7RY
 

I removed the [{ENTER} from the transmit button...
 
I already have {enter} in my macros for proper formatting of my buffers. This isn't my first RTTY contesting rodeo...
 
So really the transmit function should only have the [ in it because folks SHOULD already have the proper carriage return/line feeds in their macros. That is my opinion. But to each their own.
 
 
 
 
Thanks
73
Jim W7RY


 

From: ve3ki
Sent: Tuesday, May 15, 2018 10:18 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Jim W7RY
 

Yup! You are correct... I forgot to put the {TX} and {RX} commands back in... I just did some testing and it does work.
 
Sorry for the fire drill...
 
 
 
Thanks
73
Jim W7RY


 

From: ve3ki
Sent: Tuesday, May 15, 2018 10:18 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

ve3ki
 

Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Jim W7RY
 

Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 

From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Skip
 

Good practice is to begin your transmission with {TX}{ENTER} and end it with a single space before the {RX}.  This puts your transmission at the beginning of a new line, and separates the end of it from the noise he will print at your {RX}.  Multiple line feeds are a real PITA for those receiving on a window that scrolls up [or down] as he then needs to chase your call and maybe exchange with the mouse.

73,

Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 5/14/2018 8:00 PM, Jim W7RY wrote:
Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.
 
So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?
 
There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.
 
Anyone have any links?
 
Thanks
73
Jim W7RY

RTTY Roundup full results article posted

jeff stai wk6i
 

Here's the direct link. If it stops working it means a corrected version has been posted so just navigate there normally.


bon appetit! 73 jeff wk6i

--
RTTY op at W7RN

Re: Fresh Install

Jan
 
Edited

I use advanced uninstaller and after unintall I use Ccleaner

73

Jan

PA4JJ


Op 15.mei.2018 om 16:37 schreef Joe WB9SBD:
I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com


-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

Fresh Install

Joe WB9SBD
 
Edited

I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

locked Re: New Version

Tom - N1MM
 

Version 1.0.7174 (May 15, 2018)
GA QSO: Change county abbreviation OCNE back to OCON. (KU8E) (Coded by K3CT)
Volta RTTY: 0 points were given for USA Same call area qso's. This has been corrected. (Coded by N2AMG)
QSO Party: Update section field after a QSO edit. (several) (Coded by N1MM)
MD QSO Party: QSO party end time change. (K3MAW) (Coded by K3CT)

Re: N1MM fails to start. No message on screen.

John Bednar
 

Bob,

 

It also looks like you renamed the wrong directory. Two self-inflicted errors.

 

>…..I would rename the user N1MM Logger+ directory and start the program. The default location of the directory is MyDocuments.

 

Un-install does not remove all files (for good reason). Often a user will un-install, re-install and have the same issue. This is why I suggested that you remove the user N1MM Logger+ directory.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Turner
Sent: Monday, May 14, 2018 10:08 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

John,

 

I could check NTFS perms, but it’s a moot point because It’s working.  However, it seems odd that I renamed it to .old to make it “not found”,  yet N1MM+ it realized the name was changed and tried anyway.  I did look at NTFS perms for both the .old version and the newly installed version.  At first glance they look the same.  To be sure, I’d have to create a document as Windows does not give me a way to create a list of perms for both old and new install.  There are tens, if not hundreds of setting to remember.   If I had such a list I could compare in detail.  I don’t want to build that list as its now working.

 

I believe the root cause is moving my docs from \\FS1 to \\FS2, yet something insisted on going to \\FS1 and that server is “gone”.  It probably retried X number of times, and eventually just gave up and exited the program.  I need to remember to not do that.

 

I probably could have just done the uninstall / reinstall on my own without posting to list, yes I know the uninstall is not needed.  Sorry to bother you.

 

Anyway, its working, thanks for the help.

 

Bob

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of John Bednar
Sent: Sunday, May 13, 2018 8:07 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

Bob,

 

The cause of the error is  that access to C:\Program Files (x86)\N1MM Logger+.old\LogError.txt is denied.

This is not a N1MM Logger+ issue.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Turner
Sent: Sunday, May 13, 2018 7:41 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

John,

 

I renamed.  It went further with “A runtime error occurred during error processing” .  That message is below, but I think may get stripped out.

 

 

Running the Full Installer, boot, Run Updater worked on 2nd try.    First time it hung trying to go to a non-existent file server (that was my clue).  I told it c:\N1MM Logger+ instead.    It created it, but it’s still empty.   It did find my old databases in the Docs folder.   While running installer it was trying to go to a non-existent file server which I rebuilt under a new name months ago.  \\FS2\Docs versus \\FS1\Docs.    Windows document folder is redirected there.  Changing File Server name probably was the root cause.  Rather than go to the docs folder, it insisted to going to the location of the old docs folder.  Had it simply looked at whatever Docs was pointing at it would have worked.  Not sure if that is a Windows issue or N1MM, but it’s a minor issue now that I know about it.

 

Thanks for your help.

 

Bob

 

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Turner
Sent: Sunday, May 13, 2018 6:48 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

John,

 

I’ll try that.  I have no data to save.  I exported and imported into my general logger at end of last contest.

 

Bob

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of John Bednar
Sent: Sunday, May 13, 2018 6:26 AM
To:
N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

Bob,

 

I would rename the user N1MM Logger+ directory and start the program. The default location of the directory is MyDocuments. If the program starts your database file(s) are corrupt.

 

If it doesn’t start, the installation is damaged, likely from a computer scan or hardware issue. Rerun the Full Installer. There is no need to un-install. If the installer tells you to reboot, then restart the computer. Install the latest update before starting the program for the first time.

 

Make sure the database directory is located on the computer physical disk drive (not on a network share, cloud, USB disk, etc).

 

Some computer virus/security programs are known to damage the installation.

 

Never allow shadow backup of the database directory files when the program is running.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Turner
Sent: Sunday, May 13, 2018 6:03 AM
To:
N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

John,

 

No.  It was first installed 2-3 years ago.   Windows 10 has been upgraded several times via the forced updates.  It is now at 1709, Build 16299.431 .

 

Bob

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of John Bednar
Sent: Sunday, May 13, 2018 2:54 AM
To:
N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

Bob,

 

Is this a new install?

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Turner
Sent: Saturday, May 12, 2018 3:14 PM
To:
N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] N1MM fails to start. No message on screen.

 

I’m getting ready for June VHF.  N1MM fails to start.  No error message on screen.  I extracted this from Windows Application log.  I was thinking about uninstall / reinstall but perhaps there is a better way?

 

7 3  Bob

N2SCJ

 

App log follows---------------------------------------

 

Log Name:      Application

Source:        Windows Error Reporting

Date:          5/12/2018 3:08:07 PM

Event ID:      1001

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      I3

Description:

Fault bucket 1662346856206063835, type 5

Event Name: CLR20r3

Response: Not available

Cab Id: 0

 

Problem signature:

P1: N1MMLogger.net.exe

P2: 1.0.7147.0

P3: 5ac60004

P4: mscorlib

P5: 4.7.2650.0

P6: 5ab1cc12

P7: 1672

P8: 219

P9: System.IO.IOException

P10:

 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B87.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C73.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C83.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C93.tmp.txt

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_N1MMLogger.net.e_a8a1e4e5abed2ed54e9df19ee8e52e4d41e64660_fbdde670_093e5078

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 57f12cba-5edf-4956-b876-3182caa9ea08

Report Status: 268435456

Hashed bucket: fbcaf3ef94aeb5d9a711d7a881a658db

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Windows Error Reporting" />

    <EventID Qualifiers="0">1001</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-05-12T19:08:07.138031200Z" />

    <EventRecordID>43500</EventRecordID>

    <Channel>Application</Channel>

    <Computer>I3</Computer>

    <Security />

  </System>

  <EventData>

    <Data>1662346856206063835</Data>

    <Data>5</Data>

    <Data>CLR20r3</Data>

    <Data>Not available</Data>

    <Data>0</Data>

    <Data>N1MMLogger.net.exe</Data>

    <Data>1.0.7147.0</Data>

    <Data>5ac60004</Data>

    <Data>mscorlib</Data>

    <Data>4.7.2650.0</Data>

    <Data>5ab1cc12</Data>

    <Data>1672</Data>

    <Data>219</Data>

    <Data>System.IO.IOException</Data>

    <Data>

    </Data>

    <Data>

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B87.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C73.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C83.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C93.tmp.txt</Data>

    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_N1MMLogger.net.e_a8a1e4e5abed2ed54e9df19ee8e52e4d41e64660_fbdde670_093e5078</Data>

    <Data>

    </Data>

    <Data>0</Data>

    <Data>57f12cba-5edf-4956-b876-3182caa9ea08</Data>

    <Data>268435456</Data>

    <Data>fbcaf3ef94aeb5d9a711d7a881a658db</Data>

  </EventData>

</Event>

Re: QSO Recorder

Peter Krüger
 

45 seconds is a good length - do it not too short as sometimes not everything is "heard" - e.g. you need too long for logging the QSO and then the QSO is not in the MP3 File.

Audacity Recording is really not the best for recording in this area.
Sometime I use "No.23" recorder - which is really simple to use.

I am waiting for the GUI version with PyQT support :) or QSorder

--
---
N1mm+Toolbox -> see at  https://df1lx.darc.de 
Short video see https://www.dropbox.com/s/q1ab2u4t14m79gr/n1mm_hostilog.wmv?dl=0
---

Re: MORTTY Working

Max NG7M
 

Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Rick Ellison
 

Follow the directions in 10.1 and not the way Andy describes it in the second paragraph..…

 

73 Rick N2AMG

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jim W7RY
Sent: Monday, May 14, 2018 11:34 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

Perfect! Thanks!

 

Wonder why a Google search on N1MM and Tiny FSK didn’t bring this up...

 

Looks like I need to make a couple of tweaks... But I had it mostly right.

 

Thanks again Rich

 

 

73
Jim W7RY

 

From: ve3ki

Sent: Monday, May 14, 2018 10:20 PM

Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#TinyFSK_by_Andy_Flowers_K0SM> .

73,
Rich VE3KI


On Mon, May 14, 2018 at 08:00 pm, Jim W7RY wrote:

Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.

 

So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?

 

There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.

 

Anyone have any links?

 

 

 

Thanks
73
Jim W7RY

Re: MORTTY Working

Jim W7RY
 

Perfect! Thanks!
 
Wonder why a Google search on N1MM and Tiny FSK didn’t bring this up...
 
Looks like I need to make a couple of tweaks... But I had it mostly right.
 
Thanks again Rich
 
 
73
Jim W7RY


 

From: ve3ki
Sent: Monday, May 14, 2018 10:20 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#TinyFSK_by_Andy_Flowers_K0SM> .

73,
Rich VE3KI


On Mon, May 14, 2018 at 08:00 pm, Jim W7RY wrote:
Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.
 
So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?
 
There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.
 
Anyone have any links?
 
 
 
Thanks
73
Jim W7RY


Re: MORTTY Working

ve3ki
 

<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#TinyFSK_by_Andy_Flowers_K0SM> .

73,
Rich VE3KI


On Mon, May 14, 2018 at 08:00 pm, Jim W7RY wrote:
Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.
 
So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?
 
There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.
 
Anyone have any links?
 
 
 
Thanks
73
Jim W7RY


MORTTY Working

Jim W7RY
 

Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.
 
So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?
 
There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.
 
Anyone have any links?
 
 
 
Thanks
73
Jim W7RY


Re: Spectrum display - Icom 7300 #IC7300 #spectrum

Tom Blahovici <tomb18@...>
 

Further to the above, the same thing happens with the Silicon Labs drivers for Yaesu radios.  They cannot connect over 19200 baud.
Do not use the version 10 drivers.

Re: QSO Recorder

ve3ki
 

See <https://n1mm.hamdocs.com/tiki-index.php?page=Third+Party+Software&structure=N1MM+Logger+Documentation#QSOrder_by_Vasily_K3IT_> (read the last paragraph). The detailed descriptions of the command-line arguments are in the readme.txt file in the QSOrder download.

73,
Rich VE3KI


On Mon, May 14, 2018 at 01:50 pm, Drago Turin wrote:

 

I have installed_.Qsorder into N1MM+.I setup Broadcasting,Stared N1MM+ and Qsorecording.

When I tested_,I found after enter each QSO, the recorder make separate recording for the particular QSO-CALL sign.

How can I change  the recording time lower than default 45 seconds?

Tnx

Drago,S59A._,_

Re: QSO Recorder

Drago Turin <s59a@...>
 

 

I have installed_.Qsorder into N1MM+.I setup Broadcasting,Stared N1MM+ and Qsorecording.

When I tested_,I found after enter each QSO, the recorder make separate recording for the particular QSO-CALL sign.

How can I change  the recording time lower than default 45 seconds?

Tnx

Drago,S59A._,_

Changes to the MDC QSO Party in August

Michael Watterson
 

Hello,

I am emailing you as you either publish Amateur Radio Contests or you develop contesting software.

The MDC QSO Party is being changed and will be a one day event now and this year it will be Saturday, August 11 from 1600z to August 12 0400z (Noon to Midnight EDT).

I've attached the updated rules if you need them.  The web site will have the new rules posted soon, but the site already mentions it is now a one day event.

Please forward this email as you see fit.

Let me know if you have any questions.

Mike Watterson - K3MAW
MDC QSO Party Chairman