Date   

Re: NBEMS Testing

Dave AFA1HV <afa1hv@...>
 

Hi everyone.
It was an interesting test to say the least.
After discontinuing my attempts to allow someone else to try, I noticed the MFSK stations moved up a bit. In reading the mail they feel we stepped on their toes. If I did, I'm sorry. I think part of the misunderstanding with other operators is the fact that once we go into the ARQ or beacon mode we are in a semi-automatic mode but they, not understanding the new system, feel they can jump in on the frequency if no one else comes back.
I have had a successful connect several weeks ago and I did show a connect to you Ed but I do not know your end confirmed it. You had a good strong signal here also and it should have worked. Our direct keyboard to keyboard seemed to work ok.
But this is what BETA testing is all about.
Maybe we need to do our psk testing more toward the psk area of the band.

Ed wrote:


Bill McLaughlin wrote:
Hi Ed,

I see a a few there: yourself, WB2HVF, KI8AF and N4UM. Perhaps once
connected the beacon should not activate?

See colliding signals due to that. Signals from all were very good but
a bit congested.

73,

Bill N9DSJ
First off, thanks to all who tried to connect. KI8AF was the weakest and
the only one to successfully connect. WB2HVF was the strongest, but we
never did connect. Then a MFSK-16 station opened up right on frequency,
so I moved up band a little. Only to be clobbered by a RTTY station
calling CQ. I have my TX locked, but I noticed my AFC had to move quite
a bit to copy some of you.

Here is the lineup for tomorrow. I'll be on 3578.5 +1500 at 5:00 A.M EST
in the morning. If that QRG is busy Ill try 3576.0 +1500 and will CQ and
beacon for an hour PSK63. The evening foray will depend on the YL's plans.

I was dismayed to see that one of the offending MFSK-16 stations is a
member of this list. Hopefully the QRM was unintentional.

Good night all...73 and thanks again.

Ed W3NR

Using fldigi/flarq Linux version of NBEMS


Re: NBEMS Testing Wednesday

w1hkj <w1hkj@...>
 

I would say that you have a good understanding of the process Travis.

73, Dave, W1HKJ


Re: NBEMS Testing Wednesday

"travhardin" <ke3y@...>
 

Hi Ed (W3NR),

