WinUSB Notes - Revision history

OZ1HFT: catchg Category:USB libraries

2011-04-22T10:47:35Z

catchg Category:USB libraries

VK2NRA: /* Other interesting projects and info on WinUSB */ URL vs IP

2011-01-06T23:40:13Z

‎Other interesting projects and info on WinUSB: URL vs IP

VK2NRA: URL vs IP

2011-01-06T23:32:58Z

URL vs IP

KV0S at 01:02, 4 January 2011

2011-01-04T01:02:05Z

VK2NRA: new ip

2010-12-31T00:01:51Z

new ip

KV0S at 03:01, 2 August 2010

2010-08-02T03:01:47Z

KV0S: /* So, you're going to be running or recompiling the KISS code on a 64 bit machine? */

2010-08-02T02:30:47Z

‎So, you're going to be running or recompiling the KISS code on a 64 bit machine?

KV0S: /* So, you're going to be running or recompiling the KISS code on a 64 bit machine? */

2010-08-02T02:30:23Z

‎So, you're going to be running or recompiling the KISS code on a 64 bit machine?

KV0S: /* So, you're going to be running or recompiling the KISS code on a 64 bit machine? */

2010-08-02T02:29:00Z

‎So, you're going to be running or recompiling the KISS code on a 64 bit machine?

KV0S at 03:14, 29 July 2010

2010-07-29T03:14:11Z

← Older revision		Revision as of 10:47, 22 April 2011
Line 68:		Line 68:
	If you change the setting for KISS Konsole, make SURE that you make the setting for Sharp_DSP match! Otherwise, things just won't work... In my KISS branch, the Sharp_DSP project is part of the KISS Konsole solution, so this is easier to do. If you are using Phil's branch, you either need to add the Sharp_DSP project to the KISS solution, or make sure that you open the Sharp_DSP solution and make the needed changes in the Sharp_DSP project build settings and rebuild.		If you change the setting for KISS Konsole, make SURE that you make the setting for Sharp_DSP match! Otherwise, things just won't work... In my KISS branch, the Sharp_DSP project is part of the KISS Konsole solution, so this is easier to do. If you are using Phil's branch, you either need to add the Sharp_DSP project to the KISS solution, or make sure that you open the Sharp_DSP solution and make the needed changes in the Sharp_DSP project build settings and rebuild.

−	[[Category:~~Software~~]]	+	[[Category:USB libraries]]

