Date   
Problem: Cannot RX/TX QTC While SO2R

Michael Sims
 

Been having a problem with 1.0.7300.0 when trying to send or receive QTC when in SO2R. 

Sequence is work a station on R2 and after sending my QSO information to the other station and he sends his he asks if I want to send or receive QTC.  I do a CNRL Z and press RX Ready.  Unfortunately, the request for him to-send is transmitted on my Radio 1.  At the same time, the R2 QSO information is logged cleared, followed by the other station's call placed once more in the R2 Call Entry window and a Dupe is displayed. 

I've cancelled the QTC and started over, but the same thing happens - get the other stations call in the Call Entry window along with Dupe.   I have been able to send and receive QTCs, but have no idea of all the things I went through to get R2 to be the one sending and receiving the few QTCs I have been able to receive/transmit. 

Is there some special sequence of actions that should be taken for sending or receiving QTC while in SO2R? 

My SO2R operation is a run/run so while xmitting on one radio receiving on the other radio on a different band.  However, I am locked out from trying to send on both radios at the same time. 

Will keep going and try to figure out a sequence to send/receive QTC in SO2R.  Let you know if I find one.

  73,
  Mike, K4GMH

Re: Kenwood TS-890 Connectivity to N1MM

Jim Vilbert
 

Thanks Tom. I have been able to connect the radio to the Kenwood control software.

I am using 38,400 baud rate and the "enhanced" com port is 24. The "standard" port is 23.

Do you have any suggestions for which radio to select?

Jim
K3WU

On Nov 9, 2018, at 6:39 PM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

Please report how you connected the PC and the radio and whether you followed these instructions.

I would start with Kenwood 115000 N, 8, 1 with handshake on both lines. Switch to Always on for both if that does not work.

PC Control
The ARCP-890 radio control program, ARHP-890 radio host
program, ARUA-10 USB audio control program and PC
commands are used to control this transceiver or to enable the use
of a PC speaker or microphone.
• This manual describes only the procedures for configuring the
baud rate of the COM/USB port used for PC control. For more
details on the necessary preparations and method of operation,
please refer to the descriptions of the respective program
software (Help text) and PC command list.
• To control this transceiver via USB cable connection, download
the virtual COM port driver.
• To output the RX audio from the PC speaker using the USB
audio function or transmit the audio input to the PC microphone,
download the ARUA-10 audio controller. (In principle, delay
occurs when USB audio is used. Make use of it for
communication where time lag does not constitute an issue.)
• The abovementioned program, virtual COM port driver and PC
command list can be downloaded from the website below.
http://www.kenwood.com/i/products/info/amateur/
software_download.html
● Make sure not to connect this transceiver and the PC
with the USB cable until the installation of the virtual COM
port driver downloaded from the above URL is
completed.
● If this transceiver is connected to the PC without
installing the virtual COM port driver, a wrong driver that
is not compatible with this transceiver may be installed
and communication with the PC may not be established
properly. To prevent a wrong driver from being installed,
the virtual COM port driver must be installed before
connecting to the PC.
● Before connecting this transceiver with a PC, make sure
to turn off the power of this transceiver.
● The USB function of this transceiver complies with the
USB 2.0 standard. (USB audio complies with USB Audio
Class 1.0.)
Configuring the COM/USB (Rear Panel) Baud Rate
This is used to configure the baud rate of the COM/USB port used
for PC control.
Configure in Menu [7-00] “Baud Rate (COM Port)”
(COM) or Menu [7-01] “Baud Rate (Virtual Standard
COM)” (USB)
COM
Setting Value 4800/ 9600 (default)/ 19200/ 38400/ 57600/
115200 [bps]
USB
Setting Value 9600/ 19200/ 38400/ 57600/ 115200 (default)
[bps]
● To use the baud rate of 38400, 57600 or 115200 bps,
configure the baud rate of the RS-232C port of the PC
you are using to a high speed.
● When using the ARCP-890, use a transfer rate that is as
fast as possible.
● To display the bandscope at the normal speed during
remote control of this transceiver using the ARCP-890
and ARHP-890, it is necessary to use an even higher
baud rate. Connect a home LAN to the LAN connector
on the rear panel.


