FlexLogger Emerges

  • 18
  • Idea
  • Updated 1 week ago
Hi All,

A while back I showed my quickly spun logging program and found a fair number of you had some interest.  So... being the idiot I am I decided what I had was far from ready for others to use and I basically rewrote it from scratch.

The new program is currently called FlexLogger.  It currently has a fair number of cool features and the list will continue to grow:
  • Interfaces with your flex, provides a number of in logger flex controls
  • Fast database logging
  • Integrated spots with user configurable spot sources
  • Spots interact with your logger and any online looks you have enabled
  • Monitoring and automatic logging of WSJT-X QSOs
  • SPE serial amp monitoring and control
  • Scripting, assignment of scripts to quick buttons
  • Call lookup via QRZ or HamQTH
  • Qso posting to HRDLOG.NET  (club log coming)
  • CWX macros including speed changes and send of variables
And much more to come!  I have a really big list of future features.

It is in a very early state right now and there are bound to be some issues but I am dedicated to fixing what I can find and making this a really good little logging program.

If you would like to give it a try the installer can be downloaded from here:

http://184.154.226.168/flinstallers/FlexLoggerSetup-0.0.7.0.exe

There are a few things you need to do once it is installed before it is ready to use:
  • Click the gear icon, top left, to enter program configuration.  In here enter any online lookup services you use like QRZ or HamQTH.  There are also some preferences and if you have an SPE and wish to control it over RS-232 you can enable that here as well.
  • Next icon over you must create a station.  The next icon over allows you to define and save a station definition.  This includes things like call, location, grid, etc.
  • Next icon over will let you define an operator.  You can have multiple operators if you are lucky to have multiple hams in the house.
  • Next icon over will let you create a radio definition.  Currently Smartlink connect is not working but you can define details or IP addresses for where your radio is.
  • Next icon over will let you create a database.  FlexLogger will remember and use the last database you open but you can have as many databases as you wish.  For example if you are working a contest you might start a new contest only database.  Totally up to you.
Once you have done these steps you should be able to connect to your radio and the data shown in the slice panels should follow changes to your radio.

At this point you can poke around and look at things.  If you want to import your data from another logging program just export that data to an ADI file then use the log management tab to import the data into your FlexLogger database.

Once you have this version installed, future updates are handled by an in program updater that can download and update your copy to the latest version.

Operationally if you manually enter a call sign into the call field in the log, use the tab key to trigger lookups.   The esc key will clear log entries.

Again, this is very early.  there are some things that will change.  But let me know what you think.


Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes

Posted 3 months ago

  • 18
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3303 Posts
  • 751 Reply Likes
Mark, I admire your work on this. For me though it is still a little complicated because I am not a contester. All I need is something simple to loge contacts I chat with. Nice job...
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi Bill,

I think if you keep an eye on where this is going you will find it can be exactly what you want.

Tonight I worked on dockable panels with the idea that for people exactly like you all you might ever want to use is the log panel.  

This means you can turn off all the other panels, have the log panel be a simple panel where you log your contacts. 

I do think it will get there for you so keep an eye on it.

Mark
Photo of FRED  W9TB

FRED W9TB

  • 156 Posts
  • 56 Reply Likes
Mark
What happened to the update ?
Photo of WW1SS - Steve

WW1SS - Steve

  • 706 Posts
  • 232 Reply Likes
Latest is 0.1.0.0.  Working great here
Photo of FRED  W9TB

FRED W9TB

  • 156 Posts
  • 56 Reply Likes
I have 0.9.2 when I check for updates it tells me I have the latest update.
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Fred,  that is the latest... for now.  A much nicer version is in test and will be out soon.
Photo of FRED  W9TB

FRED W9TB

  • 156 Posts
  • 56 Reply Likes
Thanks Mark I know you will do a good job.
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 957 Posts
  • 179 Reply Likes
Hi Mark and HNY! 

I like FlexLogger although it increases my i7 quadcore CPU
load by 40% running version 0.0.9.0.

Is there a way to lower CPU load? With all the other programs I have to
run CPU load is up to 80%!

Vy 73, Alex - DH2ID
(Edited)
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
Alex- I'm seeing about half of the CPU usage you are (around 26.7%) here on an AMD 8 core for the FlexLogger program. But that is still a fairly high resource amount- considering SSDR is only using 5.2% here.
(Edited)
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
There is a bug in 0.0.9.0 that is running the CPU up at 26%.

I will be fixed in the next release, hopefully this weekend.  But that release will also have a totally new window setup.

So... Let me see if I can pull out a 0.0.9.1 that fixes the CPU load.  Standby
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi all,

Please update to 0.0.9.1 using the check for updates in the help menu.  This release takes the CPU load down to 0.1% for 90% of the operations.

Sorry about the issue.
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
Nice work Mark,  now seeing .1-.3% - 
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Great... Tasks decided to have a little party without permission...
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1770 Posts
  • 542 Reply Likes
WOW, how did I miss this thread?? Thank you so very much Mark. This is something that was really missing for "Flexers". I can't wait to test it out and provide feedback. Thanks again for doing this!
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi All,

If you have FlexLogger installed, please use the help menu and check for updates.  Please update to V0.0.9.1 as it reduces a very high CPU load created by two renegade tasks.

Mark
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Mark,
my "database is empty" How do I put in a file?


Don...w2xb
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Don, 

If the menu bar at the top shows this:



Then you first need to create a database.  Pull down under that menu and select New Database...  Give it a name.  that will create an empty database.  

The next time you run the program this database will automatically be selected for you but it is designed so you can have multiple databases and open which one you want to use.

If you have done the above step then to get existing data into the new database you first need to export your data from your prior logging program.  Currently the only export format supported is ADIF and the output file should be something like <mydata>.adi.