@@ Line 53: / Line 53: @@
 Try this svn path (K9TRV's KISS Branch):
-svn://184.81.173.3/svn/repos_hpsdr_kiss/branches/K9TRV
+svn://svn.openhpsdr.org/svn/repos_hpsdr_kiss/branches/K9TRV
 == '''So, you're going to be running or recompiling the KISS code on a 64 bit machine?''' ==

@@ Line 7: / Line 7: @@
 Here are the signed libusb0 drivers:
-   svn://184.81.173.3/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
+   svn://svn.openhpsdr.org/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
 Please see my listserver posting on 12 May 2010 in the archives...

@@ Line 7: / Line 7: @@
 Here are the signed libusb0 drivers:
-   svn://184.81.170.126/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
+   svn://184.81.173.3/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
 Please see my listserver posting on 12 May 2010 in the archives...
@@ Line 52: / Line 52: @@
 Where can I find this new code that uses WinUSB?
 Try this svn path (K9TRV's KISS Branch):
-−
-    svn://64.245.179.219/svn/repos_hpsdr_kiss/branches/K9TRV
+svn://184.81.173.3/svn/repos_hpsdr_kiss/branches/K9TRV
 == '''So, you're going to be running or recompiling the KISS code on a 64 bit machine?''' ==

@@ Line 7: / Line 7: @@
 Here are the signed libusb0 drivers:
-   svn://64.245.179.219/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
+   svn://184.81.170.126/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-signed
 Please see my listserver posting on 12 May 2010 in the archives...

@@ Line 15: / Line 15: @@
 </blockquote>
-George Byrkit, K9TRV, 28 July 2010
+''Update, 28 July 2010, George Byrkit, K9TRV''
-−
-THERE WILL SOON BE A libusb0 WIKI PAGE WHERE INFO ON LIBUSB WILL BE LOCATED
 This page contains information on using WinUSB with HPSDR hardware.
-First, let's all be clear that WinUSB used as a driver replaces libusb0 used as a driver for some particular device, like the Ozy board.  If you install WinUSB as the driver for Ozy, libusb0 is no longer the driver.  So applications that use libusb0 (like PowerSDR, until Bill Tracey KD5TFD finished porting PowerSDR to WinUSB, or like CWSkimmer, which seems to use libusb0 to speak to Ozy) are not able to coexist with my branch of KISS.  My branch of KISS uses WinUSB.
+First, let's all be clear that WinUSB used as a driver replaces libusb0 used as a driver for some particular device, like the Ozy board.  If you install WinUSB as the driver for Ozy, libusb0 is no longer the driver.  So applications that use libusb0 (like PowerSDR, until Bill Tracey KD5TFD finished porting [[PowerSDR]] to WinUSB, or like [http://www.dxatlas.com/CwSkimmer/ CWSkimmer], which use libusb0 to speak to [[OZY]]) are not able to coexist with my branch of KISS.  My branch of [[KISS Konsole]] uses WinUSB.
-So it's an either/or proposition.  If you need libusb0, and can install libusb0 as the driver, and can run PowerSDR, you want to use Phil VK6APH's branch of KISS.  His branch is the 'original', and is considered to be the main development branch.  I try to keep step with his branch, and feed common bugs and hopefully their solutions back to him.  I'm keeping step best as I can with Phil's development work using the Hermes board, as well.
+So it's an either/or proposition.  If you need libusb0, and can install libusb0 as the driver, and can run [[PowerSDR]], you want to use Phil VK6APH's branch of [[KISS Konsole]].  His branch is the 'original', and is considered to be the main development branch.  I try to keep step with his branch, and feed common bugs and hopefully their solutions back to him.  I'm keeping step best as I can with Phil's development work using the [[HERMES]] board, as well.
-It seems that WinUSB is needed to use KISS (thus my branch is needed...) on Windows 64 bit OS versions, such as Vista 64 bit and Windows 7, 64 bit.  Some have reported trouble using libusb0-based KISS on Windows 7 32 bit.  These people report that my WinUSB branch does work fine on Windows 7, 32 bit (with WinUSB installed as the driver).  This problem on 32 bit Vista and 32 bit Windows 7 has recently (approx 15 Jan 2010) traced to a problem in HPSDR_USB_LIB_V1.dll by Bill Tracey (KD5TFD), who has fixed this problem!  He has mentioned this on the reflector (hpsdr mailing list), and has posted a fixed library.  Phil is testing and updating his development branch to include this fixed file.  Those of you using Vista 32 bit and Windows 7 32 bit may well wish to use that version and not my WinUSB version!  That way, you can use both PowerSDR and KISS, and optionally use CWSkimmer and other similar applications.
+It seems that WinUSB is needed to use KISS (thus my branch is needed...) on Windows 64 bit OS versions, such as Vista 64 bit and Windows 7, 64 bit.  Some have reported trouble using libusb0-based KISS on Windows 7 32 bit.  These people report that my WinUSB branch does work fine on Windows 7, 32 bit (with WinUSB installed as the driver).  This problem on 32 bit Vista and 32 bit Windows 7 has recently (approx 15 Jan 2010) traced to a problem in HPSDR_USB_LIB_V1.dll by Bill Tracey (KD5TFD), who has fixed this problem!  He has mentioned this on the reflector (hpsdr mailing list), and has posted a fixed library.  Phil is testing and updating his development branch to include this fixed file.  Those of you using Vista 32 bit and Windows 7 32 bit may well wish to use that version and not my WinUSB version!  That way, you can use both PowerSDR and KISS, and optionally use [http://www.dxatlas.com/CwSkimmer/ CWSkimmer] and other similar applications.
-Is there anything that WinUSB can do that libusb0 cannot do, other than work on a 64 bit machine?  It seems that, yes, there is at least one advantage to WinUSB.  WinUSB is able to detect an Ozy or Hermes board that is plugged in or powered on AFTER KISS has been launched.  Libusb0 required that Ozy be plugged in and powered on BEFORE launching/running KISS (or PowerSDR).  So this is an advantage.  Is there any disadvantage?  I think that yes, there is.  I don't have data to back it up, but libusb0 seems more 'performant' than WinUSB.  What do I mean by that?   I think that libusb0 has fewer delays and may use a larger blocksize for transfers than WinUSB does.  What is the evidence?  KISS using libusb0 has no troubles doing the normal (band) spectrum display, along with the full bandwidth display.  I found that I had to reduce the number of data points (samples) for the full spectrum display from 8192 to 4096, to get rid of distorted, chopped audio.  I think that Alberto came to the same conclusion.
+Is there anything that WinUSB can do that libusb0 cannot do, other than work on a 64 bit machine?  It seems that, yes, there is at least one advantage to WinUSB.  WinUSB is able to detect an [[OZY]] or [[HERMES]] board that is plugged in or powered on AFTER KISS has been launched.  Libusb0 required that Ozy be plugged in and powered on BEFORE launching/running KISS (or PowerSDR).  So this is an advantage.  Is there any disadvantage?  I think that yes, there is.  I don't have data to back it up, but libusb0 seems more 'performant' than WinUSB.  What do I mean by that?   I think that libusb0 has fewer delays and may use a larger blocksize for transfers than WinUSB does.  What is the evidence?  KISS using libusb0 has no troubles doing the normal (band) spectrum display, along with the full bandwidth display.  I found that I had to reduce the number of data points (samples) for the full spectrum display from 8192 to 4096, to get rid of distorted, chopped audio.  I think that Alberto came to the same conclusion.
 ====WinRad origins====
@@ Line 50: / Line 48: @@
 :3) there is also a Visual Studio 2008 project called WinUSBAPI that is Alberto's Borland C++ Builder code ported to VS2008 C++.  It doesn't yet have all the methods that the C# project WinUSBManaged that I wrote does.  Hopefully, I'll find the time to back-port those methods from WinUSBManaged to WinUSBApi.
-The purpose of the 'supporting programs' (which also use winusbmanaged.dll) is to replace the current versions that use libusb0.  With these, you can update the versions in your usbblaster-binaries folder so that you can still update the firmware in Penelope, Mercury and other boards.  You may have multiple places where these are needed.  Up-to-date copies are in my "KISS Console\bin\release" and "Kiss Console\bin\debug" folders, so that initozy11.bat that is in those folders will continue to work.
+The purpose of the 'supporting programs' (which also use winusbmanaged.dll) is to replace the current versions that use libusb0.  With these, you can update the versions in your usbblaster-binaries folder so that you can still update the firmware in Penelope, Mercury and other boards.  You may have multiple places where these are needed.  Up-to-date copies are in my "KISS Konsole\bin\release" and "Kiss Konsole\bin\debug" folders, so that initozy11.bat that is in those folders will continue to work.
 Where can I find this new code that uses WinUSB?

← Older revision		Revision as of 02:30, 2 August 2010
Line 60:		Line 60:


−	If so, then you'll need to check the 'fftw' subfolder in my branch for the 64 bit dll. I've provided the installers for the 32 bit and 64 bit fftw dlls, from the [http://www.fftw.org/ http://www.fftw.org/] website. Please either install the 64 bit package and replace all versions of the 32 bit dll with the dll it installs. Much easier is to copy and rename the libfftw3f64.dll to libfftw3f.dll, especially in the bin\release and bin\debug folders of my version of the [[KISS ~~Console~~]] project. I've already placed libfftw3f64.dll in those directories for your convenience. Replacing the current libfftw3f.dll is then all you need to do. I suggest that you rename the current libfftw3f.dll file (to anything else...), then copy libfftw3f64.dll and rename the copy to libfftw3f.dll. Thanks to Dr. Hermann von Hasseln, DL3HVH, for this information!	+	If so, then you'll need to check the 'fftw' subfolder in my branch for the 64 bit dll. I've provided the installers for the 32 bit and 64 bit fftw dlls, from the [http://www.fftw.org/ http://www.fftw.org/] website. Please either install the 64 bit package and replace all versions of the 32 bit dll with the dll it installs. Much easier is to copy and rename the libfftw3f64.dll to libfftw3f.dll, especially in the bin\release and bin\debug folders of my version of the [[KISS Konsole]] project. I've already placed libfftw3f64.dll in those directories for your convenience. Replacing the current libfftw3f.dll is then all you need to do. I suggest that you rename the current libfftw3f.dll file (to anything else...), then copy libfftw3f64.dll and rename the copy to libfftw3f.dll. Thanks to Dr. Hermann von Hasseln, DL3HVH, for this information!

	The alternative to this renaming is to rebuild SharpDSP, but ONLY after editing its file DSPBuffer.cs to change the line containing library_name = "libfftw3f.dll" to library_name = "libfftw3f64.dll".		The alternative to this renaming is to rebuild SharpDSP, but ONLY after editing its file DSPBuffer.cs to change the line containing library_name = "libfftw3f.dll" to library_name = "libfftw3f64.dll".

← Older revision		Revision as of 02:29, 2 August 2010
Line 60:		Line 60:


−	If so, then you'll need to check the 'fftw' subfolder in my branch for the 64 bit dll. I've provided the installers for the 32 bit and 64 bit fftw dlls, from the http://www.fftw.org/ website. Please either install the 64 bit package and replace all versions of the 32 bit dll with the dll it installs. Much easier is to copy and rename the libfftw3f64.dll to libfftw3f.dll, especially in the bin\release and bin\debug folders of my version of the KISS Console project. I've already placed libfftw3f64.dll in those directories for your convenience. Replacing the current libfftw3f.dll is then all you need to do. I suggest that you rename the current libfftw3f.dll file (to anything else...), then copy libfftw3f64.dll and rename the copy to libfftw3f.dll. Thanks to Dr. Hermann von Hasseln, DL3HVH, for this information!	+	If so, then you'll need to check the 'fftw' subfolder in my branch for the 64 bit dll. I've provided the installers for the 32 bit and 64 bit fftw dlls, from the [http://www.fftw.org/ http://www.fftw.org/] website. Please either install the 64 bit package and replace all versions of the 32 bit dll with the dll it installs. Much easier is to copy and rename the libfftw3f64.dll to libfftw3f.dll, especially in the bin\release and bin\debug folders of my version of the KISS Console project. I've already placed libfftw3f64.dll in those directories for your convenience. Replacing the current libfftw3f.dll is then all you need to do. I suggest that you rename the current libfftw3f.dll file (to anything else...), then copy libfftw3f64.dll and rename the copy to libfftw3f.dll. Thanks to Dr. Hermann von Hasseln, DL3HVH, for this information!

	The alternative to this renaming is to rebuild SharpDSP, but ONLY after editing its file DSPBuffer.cs to change the line containing library_name = "libfftw3f.dll" to library_name = "libfftw3f64.dll".		The alternative to this renaming is to rebuild SharpDSP, but ONLY after editing its file DSPBuffer.cs to change the line containing library_name = "libfftw3f.dll" to library_name = "libfftw3f64.dll".

@@ Line 1: / Line 1: @@
 <blockquote>
 '''THIS MATERIAL SHOULD BE CONSIDERED AS OBSOLETE, BUT INFORMATIVE''' <br>
@@ Line 29: / Line 28: @@
 Is there anything that WinUSB can do that libusb0 cannot do, other than work on a 64 bit machine?  It seems that, yes, there is at least one advantage to WinUSB.  WinUSB is able to detect an Ozy or Hermes board that is plugged in or powered on AFTER KISS has been launched.  Libusb0 required that Ozy be plugged in and powered on BEFORE launching/running KISS (or PowerSDR).  So this is an advantage.  Is there any disadvantage?  I think that yes, there is.  I don't have data to back it up, but libusb0 seems more 'performant' than WinUSB.  What do I mean by that?   I think that libusb0 has fewer delays and may use a larger blocksize for transfers than WinUSB does.  What is the evidence?  KISS using libusb0 has no troubles doing the normal (band) spectrum display, along with the full bandwidth display.  I found that I had to reduce the number of data points (samples) for the full spectrum display from 8192 to 4096, to get rid of distorted, chopped audio.  I think that Alberto came to the same conclusion.
 The first thing that you will need is the WinUSB driver package from Alberto, I2PHD, from www.weaksignals.com.  [http://www.weaksignals.com Alberto I2PHD's WinRad site]  Go to his website and download his WinRad package, which will give you his WinUSB driver installer.  Using this installer should let you install WinUSB as the driver for your hardware on Windows XP, Vista and Windows 7, whether you have a 32 bit OS, or Intel/AMD 64 bit OS (x86 architecture) or Intel Itanium IA64 64 bit OS versions of windows installed.