On 11/9/2018 6:16 PM, Jim Vilbert wrote:
Thanks Gilbert. I really do not know how close to a TS-590 the TS-890 is. I have tried the TS-990, TS-590 and the other Kenwood radios listed in N1MM with no success.

The TS-890 may be a new approach by Kenwood but I really do not know.

Jim
K3WU


On Nov 9, 2018, at 3:29 PM, Gilbert Baron W0MN <w0mn00@... <mailto:w0mn00@...>> wrote:

Is it anything like the 590? I have no trouble with the 590.

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

*From:* N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io> <N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>> *On Behalf Of *Jim Vilbert
*Sent:* Friday, November 9, 2018 14:17
*To:* N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
*Subject:* [N1MMLoggerPlus] Kenwood TS-890 Connectivity to N1MM

Good afternoon all. I am the owner of a new TS-890 and really like the rig. Still having issues trying to connect it to N1MM. Has anyone had any success in getting a TS-890 to connect to N1MM? If so, can you please share the settings?

Thanks!

Jim K3WU


Re: Kenwood TS-890 Connectivity to N1MM

Tom Wagner (N1MM)
 

Please report how you connected the PC and the radio and whether you followed these instructions.

I would start with Kenwood 115000 N, 8, 1 with handshake on both lines.  Switch to Always on for both if that does not work.

PC Control
The ARCP-890 radio control program, ARHP-890 radio host
program, ARUA-10 USB audio control program and PC
commands are used to control this transceiver or to enable the use
of a PC speaker or microphone.
• This manual describes only the procedures for configuring the
baud rate of the COM/USB port used for PC control. For more
details on the necessary preparations and method of operation,
please refer to the descriptions of the respective program
software (Help text) and PC command list.
• To control this transceiver via USB cable connection, download
the virtual COM port driver.
• To output the RX audio from the PC speaker using the USB
audio function or transmit the audio input to the PC microphone,
download the ARUA-10 audio controller. (In principle, delay
occurs when USB audio is used. Make use of it for
communication where time lag does not constitute an issue.)
• The abovementioned program, virtual COM port driver and PC
command list can be downloaded from the website below.
http://www.kenwood.com/i/products/info/amateur/
software_download.html
● Make sure not to connect this transceiver and the PC
with the USB cable until the installation of the virtual COM
port driver downloaded from the above URL is
completed.
● If this transceiver is connected to the PC without
installing the virtual COM port driver, a wrong driver that
is not compatible with this transceiver may be installed
and communication with the PC may not be established
properly. To prevent a wrong driver from being installed,
the virtual COM port driver must be installed before
connecting to the PC.
● Before connecting this transceiver with a PC, make sure
to turn off the power of this transceiver.
● The USB function of this transceiver complies with the
USB 2.0 standard. (USB audio complies with USB Audio
Class 1.0.)
Configuring the COM/USB (Rear Panel) Baud Rate
This is used to configure the baud rate of the COM/USB port used
for PC control.
Configure in Menu [7-00] “Baud Rate (COM Port)”
(COM) or Menu [7-01] “Baud Rate (Virtual Standard
COM)” (USB)
COM
Setting Value 4800/ 9600 (default)/ 19200/ 38400/ 57600/
115200 [bps]
USB
Setting Value 9600/ 19200/ 38400/ 57600/ 115200 (default)
[bps]
● To use the baud rate of 38400, 57600 or 115200 bps,
configure the baud rate of the RS-232C port of the PC
you are using to a high speed.
● When using the ARCP-890, use a transfer rate that is as
fast as possible.
● To display the bandscope at the normal speed during
remote control of this transceiver using the ARCP-890
and ARHP-890, it is necessary to use an even higher
baud rate. Connect a home LAN to the LAN connector
on the rear panel.