Then go to the "Log Management" tab.  On that tab select the "Import" tab.

The import is a three step process:

1) Select file.  This will allow you to select the ADI file you exported from your old logging program.

2) Process import file.  This will read the selected file and process the text data and create a list of QSOs to import.  This list will be shown to you in the grid at the bottom of the window.  You have the option at this point in time to edit, fix or decide to clear errors or even not import at all.  Nothing has been put in your database yet.

To get the data in your database, this is important:

3) Commit to database.  This will take the list read in from step two and actually commit it to your database.
Photo of Ed Johnson

Ed Johnson

  • 67 Posts
  • 11 Reply Likes
Tried it out for a short while last night.  Works great... appreciate all the effort that must have gone into it.  I have imported my logs from Log4OM and will see how it works over time.
Photo of Mark - WS7M

Mark - WS7M

  • 1189 Posts
  • 418 Reply Likes
Hi Ed...  Make sure you are on 0.0.9.1.  Use help->Check for updates to update.

Check for changes regularly as there are quite a few things that will come online. and Feel free to email me issues.
Photo of Ross Biggar

Ross Biggar

  • 129 Posts
  • 2 Reply Likes
Mark, at last I can now see the complete logger panel.
I only want to show the logger panel, but I still have a white screen  covering all of my 26 inch monitor.
How do I further reduce the size of the screen? Note the white screen is on reduced size nown if I go to a full screen on Flexlogger it covers almost 1 and a half of my monitors.

Photo of Mark - WS7M

Mark - WS7M

  • 1181 Posts
  • 413 Reply Likes
Hi Ross,

In the version you have the lower right corner of the window acts as a size handle.  You can resize the window by grabbing that.  When you find the right spot the cursor will change to a diagonal arrow.

In a version I hope to release this weekend, the screen management, sizing and placement of the windows/panels will be much easier.

Let me know if the size handle makes it usable for you.
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
Mark

9.2 has broken connection to the rig, cant find it, even tried a fresh (add new) no luck
Photo of Mark - WS7M

Mark - WS7M

  • 1176 Posts
  • 412 Reply Likes
In your radio definition, for local connection type, put in or select find "Find"

this was an attempt to get a VPN radio working.
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
thanks - 
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi all,

For anyone that has upgraded to 0.0.9.2 please be advised your radio connection may not work.  This version attempts to fix a VPN based radio connection and as a result it requires a few more parameters in your radio definition.

Please edit your radio definition and select "Find" as the local connection type.

Alternatively if you are using a static IP you can select "Address" and put in the IP.

Lastly, if you are a lucky muliple flex radio owner and you know your serial numbers you can enter the serial number.  Select Find for the local connection type and the code should find the radio with that serial number and connect.
Photo of Chris DL5NAM

Chris DL5NAM

  • 650 Posts
  • 142 Reply Likes