I was in there at 6:30 CST Wednesday and heard you well. Lots of other
stations did too. Another station and I moved down below you. Then we
moved again. Then we moved up to 3596. If I was the interfering
station (I don't think I was), is was certainly not intentional, and I
am sorry.

You may want to go back and read message #159 from KH6TY, one of the
program developers. Calling "CQ NBEMS" is the best way to start.
Beacon ONLY after establishing contact with ONE station. NBEMS is a
one-on-one mode, it appears. You must narrow the contact down to one
station by writing in the VBDIGI window. Then you as station 1 ask the
selected station to beacon, again by writing in the VBDIGI window.
After station 2 beacons, you -- station 1 -- will soon see station 2's
call letters appear in the top box in FLARC. When the call letters
appear, you -- station 1 -- then select "Connect". The two
transmitters will AUTOMATICALLY query each other a couple of times.
After both stations get a green diamond, either one of you can send a
file, and write coordinating messages in the very bottom line of the
plain talk box.

Any other stations on the frequency may as well move somewhere else
for an hour. The "net control" may want to let them coordinate on
frequency before beginning a transfer himself.

During the file transfer process, the program activates both
transmitters when it needs to. The received file appears in
C:&#92;NBEMS&#92;ARQrecv. File sizes of 500 bytes are appropriate for testing.
Takes about 4 minutes in MFSK16.

The method has worked for me several times. If the path is noisy you
may lose the green diamond. You simply re-beacon. Station 2, when he
sees your call letters in the box, selects "Connect" and the handshake
continues. (It doesn't matter which station beacons and which station
presses "Connect")

I hope if there are corrections or improvements to this the developers
will correct me.

Travis Hardin, KE3Y
Huntsville, Alabama

--- In NBEMSham@..., Ed <autek@...> wrote:

Bill McLaughlin wrote:
Hi Ed,

I see a a few there: yourself, WB2HVF, KI8AF and N4UM. Perhaps once
connected the beacon should not activate?

See colliding signals due to that. Signals from all were very good but
a bit congested.

73,

Bill N9DSJ
First off, thanks to all who tried to connect. KI8AF was the weakest
and
the only one to successfully connect. WB2HVF was the strongest, but we
never did connect. Then a MFSK-16 station opened up right on frequency,
so I moved up band a little. Only to be clobbered by a RTTY station
calling CQ. I have my TX locked, but I noticed my AFC had to move quite
a bit to copy some of you.

Here is the lineup for tomorrow. I'll be on 3578.5 +1500 at 5:00 A.M
EST
in the morning. If that QRG is busy Ill try 3576.0 +1500 and will CQ
and
beacon for an hour PSK63. The evening foray will depend on the YL's
plans.

I was dismayed to see that one of the offending MFSK-16 stations is a
member of this list. Hopefully the QRM was unintentional.

Good night all...73 and thanks again.

Ed W3NR

Using fldigi/flarq Linux version of NBEMS


Re: NBEMS Testing

Ed <autek@...>
 

Bill McLaughlin wrote:
Hi Ed,
I see a a few there: yourself, WB2HVF, KI8AF and N4UM. Perhaps once
connected the beacon should not activate?
See colliding signals due to that. Signals from all were very good but
a bit congested.
73,
Bill N9DSJ
First off, thanks to all who tried to connect. KI8AF was the weakest and the only one to successfully connect. WB2HVF was the strongest, but we never did connect. Then a MFSK-16 station opened up right on frequency, so I moved up band a little. Only to be clobbered by a RTTY station calling CQ. I have my TX locked, but I noticed my AFC had to move quite a bit to copy some of you.

Here is the lineup for tomorrow. I'll be on 3578.5 +1500 at 5:00 A.M EST in the morning. If that QRG is busy Ill try 3576.0 +1500 and will CQ and beacon for an hour PSK63. The evening foray will depend on the YL's plans.

I was dismayed to see that one of the offending MFSK-16 stations is a member of this list. Hopefully the QRM was unintentional.

Good night all...73 and thanks again.

Ed W3NR

Using fldigi/flarq Linux version of NBEMS


Re: NBEMS Testing

"dahupmich" <ki8af@...>
 

Hi All,

Bill glad you heard me in there. Eventually Ed connected with me for a
short one but then lots of QRM with RTTY on one side and MFSK on the
other. Ed helped me out with the "Plain Talk" box so I learned
something new tonight. I had some trouble with the rig wanted to key
up unexpectedly so I need to check that out. I also heard N4UM, WB2HVF
and KE3Y in there. I can't do any testing tomorrow evening but will
give it a try again on Friday.

73,Greg
KI8AF
from da U.P. of Michigan
--- In NBEMSham@..., "Bill McLaughlin" <bmc@...> wrote:

Hi Ed,

I see a a few there: yourself, WB2HVF, KI8AF and N4UM. Perhaps once
connected the beacon should not activate?

See colliding signals due to that. Signals from all were very good but
a bit congested.

73,

Bill N9DSJ




--- In NBEMSham@..., Ed <autek@> wrote:

Tonite.......7:30 till 8:30 EST

3582 +1500
PSK63

I will call cq nbems test, if we can make a connect then I'll
start the
beacon and have a file ready to send once the connection is made to
flarq. We will try PSK63 first and go from there.

Ed W3NR
Chickamauga,GA


Re: NBEMS Testing

"Bill McLaughlin" <bmc@...>
 

Hi Ed,

I see a a few there: yourself, WB2HVF, KI8AF and N4UM. Perhaps once
connected the beacon should not activate?

See colliding signals due to that. Signals from all were very good but
a bit congested.

73,

Bill N9DSJ

--- In NBEMSham@..., Ed <autek@...> wrote:

Tonite.......7:30 till 8:30 EST

3582 +1500
PSK63

I will call cq nbems test, if we can make a connect then I'll start the
beacon and have a file ready to send once the connection is made to
flarq. We will try PSK63 first and go from there.

Ed W3NR
Chickamauga,GA


NBEMS Testing

Ed <autek@...>
 

Tonite.......7:30 till 8:30 EST

3582 +1500
PSK63

I will call cq nbems test, if we can make a connect then I'll start the beacon and have a file ready to send once the connection is made to flarq. We will try PSK63 first and go from there.

Ed W3NR
Chickamauga,GA


New file uploaded to NBEMSham

NBEMSham@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the NBEMSham
group.

File : /Short test files/TED.COM
Uploaded by : travhardin <ke3y@...>
Description : DOS tiny editor from 1988 - 3200 bytes com file

You can access this file at the URL:
http://groups.yahoo.com/group/NBEMSham/files/Short%20test%20files/TED.COM

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.htmlfiles

Regards,

travhardin <ke3y@...>


Re: ted.com

"kh6ty" <hteller@...>
 

TED for DOS! That brings back fond memories! TED.COM was my favorite for years. Maybe written by Tom Kihlken? Can't remember...

Travis, KE3Y, wants to use it to test the binary transfer of NBEMS, and is TED.COM 4K in size. Good choice, I think, and I would not mind trying TED.COM again! :-)