On 11/9/2018 6:16 PM, Jim Vilbert wrote:
Thanks Gilbert.  I really do not know how close to a TS-590 the TS-890 is.  I have tried the TS-990, TS-590 and the other Kenwood radios listed in N1MM with no success.

The TS-890 may be a new approach by Kenwood but I really do not know.

Jim
K3WU


On Nov 9, 2018, at 3:29 PM, Gilbert Baron W0MN <w0mn00@... <mailto:w0mn00@...>> wrote:

Is it anything like the 590? I have no trouble with the 590.

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

*From:* N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io> <N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>> *On Behalf Of *Jim Vilbert
*Sent:* Friday, November 9, 2018 14:17
*To:* N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
*Subject:* [N1MMLoggerPlus] Kenwood TS-890 Connectivity to N1MM

Good afternoon all.  I am the owner of a new TS-890 and really like the rig.  Still having issues trying to connect it to N1MM.  Has anyone had any success in getting a TS-890 to connect to N1MM?  If so, can you please share the settings?

Thanks!

Jim K3WU

cabrillo format for RSGBCLUB calls

JAMES SCOTT
 

We have been setting up and testing for the RSGB Club calls contest which is under 24 hours away.
On our test  cabrillo file the RST is omitted and cannot find any way of getting it included.
We are using the RSGBCLUB database which seems to log all of the correct information, just get a gap in the cabrillo file though.
Any advice please?

Re: Kenwood TS-890 Connectivity to N1MM

Jim Vilbert
 

Thanks Gilbert.  I really do not know how close to a TS-590 the TS-890 is.  I have tried the TS-990, TS-590 and the other Kenwood radios listed in N1MM with no success.

The TS-890 may be a new approach by Kenwood but I really do not know.

Jim
K3WU


On Nov 9, 2018, at 3:29 PM, Gilbert Baron W0MN <w0mn00@...> wrote:

Is it anything like the 590? I have no trouble with the 590.

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Jim Vilbert
Sent: Friday, November 9, 2018 14:17
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Kenwood TS-890 Connectivity to N1MM

 

Good afternoon all.  I am the owner of a new TS-890 and really like the rig.  Still having issues trying to connect it to N1MM.  Has anyone had any success in getting a TS-890 to connect to N1MM?  If so, can you please share the settings?

Thanks!

Jim K3WU

WAE RTTY QTC sending with N1MM+ and TinyFSK

Larry K8UT
 

Today we discovered a bug that could truncate a transmitted QTC message in the WAE RTTY contest if you are sending WAE QTC messages from N1MM+ in FSK mode with an Arduino running TinyFSK. This bug ONLY applies if you have connected and configured your TinyFSK in the Configurer >Hardware Port column as a direct serial port.


If your configuration uses that type of a serial port definition then you can download a fix from the www.n1mm.com website's >Files Experimental Versions gallery. (or you could reconfigure your station using the methods for MMTTY or 2Tone listed below).

This fix is not required if your TinyFSK is defined within 2Tone as a >Setup >Settings >Tx Operating Mode "TinyFSK TX", or if within MMTTY as an >Options >Settings >TX >PTT & FSK Port = "tinyfsk."

-larry (K8UT)

Re: History file in OKOMDX

Bruno SA6AXR
 

Thanks Claude,

Now it works! Thank you very much for a quick response.

73

Bruno SA6AXR/SE6N

 

Från: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> För VE2FK
Skickat: den 9 november 2018 20:55
Till: N1MMLoggerPlus@groups.io
Ämne: Re: [N1MMLoggerPlus] History file in OKOMDX

 

Corrected... pse download again and test.

 

73, Claude VE2FK

 

Re: Kenwood TS-890 Connectivity to N1MM