Please can you move SPOT button in upper Log window (we spot only actual QSO's) and remove Edit and Delete from Log window? A double click on a QSO should move this QSO in Log window, then i can edit and click Save

Good work, TNX 
73 Chris


Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Chris, I am not sure I understand your requests.

The intent of the spot button in the log entry window is exactly for what you mention.  You've just had a qso or you are in the middle of one about to complete it, you can hit spot before you save to your log.

Then if you have logged it and realize you want to spot it, there is a spot button in the log list so you can quickly spot the last qso.

I get what you are saying about double click, and that certainly could be done, however the log entry window could get confusing to use as an edit window.  It has features that allow you to update times, modes, frequences to current values which you may not want to do when trying to fix only your RST.

I do plan to provide a "better" qso editor than the extremely low-level version in place now but I am not sure putting the data back into the entry window makes total sense.

But I can be convinced.
Photo of Chris DL5NAM

Chris DL5NAM

  • 650 Posts
  • 142 Reply Likes
Mark, sorry for my writing. In lower logbook  window ( where the QSO's from the past) we dont need a EDIT, SPOT  or DELETE button.

1. a double click on a QSO should open the edit window
2. a old QSO nobody want spot it (Spot button is in upper log window - that's the right place)
3. Delete button should be a button in Edit window

= the logbook window is then better visible  

Hope now it's a bit more clear :-)

73 Chris
Photo of Mike RA3FY

Mike RA3FY

  • 6 Posts
  • 0 Reply Likes
If i right understanding Chris spoke about these pieces.

Photo of Chris DL5NAM

Chris DL5NAM

  • 650 Posts
  • 142 Reply Likes
Yes
Photo of Mike RA3FY

Mike RA3FY

  • 6 Posts
  • 0 Reply Likes
Suppose so, a good idea delete the buttons (Edit Delete Spot) from these scale, and to opens the Edit window by double clicking on a QSO.

Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
I understand the changes you want.  Here is what I am going to likely do:

Currently the columns in the log list are somewhat fixed.  During a particular run of of the program you can right click on the column header and deselect the columns you don't wish to see.  This works right now for all but the edit column.

The issue is that your choices to hide/show columns are not remembered, yet.  They will be.

So here is what I propose to do:

1) Implement the ability to remember the selected columns in the log list.  This means a one time effort by people to turn off the columns they don't want to see.  Each the program is run the columns will only show that the user has enabled.  Obviously you can reenable a column.

2) Add a double click to bring a log entry up in an editor window.

So with these two changes we get the best of both worlds.  For people that want to have the edit, delete, spot buttons they can leave them turned on.  For those who want it more like you describe they can turn them off and then double click will still edit a log entry.
Photo of Mike RA3FY

Mike RA3FY

  • 6 Posts
  • 0 Reply Likes
TNX Mark 
We're believe in your abilities!
Photo of Ross Biggar

Ross Biggar

  • 129 Posts
  • 2 Reply Likes
Thanks Mark that works, and yes I have multiple Flex radios

Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
Super Job Mark so far it is an easy one to use and the connect to Flex is fantastic, still a bug or two but coming along very nice. That said, I tried, after a couple of days, to export a log I had imported a couple of days(versions) ago, and it came up with an error. What follows is a log of the error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: source
   at System.Linq.Enumerable.Count[TSource](IEnumerable`1 source)
   at FlexLoggerApp.MainForm.btnExport_Click(Object sender, EventArgs e) in C:\Dropbox\MRHData\Radio\dev\FlexLogger\Sources\V0.0.9.2\FlexLogger\FlexLoggerApp\MainForm.cs:line 4014
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Fram...
----------------------------------------
FlexLoggerApp
    Assembly Version: 0.0.9.2
    Win32 Version: 0.0.9.2
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Fl...
----------------------------------------
ApplicationLogger
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Ap...
----------------------------------------
Shared
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Sh...
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3314.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
NLog
    Assembly Version: 4.0.0.0
    Win32 Version: 4.5.11.8645
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/NL...
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.ServiceModel
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Deployment
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
System.Collections.Immutable
    Assembly Version: 1.2.3.0
    Win32 Version: 4.6.26515.06
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Sy...
----------------------------------------
netstandard
    Assembly Version: 2.0.0.0
    Win32 Version: 4.7.3190.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
RadioInterface
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Ra...
----------------------------------------
VU_MeterLibrary
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/VU...
----------------------------------------
ObjectListView
    Assembly Version: 2.9.1.1072
    Win32 Version: 2.9.1.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Ob...
----------------------------------------
AutomaticUpdater
    Assembly Version: 2.6.18.4
    Win32 Version: 2.6.18.4
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Au...
----------------------------------------
AudioInterface
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Au...
----------------------------------------
NAudio
    Assembly Version: 1.8.5.0
    Win32 Version: 1.8.5.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/NA...
----------------------------------------
FlexLib
    Assembly Version: 2.4.9.10220
    Win32 Version: 2.4.9.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Fl...
----------------------------------------
Flex.UiWpfFramework
    Assembly Version: 1.0.1.10220
    Win32 Version: 1.0.1.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Fl...
----------------------------------------
Util
    Assembly Version: 1.0.1.10220
    Win32 Version: 1.0.1.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Ut...
----------------------------------------
Vita
    Assembly Version: 1.0.1.10220
    Win32 Version: 1.0.1.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Vi...
----------------------------------------
System.Data.SQLite
    Assembly Version: 1.0.109.0
    Win32 Version: 1.0.109.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Sy...
----------------------------------------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
Dapper
    Assembly Version: 1.50.5.0
    Win32 Version: 1.50.5.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Da...
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------
Spots
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/WS7MApps/FlexLogger/bin/Sp...
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/asse...
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Thoughts?...Jim  KJ7S

Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
Just for clarification: 0.0.9.2
and yes I used the commit button and all that when I originally imported the file, 4992 entries in all, errors corrected or ignored. And I told it to do All entries, not the date limited version.
(Edited)
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi Jim,

Thanks.  It looks like you have some empty entries in the dictionary.  Would you mind sending me your ADI import file.  I can import, and try the export.

Please email to:  ws7m@arrl.net

As far as the JIT debugger, yes, if you have one installed currently it will vector to that.
Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
I looked closer, and it shows no databases, so I re-imported the 'master' .adi file, committed it, and it still shows no database file...?? what am I missing?
Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
 the first time I imported I told it to ignore the errors. The second time I think I did the same with no attempt to change anything, same result...I'll see if I can get the master file to you. Thanks for such a fun logging program. I've been kinda use to N1MM but have really taken a chining to this one.
Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
I noticed someone saying they couldn't connect to the rig with .9.2, mine connects fine, just having trouble showing voltage and temp.
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Jim,

Did you create a database using the top menu where it says <no database>   Pull down under there and create a database.  then try your import.
Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
I believe I did that but I'll try that again and get back.
Photo of Jim  KJ7S

Jim KJ7S

  • 165 Posts
  • 25 Reply Likes
That Did the Trick Mark Thanks for the smack up side the head hihihi... I had to create what is a blank database in order to import an ADI file to the database..duhh.. again, thanks, it's working much better ;)
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Mark,
the software is great! 

workin fb. I am not a dxer , do mostly ragchewing on cw. Can I use Flexlogger as a regular log? Making single entry and entering into the log?


Don...w2xb
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi Don,
I'm trying to make FlexLogger a one-size-fits-all as best I can.  For someone like yourself I could see you just having the slice window open for say Slice A and the log entry and list windows open.

When you want to log a ragchew just enter the data and hit save.  The only thing this mode will help you with is that you won't have to type in the frequency and radio mode as they will be filled in for you.

You can turn on;off the online lookup if desired.  In this simple mode it is nothing more than a logger.  You do not enable spots or any other features.

In a future release all of the panels you currently see now can be drug out into windows.  You can even combine two features like the log entry and log list into a single window and place that anywhere you want on your monitor.

So it is my hope that can be a good "general purpose logger" but it can also be good for the guys needing spots and using WSJT

Mark
Photo of VE3DZP

VE3DZP

  • 25 Posts
  • 6 Reply Likes
Fantastic job from the get go and getting better. Thanks a bunch Mark great job and guess what? No coal for you next Christmas you deserve the best.

Gary~73
VE3DZP
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Mark<
Figured it out. All is fb now





tu...Don  w2xb
Photo of Sergey Abrikosov

Sergey Abrikosov

  • 187 Posts
  • 16 Reply Likes
Hi Mark,
I am getting my radio from service next Monday, so i cannot test it with radio.
I installed latest version out of curiosity.
One of the challange i have (and it is not just your programs) how the scaling work on 4k monitors.
I have 2x27" 4k monitors with scaling 150%.
So, at normal 150% scaling it everything looks unsharp



when changing "override DPI scalling" everything looks messy



Is there any work around?
Thanks
Sergey, KN7K
Photo of Mark - WS7M

Mark - WS7M

  • 1195 Posts
  • 422 Reply Likes
Hi Sergey,

I will do some poking around but the scaling issue can be problematic for a lot of software.   Anyway I'll see what I can find out.
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Hello Mark,
When using flexlogger rig seems to cut out iwck click the restarts. /

seems to pause a split second.then starts agn. Memory in pc?


Don w2xb 
Photo of Mark - WS7M

Mark - WS7M

  • 1195 Posts
  • 422 Reply Likes
Don,

You will need to be a bit more specific.   When any external program connects to a Flex Radio using the API there is a momentary pause, click as the new program gathers data from the radio.  But after that it should be very smooth.

That being said there have been reports that when programs post spots to the radio as FlexLogger can eventually the radio starts to have audio clicks when posting a new spot.  This is a known bug with the radio/API and not something FlexLogger can do anything about.

So if you click/jump you are seeing happens pretty much right after you connect to your radio only then that is normal.  It should be very quick.  Just a click, slight pause then everything should be fine from there.

If you are seeing this happen more often then it could be several things:

1) network - If your network is quite busy then things can get bottled up a bit.  Make sure you have gigabit ethernet.  If you don't, then it is probably time to start thinking about an update.

2) network and SSDR settings.  SSDR allows you to set very fast frame rates on the pans and very fast update rates on the waterfalls.   Keep in mind that fast = more data and more network traffic.   In all honesty you should examine your frame rates and lower them whenever you can.  This puts way less stress on your computer and network.  I find there is a balance between frame rate, waterfall rate, averaging that makes for a nice display without blasting data which has no real purpose.  IE if you are doing frame rates of 25 FPS on all of your slices, keep in mind that it is unlikely you are seeing more of your signals than 18 FPS.   The human visual tolerance level is actually down around 15.  When you go below that you start to see some things.  And probably their are some people that can tell a difference in the display between 15 and 25 FPS but what are they really seeing?

3) Without a doubt, high powered computers are good and good video cards certainly help.   But FlexLogger is NOT a CPU intensive program.  It is not trying (yet) to do real time graphics or anything really fancy.  So it should work quite well on medium power computers.
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
Don,  What are the specs on the system you are running? also what if any A/V
I've seen some A/V programs that start to eat CPU resources badly. McAfee and Norton two of the worst for eating up unneeded resources. If your using one of those could you try and either create an exception rule for SSDR and Flexloger or as a simple test disable it for a minute or so and see if the problem continues.
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 416 Posts
  • 192 Reply Likes
A few suggestions:
  1. In the slices I see the XIT is not directly under the RIT probably because need another slider to balance things out. How about putting Headphone volume either below or to the right of Volume allowing other sliders to shift down.
  2. When selecting bandwidth filter it should be highlighted similar to WNB, NB, NR, etc.
  3. In the logs the refresh button and show last x QSO selection should be placed to the right of the Log/Spots/WSJT-x/Audio tabs and above the log listings, so the log window can be stretched all the way to left as the graphical chart is a nice touch but taking up valuable space.
  4. Making that QSO chart hide/show for same reason. Possibly move it to a tab.

Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi Mike,

A version that will be available next week sometime will have dockable windows for all things.   So you will have MUCH MORE flexibility in where you put things.

As part of this change the slice code has been generalized so that once instance works for all slices.  This will make organization of the slice window much easier.  You are the second person to request the XIT and RIT line up.

The filter button highlighting is a little difficult because there is not a direct API that says this button is on.  it seems to be based on the filter and they are somewhat different between modes.  It is a goal to do this.

Qso chart hiding.  This can sort of be done right now.  Between the chart and the list is a splitter.  You cannot see it but hover your mouse over it and it will show a left-right arrow.  You can drag left to cover most of the stats.

However in the dockable windows version I believe they may become their own window so you can show them or not.

For the refresh and n qsos, I am considering a flyout that is by default hidden so you will get the full space but hovering over it will flyout and make the controls available.  Not sure yet.  But is is under consideration.
Photo of bobby

bobby

  • 55 Posts
  • 21 Reply Likes
Mark can you send me the install zip file for the 0.9.2 versiom, I have installed and upgraded to that version but its doing so well I dont want to upgrade any further but need an install file if I want to install it on another computer. Im happy with it now and dont want to lose it or have to upgrade again. Great job. Maybe you could put the different versions on github its free then anyone could get the version they are happiest with. Thanks so much for a super program.
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Bobby,

All of the versions will be hosted.  Working on setting that up.

The download for 0.0.9.2 is:

http://184.154.226.168/flinstallers/FlexLoggerSetup-0.0.9.2.exe

You can get the older installers using the same URL but change the version number for example:   FlexLoggerSetup-0.0.9.1.exe etc.

As far as not upgrading further that is nice to know it is working well however the next version and ones that follow will offer a number of very nice things.  But of course update is up to you.

Mark
Photo of Joe Camilli

Joe Camilli

  • 3 Posts
  • 0 Reply Likes
Any chance the app will work with PSDR for us lonely 5000 users
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi Joe, I wish I could say yes.  The radio connection is the issue.  The API as I understand it is very different.

That being said, you do not need to connect to the radio.  FlexLogger will work as a logger, show you spots in a list etc.  But connection to the older Flex Radios won't work.
Photo of Craig Williams

Craig Williams

  • 139 Posts
  • 34 Reply Likes
I knew if I just waited quietly the 45% CPU usage would get fixed.
Photo of N8SDR

N8SDR

  • 145 Posts
  • 23 Reply Likes
Mark- Not sure if this is an issue with Flexlogger or HAMqth, when entering a qso (logging) the state field is not being populated, all else looks good, with the exception of the state
Photo of Mark - WS7M

Mark - WS7M

  • 1184 Posts
  • 417 Reply Likes
Ok I got that Rick.   Thanks.  It was not filling the state but it is added now.
Photo of Mark - WS7M

Mark - WS7M

  • 1196 Posts
  • 422 Reply Likes
Hi all,

I just released FlexLogger V0.1.0.1.   PLEASE PLEASE PLEASE take the time to review this movie on how to deal with the panels:

https://www.dropbox.com/s/p3oecu0xg8vxuqb/Docking.mp4?dl=0

I am sorry it is a bit long but I think once you have a chance to check out the panels you will find you can do almost anything you want.

You can update to V0.1.0.1 using the check for updates under the help menu.  Alternatively you can uninstall using control panel and install using the installer at this link:

http://184.154.226.168/flinstallers/FlexLoggerSetup-0.1.0.1.exe

Please do not attempt to run this installer without uninstalling the prior version first.  

Mark
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Mark, EXCELLENT!

Don..W2XB
Photo of Bernie W7DMC

Bernie W7DMC

  • 25 Posts
  • 4 Reply Likes
Mark, great video and program. Like all the new functionality. So wish there were videos like that for other programs and Flex features. Keep up the great work !
Photo of Don

Don

  • 90 Posts
  • 5 Reply Likes
Mark, using the new version and working great. But when I use dx or spoting I can't send cw. Clicking cuts out my signal when I am sending. Don't get this with other logging software. With the clicking and cutting out for a second  makes it unusable for me. But can't say enough about how great the software is....

Don....w2xb
Photo of Mark - WS7M

Mark - WS7M

  • 1195 Posts
  • 422 Reply Likes
Hi Don,

That is actually a reported problem with the Flex Spot API.  It is not a FlexLogger bug.  See:  https://community.flexradio.com/flexradio/topics/slice-master-audio-pop-sending-spots-to-panadapter

It is variable though.  Sometimes I get pops, sometimes I don't.

here is the good thing... While the spots are not on the pan if you turn off posting spots to the radio, they still are in the list and you can click the trigger button.

Mark
(Edited)
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 416 Posts
  • 192 Reply Likes
Just keeps getting better. I've got to comment on the audio portion and how simple it is to record QSOs or from DAX mic and replay them locally or thru radio and rename them. Very nice. Perhaps adding the ability to tie function keys to saved audio.
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Thanks Mike!

I will say that every now and then the audio panel refuses to record from Dax.  I think it is a DAX thing as if I restart Dax it works.

Anyway any and all suggestions will be considered!
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 957 Posts
  • 179 Reply Likes
Hi Mark, I like your program and the new layout possibilities. 
In the radio control window voltage is shown as "3.1V" although the real voltage
is 13.6V. All else works really well.
I also have some suggestions: 
1. Creating slices and panadapters from the program
2. Reading/writing profiles and memories 

73 and thank you again for the great addition to SSDR,
Alex - DH2ID



 
(Edited)
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi Alex,  Yes... Looks like the 1 is getting cut off.  I will take a look.

Creation of slices and pans is on the list too!
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 957 Posts
  • 179 Reply Likes
Thank you, Mark! 
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1770 Posts
  • 542 Reply Likes
Really enjoying seeing updates all the time. Great job Mark.

Minor thing, if I put a call sign in the log and then a make a minor change the Lookup info doesn't update. For example, I type EA4GLJ incorrectly, when I meant to type EA4GLI, so I go into the call sign field and delete the J and replace it with an I, I click on UPDATE or LOOKUP but the information from the first call sign I typed remains. I have to click CLEAR, type the full call sign again and then click on LOOKUP. It would be great if changes on the call sign will trigger the lookup or at least that I can click lookup and get the info without having to clear and type it again.

Thanks!
Photo of Mark - WS7M

Mark - WS7M

  • 1176 Posts
  • 412 Reply Likes
Hi Salvador,

Yes the mistake callsign is awkward.  I will put some more effort into cleaning that up for better functionality.

Thanks for the support!

Mark
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1770 Posts
  • 542 Reply Likes
If you ever decide to add a LOCALIZATION layer I will help you with the SPANISH version.
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 416 Posts
  • 192 Reply Likes
Latest version 1.0.2 Spots no longer were populating bearing, distance or grid. Exited the program does not remember what spot server (eg. ve7cc) selected. Exited the program again, checked ve7cc and bearing, distance and grid again being populated. Then exited again, and 50% of the time those fields are being populated so must be some traffic hangup.
Want to confirm the checkbox POST TO RADIO does work, I had closed down SliceMaster to be sure.
FlexLogger is in desperate need of a large clock display, perhaps at the bottom of Radio Controls where right now there is lots of room, or I suppose a separate panel with grey line feature.
Looking forward to LOTW support as well as awards tracking. Huge feature in HRD I used to target my DX and country/band count.

(Edited)
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi Mike,

At the bottom, left are some outputs called Queues... The next time you see nothing being populated for spots check and see what the Queue readings say.

There are three:   Q1,  Q2, and PQ.    Q1 are priority lookups like when you enter a call into the log entry screen.   Q2 are lower priority lookups and the spots use this.

If the Q2 number is growing it means that the network or the lookup server is not able to supply the data fast enough.  The result will be no grid, bearings etc.

So let me know if that is happening.

On remembering the selected spot server, I will check that out.  It is supposed to remember the ones you had selected and restart them.

Yes on bigger clock.  Agree.  I have downloaded some map images and when things are a little more stable I want to put in grid tracking map, grayline map, bearing and distance map etc.

One more thing on spots and WSJT lookups.  It can hit the online services pretty hard so I am working on a prefix file.  The idea behind the prefix file is that we will attempt to match callsigns to known countries and from a country we will know continent and center grid square.  

I do understand that there is some overlap and mismanagement of callsigns so this will not be 100% but it may be enough to get a beam pointed the right direction for a vast majority of calls.

Where the prefix will fall apart is in the US where you can be a W1 and reside in Alaska.   So in the end lookups will be the best but I'm trying to get relatively good data in all cases.

I will have a simple LOTW working in the next version.  I would like to enhance it further.

Awards tracking is going to come but it is such a large undertaking that I want to make sure I fully understand it before I start down a road and realize what I am doing will not work.

Mark
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Alex,

This thread is so long I could not find your comment about the missing bin and updates not working.

Here is what I suggest:

1) Using control panel, uninstall FlexLogger.  Don't worry it will leave your data in place.

2) Download and install the latest version again:

http://184.154.226.168/flinstallers/FlexLoggerSetup-0.1.0.2.exe
Photo of FRED  W9TB

FRED W9TB

  • 156 Posts
  • 56 Reply Likes
Mark
will we be able to change font sizes later on ?
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
Hi Fred,

Where would font size change make sense to you?   I had not planned to do this but certainly we could take a look.

Mark
Photo of FRED  W9TB

FRED W9TB

  • 156 Posts
  • 56 Reply Likes
Mark
I am old so I would say all of it.
Photo of Mark - WS7M

Mark - WS7M

  • 1194 Posts
  • 422 Reply Likes
LOL Fred, I highly doubt that!   Let me see what can be done.

Mark
Photo of K6HN

K6HN

  • 18 Posts
  • 2 Reply Likes
Mark,

Great work! Love the progress so far and thanks for sharing your work with the community.

One question, I have the KPA500 and KAT500 and both are connected but neither display power etc on the bar graphs. Are the indicators supposed to be operational?

Gary

Photo of Mark - WS7M

Mark - WS7M

  • 1184 Posts
  • 417 Reply Likes
Hi Gary,

Yes Bill has reported the same behavior.  I'm writing code for those in the blind as I don't have those devices.  I expect to release V0.1.0.3 soon and it will have some corrections in it for KAT and KPA
Photo of K6HN

K6HN

  • 18 Posts
  • 2 Reply Likes
Hi Mark,

I'll look for the next release and get you feedback on it's operation.

As to feature requests, is there a way to interface to an antenna rotor in the works or is it possible now somehow? Also I look forward to a map display.

Gary
Photo of Mark - WS7M

Mark - WS7M

  • 1184 Posts
  • 417 Reply Likes
Always possible Gary.  What rotor to you have?  I already have people using the PSTRotator software successfully as FlexLogger can send bearing or grid to that.

Maps are on the list.  Just takes time.

Mark
Photo of K6HN

K6HN

  • 18 Posts
  • 2 Reply Likes
Hmm, I must have missed the PSTRotator comments as that is what I am using. Is there info somewhere on here?

Gary
Photo of Dale - K4DG

Dale - K4DG

  • 17 Posts
  • 3 Reply Likes

Mark:

What a great program! I installed it last week and successfully imported 8000+ QSOs into FlexLogger. I really like the new configurable windows, the direct integration with the Flex 6xxx series radios, and the ability to log a QSO from any active slice.

FYI, I’m currently running ver. 0.1.0.2 of FlexLogger. My OS is Windows 7 64-bit home edition, with all updates. My rig is a Flex 6600 connected to my computer via a gigabit Ethernet switch. I am running version 2.4.9 of SmartSDR.

I’ve noticed a few things in FlexLogger that may be bugs (or user issues):

1.       The latitude/longitude and bearing boxes are not being populated when I enter a call sign into the logging window (I do have my lat/long correctly set in the set up screen). I am using the QRZ.com lookup function which is working OK.

2.       The window for WSJT spots, which was working in the previous version, no longer works. Spots from WSJT-X that were being broadcast to FlexLogger are no longer being picked up by FlexLogger. I have checked my WSJT-X setup (I am running current ver. 2.0) and it hasn’t changed. Spots are going to the Flex panadapter and showing up, but not to the WSJT spots window.

3.       A similar issue is that QSOs from WSJT-X are not being logged to FlexLogger. I do have the WSJT settings in FlexLogger set to automatically log WSJT-X QSOs (I tried this several times with FT-8 QSOs) but nothing happens.

FYI, I normally run SliceMaster by K1DBO when also running WSJT-X. However, I have also run WSJT-X without Slicemaster and see the same behavior, so I don’t think it’s an issue caused by Slicemaster.

4.       The Spots function appears to be working OK, except that the dialog box to enter messages to a cluster server doesn’t appear to do anything. For example, I would like to tell the cluster I have logged into initially to “SH/DX/20” to get the latest 20 DX spots. When I enter this into the dialog box (with the appropriate cluster prefix, such as “VE7CC: message “ nothing gets sent to the cluster. I can confirm that I am logged into the cluster and that I am getting spots from the cluster, but I can’t send a message to the cluster from the dialog box.

On my wish list would be:

·       Rotor control support for Green Heron controllers or at least Hy-Gain DCU protocol, so users don’t have to buy a PstRotor license. PstRotor is a nice program but is overkill for what I need. Something that just takes the beam heading calculated on the logging window and sends a command to the rotor controller is all I need. A nice graphic centered on the user’s QTH (similar to what is done in Logger32) would be nice little extra.

·       Resizable/configurable fonts. I note this is something others have suggested.

·       Option to customize the dialog boxes in the logging window. There are a lot of supplemental fields currently in the logging window that users may never use or need. It would be nice to display just have the ones you want to unclutter this window.

·       Awards tracking and alerts (e.g. for all time new countries or band/mode countries). I see the tab for this (currently blank) and understand this will be added in the future.

·       LOTW upload/download capability, with option to either run on startup/shutdown, or manually.

Mark, thanks again for all your efforts in developing FlexLogger. I’m looking forward to all the improvements and new features you plan to add to this program.

73,

Dale – K4DG
Photo of Mark - WS7M

Mark - WS7M

  • 1176 Posts
  • 412 Reply Likes
Hi Dale,

Thank you very much.  Here are a few comments:

Lat/Long not populating - Located in C:\WS7MApps\FlexLogger\Logs will be a number of log files.  Please run FlexLogger.  Try entering a call sign, ensure the lat/long do not populate then send me the log that matches the day you do this test.

WSJT window - The WSJT window receives its data directly from the UDP broadcast made by WSJT-X.  You must have the UDP broadcast enabled in WSJT-X and make sure the port number matches what you set in FlexLogger configuration.  If you are using JTAlert then it will swallow the full broadcast from WSJT-X meaning nothing will show.  I have sent a message asking for support on this but not received anything so far.

WSJT qso logging.  Most likely this is because you are using JTAlert.  Again it swallows the entire broadcast.  What you can do is turn on in WSJT-X the N1MM log broadcast and change the port in FlexLogger to listen to that port.  That will allow logging to work.

Send spot messages - Are you pressing the SEND button?  That is the only thing that triggers the transmission of the message.  It does look like you are doing it right with the prefix.   To help debug this if you are pressing send:   Check the "Debug" checkbox BEFORE you check the checkbox to connect to the spot server.  This will log a lot of data to the same log file mentioned above.  Try sending a message.  Then send me the log file.

Rotor control - I have on my list to confirm that the scripting language can support RS-232 transmission, I know it can do network.  Assuming this works or if it doesn't I will fix it then it is possible to write a short script to send anything to any device that is RS-232 which would include rotators.   I am willing to help create such scripts for people.  It is fun this comes up because I am looking at an AZ/EL rotator system myself.  Trying to find something reasonably priced.

Resize fonts - I have this request and I am considering it.  It presents big problems that need to be solved.  If you have ever used ACLog they offer a font size option and when you change it many things have to be shuffled around.  It is difficult to make this work well.

Customize dialogs - Again I have this request.  I am considering the best way to do it.

Awards tracking - This is definitely on the list but I want to make sure that the system I design can be flexible enough to track the vast majority of possible awards.  Almost all of these require some fairly intense database queries as well.

LOTW - Next version will include a first pass at LOTW up as well as LOTW check status.  They will need to be triggered manually but they do all the work automatically.   These will be used as a test bed to ensure they work and then we can consider how to automate them better.
Photo of Dale - K4DG

Dale - K4DG

  • 17 Posts
  • 3 Reply Likes
Mark:

I'll go and try your suggestions.

Lat/Long/heading issue: I will get you a debug file.

WSJT issues: FYI, I am not using JT-Alert, so that shouldn't be causing my issues with WSJT-X spots not being picked up by FlexLogger. As I noted earlier, this feature was working in the prior version of FlexLogger I had been using. I will double check my settings in WSJT-X and FlexLogger to be sure FlexLogger is listening to the UDP port set in WSJT-X. I'll let you know if I continue to have issues.

Send spots messages: Yes, I am hitting enter after typing in the message. I'll try to get you a debug file for this.

Thanks again for your efforts!

73,

Dale - K4DG
Photo of Dale - K4DG

Dale - K4DG

  • 17 Posts
  • 3 Reply Likes
Mark:

I've had some more time to play with FlexLogger to see if I can replicate the issues I mentioned a few days ago. I have now upgraded to v 0.1.0.4.

1. Log Entry window: Lat/Long and bearing boxes are not being populated when I enter a call. The other data from QRZ.com is being entered automatically. I'll email you a debug file shortly.

2. Window for WSJT-X is working again. FlexLogger is seeing the broadcasts from WSJT-X and populating this window. BTW, my UDP broadcast port is set to 7831 in both WSJT-X and the FlexLogger configuration editor.

3. Calls logged in WSJT-X are not being automatically logged in Flex Logger. The "automatically log" checkbox in the WSJT "Settings" tab in FlexLogger is checked. FlexLogger is seeing the UDP broadcasts from WSJT-X (see item 2, above). I am not using JTalert.

4. Dialog with Packet Clusters still doesn't seem to work properly. I connect OK, and see spots. If I send a message to the packet cluster server (e.g. ve7cc: sh/dx/20) the cluster responds and displays the most recent 20 DX spots in the Messages window. However, these same 20 spots then do not get entered into the Spots window in FlexLogger. Subsequent spots that are sent by the cluster will show up in the FlexLogger Spots window, but not ones I request via the message dialog.

I'm not sure if this is a "bug" or just unfinished code but the new DX map/clock window is not showing the day/night or gray line terminator positions correctly. The sun position is incorrect also. See the picture I will send you with the debug file for item #1. Also it would be nice if the Clock/Map window was resizable - as it is now, it has to be expanded to get rid of the scroll bars and takes up a lot of space on my monitor.

5. SPE 1.3K-FA support. I still cannot control my amp from the SPE panel in FlexLogger.  I have triple-checked the communications parameters of my set up in FlexLogger, so it is set up to the correct port, correct baud rate, etc. I can confirm that DDUtil v3 also communicates with my SPE amp and operates it properly with these same settings. DDUtil will turn the amp on from the DDUtil control panel and set any of the operating paramters without having to physically touch the amp.

With FlexLogger I first must manually turn on my amp, and then press the Connect button in FlexLogger. The SPE panel in FlexLogger begins pulling data from my amp (heat sink temp, antenna in use, band in use). If I click on the Mode, Power, Input or Antenna buttons it will cause these settings to change in the SPE panel in FlexLogger and the display of my amp. However, clicking on Tune button in the SPE panel does nothing (radio does not key up). Keying up my Flex 6600 does not engage the SPE amp, even if the mode button on the SPE panel in FlexLogger shows "Operating". 

I can try capturing a debug file for this behavior if you think it would be helpful.

Many thanks again for all your efforts in developing FlexLogger. It is a great addition to the Flexer's arsenal. Even with its rough edges, it is my go to logger after having used Logger32 for over a decade.

73,

Dale K4DG
Photo of Mark - WS7M

Mark - WS7M

  • 1176 Posts
  • 412 Reply Likes
Hi Dale,

See below with MARK: in front:

1. Log Entry window: Lat/Long and bearing boxes are not being populated when I enter a call. The other data from QRZ.com is being entered automatically. I'll email you a debug file shortly.

MARK: Debug file will help.  Several other people have this issue.  I do not understand it yet but will keep it on the list to figure out.

2. Window for WSJT-X is working again. FlexLogger is seeing the broadcasts from WSJT-X and populating this window. BTW, my UDP broadcast port is set to 7831 in both WSJT-X and the FlexLogger configuration editor.

MARK: Good to hear.

3. Calls logged in WSJT-X are not being automatically logged in Flex Logger. The "automatically log" checkbox in the WSJT "Settings" tab in FlexLogger is checked. FlexLogger is seeing the UDP broadcasts from WSJT-X (see item 2, above). I am not using JTalert.

MARK: What version of WSJT-X are running?  I will add some debug in the next version so we can see what WSJT-X is sending us.

4. Dialog with Packet Clusters still doesn't seem to work properly. I connect OK, and see spots. If I send a message to the packet cluster server (e.g. ve7cc: sh/dx/20) the cluster responds and displays the most recent 20 DX spots in the Messages window. However, these same 20 spots then do not get entered into the Spots window in FlexLogger. Subsequent spots that are sent by the cluster will show up in the FlexLogger Spots window, but not ones I request via the message dialog.

MARK: All the message send does is transmit the message to the spot server.   If the spot server is responding, IE sending the last 20 as you say then the message is getting there.   Why they are not appearing in the spots window is interesting.  I will try the command you mention  on ve7cc sh/dx/20 and see what happens.

I'm not sure if this is a "bug" or just unfinished code but the new DX map/clock window is not showing the day/night or gray line terminator positions correctly. The sun position is incorrect also. See the picture I will send you with the debug file for item #1. Also it would be nice if the Clock/Map window was resizable - as it is now, it has to be expanded to get rid of the scroll bars and takes up a lot of space on my monitor.

MARK: Unfinished code.  I am working on the sun position computation and quite surprisingly with all our technology, maps and stuff there is not a good implementation of this algorithm that does what I need so I'm having to modify it to get the results we want.

5. SPE 1.3K-FA support. I still cannot control my amp from the SPE panel in FlexLogger.  I have triple-checked the communications parameters of my set up in FlexLogger, so it is set up to the correct port, correct baud rate, etc. I can confirm that DDUtil v3 also communicates with my SPE amp and operates it properly with these same settings. DDUtil will turn the amp on from the DDUtil control panel and set any of the operating paramters without having to physically touch the amp.

With FlexLogger I first must manually turn on my amp, and then press the Connect button in FlexLogger. The SPE panel in FlexLogger begins pulling data from my amp (heat sink temp, antenna in use, band in use). If I click on the Mode, Power, Input or Antenna buttons it will cause these settings to change in the SPE panel in FlexLogger and the display of my amp. However, clicking on Tune button in the SPE panel does nothing (radio does not key up). Keying up my Flex 6600 does not engage the SPE amp, even if the mode button on the SPE panel in FlexLogger shows "Operating". 

MARK:  Ok the tune button may not be connected yet.  I will check.   So you are saying that you are getting readings and modes change etc.  That means we are communicating so it is not an issue with your comm settings.

MARK: I have not tried to implement the on/off via RS-232 yet.   I will put that on the list.  I believe it is as simple as raising or lowering the DTR line.  But I will check.

MARK:  Now on your last comment:  You put the amp in operate mode using FlexLogger and does the front of your amp show operate?  IE light lit?    If you say that keying up your flex does not engage the amp it seems that you do not have a PTT connection.  Were you relying on DDUTIL to do that for you?  FlexLogger does not key the amp.  Typically that is done via a PTT connection from Flex to SPE amp.

MARK:  Anyway Dale, we will get these things resolved.

Mark
Photo of Dale - K4DG

Dale - K4DG

  • 17 Posts
  • 3 Reply Likes
Mark:

Thanks for your reply.

Re #1 and #4; I will await your testing.

Re #2: I am using the latest version of WSJT-X, v 2.0.0

Re #5: I sent you further info about my SPE amp set up in a separate email. Thanks for your response. I will double check the connections between the amp, Flex radio and computer. I will also check again whether the OP and TX indicators on the amp come on when the SPE control panel buttons for these functions are clicked on. 

These are part of the growing pains for any software package. I thank you again for your efforts to bring us a full-fledged logging program for our Flex radios.

73,

Dale - K4DG
Photo of W7NGA

W7NGA

  • 437 Posts
  • 188 Reply Likes
Egad Mark ... I thought you had a *real* job. Where the heck do you find the time for all this?
 -dan
(Edited)