[Dx4win] Detection of RTTY spots
Hello, I have some problems with RTTY and PSK cluster spots: Clusterspots without the keywords (RTTY, PSK…) are detected as CW or Phone (depending on the CW frequency cutoff for the band) – as a consequence of this, there are wrong or missing DX alerts. It would be a great improvement, to configure band-areas instead of CW frequency cutoff – for exemple on 20m: 14.000-14.070 = CW, 14.070-14.100 = DIG, 14.100-14.350 = Phone. Of corse the detection by keywords should be kept, so that Digital Spots out of this band-areas are still detected. What do you think about this suggestion – is it overdone? ist it pracicable? do you have better ideas? I am looking forward to your opinion! vy 73 Tom, DL4MCF dl4...@web.de[mailto:dl4...@web.de] ___ Ihr WEB.DE Postfach immer dabei: die kostenlose WEB.DE Mail App für iPhone und Android. https://produkte.web.de/freemail_mobile_startseite/ __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4WIN and Icon IC PW-1 data clashes
Jim (et al), Yes, Jim and I have exchanged email about the CI-V protocol and his efforts to tame the PW1. As I understand it, K9JM's (www.k9jm.com) device is a piece of hardware, running custom software developed by Jim, that breaks the CI-V bus into segments and isolates traffic to the PC, the radio, and the PW1 amplifier as necessary. A neighboring ham has recently ordered one of Jim's CI-V Routers and has promised to let me run my CI-V tests against. If I encounter any issues (which I don't anticipate) I'll work with Jim to their resolution. Otherwise, I plan to refresh my Riding the CI-V Bus articles with the results... and of course will post a message to the reflector. -larry (K8UT) Several other solutions exist for the Icom/PW-1 CI-V bus clash and have been available for several years. microHAM microKEYER II, DigiKeyer II, and MK2R/MK2R+ all provide an optional isolated CI-V bus emulating an Icom transceiver that will handle a PW-1 (or any other accessory that uses CI-V for frequency control). microHAM Station Master is a CI-V interfaced band decoder that has been available for more than three years that includes a PA Port that will control a PW-1 (including, again, an isolated CI-V bus emulating an Icom transceiver) as well as several CI-V or Band Data (BCD) amps - including PW-1, SPE Expert 1K or 2K, Tokyo High Power 1.5Kfx or 2.5Kfx and Yaesu Quadra or FL-7000. Coupled with a BCD to 1 of 10 decoder, this support can also be extended to control 1 of n selected amplifiers like the MFJ ALS600/1300 and TenTec Hercules. For at least five years prior to Station Master, the original microHAM Band Decoder had an optional CI-V output (as well as BCD amplifier control) accessories to provide the same isolated CI-V bus capability. In all cases the microHAM solutions are not limited to Icom rigs as the auxiliary/isolated CI-V output is available with supported rig. 73, ... Joe Subich, W4TV microHAM America, LLC. http://www.microHAM-USA.com http://groups.yahoo.com/group/microHAM __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] packet questios new user
Is it necessary to specify the cluster node and my call each time the packet function is initiated? Is it possible to identify the station that entered the spot? Thanks art W1RZF __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Detection of RTTY spots
On Mon, Feb 27, 2012 at 4:36 AM, Thomas Platz DL4MCF wrote: It would be a great improvement, to configure band-areas instead of CW frequency cutoff – for example on 20m: 14.000-14.070 = CW, 14.070-14.100 = DIG, 14.100-14.350 = Phone. Of course the detection by keywords should be kept, so that Digital Spots out of this band-areas are still detected. This may be OK during non-contest periods. However, during contests, people tend to spread out. CW contest stations end up in the places where the bandplan says there should be RTTY, and RTTY contest stations can take up most of the CW band, for example 7030 to 7099, or 14070 to 14120. It's an OK idea, but it does have limitations. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] packet questios new user
Unfortunately, there's no auto-login feature built into DX4WIN. However, you can make things easier by using this technique: After starting DX4WIN, click anywhere on the packet window, then press Enter. You'll get a little popup that says No connection active. Press enter again and you'll get the list of available packet clusters. The most recently used one will be on top (at least in recent versions.) Press enter one more time and you'll be connected. At that point, you do have to type in a callsign, though you can also program it onto one of the function keys which might save a little time. As for seeing the spotter's callsign, try making the DX spots window wider (or adjust the size of some of the other columns by positioning the cursor over the | at the top and dragging) and you'll see the Spotter column, it's the second from the end on the right. On 2/27/2012 7:27 PM, Art Holmes wrote: Is it necessary to specify the cluster node and my call each time the packet function is initiated? Is it possible to identify the station that entered the spot? Thanks art W1RZF -- 73, David, K2DBK http://k2dbk.blogspot.com http://k2dbk.com twitter: @k2dbk __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] packet questios new user
Thanks Jim, Appreciate your support. 73 Art -Original Message- From: jjreis...@gmail.com [mailto:jjreis...@gmail.com] On Behalf Of Jim Reisert AD1C Sent: Monday, February 27, 2012 8:06 PM To: Art Holmes Cc: dx4win@mailman.qth.net Subject: Re: [Dx4win] packet questios new user On Mon, Feb 27, 2012 at 5:27 PM, Art Holmes W1RZF wrote: Is it necessary to specify the cluster node and my call each time the packet function is initiated? Yes, there is no auto-login. However, once you have chosen a node, the next time you start DX4WIN, move the mouse pointer into the the Packet Spots window, then type the ENTER key three times. The first time it says there's no connection. The second time brings up node list. And the third time selects node at the top of the list. Then you should get your node login prompt in the Packet Spots window. Is it possible to identify the station that entered the spot? The spotter callsign is a column in the DX Spots window. If you don't see the spotter callsign, maybe your DX Spots window needs to be widened (just like any other Windows window, pull the right-hand margin to the right). When you exit DX4WIN and restart, the window should return to the size you set it to. Once you get things set up the way you like it, export your preferences to a .INI file. File | Preferences then File | Write INI file. Default name is DX4WIN, that's fine. It will be stored in your SAVE directory. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html