WinPSKX ActiveX Control

Version 1.1a - Released June 3, 2001

Version 2.0 - Release planned for September, 2001

Moe Wheatley, AE4JY has kindly allowed me to collaborate with him on developing a PSK31 ActiveX control based on his PSK31 engine DLL. This control provides all the functionality you need to build your own PSK31 application using Visual Basic, Delphi, or C++ and with integrated visual data displays typically used in PSK31 applications. You drop this control into a Visual Basic form and within minutes can have a functioning PSK31 receiver. With a bit more coding for handling TX/RX control and persisting the user's settings, you can build a full-blown PSK31 application.

Information and downloads for the WinPSKX ActiveX control:
Screenshot This is a screenshot of the control in a demonstration application.
Documentation Download the documentation if you would like to learn more about the control.
WinPSKX SDK Download the WinPSKX ActiveX control SDK.
ActivePSK Download Moe's WinPSK converted to use the ActiveX control.

Caviats:

Lastly, I appreciate your interest in the WinPSKX control, and I welcome your suggestions and comments.


Updates since the original release

Version 1.2 Release Notes, August 18, 2001:
  1. Version 1.2 is available for experimental use. However, I recommend that you use the Version 1.1a for any PSK31 applications that you intend to distribute. You will find more information on the WinPSKX V1.2 description page.
Version 1.1a Release Notes, June 3, 2001:
  1. There was a problem with returning data in the GetRawData and GetFFTData methods. A minor change in the PSKCore DLL has resolved this.
Version 1.1 Release Notes, May 31, 2001:
  1. Re-linked with Moe's Version 1.11 PSKCore codebase.

  2. Resolved the problem with passing arrays in Visual Basic. The documentation has been updated and describes how to pass arrays properly.
Incremental bug fixes or feature improvements were added since the original April 7, 2001 release:
  1. Setting the TXFrequency property did not cause the xmit frequency to change. Debugging this led to a series of interrelated issues between the TXFrequency and RXFrequency properties, and the TX and RX visual cursor positioning. This is all fixed now. Please read the documentation for further information on how these properties and cursor positions interact.

  2. Added a new property, AutoTrack. Setting this causes the TX frequency to follow the RX freqency. Read the documentation for further details.

  3. Found the bug that was responsible for the wild fluctutations in the received signal level.

Send e-mail to Dave:

Go to the WAØTTN Web page.

Go to the Dave Cook Consulting Web page.

Last updated August 28, 2001