Date   
Re: Bug in DATA using MMTTY ?

Rick Ellison
 

I have been thinking about this since I first read the messages and this bug came up.

And 2 things that keep coming up is:

A>    The last time that I made a change to the MMTTY routines was back in May 2017 and that was a menu correction. The next previous to that was 2015.

B>    MMTTY v1.68 has been around since 9/2010 without any changes to that version. (It has been upgraded by other programmers to version 1.70I)

So with that in mind if this is the first or second time seeing this and you haven’t seen it before then it’s time to look in your shack for some stray RF. Something is causing MMTTY to get hung up and my guess is RF is entering the computer someplace.

 

73 Rick N2AMG

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bob Epstein via Groups.Io
Sent: Monday, October 1, 2018 9:37 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

 

My past experience with two instances of N1MM and two instances of 2Tone (probably 20K RTTY qsos with that configuration and same computer) has shown to be reliable and stable.

 

 The only reason I even mentioned this issue is that two other big volume RTTY contesters (G2F and WW3S) saw the same thing. 

 

I realize there is a myriad of variables surrounding this low percentage problem, but I figured it would be helpful to support G2F and mention he wasn't a singular observer.

 

Bob K8IA (N7AT)

Arizona Outlaws Contest Club

 

-------- Original message --------

From: ShelbyK4WW <shelbyk4ww@...>

Date: 10/1/18 5:05 AM (GMT-07:00)

To: N1MM Reflector <N1MMLoggerPlus@groups.io>

Subject: Re: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

 

This being my first RTTY contest, using N1MM, other than a few operator errors, I would say that N1MM performed flawlessly. One radio, one decoder, probably has a lot to do with that?

 

On Mon, Oct 1, 2018 at 7:59 AM Bob Epstein via Groups.Io <bobk8ia=aol.com@groups.io> wrote:

Twice, in CQWW RTTY, I saw the same thing in SO2V. Once, I saw the "reoccurring character" situation and the other time the Main (A) receiver side decoders just froze. My only fix was to kill and reboot N1MM+.

 

The B-receiver side was unaffected. It still operated fine while the A-side froze up.

 

Setup here Win7, MMTTY and 2Tone on both K3 receivers, i3 processor, 10 GB RAM and not much running in the background. Latest versions of N1MM+ and 2Tone and v1.68a of MMTTY (not latest MMTTY v1.70).

 

The operation of the K3 remained unaffected during these glitches. 

 

Any ideas?

 

Bob K8IA (N7AT)

Arizona Outlaws Contest Club

 

-------- Original message --------

From: Jim M0CKE <makidoja@...>

Date: 10/1/18 12:56 AM (GMT-07:00)

Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

 

Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ 

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE


 

--

73, Shelby - K4WW

As I don't have an iPad nor iPhone, sent from my PC

Re: Bug in DATA using MMTTY ?

Bob Epstein K8IA
 

My past experience with two instances of N1MM and two instances of 2Tone (probably 20K RTTY qsos with that configuration and same computer) has shown to be reliable and stable.

 The only reason I even mentioned this issue is that two other big volume RTTY contesters (G2F and WW3S) saw the same thing. 

I realize there is a myriad of variables surrounding this low percentage problem, but I figured it would be helpful to support G2F and mention he wasn't a singular observer.

Bob K8IA (N7AT)
Arizona Outlaws Contest Club

-------- Original message --------
From: ShelbyK4WW <shelbyk4ww@...>
Date: 10/1/18 5:05 AM (GMT-07:00)
To: N1MM Reflector <N1MMLoggerPlus@groups.io>
Subject: Re: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

This being my first RTTY contest, using N1MM, other than a few operator errors, I would say that N1MM performed flawlessly. One radio, one decoder, probably has a lot to do with that?

On Mon, Oct 1, 2018 at 7:59 AM Bob Epstein via Groups.Io <bobk8ia=aol.com@groups.io> wrote:
Twice, in CQWW RTTY, I saw the same thing in SO2V. Once, I saw the "reoccurring character" situation and the other time the Main (A) receiver side decoders just froze. My only fix was to kill and reboot N1MM+.

The B-receiver side was unaffected. It still operated fine while the A-side froze up.

Setup here Win7, MMTTY and 2Tone on both K3 receivers, i3 processor, 10 GB RAM and not much running in the background. Latest versions of N1MM+ and 2Tone and v1.68a of MMTTY (not latest MMTTY v1.70).

