Re: [digitalradio] Re: Keeping NBEMS in mind
John, Our NBEMS for Linux now supports DominoEX-11, DominoEX-16, and DominoEX-22 with ARQ. You might want to experiment with using DominoEx to combat flutter. However, I suggest that yhou disable the AFC on fldigi to keep random noise from dragging the receive frequency around. DominoEX is very tolerant to mistuning, and seems to work well without AFC, even on 2m. In order to compensate for the latency of DominoEx and MFSK16, we have added 9 additional SOH characters to the beginning of each transmission, which is allowed under the ARQ specification, so DominoEx modes will only work under ARQ with the NBEMS flarq program. The comparisons for a 3.3K text file transfer on VHF are: MFSK16: 724 sec PSK63: 403 sec DominoEx16: 378 sec DominoEx22: 276 sec PSK125: 207 sec PSK250: 120 sec Winlink average on HF (Pactor-3) for a 3.3K file: about 224 sec For comparison, Patrick's numbers for his Domino (DF), which is probably DominoEx-8, is -12 db for the lowest S/N. For PSK63, it is -7 dB. For PSK125 it is -5 dB. For MFSK16, it is -13.5 dB. So, the advantage in using DominoEx will mostly be to counter flutter and mistuning. MFSK16 will still hold up the best under deep QSB fades, but is slower and harder to tune. You can download the NBEMS EMCpup ISO from this link: http://www.w1hkj.com/emcpup.html . Just burn a bootable CD and try DominoEx with flarq on a Windows system by booting with the CD and running it live to compare, but you will need someone else also using EMCpup or NBEMS on Linux to test with. Since you will probably be testing on HF, there is probably someone on this list already set up to test with. In fact, I can do it with you on HF. We would be very interested in any results you come up with. 73, Skip NBEMS Development Team - Original Message - From: John Bradley [EMAIL PROTECTED] To: digitalradio@yahoogroups.com Sent: Sunday, March 02, 2008 10:45 PM Subject: RE: [digitalradio] Re: Keeping NBEMS in mind on occasion less than 100 miles on VHF and sometimes as little as 30 miles on 80M HF I disagree with the assumption that for Emcomms we only need span 100 miles. That may be true in higher population areas, and where the state is broken down into counties. Up here we will be working into provincial EOC's, which could be up to 500km away (300 Miles), too far for VHF point to point. Furthermore we don't have the density of hams in the rural areas which we allow for relay points. We have good cellular coverage along our highways, but once off the major roads rural cellular service is very spotty. Internet access via cellular to pass text messages cannot be relied upon, so that throws us back to HF as the most likely link (besides sat Phone) I really don't understand the restrictions that you have in the USA on baud rate and mode restrictions. Your mode works well but would be wonderful a little faster. RFSM 8000 works well, but is wide, and am still not sure how it will work under poor HF conditions. ALE400 works well into the weeds, and it would be great to see you and Patrick team up to combine NBEMS and Ale400 in one package. John VE5MU From: digitalradio@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of kh6ty Sent: Sunday, March 02, 2008 9:13 PM To: digitalradio@yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind John, Over what distance are you getting flutter or Doppler on VHF? I only get the flutter (usually all the time!) when I try to work Charlotte, NC from Charleston, SC on 70 cm, which is 173 miles away, but I am not far enough north for Aurora. For emcomm, we only need to span up to 100 miles. I am interested to know if you also find flutter on VHF within 100 miles. Skip KH6TY - Original Message - From: John Bradley [EMAIL PROTECTED] mailto:jbradley%40sasktel.net To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Sent: Sunday, March 02, 2008 9:30 PM Subject: RE: [digitalradio] Re: Keeping NBEMS in mind This may be true at lower latitudes, but up here at 50 degrees north, we get sustained aurora flutter or Doppler on HF and VHF. Sometimes the audio has a distinct echo. PSK125 and 250 are worse. we do have days where we have strong signals but cannot decode anything. it would be nice to have something a little faster than regular MFSK for a robust mode John VE5MU -Original Message- From: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com [mailto:digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com ] On Behalf Of kh6ty Sent: Sunday, March 02, 2008 4:18 PM To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind I have seen some multiipath, especially when I have tested PSK31 on VHF, but much of that was from aircraft. I am not sure how I can discern multipath when on HF. Is
RE: [digitalradio] Re: Keeping NBEMS in mind
Thanks for the info I have had absolutely no luck with linux, so will wait for a windows update. John VE5MU From: digitalradio@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of kh6ty Sent: Monday, March 03, 2008 9:46 AM To: digitalradio@yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind John, Our NBEMS for Linux now supports DominoEX-11, DominoEX-16, and DominoEX-22 with ARQ. You might want to experiment with using DominoEx to combat flutter. However, I suggest that yhou disable the AFC on fldigi to keep random noise from dragging the receive frequency around. DominoEX is very tolerant to mistuning, and seems to work well without AFC, even on 2m. In order to compensate for the latency of DominoEx and MFSK16, we have added 9 additional SOH characters to the beginning of each transmission, which is allowed under the ARQ specification, so DominoEx modes will only work under ARQ with the NBEMS flarq program. The comparisons for a 3.3K text file transfer on VHF are: MFSK16: 724 sec PSK63: 403 sec DominoEx16: 378 sec DominoEx22: 276 sec PSK125: 207 sec PSK250: 120 sec Winlink average on HF (Pactor-3) for a 3.3K file: about 224 sec For comparison, Patrick's numbers for his Domino (DF), which is probably DominoEx-8, is -12 db for the lowest S/N. For PSK63, it is -7 dB. For PSK125 it is -5 dB. For MFSK16, it is -13.5 dB. So, the advantage in using DominoEx will mostly be to counter flutter and mistuning. MFSK16 will still hold up the best under deep QSB fades, but is slower and harder to tune. You can download the NBEMS EMCpup ISO from this link: http://www.w1hkj.com/emcpup.html . Just burn a bootable CD and try DominoEx with flarq on a Windows system by booting with the CD and running it live to compare, but you will need someone else also using EMCpup or NBEMS on Linux to test with. Since you will probably be testing on HF, there is probably someone on this list already set up to test with. In fact, I can do it with you on HF. We would be very interested in any results you come up with. 73, Skip NBEMS Development Team - Original Message - From: John Bradley [EMAIL PROTECTED] mailto:jbradley%40sasktel.net To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Sent: Sunday, March 02, 2008 10:45 PM Subject: RE: [digitalradio] Re: Keeping NBEMS in mind on occasion less than 100 miles on VHF and sometimes as little as 30 miles on 80M HF I disagree with the assumption that for Emcomms we only need span 100 miles. That may be true in higher population areas, and where the state is broken down into counties. Up here we will be working into provincial EOC's, which could be up to 500km away (300 Miles), too far for VHF point to point. Furthermore we don't have the density of hams in the rural areas which we allow for relay points. We have good cellular coverage along our highways, but once off the major roads rural cellular service is very spotty. Internet access via cellular to pass text messages cannot be relied upon, so that throws us back to HF as the most likely link (besides sat Phone) I really don't understand the restrictions that you have in the USA on baud rate and mode restrictions. Your mode works well but would be wonderful a little faster. RFSM 8000 works well, but is wide, and am still not sure how it will work under poor HF conditions. ALE400 works well into the weeds, and it would be great to see you and Patrick team up to combine NBEMS and Ale400 in one package. John VE5MU From: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com [mailto:digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com ] On Behalf Of kh6ty Sent: Sunday, March 02, 2008 9:13 PM To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind John, Over what distance are you getting flutter or Doppler on VHF? I only get the flutter (usually all the time!) when I try to work Charlotte, NC from Charleston, SC on 70 cm, which is 173 miles away, but I am not far enough north for Aurora. For emcomm, we only need to span up to 100 miles. I am interested to know if you also find flutter on VHF within 100 miles. Skip KH6TY - Original Message - From: John Bradley [EMAIL PROTECTED] mailto:jbradley%40sasktel.net mailto:jbradley%40sasktel.net To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com mailto:digitalradio%40yahoogroups.com Sent: Sunday, March 02, 2008 9:30 PM Subject: RE: [digitalradio] Re: Keeping NBEMS in mind This may be true at lower latitudes, but up here at 50 degrees north, we get sustained aurora flutter or Doppler on HF and VHF. Sometimes the audio has a distinct echo. PSK125 and 250 are worse. we do have days where we have strong signals but cannot decode anything. it would be nice to have something a little faster than
[digitalradio] JT65 in Multipsk
Hi Patrick I let my radio monitor 14.076 when I was at job today. The mode definitively worked. This is my catch: 207:06:52 5 -18 3 30 CQ F8RZ IN95 07:08:52 4 -19 3 30 CQ F8RZ IN95 07:10:52 6 -17 3 30 CQ F8RZ IN95 07:12:52 8 -17 3 30 CQ F8RZ IN95 07:14:52 6 -18 3 30 CQ F8RZ IN95 07:16:52 4 -18 3 30 CQ F8RZ IN95 07:18:52 7 -19 3 30 CQ F8RZ IN95 07:21:52 3 -7 3 27 CQ RU0AOA NO66 07:23:52 10 -9 4 -73 CQ RU0AOA NO66 07:25:52 10 -10 4 -73 DK1YF RU0AOA NO66 07:27:52 10 -13 4 24 DK1YF RU0AOA -13 07:29:52 10 -11 4 -75 DK1YF RU0AOA -13 07:30:52 5 -16 3 277 CQ F8RZ IN95 07:31:52 10 -9 4 -75 DK1YF RU0AOA 07:32:52 4 -15 3 277 CQ F8RZ IN95 07:34:52 7 -17 3 277 CQ F8RZ IN95 07:35:52 9 -13 4 275 F8RZ RU0AOA NO66 07:36:52 5 -17 3 277 RU0AOA F8RZ -5 07:37:52 10 -9 4 275 F8RZ RU0AOA -5 07:38:52 9 -17 3 277 TNX NEW QSO 07:39:52 5 -12 4 275 F8RZ TNX 73 07:41:52 6 -19 3 277 TNX NEW QSO 07:43:52 5 -18 3 277 TNX NEW QSO 07:44:52 8 -15 4 587 JO3MYX RU0AOA NO66 07:46:52 8 -9 4 584 JO3MYX RU0AOA -16 07:48:52 10 -8 4 587 JO3MYX RU0AOA 08:02:52 6 -9 4 396 CQ DG5VO JO71 08:03:52 6 -23 4 581 CQ JO3MYX PM74 08:04:52 10 -8 4 396 CQ DG5VO JO71 08:19:52 10 -10 4 264 CQ EA2ABJ IN82 08:23:52 10 -10 4 264 CQ EA2ABJ IN82 08:25:52 10 -11 4 264 CQ EA2ABJ IN82 08:26:52 10 -7 3 293 CQ DK1YF JN57 08:27:52 10 -9 7 264 CQ EA2ABJ IN82 08:28:52 10 -9 3 293 CQ DK1YF JN57 08:29:52 10 -11 7 264 CQ EA2ABJ IN82 08:30:52 10 -8 3 293 CQ DK1YF JN57 08:31:52 10 -12 7 261 CQ EA2ABJ IN82 08:32:52 10 -9 3 293 CQ DK1YF JN57 08:55:52 5 -15 4 347 CQ S51RB JN76 08:57:52 2 -12 4 345 CQ S51RB JN76 08:59:52 10 -11 4 345 CQ S51RB JN76 09:01:52 10 -13 4 342 CQ S51RB JN76 09:06:52 10 -10 4 320 S51RB DK1YF JN57 09:07:52 10 -8 4 331 DK1YF S51RB -14 09:08:52 10 -11 3 320 S51RB DK1YF JN57 09:09:52 10 -10 4 328 DK1YF S51RB -14 09:10:52 10 -13 3 342 S51RB DK1YF JN57 09:11:52 10 -8 4 326 DK1YF S51RB -14 09:12:52 10 -12 3 342 S51RB DK1YF JN57 09:13:53 10 -11 4 323 CQ S51RB JN76 09:14:52 10 -7 3 345 CQ DK1YF JN57 09:15:53 8 -9 4 322 CQ S51RB JN76 09:16:52 3 -19 4 511 VK5OA JA3CAY PM74 09:17:52 8 -11 4 318 CQ S51RB JN76 09:19:52 10 -10 4 318 CQ S51RB JN76 09:20:52 4 -18 0 538 S51RB SM2DR JP93 09:22:52 6 -15 0 536 S51RB SM2DR JP93 09:23:52 9 -9 4 312 CQ S51RB JN76 09:24:52 6 -15 0 530 S51RB SM2DR JP93 09:26:52 8 -24 0 528 S51RB SM2DR JP93 09:29:52 10 -10 4 307 G3CCO S51RB JN76 09:30:52 9 -15 0 519 CQ SM2DR JP93 09:31:53 7 -17 4 304 G3CCO S51RB JN76 09:32:52 4 -17 4 517 CQ SM2DR JP93 09:33:52 8 -15 4 304 G3CCO S51RB R-4 09:35:52 10 -14 4 301 G3CCO S51RB R-4 09:39:52 2 -10 3 202 CQ F1JFR JN38 09:40:52 10 -11 4 299 CQ S51RB JN76 09:41:52 10 -16 3 202 CQ F1JFR JN38 09:42:52 7 -11 4 -215 CQ DX DX G3CC 09:43:52 7 -6 3 202 CQ F1JFR JN38 09:46:52 3 -14 4 -215 CQ DX DX G3CC 09:49:52 6 -20 4 -213 CHK WHAT U TX 09:50:52 8 -20 4 280 G3CC JA1FMU PM96 09:54:52 6 -21 5 390 CQ DG5VO JO71 09:56:52 5 -20 5 390 CQ DG5VO JO71 09:58:52 5 -19 5 393 CQ DG5VO JO71 09:59:52 4 -16 4 261 DG5VO 9K2YM LL48 10:00:52 10 -17 5 396 CQ DG5VO JO71 10:01:52 7 -8 3 261 DG5VO 9K2YM LL48 10:04:52 4 -11 4 398 9K2YM DG5VO -4 10:06:52 1 -21 4 258 CQ DJ2CV JO64 10:07:52 7 -8 3 261 DG5VO 9K2YM 10:08:52 10 -7 4 404 9K2YM DG5VO 10:12:52 10 -6 4 404 TNX YAS 73 T 10:13:52 10 -9 3 -59 CQ F1JFR JN38 10:14:52 5 -14 4 404 CQ DG5VO JO71 10:15:52 10 -7 3 -59 CQ F1JFR JN38 10:17:52 10 -9 3 -59 CQ F1JFR JN38 10:18:52 6 -22 4 -57 F1JFR GW8ASA IO81 10:19:52 10 -9 3 -59 GW8ASA F1JFR JN38 OOO 10:21:52 10 -10 3 -59 GW8ASA F1JFR JN38 OOO 10:22:52 6 -20 4 -57 F1JFR GW8ASA R-11 10:23:52 10 -7 4 404 CQ DG5VO JO71 10:24:52 7 -22 4 -57 F1JFR GW8ASA 10:25:52 10 -8 -61 73 10:27:52 9 -8 4 280 CQ JR3MCV PM74 10:29:52 9 -17 3 -59 CQ F1JFR JN38 10:31:52 10 -11 4 -62 CQ F1JFR JN38 10:34:52 10 -8 4 293 CQ DK1YF JN57 10:41:52 4 -16 4 304 JR3MCV DL7VKD -24 10:43:52 8 -16 4 307 JR3MCV DL7VKD 10:44:52 10 -7 4 32 CQ F8RZ IN95 10:45:52 7 -14 4 307 75W/AV-640 73 10:46:52 10 -6 4 32 CQ F8RZ IN95 10:47:52 6 -7 2 27 F8RZ DL1DWL JO71 10:48:52 10 -10 4 32 DL1DWL F8RZ -6 10:49:52 7 -10 2 19 F8RZ DL1DWL 10:50:52 10 -11 4 30 DL1DWL F8RZ -6 10:51:52 10 -7 15 RRR 10:52:52 10 -7 4 30 DL1DWL TKS 73 10:53:52 10 -7 2 13 TNX 73 DL1DW 11:04:52 10 -25 474 RO 11:06:52 10 -19 4 248 CQ JE5FLM PM74 11:08:52 10 -12 1 277 JA6XBH DH6KOS JO61 11:10:52 4 -9 3 277 JA6XBH DH6KOS JO61 11:11:52 5 -11 3 -19 JN1VNW DK1YF JN57 11:12:52 6 -11 4 326 K2RMM DL3VDL JO60 11:14:52 10 -9
RE: [digitalradio] JT65 in Multipsk
Also copied F8RZ over here, in DO70 .good signal. now need F6CTE ;) John VE5MU Subject: [digitalradio] JT65 in Multipsk Hi Patrick I let my radio monitor 14.076 when I was at job today. The mode definitively worked. This is my catch: 207:06:52 5 -18 3 30 CQ F8RZ IN95 07:08:52 4 -19 3 30 CQ F8RZ IN95 07:10:52 6 -17 3 30 CQ F8RZ IN95 07:12:52 8 -17 3 30 CQ F8RZ IN95 07:14:52 6 -18 3 30 CQ F8RZ IN95 07:16:52 4 -18 3 30 CQ F8RZ IN95 07:18:52 7 -19 3 30 CQ F8RZ IN95
Re: [digitalradio] Re: Keeping NBEMS in mind
Not only are EOC's that far away, but when a hurricane hits the Gulf Coast, you can have all communications interrupted for much more than 100 miles. 73, Walt/K5YFW John Bradley wrote: on occasion less than 100 miles on VHF and sometimes as little as 30 miles on 80M HF I disagree with the assumption that for Emcomms we only need span 100 miles. That may be true in higher population areas, and where the state is broken down into counties. Up here we will be working into provincial EOC's, which could be up to 500km away (300 Miles), too far for VHF point to point. Furthermore we don't have the density of hams in the rural areas which we allow for relay points. We have good cellular coverage along our highways, but once off the major roads rural cellular service is very spotty. Internet access via cellular to pass text messages cannot be relied upon, so that throws us back to HF as the most likely link (besides sat Phone) I really don't understand the restrictions that you have in the USA on baud rate and mode restrictions. Your mode works well but would be wonderful a little faster. RFSM 8000 works well, but is wide, and am still not sure how it will work under poor HF conditions. ALE400 works well into the weeds, and it would be great to see you and Patrick team up to combine NBEMS and Ale400 in one package. John VE5MU From: digitalradio@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of kh6ty Sent: Sunday, March 02, 2008 9:13 PM To: digitalradio@yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind John, Over what distance are you getting flutter or Doppler on VHF? I only get the flutter (usually all the time!) when I try to work Charlotte, NC from Charleston, SC on 70 cm, which is 173 miles away, but I am not far enough north for Aurora. For emcomm, we only need to span up to 100 miles. I am interested to know if you also find flutter on VHF within 100 miles. Skip KH6TY - Original Message - From: John Bradley [EMAIL PROTECTED] mailto:jbradley%40sasktel.net To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Sent: Sunday, March 02, 2008 9:30 PM Subject: RE: [digitalradio] Re: Keeping NBEMS in mind This may be true at lower latitudes, but up here at 50 degrees north, we get sustained aurora flutter or Doppler on HF and VHF. Sometimes the audio has a distinct echo. PSK125 and 250 are worse. we do have days where we have strong signals but cannot decode anything. it would be nice to have something a little faster than regular MFSK for a robust mode John VE5MU -Original Message- From: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com [mailto:digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com ] On Behalf Of kh6ty Sent: Sunday, March 02, 2008 4:18 PM To: digitalradio@yahoogroups.com mailto:digitalradio%40yahoogroups.com Subject: Re: [digitalradio] Re: Keeping NBEMS in mind I have seen some multiipath, especially when I have tested PSK31 on VHF, but much of that was from aircraft. I am not sure how I can discern multipath when on HF. Is there any clue in the waterfall or do you go by the sound? 73, Rick, KV9U You will see three kinds of multipath on VHF, which you can see on the waterfall. One is reflections from airplanes, which tends to look like a ghost signal accelerating across the main signal. When it coincides with the main signal, all copy will be momentarily lost, no matter how strong the signal. The second correlates with wind conditions, and the ghost signal moves slightly in and out of the main signal during wind gusts, especially when a weather front is moving through. The third is reflections from fixed objects, and the ghost signal tends to stay a fixed distance away from the main signal. PSK63 is less affected by multipath reflections than PSK31 is on VHF, and PSK125 even less so. When cancellation does occur, if you are using ARQ, that frame is just resent and the transfer is delayed by that much. Of course, only ARQ is going to guarantee error-free copy. FEC only helps, but does not insure no errors. QRN seems to be the biggest problem on HF and QSB second. During a period of thunderstorm activity, as we often have in South Carolina, and more especially in Florida, PSK125 is greatly disturbed and PSK250 so much that it is unusable, but PSK63 not nearly as much. All the decoders seem to have this problem, and there may be a way to improve that cascaded loss of sync in the faster modes, due to QRN, but we have not yet tackled this problem. Fortunately, for our 100 mile emcomm uses, QRN and QSB are not problems on VHF, and ARQ takes care of the multipath reflection problem. 73, Skip KH6TY Announce your digital presence via our Interactive Sked Page at http://www.obriensweb.com/sked Check our other Yahoo Groups http://groups.yahoo.com/group/dxlist/
Re: [digitalradio] Re: Keeping NBEMS in mind
In that case, it will be necessary to switch to HF and use NVIS antennas, which extends the range to 300 miles but with somewhat less throughput using ARQ due to static crashes. Using ARQ will still get the messages through without errors - it just takes longer. 73, Skip KH6TY Not only are EOC's that far away, but when a hurricane hits the Gulf Coast, you can have all communications interrupted for much more than 100 miles. 73, Walt/K5YFW
Re: [digitalradio] Re: Keeping NBEMS in mind
Skip, We do plan on using HD, NVIS antennas and data modes as long as they are faster than I can receive CW (about 15 WPM accurately. The noise level is what is so high after a hurricane...and it stays that way for 2-4 days. Walt/K5YFW kh6ty wrote: In that case, it will be necessary to switch to HF and use NVIS antennas, which extends the range to 300 miles but with somewhat less throughput using ARQ due to static crashes. Using ARQ will still get the messages through without errors - it just takes longer. 73, Skip KH6TY Not only are EOC's that far away, but when a hurricane hits the Gulf Coast, you can have all communications interrupted for much more than 100 miles. 73, Walt/K5YFW
[digitalradio] MicroHAMS Digital Conference 2008, 3/22 @ Microsoft
MicroHAMS Digital Conference 2008 announcement Announcing the second annual MicroHAMS Digital Conference! The event will be held this year on the main Microsoft campus located in Redmond, WA on March 22nd, 2008. The agenda this year will include a wide variety of topics around digital communications and Amateur radio. Lunch and snacks are included with the price of the conference and we'll have free Internet access. Because of space limitations and parking requirements on the Microsoft campus, we are strongly suggesting pre-registering for the event. Registration is $12.00 if done prior to the event and will be $15.00 at the door. Door Prizes include donations from Icom and MicroHAMS. Event Details Date/Time: March 22, 2008 09:00 to 17:00 Location: Redmond, WA (Building 122 on the Microsoft Corporate Campus) Lunch: Sub sandwiches and snacks (included with registration fee) Cost: $12.00 if pre-paid or $15.00 at the door. Information Registration: http://www.microhams.com/softcontent.aspx?scId=46 Bob, W7LRD Agenda TimePresenterTitle Description 9:00AMN8GNJ / Steve StrohAmateur Radio Networking An overview of Amateur Packet Radio Networking 3.0. 1.0 was the original Packet Radio, Net/ROM networking, BBS, etc. 2.0 was TCP/IP, APRS and other follow-ons to Packet Radio. 10:00AMKK7UQ / Clint HurdMoving away from RS232 devices to the world of USB!Use a single USB cable to connect to an integrated sound card, CW and RTTY interface - and get improved performance at the same time. 11:00AMKE7DEN / Dennis HardingMicrosoft .Net and Mapping API for Hams,- an introductionMicrosoft provides several .Net API for device communications and mapping of data. This talk will focus on .Net API that can be used for local and remote control of serial devices, and the mapping of data using the MapPoint and Virtual Earth API. Example application showing the use of the API will be provided to enable participants to develop their own applications using free development tools from Microsoft. NOONLunchSandwiches, Chips and PopTurkey, Ham, Roast Beef and Veggie 1:30PMKK7P / Lyle JohnsonPSK31 Without a ComputerOpen source solution being sponsor by the AmQRP group, to build a DSP based hardware modem. Also a look at the Elecraft K3 internal CW - PSK31 function. 2:30PMN7SS / Scott HonakerGetting online with DSTARUsing DSTAR and some of the latest DSTAR tools 3:30PMKC7IGT / Miguel MayorgaRemote Station Operation via the Internet Leveraging the internet to operate your home rig from anywhere. A look at the system integration required for enabling a operating your home rig via the internet and the how much fun a remote setup can be. 4:30PMN0AX / Ward SilverModulations, Protocols and Modes - Oh My! The talk would cover these basic differences between modulation, protocol and a mode; give a review of what a stack is, and present specific instances as illustrations. The goal is to equip hams to be better able to discuss digital communications. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
[digitalradio] Re: [DigitalModes] MicroHAMS Digital Conference 2008, 3/22 @ Microsoft
What a great set of talks - wish I lived a bit closer. Simon Brown, HB9DRV -- From: Mark Thompson [EMAIL PROTECTED] MicroHAMS Digital Conference 2008 announcement
Re: [digitalradio] Re: Keeping NBEMS in mind
Walt, Give DominoEx-22 or DominoEX-16 a try. Speed will probably a litttle less than using Pactor-3. Running Emcpup live is pretty simple. You don't even need to know anything about Linux. Patrick includes all the Domino modes in Multipsk and you can try DominoEx under Windows, but without ARQ. When using ARQ, the throughput will be about half as much as without ARQ, but there will be no errors. As Rein says, the big problem on HF is not S/N (on VHF it is S/N and multipath reflections), but QRN and QRM, so you might find that DominoEx works pretty well in the presence of QRN, but I have not had an opportunity to find out myself. The DominoEx website says that it has been optimized for NVIS propagation. NVIS antennas on both ends should help reduce the static noise level, since the takeoff angles of NVIS antennas are very high, but noise generally arrives at a low angle. I can demonstrate the difference here, since I have both NVIS and regular 80m antennas. I have found around 2 S-units of static noise reduction using the NVIS antenna. 73, Skip KH6TY We do plan on using HD, NVIS antennas and data modes as long as they are faster than I can receive CW (about 15 WPM accurately. The noise level is what is so high after a hurricane...and it stays that way for 2-4 days. Walt/K5YFW
