@KM4ACK Thanks for the shout-out! And probably over-kind words. You can usually not have to worry about the .local/bin stuff if you logout and back in. Most Linux distros check .local/bin to see if it's populated when you log in and adds it to your PATH. Then you'd just type 'fdlogger' in your terminal from any directory. Also I backed down the Python version requirement down to 3.9. I had it at 3.10 because that's what my development environment was at the time and I was... well too lazy to check if it worked on 3.9, but it does and I pushed a version to pypi with the lower requirement. Mike K6GTE
This really is a GREAT piece of software. About time we had something this easy to install/use and most importantly cross platform compatible. I hope to see you continue forward with the project. I did submit a bug report through GitHub. I could be overlooking something but don't think so. After rebooting, the menu icon was in my main menu on Linux Mint. Good to know that you reverted to Python 3.9. That will make it easier for those running a Pi. Will be meeting up with others from my club this weekend to test the networking before Field Day. Myself and a couple of others run Linux, one is a Mac user, and several Windows folks. Will be interesting to test :-)
First of all thanks for the shout out. Being a CW guy, I require CW macros as well as the ability to interface with Winkeyer. This FDlogger also does that as well. 73's an hope to catch you during Field Day! WB8ERJ
Interesting, look and feel is a lot like the N3FJP program for FD. Looks like there’s no automated backup that can be set to back up by number of qso’s (i.e. backup after every 5 qso’s) or by time (backup every 5 minutes). That’s a helpful function. We always backup locally and to a thumb drive as hard drives do crash at times).
Never a bad idea to backup. Looks like the developer is pretty active. Maybe put in a feature request through his github account - github.com/mbridak/FieldDayLogger#k6gte-field-day-logger-gui
Evolve 3 Laptop - amzn.to/3WRwJcW FDLogger Site - github.com/mbridak/FieldDayLogger#k6gte-field-day-logger-gui Mikes Tech Blog - mikestechblog.com/ Instructions for Python on Pi - raspberrytips.com/install-latest-python-raspberry-pi/
@@KM4ACK (I'm stoked that it runs on linux ;-) ) - CQRLog didn't support the latest version of ubuntu last time I checked, so I've been in log limbo for a while.
If possible, I couldn't figure it out. In fact, ran into a bug while trying. github.com/mbridak/FieldDayLogger/issues/32 Hopefully it will be an easy fix that can be applied before Field Day for those that don't use rig control.
I really hope he does not stop there! Maybe integration with FT8 and other modes. Does this pull from the FCC or QRZ database to "hint" what the call might be as you are entering it?
I don't mention it much in the readme, but it does work with WSJT-X, At least it did the last time I used FT8... It will monitor port 2237 for FT8 status messages and log it when a contact is made. As for callsign hints, it matches to super check partial, which I should update...
Ok, but I still like N3FJP Field Day Logger. You never mention Dupes either. The one you had a few years ago for the pi…..that u can use a phone or tablet was much better and practical. What ever happen to that one.
The fact that this can run on a Mac. Might be the best thing yet a lot like N3FJP but it’s not. N3FJP is a great software but only for Windows and who likes Windows?
If it doesn't interface with WSJT-X, then you're manually entering every digital QSO. If it doesn't send CW messages, you're wasting time. Probably doesn't manage a voice keyer either. About the only thing going for this is the cross-platform functionality. Every year, we see someone come along with the latest-greatest field day logging program and the next year they are forgotten. Why? You install a program, play around with it, think you have it figured out, then you go out on field day. In the heat of the battle, you find out what you don't know about it because you've never used it before. And as a new program, no one else has either. You are left scratching your head. QSOs are lost or logged incorrectly. It's not the time for a new, untested program. Been there, done that. Never again. Sorry, it's not Linux or Mac compatible, but there is only one program for serious contest logging: N1MM+ It's stable, updated frequently, and because it does every contest known to man, everyone already knows how it works and it does everything. It does things you didn't know you needed. It's put out by a dedicated team of over a dozen programmers who do it for the benefit of the Amateur Radio contesting community for free.
Mike WB8ERJ has an excellent article about building a 6m quad loop. Highly recommended! That antenna is how I got my Six-Pack Activator POTA award in 2021! 73 VE3GKT
@KM4ACK Thanks for the shout-out! And probably over-kind words.
You can usually not have to worry about the .local/bin stuff if you logout and back in. Most Linux distros check .local/bin to see if it's populated when you log in and adds it to your PATH. Then you'd just type 'fdlogger' in your terminal from any directory.
Also I backed down the Python version requirement down to 3.9. I had it at 3.10 because that's what my development environment was at the time and I was... well too lazy to check if it worked on 3.9, but it does and I pushed a version to pypi with the lower requirement.
Mike K6GTE
This really is a GREAT piece of software. About time we had something this easy to install/use and most importantly cross platform compatible. I hope to see you continue forward with the project. I did submit a bug report through GitHub. I could be overlooking something but don't think so.
After rebooting, the menu icon was in my main menu on Linux Mint. Good to know that you reverted to Python 3.9. That will make it easier for those running a Pi. Will be meeting up with others from my club this weekend to test the networking before Field Day. Myself and a couple of others run Linux, one is a Mac user, and several Windows folks. Will be interesting to test :-)
@@KM4ACK Bug fixed. Thanks!
First of all thanks for the shout out.
Being a CW guy, I require CW macros as well as the ability to interface with Winkeyer. This FDlogger also does that as well.
73's an hope to catch you during Field Day!
WB8ERJ
Thanks for bringing this logger to my attention.
Interesting, look and feel is a lot like the N3FJP program for FD. Looks like there’s no automated backup that can be set to back up by number of qso’s (i.e. backup after every 5 qso’s) or by time (backup every 5 minutes). That’s a helpful function. We always backup locally and to a thumb drive as hard drives do crash at times).
Never a bad idea to backup. Looks like the developer is pretty active. Maybe put in a feature request through his github account - github.com/mbridak/FieldDayLogger#k6gte-field-day-logger-gui
It would be nice if we could get more logging options that dont look like something that ran on my Atari 800 back in the day
😂😂Granted it looks a bit dated but is the easiest cross platform logger I have seen yet.
Great. maybe I will like this one too. I'm Linux only.
looks good and straight forward. maybe he can set one up for Sweepstakes??
Awesome. Thank you
Very Nice, Thanks.
Sweet, ill give it a try. :)
Evolve 3 Laptop - amzn.to/3WRwJcW
FDLogger Site - github.com/mbridak/FieldDayLogger#k6gte-field-day-logger-gui
Mikes Tech Blog - mikestechblog.com/
Instructions for Python on Pi - raspberrytips.com/install-latest-python-raspberry-pi/
Looks like an updated/polished version of N3FJP
I'm stoked that it's cross platform!
@@KM4ACK (I'm stoked that it runs on linux ;-) ) - CQRLog didn't support the latest version of ubuntu last time I checked, so I've been in log limbo for a while.
Can you use this with out Cat control and simply enter the Frequency
If possible, I couldn't figure it out. In fact, ran into a bug while trying. github.com/mbridak/FieldDayLogger/issues/32 Hopefully it will be an easy fix that can be applied before Field Day for those that don't use rig control.
He has already fixed the bug! That took less than 30 minutes :-)
Nice! I'll use it if there is support for POTA.
As of June 2023, HAMRS is still the best logger for POTA imho
@@KM4ACK It's pretty good but I wish it had rig control.
How about auto logging?
Can you log and change who the operator is?
I really hope he does not stop there! Maybe integration with FT8 and other modes. Does this pull from the FCC or QRZ database to "hint" what the call might be as you are entering it?
Currently I believe it only pulls from list of known contesters but not positive.
I don't mention it much in the readme, but it does work with WSJT-X, At least it did the last time I used FT8... It will monitor port 2237 for FT8 status messages and log it when a contact is made. As for callsign hints, it matches to super check partial, which I should update...
@@k6gte outstanding sir!!!
how does one start the central server? I used pip install (linux mint, python 3.10.12) I have fdlogger and it works fine stand alone.
When you connect to other computer s do they need to be all Linux, or Windows, or Mac. Can they be different?
Shouldn't matter the OS they are running on. I'll be testing the network feature this weekend if things go as planned.
Ok, but I still like N3FJP Field Day Logger. You never mention Dupes either. The one you had a few years ago for the pi…..that u can use a phone or tablet was much better and practical. What ever happen to that one.
The fact that this can run on a Mac. Might be the best thing yet a lot like N3FJP but it’s not. N3FJP is a great software but only for Windows and who likes Windows?
If it doesn't interface with WSJT-X, then you're manually entering every digital QSO.
If it doesn't send CW messages, you're wasting time. Probably doesn't manage a voice keyer either.
About the only thing going for this is the cross-platform functionality.
Every year, we see someone come along with the latest-greatest field day logging program and the next year they are forgotten.
Why? You install a program, play around with it, think you have it figured out, then you go out on field day. In the heat of the battle, you find out what you don't know about it because you've never used it before. And as a new program, no one else has either. You are left scratching your head. QSOs are lost or logged incorrectly. It's not the time for a new, untested program. Been there, done that. Never again.
Sorry, it's not Linux or Mac compatible, but there is only one program for serious contest logging: N1MM+ It's stable, updated frequently, and because it does every contest known to man, everyone already knows how it works and it does everything. It does things you didn't know you needed. It's put out by a dedicated team of over a dozen programmers who do it for the benefit of the Amateur Radio contesting community for free.
Mike WB8ERJ has an excellent article about building a 6m quad loop. Highly recommended! That antenna is how I got my Six-Pack Activator POTA award in 2021! 73 VE3GKT