The operation of the K3 remained unaffected during these glitches. 

Any ideas?

Bob K8IA (N7AT)
Arizona Outlaws Contest Club

-------- Original message --------
From: Jim M0CKE <makidoja@...>
Date: 10/1/18 12:56 AM (GMT-07:00)
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ 

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE



--
73, Shelby - K4WW
As I don't have an iPad nor iPhone, sent from my PC

Re: Win4Yaesu

ve3ki
 

My first reaction was yes  - then I looked at the title of your message again. You mean the Win4Yaesu spectrum display, whereas I was thinking about the N1MM+ spectrum display. I have no idea whether it is possible to feed spots from N1MM+ back into Win4Yaesu. In the other direction, though, it is possible to feed spectrum data from Win4Yaesu into N1MM+'s Spectrum Display window (see <https://www.youtube.com/watch?v=T59hz0AISj0&feature=youtu.be>). Spots appear automatically in the N1MM+ spectrum window, the same as in the N1MM+ Bandmap window.

73,
Rich VE3KI


On Mon, Oct 1, 2018 at 09:09 AM, Dean Saxton wrote:
Has anyone managed to get N1MM+ to feed band spots to the spectrum display?

If so, How?

Dean G4WQI

Win4Yaesu

Dean Saxton
 

Has anyone managed to get N1MM+ to feed band spots to the spectrum display?

If so, How?

Dean G4WQI

Re: Bug in DATA using MMTTY ?

ve3ki
 

I saw the call stack bug others have reported, but no freezes or crashes. Unassisted HP, 24 hours, SO2V, AFSK, MMTTY as the main decoder and 2Tone as a second decoder in both DI windows, Waterfall Bandmap and N1MM+ spectrum display.

I started out with GRITTY as a third decoder in DI-1 and I saw strings of repeated characters in it, so I dumped it after an hour or so.

73,
Rich VE3KI


On Mon, Oct 1, 2018 at 08:32 AM, Larry K8UT wrote:
My configuration was similar, although I used 2Tone as my DI application, and loaded MMTTY as the 2nd decoder. With poor band conditions, dual band decoders was a tremendous help. 2Tone seemed to be right more often than MMTTY, but there were also many times when MMTTY was the only decoder to print.
 
There were no software crashes in my 12 hours of assisted operation: K3S in SO1V, Mortty in FSK, dual decoders, panadapter, high power. For me it was a trouble-free contest.
 
-larry (K8UT)
 
------ Original Message ------
From: "Jamie WW3S" <ww3s@...>
Sent: 2018-10-01 06:48:13
Subject: Re: [N1MMLoggerPlus] Bug in DATA using MMTTY ?
 
yes, I saw it a few times, same setup, Win 7 SO2R, dual decoders, in my case though a window popped up saying N1MM stopped, and it closed itself....
 
From: Jim M0CKE
Sent: Monday, October 01, 2018 3:56 AM
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?
 
Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE

Virus-free. www.avg.com

 

 

Re: Bug in DATA using MMTTY ?

Larry K8UT
 

My configuration was similar, although I used 2Tone as my DI application, and loaded MMTTY as the 2nd decoder. With poor band conditions, dual band decoders was a tremendous help. 2Tone seemed to be right more often than MMTTY, but there were also many times when MMTTY was the only decoder to print.

There were no software crashes in my 12 hours of assisted operation: K3S in SO1V, Mortty in FSK, dual decoders, panadapter, high power. For me it was a trouble-free contest.

-larry (K8UT)

------ Original Message ------
From: "Jamie WW3S" <ww3s@...>
Sent: 2018-10-01 06:48:13
Subject: Re: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

yes, I saw it a few times, same setup, Win 7 SO2R, dual decoders, in my case though a window popped up saying N1MM stopped, and it closed itself....
 
From: Jim M0CKE
Sent: Monday, October 01, 2018 3:56 AM
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?
 
Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE

Virus-free. www.avg.com

Re: Bug in DATA using MMTTY ?

ShelbyK4WW
 

This being my first RTTY contest, using N1MM, other than a few operator errors, I would say that N1MM performed flawlessly. One radio, one decoder, probably has a lot to do with that?

On Mon, Oct 1, 2018 at 7:59 AM Bob Epstein via Groups.Io <bobk8ia=aol.com@groups.io> wrote:
Twice, in CQWW RTTY, I saw the same thing in SO2V. Once, I saw the "reoccurring character" situation and the other time the Main (A) receiver side decoders just froze. My only fix was to kill and reboot N1MM+.

