Forums › BB Series Discussions › LabVIEW Device not open
- This topic has 9 replies, 7 voices, and was last updated 9 months, 2 weeks ago by
Justin Crooks.
- AuthorPosts
- November 14, 2023 at 7:09 am #244499
TPascenteParticipantHi,
I am using a BB60C and its working well with the Spike SW. But when using the LabVIEW examples, I keep getting the “Device not open” error when running the vi. I re-loaded the bb_api-64.dll driver from the LabVIEW drivers download (and deleted the -64 text) and restarted by PC and got the vi to work once. After the second time using the vi I get the same error. Any suggestions on how to fix this? Is there a different dll available? Any help is appreciated. Thanks!!Attachments:
You must be logged in to view attached files.November 14, 2023 at 7:47 am #244501
AndrewModeratorTom,
We will be responding to these questions from our support email, thanks.
November 15, 2023 at 6:32 am #244509
TPascenteParticipantThanks, email received and issue resolved!
December 8, 2024 at 11:21 pm #246533pooja.sagathiya
ParticipantHi,
I am using a BB60C and its working well with the Spike SW. But when using the LabVIEW examples, I keep getting the “Device not open” error when running the vi. I re-loaded the bb_api-64.dll driver from the LabVIEW drivers download (and deleted the -64 text) and restarted by PC and got the vi to work once.Any help is appreciated. Thanks!!December 9, 2024 at 8:17 am #246535
Nathan SnyderModeratorIf you are using the LabVIEW bindings, and an error is returned, say because Spike was opened, then most likely LabVIEW will need to be restarted and the device power-cycled. Otherwise resources may not be cleaned up properly within the LabVIEW environment, causing errors when trying to connect to the device again.
December 18, 2024 at 9:51 pm #246617pooja.sagathiya
Participantagain its same error of “Device not open” is keep coming as even I uninstalled spike for while.
Attachments:
You must be logged in to view attached files.December 8, 2025 at 10:20 am #254342CJobbers
ParticipantI 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.
December 8, 2025 at 1:59 pm #254347
RogerModeratorHi CJobbers,
A few questions for you:
1. Does the BB60C run successfully in Spike on that PC?
2. Are you attempting to run the BB60C while the VSG60A is simultaneously in use? If so, can you try without the VSG60A running?
3. Is -1 the only error seen, and is it returned from the Open Device VI?While troubleshooting, after receiving an error the LabVIEW software should be restarted.
December 9, 2025 at 9:03 am #254352CJobbers
ParticipantMy 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 9 months, 3 weeks ago by
CJobbers. Reason: Adding more detail
December 17, 2025 at 11:15 am #254372
Justin CrooksModeratorCJobbers,
Hopefully our support team was able to help you. If not, reach out to support (at) signalhound (dot) com for more direct support. - This reply was modified 9 months, 3 weeks ago by
- AuthorPosts
- You must be logged in to reply to this topic.