Gilbert Baron W0MN
 

Is it anything like the 590? I have no trouble with the 590.

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Jim Vilbert
Sent: Friday, November 9, 2018 14:17
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Kenwood TS-890 Connectivity to N1MM

 

Good afternoon all.  I am the owner of a new TS-890 and really like the rig.  Still having issues trying to connect it to N1MM.  Has anyone had any success in getting a TS-890 to connect to N1MM?  If so, can you please share the settings?

Thanks!

Jim K3WU

Re: N1MM+ operating problems

Steve London
 

Mode ?

On 11/09/2018 02:13 PM, Jim Pyle wrote:
I’ve been experiencing problems with N1MM+ either locking up or going into transmit mode requiring radio shutdown and program reboot.This has happened on two different computers.I’ll detail the sequence of steps for each computer test.
Computer 1
Started auto repeat CQ at about 6 CQs per minute running 0.8 watts into a dummy load.At 2:30 the program stopped sending CQ.The function keys were inoperative.I checked the error log and no entries.The program was closed via File/Exit/Yes.N1MM+ was restarted as was auto CQ.At 4:32 N1MM+ stopped sending.I checked the error log but no entries.I waited several minutes considering what to do next and N1MM+ began sending again.It ran for 12 minutes, CQing perfectly.I exited the program.
Computer 2
Same setup as for computer 1.Started auto repeat CQ and it stopped after 2 minutes. The function keys were inoperative.No entries in the error log.N1MM+ was closed and reopened.Auto repeat CQ was started and sending stopped after 3:30.No entries in the error log.The program was manually shut down.Restarted N1MM+ and auto repeat CQ.After 11 minutes the transmitter locked on, requiring the radio to be shut off.Had to Ctrl/Alt/Del to close the program.Restarted N1MM+ and auto repeat CQ as before.At 7 minutes sending stopped and function keys inoperative.No error log entries.I exited the program normally.
The same failures have happened to me during contests and it’s frustrating to have to reboot.Both computers are Dell laptops running Windows 7.Other programs run without issue.Both are running the latest version of N1MM+.I must add that Computer 1 was also used with version 1.0.7206 for Field Day and had the same issues.I’m hoping that someone may be able to offer some suggestions for corrective action.
Jim, AA8OY

Re: N1MM+ operating problems

ve3ki
 

Have you disabled the Windows USB selective suspend power setting and the automatic power down settings for your USB ports? See <http://n1mm.hamdocs.com/tiki-index.php?page=Installing+the+Software#Windows_Settings_that_may_affect_program_operation> , or consult the step-by-step summary of steps to take to deal with these at <http://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown> .

73,
Rich VE3KI


On Fri, Nov 9, 2018 at 04:13 PM, Jim Pyle wrote:

I’ve been experiencing problems with N1MM+ either locking up or going into transmit mode requiring radio shutdown and program reboot.  This has happened on two different computers.  I’ll detail the sequence of steps for each computer test.

 

Computer 1

Started auto repeat CQ at about 6 CQs per minute running 0.8 watts into a dummy load.  At 2:30 the program stopped sending CQ.  The function keys were inoperative.  I checked the error log and no entries.  The program was closed via File/Exit/Yes.  N1MM+ was restarted as was auto CQ.  At 4:32 N1MM+ stopped sending.  I checked the error log but no entries.  I waited several minutes considering what to do next and N1MM+ began sending again.  It ran for 12 minutes, CQing perfectly.  I exited the program.

 

Computer 2

Same setup as for computer 1.  Started auto repeat CQ and it stopped after 2 minutes. The function keys were inoperative.  No entries in the error log.  N1MM+ was closed and reopened.  Auto repeat CQ was started and sending stopped after 3:30.  No entries in the error log.  The program was manually shut down.  Restarted N1MM+ and auto repeat CQ.  After 11 minutes the transmitter locked on, requiring the radio to be shut off.  Had to Ctrl/Alt/Del to close the program.  Restarted N1MM+ and auto repeat CQ as before.  At 7 minutes sending stopped and function keys inoperative.  No error log entries.  I exited the program normally.

 

