The brand-new PN400 Phase Noise Test System is available for purchase! →

CJobbers

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: LabVIEW Device not open #254352
    CJobbers
    Participant

    My answers are embedded within your original response.
    A few questions for you:

    1. Does the BB60C run successfully in Spike on that PC? YES – It works perfectly fine.
    2. Are you attempting to run the BB60C while the VSG60A is simultaneously in use? If so, can you try without the VSG60A running? Yes. But I have tried with and without to no avail.
    3. Is -1 the only error seen, and is it returned from the Open Device VI? I have seen Err12 and Err13 as well. I saw those only when I changed the VI to allow the reference to the DLL to be setup via the diagram and not selected in the “Configure” part of the C DLL call.

    While troubleshooting, after receiving an error the LabVIEW software should be restarted. I have tried this also.

    Lastly, when I try to run an Example (Acquire Sweep) I receive this error: “The library specified for this node cannot be found or cannot be loaded. Right-click the Call Library Function node and select Configure, then choose the correct library name or path.” It is pointing to the proper DLL for the 32bit version of LabVIEW.

    • This reply was modified 10 months ago by CJobbers. Reason: Adding more detail
    in reply to: LabVIEW Device not open #254342
    CJobbers
    Participant

    I am having the same issue trying to communicate to the BB60C via LabVIEW 2017 using either 64-bit or 32-bit seem to provide the same “-1” error code. I have LabVIEW code working perfectly for the VSG60A, but am experiencing difficulties with the BB60C.

Viewing 2 posts - 1 through 2 (of 2 total)