Difference between revisions of "626"

Revision as of 12:29, 27 October 2017

C/C++ apps must call S626_DLLOpen

Why do I get null pointer exceptions when I call API functions?

Windows application programs written in C/C++ must call S626_DLLOpen before calling any other API functions; failure to do this will cause null pointer de-referencing when you try to call other API functions. The following example shows how to do this:

#include <windows.h>
#include "win626.h"

int main(int argc, char* argv[])
{
  switch (S626_DLLOpen()) {   // Open the API. MUST CALL THIS FIRST!
  case ERR_LOAD_DLL:
    printf("can't open s626.dll\n");  // check dll path
    return -1;
  case ERR_FUNCADDR:
    printf("dll function(s) not found\n");  // check dll version
    S626_DLLClose();    // Close the API.
    return -1;
  default:  // if dll was successfully opened ...
    S626_OpenBoard(0, 0, NULL, THREAD_PRIORITY_NORMAL);
    if (S626_GetErrors(0))
      printf("errors opening board\n");
    else {              // Board was successfully opened, so ...
      RunApplication();    // App can now call other API functions.
      S626_CloseBoard(0);  // Close board before app terminates.
    }
    S626_DLLClose();    // Close the API.
    return 0;
  }
}

64-bit Windows

I successfully built a 626 program for my 64-bit Windows 7 system but it crashes when it executes. What could be the problem?

The 626 works with 64-bit Windows, but only with 32-bit applications. When building your application, make sure the CPU target is selected as 32-bit or Win32.

Encoder errors

The encoder interface misses some encoder clocks, especially at higher rotation speeds.

This can be caused by slow slew rates on the encoder signals. Examine the encoder clock signals with an oscilloscope. If you don't see sharp, fast rise and fall times, you may need to add external termination or pull-up resistance to the clock lines to speed up the edges.

Migrating to PCI Express

When upgrading your system to PCIe, we recommend Model 826 as a replacement for model 626. The following table compares the interfaces on the two boards:

Windows installation debug

You must install both the board and the device driver before the 626 can be accessed by application software. If you've done this and still cannot communicate with the board:

1. Open the device manager and see if the board appears there (it will be classified as a "multimedia controller"). If you don't see the board there ...
2. Run msinfo32.exe and see if the board appears there. It will be listed as a "multimedia controller" and should appear in that section or, if the driver isn't installed, it should appear in the "problem devices" section. The board info will look like this:

Multimedia Controller    PCI\VEN_1131&DEV_7146&SUBSYS_02726000&REV_01\4&12432EBB&0&10F0