The B-receiver side was unaffected. It still operated fine while the A-side froze up.

Setup here Win7, MMTTY and 2Tone on both K3 receivers, i3 processor, 10 GB RAM and not much running in the background. Latest versions of N1MM+ and 2Tone and v1.68a of MMTTY (not latest MMTTY v1.70).

The operation of the K3 remained unaffected during these glitches. 

Any ideas?

Bob K8IA (N7AT)
Arizona Outlaws Contest Club

-------- Original message --------
From: Jim M0CKE <makidoja@...>
Date: 10/1/18 12:56 AM (GMT-07:00)
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ 

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE



--
73, Shelby - K4WW
As I don't have an iPad nor iPhone, sent from my PC

Re: Bug in DATA using MMTTY ?

Bob Epstein K8IA
 

Twice, in CQWW RTTY, I saw the same thing in SO2V. Once, I saw the "reoccurring character" situation and the other time the Main (A) receiver side decoders just froze. My only fix was to kill and reboot N1MM+.

The B-receiver side was unaffected. It still operated fine while the A-side froze up.

Setup here Win7, MMTTY and 2Tone on both K3 receivers, i3 processor, 10 GB RAM and not much running in the background. Latest versions of N1MM+ and 2Tone and v1.68a of MMTTY (not latest MMTTY v1.70).

The operation of the K3 remained unaffected during these glitches. 

Any ideas?

Bob K8IA (N7AT)
Arizona Outlaws Contest Club

