++++++++++++++++++++ Date: Tue, 20 Nov 2001 18:55:57 -0800 From: "Ed Juge/NM" Subject: Re: [Elecraft] KIO2 - lap tops Hi, Bob... I also have a Dell Inspiron but mine is the 4000. I agree with others... having a Serial port will make life a lot easier. My logging program of choice --after trying almost everything on the market-- is DXBase 2001. Solid as a rock, bulletproof and support has been exceptional! DXB has a lot of options as to how you want it to show on the screen... many small windows for different things. The Inspiron 4000 has a very bright 14-inch screen optimized for 1024x768. I can't imagine having to run DXB on anything smaller or with less resolution. This is a long way of suggesting you decide on a logging program and be sure it's going to work comfortably with the screen size/resolution you choose. Another thing I really like about the notebook is I can get +/- 8 hours of operating time from two batteries (It comes with one but will hold two if you want). I installed Windows 2000 on it and it has been 100% trouble-free since I bought it --used-- back in April. It has a printer port, USB and two PC-card (PCMCIA) slots. I use one card slot for an 802.11b wireless network card and keep it networked with two other computers in our home office. Also has audio in/out for digital modes or what have you. Works great there, too. I use this setup with both my K2 and an Icom 756PRO. No RF problems in either direction. It keeps on chugging, even when I'm running 1,500 watts out. +++++++++++++++++ Date: Fri, 15 Nov 2002 17:09:27 +0000 To: "ELECRAFT LIST" From: Brendan Minish Subject: [Elecraft] K2, KIO2 & DXBASE (logging software ) Support Hi all I have just built the KIO2 to go with my K2 setup. I use a great logging package called Dxbase 2003 from scientific solutions http://www.dxbase.com/ Dxbase 2003 does not (Yet!) officially support the K2 but I have been successful with the following addition to the radios.ini file (which can be found in the dxbase2003 program directory). I want to hear from you if you use this file, this will allow me to tell you of changes I may make and also to incorporate any changes you make, hopefully this will eventually end up being the K2 support file for DXbase in future updates. If you have any problems with this file please let me know, please include which operating system you are using. this file is not officially supported by Scientific solutions To use, open radios.ini with notepad and paste the section at the bottom of this e-mail on the end of the radios.ini file. NOTE there are NO line breaks in the middle of lines but some E-mail programs may break up the long lines so fix this in notepad. You should now have an entry in the HF radio section under OPTIONS for the ELECRAFT K2 Notes 1/ On rare occasions DXB will when clicking a spot for a cross band station try to set cross band (VFOA and VFO B on different HF bands), the K2 does not currently support this and you will end up on the transmit band. In-band Split operation is fully supported. 2/ DXBASE needs to be set to a Baudrate of 4800, No parity, 8 bits, 1 or 2 stop bits (either works) 3/ CW-R mode isn't read correctly when logging, this is a limitation of DXbase 4/ this file should work with DXB 2002 (& possibly earlier versions) but I have not tested this, PLEASE let me know if you try it on older versions. ----- file starts below this line --------------- [ELECRAFT_K2] #Elecraft K2 revision 0.3 by Brendan Minish ei6iz at oceanfree.net P_LSB=1 P_USB=2 P_CW_USB=0 P_CW_LSB=0 P_AM=5 P_FM=4 P_FM_N=0 P_DATA_LSB=0 P_DATA_USB=0 P_DATA_FM=0 P_CW=3 P_FSK=6 P_RTTY=6 P_PACKET=9 LSB=1 USB=2 CW=3 FM=4 AM=5 FSK=6 RTTY=6 HIGH=3 MEDIUM=2 LOW=1 OFF=0 ON=1 FREQDIVIN=1 FREQDIVOUT=1 USEEXTENDEDMODES=0 FREQSHIFT=0 PACING=1 DefaultCW=3 DefaultAM=5 DefaultFSK=6 DefaultRTTY=6 DefaultFM=4 SelectVFOA= eoc(100) asc( "FR0;" ) eoc(0) SetVFOA= asc( "FA" ) dec( %vfoa,11 ) asc( ";" ) asc("MD") dec( %mode,1) asc ( ";" ) eoc(0) GetVFOA= asc("FA;") rrs(14) eoc(0) PrsVFOA= asc("FA") dec(%vfoa,11) asc(";") eoc(0) SelectVFOB= eoc(0) SetVFOB= asc( "FB" ) dec( %vfob,11 ) asc( ";" ) eoc(0) GetVFOB= asc("FB;") rrs(14) eoc(0) PrsVFOB= asc("FB") dec(%vfob,11) asc(";") eoc(0) SetMode= eoc(0) GetMode= asc( "IF;" ) rrs(38) eoc(0) PrsMode= asc("IF") dec(%dummy,27) dec(%mode,1) dec(%dummy,7) asc(";") eoc(0) SetFilter= asc("K22;") asc( "FW0000" ) dec( %filter, 1 ) asc ( ";" ) eoc(0) GetFilter= asc("K22;") asc( "FW;" ) eoc(0) PrsFilter= asc("FW") dec(%dummy,4) dec( %filter, 1 ) asc ( ";" ) eoc(0) SetSplit= asc( "FT" ) dec( %split ) asc ( ";" ) eoc(0) GetSplit= asc( "IF;" ) rrs(38) eoc(0) PrsSplit= asc("IF") dec(%dummy,30) dec(%split,1) dec(%dummy,4) asc(";") eoc(0) ------ File ends above this line ------- 73 Brendan EI6IZ +++++++++++++++++ Good luck... Ed, W5EJ +++++++++++++++ Date: Wed, 21 Nov 2001 12:44:51 -0800 From: "Ed Juge/NM" Subject: Re: [Elecraft] KIO2 - lap tops Sorry, Sherman, I can't answer that one. I never go into suspend mode on any of my computers. Even the notebook I use for DXBase is normally connected to AC mains. All I do is run a screen saver. I haven't tried suspend on Win2000 but my experience with suspend on all previous versions of Windows has been that it ALWAYS returns from suspend no longer able to run certain functions or programs correctly without rebooting, so, I long ago decided to use suspend only where a notebook initiates it due to low battery condition. Then I reboot after it comes back to life. DXBase is claimed to be written in Microsoft Access, in strict compliance with MS's programming guidelines. If there is a problem, it's probably belongs to MS rather than the DXB programmers. I have found DXB to be totally bulletproof. It appears it will not lose info or entries even if the power shuts down with the program running. 73... Ed, W5EJ - ----- Original Message ----- From: "Sherman Banks (W4ATL)" To: "Ed Juge/NM" Sent: Wednesday, November 21, 2001 2:44 AM Subject: RE: [Elecraft] KIO2 - lap tops > I have a friend with a Dell laptop and Windows 2000. When he installed > DXBase on his laptop, he lost the ability to go into suspend mode. > Uninstalling fixes the problem. DXBase says that this is normal. Do you > see this with your laptop? ++++++++++++++++++ Date: Fri, 14 Feb 2003 17:32:09 +0000 To: W6IZT at aol.com, elecraft at mailman.qth.net From: Brendan Minish Subject: Re: [Elecraft] K2 and DXBase HI, I have written a K2 file for DXB that fixes this. This will be included with the next release DXB it is caused by DXB sending the mode change before the frequency change one other nice thing I found when creating the K2 file is that the K2 does not need the commands slowed down like most of the other radios. This makes for a very responsive radio. I will send you the radios.ini file with the K2 entry as an attachment directly. Copy this file over the existing radios.ini file in your dxbase directory. This file includes some ICOM 756pro and pro2 tweaks. Restart DXB and now you should have an elecraft entry, select the K2 set serial port up for 4800 Bd no parity 8 bits & 1 or 2 stop bits Will anyone else who wants this contact me directly please? Please report any remaining bugs directly to me and not to Scientific solutions regards Brendan EI6IZ ++++++++++++++++++ From: "Dan Barker" To: "Elecraft" Subject: FW: [Elecraft] K2 and DXBase Date: Fri, 14 Feb 2003 12:46:11 -0500 Correct answer, but no "why". The K2 remembers mode by band if you've hovered on that band for 30 seconds. Since you are testing, you no doubt are not hanging around for 30 seconds. If you had, the problem would have magically disappeared, although not really. Just do the commands in order, as Brendan says. But now you know why. The band change was really doing a "Band Change and revert to the mode last used on that band for at least 30 seconds", which is usually abbreviated "Band Change". Dan / WG4S / K2 #2456 +++++++++++++++++++