The same failures have happened to me during contests and it’s frustrating to have to reboot.  Both computers are Dell laptops running Windows 7.   Other programs run without issue.  Both are running the latest version of N1MM+.  I must add that Computer 1 was also used with version 1.0.7206 for Field Day and had the same issues.  I’m hoping that someone may be able to offer some suggestions for corrective action.

 

Jim, AA8OY

 

 

N1MM+ operating problems

Jim Pyle
 

I’ve been experiencing problems with N1MM+ either locking up or going into transmit mode requiring radio shutdown and program reboot.  This has happened on two different computers.  I’ll detail the sequence of steps for each computer test.

 

Computer 1

Started auto repeat CQ at about 6 CQs per minute running 0.8 watts into a dummy load.  At 2:30 the program stopped sending CQ.  The function keys were inoperative.  I checked the error log and no entries.  The program was closed via File/Exit/Yes.  N1MM+ was restarted as was auto CQ.  At 4:32 N1MM+ stopped sending.  I checked the error log but no entries.  I waited several minutes considering what to do next and N1MM+ began sending again.  It ran for 12 minutes, CQing perfectly.  I exited the program.

 

Computer 2

Same setup as for computer 1.  Started auto repeat CQ and it stopped after 2 minutes. The function keys were inoperative.  No entries in the error log.  N1MM+ was closed and reopened.  Auto repeat CQ was started and sending stopped after 3:30.  No entries in the error log.  The program was manually shut down.  Restarted N1MM+ and auto repeat CQ.  After 11 minutes the transmitter locked on, requiring the radio to be shut off.  Had to Ctrl/Alt/Del to close the program.  Restarted N1MM+ and auto repeat CQ as before.  At 7 minutes sending stopped and function keys inoperative.  No error log entries.  I exited the program normally.

 

The same failures have happened to me during contests and it’s frustrating to have to reboot.  Both computers are Dell laptops running Windows 7.   Other programs run without issue.  Both are running the latest version of N1MM+.  I must add that Computer 1 was also used with version 1.0.7206 for Field Day and had the same issues.  I’m hoping that someone may be able to offer some suggestions for corrective action.

 

Jim, AA8OY

 

 

Kenwood TS-890 Connectivity to N1MM

Jim Vilbert
 

Good afternoon all.  I am the owner of a new TS-890 and really like the rig.  Still having issues trying to connect it to N1MM.  Has anyone had any success in getting a TS-890 to connect to N1MM?  If so, can you please share the settings?

Thanks!

Jim K3WU

Re: History file in OKOMDX

VE2FK
 

Corrected... pse download again and test.
 
73, Claude VE2FK
 

History file in OKOMDX

Bruno SA6AXR
 

Hi,

I just set up for tomorrow’s OKOMDX- contest. I installed the  OKOMDX.text-file from the Call History files and checked that he Call History Lookup is enabled. However, I don’t see any response in the Exch window. Any suggestion as to what I am doing wrong?

 

73

Bruno / SA6AXR, SE6N in contest

60 meters #n1mm

Pierre HB9AMO <pirobet@...>
 

Hello,

Is there any way to add 60 meter band on DXpedition mode ?

73 Pierre HB9AMO / 5U9AMO

Odp: Re: [N1MMLoggerPlus] SO2R Dropping Serial Numbers

Maciek SQ6MS
 

Good to know that it`s actually not considered as a bug. I did used to it and normally at the end i end up with 
serial numbers difference of 20-30 (against real summary number) 

As long as you keep the callsign in one entry window and you log something on another serial number
for that remaining not logged one is kept. When you wipe it out, without the contact being made that particular
serial number is locked and it`s not released for any further QSO.

