NBEMS application version scheme

Al Womelsdorf

I think I might be the only one messed up here, so I hope I don't cause needless confusion. Personally, I get enough of that during normal life!

Here are the versions of software that I have and use:

-rw-rw-r--. 1 al al  518374 Mar  8 22:10 flamp-
-rw-rw-r--. 1 al al 3916571 Mar  8 21:48 fldigi-
-rw-rw-r--. 1 al al 4682834 Apr 24 08:55 fldigi-
-rw-rw-r--. 1 al al 4695048 May 23 08:38 fldigi-
-rw-rw-r--. 1 al al  912144 Mar  8 22:10 flmsg-
-rw-rw-r--. 1 al al  912265 Apr 24 08:56 flmsg-
-rw-rw-r--. 1 al al  200807 Mar  2 15:48 flwrap-1.3.5.tar.gz

I am current and correct on most, but flamp appear to be way ahead of schedule. I know I got all of these off the website (alpha), so what have I done, and more importantly, what should I do about it?

Thanks.  73's.

Al Womelsdorf


Current distribution versions of the NBEMS suite of programs can be found at

Current development versions of the NBEMS suite of can be found at

Drill down to the folder named for the application of interest.

Program Distribution Version Development Version
flaa 1.0.2
flamp 2.2.04
flcluster 1.0.4
fldigi 4.1.04
fllog 1.2.6 ---
flmsg 4.0.8
flrig 1.3.44
flnet 7.3.2
flwkey 1.2.3
flwrap 1.2.5 ---
linsim 2.0.3 ---
comptext 1.0.1 ---
comptty 1.0.1 ---

73,  David, W1HKJ


At the request of 3rd party NBEMS developers I am changing the version numbering scheme for all NBEMS applications including fldigi, flarq, flrig, fllog etc.

The current triad numbering is still in effect: primary . secondary . tertiary, ie: fldigi-4.1.04

The change only applies to development cycle numbering: primary . secondary . tertiary . quaternary.  In the past the tertiary . quarternary would have bumped the tertiary number to the next release value.  In the future the tertiary will remain at the current release value.

fldigi-4.1.04  - current release

fldigi- - 28th development cycle release post 4.1.04.

73, David, W1HKJ