73, Skip

----- Original Message -----
From: "Ed" <autek@...>
To: <NBEMSham@...>
Sent: Tuesday, March 04, 2008 9:20 PM
Subject: [NBEMSham] ted.com


OK, I give....what is it and where is it. In DOS days long ago, ted was
a nifty little text editor.

Ed W3NR


NBEMS TESTING

"tim.n4um" <N4UM@...>
 

Thanks for signal reports. 30 meters can be a tough band in the
evenings! For what it's worth, KE3Y and I found that MFSK16 was a bit
faster(257 seconds) than PSK63 (320 seconds) in sending a 512 byte file
under lousy conditions with static and fading.


ted.com

Ed <autek@...>
 

OK, I give....what is it and where is it. In DOS days long ago, ted was a nifty little text editor.

Ed W3NR


Signal Report NBEMS Testing

"Jeff Moore" <tnetcenter@...>
 

Just wanted to give you guys a signal report.
 
I was able to hear KE3Y pretty good most of time here in Central Oregon.  N4UM OTOH was mostly unreadable, although I did manage to get at least 2 of his beacons on MFSK.
 
Band conditions here were not very good, with a lot of severe fading, and it looks as though you two had problems as well.
 
At one point after you were on PSK63 another signal (I'm not sure what it was but it was very wideband) clobbered both you.  Shortly after that you switched to MFSK and I was able to copy  some of that.
 
I would've tried to join in, but I'm not yet transmit capable.  Soon!
 
Jeff Moore KE7ACY
Bend, Oregon
 
P.S. you're still at as I write this!
 

----- Original Message -----
Subject: Re: [NBEMSham] Tuesday 3/4 1800 & 0100 Z

Tim,
I saw you on air Monday but I was using another program. Domino.

I will be there tonight (Tuesday) at 0100Z. MFSK16.

For the rest of you, I WILL ALSO BEACON TODAY AT NOON CST (1800z). Same
details, MFSK16. After establishing contact, I will ask if you want to
go to PSK125, the fastest mode available in my NBEMS software, for the
file transfer.

Beaconing with a slow mode gives enough time to tune in. Beaconing with
PSK125 doesn't give time to tune in the signal, especially if you beacon
further apart than 15 seconds. That's my experience. Looking forward to
copying someone. I will have a 4KByte com file, TED.COM, ready to
transmit for the test.

Travis Hardin KE3Y
Huntsville, Alabama

tim.n4um wrote:
>
> Hello everybody. I'm a real newbie at NBEMS but would like to become
> more familiar with it. I'll make a special effort to be on 10.137 plus
> 1.5 audio at 0100Z for the next week or so. I'll be beaconing on
> MFSK. I can't make it this evening but will be on beginning tomorrow
> night (Tuesday night EST). If you'd like to set up a sked for some
> other time and frequency please e-mail me.
>
> Tim, N4UM

 

.


Re: NBEMS Testing Schedule

larrytkc@...
 


N4UM - strong signal into KC metro this evening!
Lots of power line noise at my QTH tonight, so copy would be difficult for any mode.

Larry kb0emb

---- Paste of copied text below ----

mFSK mode 3-04-2008 ~0120 UTC - 10.137 mhz

KE3Y KE3Y KE3Y de N4UM N4UM N4UM k
ttpotpj enfu:Mck r*tKE3Y KE3Y KE3Y de N4UM N4UM N4UM k
 tqS"lft:9kxW  N*tK1f eR  Neo edonf o   n0 e w Fni,eo Z  siSnS ok* secltdvet h
 en mmt:wvgE ocatct KE3Y de N4mYes.  Don't make it a big one tho.  Try to use a small block size... either 16 or 31... go o0endR  o Rk rg fconing.   KE3Y de N4UM

---- end of paste -----


Re: NBEMS Testing Schedule

Ed <autek@...>
 

Dave AFA1HV wrote:
There seems to be a pactor station there. I did hear you and N3NR chatting 2 down here in South Jersey. You were a bit weak and fading but N3NR was a solid +20. After you signed I tried to call both of you but it didn't happen.
Dave WB2HVF
Dave, right after I signed with Tim, a quick pitstop and then an afternoon cup of coffee. Sorry I missed you. I do appreciate the signal report, that was 20 watts from an Icom 735 and a homebrew vertical. I'm impressed with fldigi/flarq as an emergency tool. The next order of business is to read and study the help files....

Ed W3NR


Re: NBEMS Testing Schedule

Dave AFA1HV <afa1hv@...>
 

There seems to be a pactor station there. I did hear you and N3NR chatting 2 down here in South Jersey. You were a bit weak and fading but N3NR was a solid +20. After you signed I tried to call both of you but it didn't happen.
Dave WB2HVF


tim.n4um wrote:


Thanks to all who sent me e-mail. In accordance with Skip's suggestion
I will be calling CQ NBEMS (instead of beaconing as initially stated)
using PSK63 (instead of MFSK16 as initially stated) at 0100Z on 10137
plus 1.5 audio for the next week or so. After contact is established
we can try beaconing and then procede to attempt some test file
transfers. I suggest that we drop down in increments of 2 khz if 10137
is busy.


Re: NBEMS Testing Schedule

"kh6ty" <hteller@...>
 

You might also try 40m on 7072.5, USB, plus 1500 Hz if 30m is dead, or 80m at 3582.5, USB,plus 1500 Hz if 40m does not work out. These frequencies are just above the PSK31 activity and where it is suggested that PSK63 activity take place.

The problem on HF is that the F-layer and D-layer keep changing with the time of day. A good NVIS explanation is here: http://www.athensarc.org/nvis.asp

Travis, my 40m antenna coax turned out to have opened. I have now replaced it, and should be OK on 40m next time. You were S8 and Q5 here on 30m until the band dropped out, and then you went first to S2, and finally into the noise, even with MFSK16.

Since 30m is limited to data modes or CW, unless there is Pactor interference, a QSY in steps of 200 Hz is probably enough to reach a clear frequency and would have the advantage that others will still see you on the waterfall.

73 Skip KH6TY
NBEMS Development Team

----- Original Message -----
From: "tim.n4um" <N4UM@...>
To: <NBEMSham@...>
Sent: Tuesday, March 04, 2008 2:32 PM
Subject: [NBEMSham] NBEMS Testing Schedule


Thanks to all who sent me e-mail. In accordance with Skip's suggestion
I will be calling CQ NBEMS (instead of beaconing as initially stated)
using PSK63 (instead of MFSK16 as initially stated) at 0100Z on 10137
plus 1.5 audio for the next week or so. After contact is established
we can try beaconing and then procede to attempt some test file
transfers. I suggest that we drop down in increments of 2 khz if 10137
is busy.




--------------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.4/1310 - Release Date: 3/4/2008 8:35 AM


Re: NBEMS Testing Schedule

Ed <autek@...>
 

tim.n4um wrote:
Thanks to all who sent me e-mail. In accordance with Skip's suggestion I will be calling CQ NBEMS (instead of beaconing as initially stated) using PSK63 (instead of MFSK16 as initially stated) at 0100Z on 10137 plus 1.5 audio for the next week or so. After contact is established we can try beaconing and then procede to attempt some test file transfers. I suggest that we drop down in increments of 2 khz if 10137 is busy.
I was about to suggest the same.

Ed W3NR
Chickamauga,GA


NBEMS Testing Schedule

"tim.n4um" <N4UM@...>
 

Thanks to all who sent me e-mail. In accordance with Skip's suggestion
I will be calling CQ NBEMS (instead of beaconing as initially stated)
using PSK63 (instead of MFSK16 as initially stated) at 0100Z on 10137
plus 1.5 audio for the next week or so. After contact is established
we can try beaconing and then procede to attempt some test file
transfers. I suggest that we drop down in increments of 2 khz if 10137
is busy.


Re: Tuesday 3/4 1800 & 0100 Z

"dahupmich" <ki8af@...>
 

Travis,

I heard your station loud and clear 04Mar08 1810 UTC. I sync with you
almost immediately but you had lots of QSB on your end. I will try
again this evening at 0100 UTC around the same frequency (10137 +/_.

I did make one regular PSK31 contact shortly after that so I know the
NBEMS software (VBdigi) is working.

I'd like to see some sort of net or general time and frequencies so we
could practice and improve on procedures and to get to better
understand the software.

73,
Greg
KI8AF
EN66eh

-- In NBEMSham@..., Travis Hardin <ke3y@...> wrote:

Tim,
I saw you on air Monday but I was using another program. Domino.

I will be there tonight (Tuesday) at 0100Z. MFSK16.

For the rest of you, I WILL ALSO BEACON TODAY AT NOON CST (1800z). Same
details, MFSK16. After establishing contact, I will ask if you want to
go to PSK125, the fastest mode available in my NBEMS software, for the
file transfer.

Beaconing with a slow mode gives enough time to tune in. Beaconing with
PSK125 doesn't give time to tune in the signal, especially if you
beacon
further apart than 15 seconds. That's my experience. Looking forward to
copying someone. I will have a 4KByte com file, TED.COM, ready to
transmit for the test.

Travis Hardin KE3Y
Huntsville, Alabama


tim.n4um wrote:

Hello everybody. I'm a real newbie at NBEMS but would like to become
more familiar with it. I'll make a special effort to be on 10.137 plus
1.5 audio at 0100Z for the next week or so. I'll be beaconing on
MFSK. I can't make it this evening but will be on beginning tomorrow
night (Tuesday night EST). If you'd like to set up a sked for some
other time and frequency please e-mail me.

Tim, N4UM


Messages in this topic
<http://groups.yahoo.com/group/NBEMSham/message/147;_ylc=X3oDMTMzYjZ1ZTRvBF9TAzk3MzU5NzE0BGdycElkAzIxNDU0Nzk3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxNDcEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjA0NTc3MjI0BHRwY0lkAzE0Nw-->

(1)
<http://groups.yahoo.com/group/NBEMSham/post;_ylc=X3oDMTJwZWpxNHA2BF9TAzk3MzU5NzE0BGdycElkAzIxNDU0Nzk3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxNDcEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjA0NTc3MjI0?act=reply&messageNum=147>


Re: Recommended procedure change

"kh6ty" <hteller@...>
 

We have changed the recommended procedure for NBEMS. Instead of beaconing, just call CQ (or CQ EM in a real emergency), or CQ NBEMS. This also gives a station a signal to tune in, and it is a little easier to tune in a PSK63 signal than a MFSK16 signal. Then when a stations answers, you ask him to beacon. This will verify that he also has the NBEMS software, or he obviously will not be able to send a beacon. It will also result in his callsign automatically displaying in your flarq and you can then press Connect when it does. When your flarq shows "Connected", you can proceed to send a message or a file.

Unless conditions appear to be very bad, try first calling CQ in PSK63, and if copy appears to be pretty good, you can try a transfer with flarq using ARQ and PSK63. If there is consistent QRN, MFSK16 might still be the best alternative on HF, but with the slowest transfer times.

Solid print when using PSK63 will often mean that PSK125 can be used successfully on HF, except when there is a high level of repetitive static crashes.

73 Skip KH6TY
NBEMS Develepment Team


For the rest of you, I WILL ALSO BEACON TODAY AT NOON CST (1800z). Same
details, MFSK16. After establishing contact, I will ask if you want to
go to PSK125, the fastest mode available in my NBEMS software, for the
file transfer.

Beaconing with a slow mode gives enough time to tune in. Beaconing with
PSK125 doesn't give time to tune in the signal, especially if you beacon
further apart than 15 seconds. That's my experience. Looking forward to
copying someone. I will have a 4KByte com file, TED.COM, ready to
transmit for the test.

Travis Hardin KE3Y
Huntsville, Alabama


tim.n4um wrote:

Hello everybody. I'm a real newbie at NBEMS but would like to become
more familiar with it. I'll make a special effort to be on 10.137 plus
1.5 audio at 0100Z for the next week or so. I'll be beaconing on
MFSK. I can't make it this evening but will be on beginning tomorrow
night (Tuesday night EST). If you'd like to set up a sked for some
other time and frequency please e-mail me.

Tim, N4UM


Messages in this topic
<http://groups.yahoo.com/group/NBEMSham/message/147;_ylc=X3oDMTMzYjZ1ZTRvBF9TAzk3MzU5NzE0BGdycElkAzIxNDU0Nzk3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxNDcEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjA0NTc3MjI0BHRwY0lkAzE0Nw-->
(1)
<http://groups.yahoo.com/group/NBEMSham/post;_ylc=X3oDMTJwZWpxNHA2BF9TAzk3MzU5NzE0BGdycElkAzIxNDU0Nzk3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxNDcEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjA0NTc3MjI0?act=reply&messageNum=147>

--------------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.4/1310 - Release Date: 3/4/2008 8:35 AM