To avoid that you can keep the callsign window clear untill you are sure that QSO will be made.
With ESM it`s difficult to control because in S&P mode second press of ENTER will assign and
lock the number automatically.

Or you can ignore this litlle inconvenience and follow Tom`s advice. I never had an issue with inconsistent
serial number order from the organiser...

Vy73`s de Maciek SQ6MS/F4VSQ

Dnia 9 listopada 2018 02:04 Tyler Stewart <k3mm@...> napisał(a):

Boy I remember the days when I had to fight with developers for that feature!  ;)

Ty K3MM

Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Monday, November 5, 2018, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

We need to reserve a serial number if you start a QSO on a radio.  If
you never finish that QSO, it could get dropped. If you finish a couple
of QSOs on the other radio, serial numbers could end up being sent out
of order.  This both normal and unavoidable.

Serial numbers are free, and the contest sponsors don't really care what
order you send them or if they are contiguous, because they understand
the issues with SO2R. All they care about is that the number you sent is
the number that is logged.

Tom - N1MM


On 11/5/2018 2:43 PM, Bill Gillenwater wrote:
> When operating SO2R in a contest with sequential serial numbers I find
> that N1MM drops numbers somehow.
> Jumping from one window to another and back sometimes the serial
> numbers get screwed up.
> Am I missing a setting?
> tnx
> 73 Bill K3SV
>




Re: Flickering Call entry window SOLVED

Stephen Tompsett
 

Try disabling 'serial port enumeration' in the advanced properties of any port not connected to a mouse. This option is normally available for real COM ports and FTDI USB serial ports.

Stephen Tompsett

On Fri, 9 Nov 2018, 13:07 GIWagner@... <giwagner@... wrote:
After a lot of troubleshooting and help by N6TV, the Entry Window flickering was solved by using COM1 (on the motherboard), or by using a USB-to-Serial (FTDI) cable and a virtual COM port.  Using either one of my two hardware serial ports (on a serial card) caused the flickering. 

It was never determined exactly why the hardware serial ports caused the flickering.  However, they did work if the K3's RS232 port was connected directly to a hardware serial port, and not routed through the P3.

73, George, K5KG

Re: Flickering Call entry window SOLVED

GIWagner@k5kg.com
 

After a lot of troubleshooting and help by N6TV, the Entry Window flickering was solved by using COM1 (on the motherboard), or by using a USB-to-Serial (FTDI) cable and a virtual COM port.  Using either one of my two hardware serial ports (on a serial card) caused the flickering. 

It was never determined exactly why the hardware serial ports caused the flickering.  However, they did work if the K3's RS232 port was connected directly to a hardware serial port, and not routed through the P3.

73, George, K5KG

Re: N1MM logger+ on WINE on Linux.

Andy (KU7T)
 

Out of memory. How much RAM do you have?

Andy


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of N S via Groups.Io <kl7rs@...>
Sent: Thursday, November 8, 2018 9:38:31 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] N1MM logger+ on WINE on Linux.
 
Everything works under wine except the Spectrum Scope.  The top half of the screen has a huge X across it (from corner to corner).  All of the controls work though.  I can even tap on the screen and change frequency on the rig.

I hope it's ok to post this log file.  Maybe someone can see something in it that will help figure out how to get the spectrum scope working under wine.


N1MMLogger.net - Version 1.0.7300.0
Built: 10/16/2018 5:20:48 AM
Microsoft Windows NT 6.1.7601 Service Pack 1,64:1,en-US,en-US
Error occurred at: 11/8/2018 10:36:26 PM in Thread: Spectrum UI Thread - a04e7275-83b8-441c-81a1-a84a69775996
---------------------------------------------------------------------------------------
System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.GdiGraphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.ChartGraphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.AreaChart.DrawLine(ChartGraphics graph, CommonElements common, DataPoint point, Series series, PointF[] points, Int32 pointIndex, Single tension)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.LineChart.ProcessChartType(Boolean selection, ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.AreaChart.ProcessChartType(Boolean selection, ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.LineChart.Paint(ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartArea.Paint(ChartGraphics graph)
   at System.Windows.Forms.DataVisualization.Charting.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly)
   at System.Windows.Forms.DataVisualization.Charting.ChartPicture.PaintOffScreen()
   at System.Windows.Forms.DataVisualization.Charting.Selection.HitTest(Int32 x, Int32 y, Boolean ignoreTransparent, ChartElementType[] requestedElementTypes)
   at System.Windows.Forms.DataVisualization.Charting.Chart.HitTest(Int32 x, Int32 y)
   at N1MMLogger.Net.SpectrumWindow.Spectrum_MouseUp(Object sender, MouseEventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1568
---------------------------------------------------------------------------------------


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 57
   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 212
   at N1MMLogger.Net.SpectrumWindow.Spectrum_MouseUp(Object sender, MouseEventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1626
   at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.DataVisualization.Charting.Chart.OnChartMouseUp(MouseEventArgs e)
   at System.Windows.Forms.DataVisualization.Charting.Chart.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.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 System.Windows.Forms.Application.Run(Form mainForm)
   at N1MMLogger.Net.N1MMLoggerCommon.StartSpectrumWindow(Object aGuid) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\N1MMLoggerCommon.vb:line 11403
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)



Norm

Re: N1MM logger+ on WINE on Linux.

N S
 

Everything works under wine except the Spectrum Scope.  The top half of the screen has a huge X across it (from corner to corner).  All of the controls work though.  I can even tap on the screen and change frequency on the rig.

I hope it's ok to post this log file.  Maybe someone can see something in it that will help figure out how to get the spectrum scope working under wine.


N1MMLogger.net - Version 1.0.7300.0
Built: 10/16/2018 5:20:48 AM
Microsoft Windows NT 6.1.7601 Service Pack 1,64:1,en-US,en-US
Error occurred at: 11/8/2018 10:36:26 PM in Thread: Spectrum UI Thread - a04e7275-83b8-441c-81a1-a84a69775996
---------------------------------------------------------------------------------------
System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.GdiGraphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.ChartGraphics.FillPath(Brush brush, GraphicsPath path)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.AreaChart.DrawLine(ChartGraphics graph, CommonElements common, DataPoint point, Series series, PointF[] points, Int32 pointIndex, Single tension)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.LineChart.ProcessChartType(Boolean selection, ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.AreaChart.ProcessChartType(Boolean selection, ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartTypes.LineChart.Paint(ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at System.Windows.Forms.DataVisualization.Charting.ChartArea.Paint(ChartGraphics graph)
   at System.Windows.Forms.DataVisualization.Charting.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly)
   at System.Windows.Forms.DataVisualization.Charting.ChartPicture.PaintOffScreen()
   at System.Windows.Forms.DataVisualization.Charting.Selection.HitTest(Int32 x, Int32 y, Boolean ignoreTransparent, ChartElementType[] requestedElementTypes)
   at System.Windows.Forms.DataVisualization.Charting.Chart.HitTest(Int32 x, Int32 y)
   at N1MMLogger.Net.SpectrumWindow.Spectrum_MouseUp(Object sender, MouseEventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1568
---------------------------------------------------------------------------------------


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 57
   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 212
   at N1MMLogger.Net.SpectrumWindow.Spectrum_MouseUp(Object sender, MouseEventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1626
   at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.DataVisualization.Charting.Chart.OnChartMouseUp(MouseEventArgs e)
   at System.Windows.Forms.DataVisualization.Charting.Chart.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.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 System.Windows.Forms.Application.Run(Form mainForm)
   at N1MMLogger.Net.N1MMLoggerCommon.StartSpectrumWindow(Object aGuid) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\N1MMLoggerCommon.vb:line 11403
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)



Norm