-------- Original message --------
From: Jim M0CKE <makidoja@...>
Date: 10/1/18 12:56 AM (GMT-07:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?

Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ 

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE

Re: Bug in DATA using MMTTY ?

Jamie WW3S
 

yes, I saw it a few times, same setup, Win 7 SO2R, dual decoders, in my case though a window popped up saying N1MM stopped, and it closed itself....
 

From: Jim M0CKE
Sent: Monday, October 01, 2018 3:56 AM
Subject: [N1MMLoggerPlus] Bug in DATA using MMTTY ?
 
Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE

Virus-free. www.avg.com

Bug in DATA using MMTTY ?

Jim M0CKE
 

Hi All

Was active in CQWW RTTY as G2F at the weekend SO2R and I had a re-occuring crash

Using windows 7 on a desktop i5 processor

I couldn't replicate but every so often DI1 MMTTY would freeze and sometimes just fill the RX window with reoccurring characters like IIIIII or QQQQQQQ 

Only way out was CTRL-ALT-DEL .. task manager and end task on N1MM and all associated windows then restart N1MM

Anyone else seen this?

Had multiple decoders on each radio, using MMTTY as decoder 1 and 2TONE as decoder 2 .. both using the latest versions available for general download.

Jim M0CKE

Re: Call stack bug - using RTTY DI window in So2r

Jim M0CKE
 

Same issue here .. was a complete pain in the bottom!!!!



Jim M0CKE

-------- Original message --------
From: Jeff AC0C <keepwalking188@...>
Date: 01/10/2018 03:34 (GMT+00:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Call stack bug - using RTTY DI window in So2r

There is a bug in the call stack bug.
>
> If you do not try to terminate the process before it finishes, it
> works ok.  But if you need to stop it (for example you stack the wrong
> call into the list) then trouble begins.
>
> Right clicking on a name seems to work (meaning causes no ill effect).
>
> Click on the "C" mark does clear the window and close it.  But it
> causes a bug.
>
> I am not sure if using the "X" to close the window works or not - i
> recall that pushing the "C" is supposed to be the proper way to clear
> the window (from earlier board comments).
>
> The bug is that N1MM still thinks there is a call - but no call is
> passed to the call entry window.  So a "NOW" event proceeds but a
> blank call is passed - even if the window is closed or empty and still
> open.  If there is a call listed in the box, you can't force it to
> drop into the call entry window by pressing the space button.
>
> This "NOW" event is triggered every time a qso is entered until a full
> uninterrupted sequence (at least one call is stacked, and both calls
> are allowed to flow out).  Restarting the program of course also
> clears the issue.
>
> At one point I did get a crash report.  I can send it to a developer
> if needed.
>
> 73/jeff/ac0c
> alpha-charlie-zero-charlie
> www.ac0c.com
>




Call stack bug - using RTTY DI window in So2r

Jeff AC0C
 

There is a bug in the call stack bug.


If you do not try to terminate the process before it finishes, it works ok.  But if you need to stop it (for example you stack the wrong call into the list) then trouble begins.

Right clicking on a name seems to work (meaning causes no ill effect).

Click on the "C" mark does clear the window and close it.  But it causes a bug.

I am not sure if using the "X" to close the window works or not - i recall that pushing the "C" is supposed to be the proper way to clear the window (from earlier board comments).

The bug is that N1MM still thinks there is a call - but no call is passed to the call entry window.  So a "NOW" event proceeds but a blank call is passed - even if the window is closed or empty and still open.  If there is a call listed in the box, you can't force it to drop into the call entry window by pressing the space button.

This "NOW" event is triggered every time a qso is entered until a full uninterrupted sequence (at least one call is stacked, and both calls are allowed to flow out).  Restarting the program of course also clears the issue.

At one point I did get a crash report.  I can send it to a developer if needed.

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com

Re: K3s + N1MM + FLDIGI setup using USB cable.

ve3ki
 

Instead of looking for a cookbook recipe, try working through what functions are needed and how to implement them.

First, rig control from N1MM+. If you don't already have this working, then to do it using the USB cable the K3S's CONFIG:RS232 needs to be set to USB. Plugging the cable into the rig and powering up the rig should cause Windows to install a driver for the K3S's USB to serial adapter if it hasn't already done so, and the COM port number assigned to the port by Windows will show up in the Windows Device Manager under Ports (COM & LPT). If there is more than one port listed there, you can tell which one is the correct one by unplugging the cable for half a minute or so and plugging it back in while watching Device Manager to see which port number disappears and reappears as you do this. That is the port number you need to configure for rig control in N1MM+. Check that N1MM+ can read the frequency from the rig as you rotate the knob on the radio, and that you can change bands on the radio from N1MM+.

You will also want to set the Mode Control in the N1MM+ Configurer to select the correct modes - Mode sent to radio for RTTY will be AFSK (this will put the K3S into AFSK A when the program is in RTTY mode), and for PSK will be PSK (this will put the K3S into DATA A when the program is in PSK mode).

Next, PTT (TX/RX switching). Since you said you don't want to use VOX (the simplest choice), you have two other choices using the USB cable. The simpler of the two is by radio command. In the N1MM+ Configurer, using the Set button for the COM port you are using for rig control, check the check box that says PTT via Radio Command Digital Mode.

Now, audio. Fldigi needs a sound card to do its thing, and the audio to and from the rig needs to get into that sound card. You want to do that without extra audio cables, so your only choice for a sound card is the USB audio codec inside the rig. You must configure the sound card settings in fldigi to use the rig's USB Audio Codec for both receive and transmit (capture and playback). In the K3S, with the rig in either AFSK A or DATA A, make sure MAIN:MIC SEL is set to LINE IN, and rotate the MIC gain knob so that the setting is not at zero (somewhere between LINE 5 and LINE 10 is usually good). With the K3S's meter in ALC mode, transmitting into a dummy load or on a dead band, set the Windows level control for the USB Audio Codec's "speaker" output and/or the K3S's MIC gain control to get 4-5 bars of indication on the ALC meter.

73,
Rich VE3KI




On Sat, Sep 29, 2018 at 04:44 PM, Jim Shepherd wrote:
I am not getting TX using that combination.  I need the configuration for N1MM and FLDIGI to make this work. I have looked at a lot of websites and no one has just the correct info to make it work........ No, I don't need VOX, CW, FSK, or additional add in programs.  This is supposed to work with just the USB cable between my radio and the computer. I have the latest version of FLDIGI and its location in the 'digital modes' box in the N1MM configuration, and N1MM is fully up to date.

Thanks,
Jim W6US

K3s + N1MM + FLDIGI setup using USB cable.

Jim Shepherd
 

I am not getting TX using that combination.  I need the configuration for N1MM and FLDIGI to make this work. I have looked at a lot of websites and no one has just the correct info to make it work........ No, I don't need VOX, CW, FSK, or additional add in programs.  This is supposed to work with just the USB cable between my radio and the computer. I have the latest version of FLDIGI and its location in the 'digital modes' box in the N1MM configuration, and N1MM is fully up to date.

Thanks,
Jim W6US

Re: Continuing contest on other computer

Juergen Haefele
 

Hello Tom,

thank you for the fast answer. You have saved my weekend!

73 Juergen, DL4SDW

Tom Wagner (N1MM) schrieb:

Yes, it is that simple in your case.

Shut down N1MM+ on the home machine. The database must be closed to copy it.

Copy the database (ending in .s3db) to a thumb drive.

Copy it to the database directory on your remote machine. Don't overwrite the db that is already there if you have a name collision rename it on the remote machine.

Start N1MM+ and open the database.

If you want all your settings copied over, that is more complex.

Tom - N1MM


On 9/29/2018 4:18 PM, Juergen Haefele wrote:
Hello Guys,

is it posible continuing a contest on a second computer? The problem is,
that i began the actual wwdx rtty on my computer at home. Now i have to
go to work tomorrow. At work i can remote my station with my notebook
and perhaps do some qsos. The problem is, that i have to use N1MM+ with
different adjustments when i remote the station. Is there a easy way to
copy the log and continue the contest on a second computer? is it quite
simple like copying the database on the other machine? What do i have to
consider?

73 de Juergen, DL4SDW

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus






Re: Continuing contest on other computer

Tom Wagner (N1MM)
 

Yes, it is that simple in your case.

Shut down N1MM+ on the home machine. The database must be closed to copy it.

Copy the database (ending in .s3db) to a thumb drive.

Copy it to the database directory on your remote machine. Don't overwrite the db that is already there if you have a name collision rename it on the remote machine.

Start N1MM+ and open the database.

If you want all your settings copied over, that is more complex.

Tom - N1MM

On 9/29/2018 4:18 PM, Juergen Haefele wrote:
Hello Guys,

is it posible continuing a contest on a second computer? The problem is,
that i began the actual wwdx rtty on my computer at home. Now i have to
go to work tomorrow. At work i can remote my station with my notebook
and perhaps do some qsos. The problem is, that i have to use N1MM+ with
different adjustments when i remote the station. Is there a easy way to
copy the log and continue the contest on a second computer? is it quite
simple like copying the database on the other machine? What do i have to
consider?

73 de Juergen, DL4SDW

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus



Continuing contest on other computer

Juergen Haefele
 

Hello Guys,

is it posible continuing a contest on a second computer? The problem is,
that i began the actual wwdx rtty on my computer at home. Now i have to
go to work tomorrow. At work i can remote my station with my notebook
and perhaps do some qsos. The problem is, that i have to use N1MM+ with
different adjustments when i remote the station. Is there a easy way to
copy the log and continue the contest on a second computer? is it quite
simple like copying the database on the other machine? What do i have to
consider?

73 de Juergen, DL4SDW

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: MMTTY font color change

Tom Wagner (N1MM)
 

On 9/29/2018 2:45 PM, AL7L@... wrote:
Is there a way to change the color that my own callsign prints when running MMTTY under N1MM? That light yellow color disappears to my old eyes. I can change it in MMTTY, but that part of the pallet screen is not visible when running under N1MM+
Tnx es 73 de AL7L

MMTTY font color change

AL7L@...
 

Is there a way to change the color that my own callsign prints when running MMTTY under N1MM? That light yellow color disappears to my old eyes. I can change it in MMTTY, but that part of the pallet screen is not visible when running under N1MM+
Tnx es 73 de AL7L

Re: QSYing does not wipe the call and spots QSO in Bandmap for Search and Pouce

Tom Wagner (N1MM)
 

If you lose communications with your radio and don't notice it, you would see this behavior.

RF in the CAT cable can cause you to lose comm.  Try setting the Transceiver Timeout Time from the bandmap right-click menu to a higher value.

73,

Tom - N1MM

On 9/29/2018 12:38 PM, Larry K8UT wrote:
Hi Al

Sorry - not seeing that. I'm operating in the CQ WW RTTY today and using this feature successfully.

-larry (K8UT)

------ Original Message ------
From: "Al - N1API" <n1api@... <mailto:n1api@...>>
To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
Sent: 2018-09-29 08:40:08
Subject: [N1MMLoggerPlus] QSYing does not wipe the call and spots QSO in Bandmap for Search and Pouce

Running CQWW RTTY This weekend.

I've reset the option a number of times even restarted the program.  But after awhile the call stays and I have to recheck the option under the Config Tab.  Anyone else see this?

Al - N1API