Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not detecting NeoVi Fire 2 Device #50

Open
danieldiaz7 opened this issue May 20, 2022 · 6 comments
Open

Not detecting NeoVi Fire 2 Device #50

danieldiaz7 opened this issue May 20, 2022 · 6 comments

Comments

@danieldiaz7
Copy link

danieldiaz7 commented May 20, 2022

My program which successfully compiles, can't detect my NeoVi Fire 2 device. When running cmake, I get this:

Include paths
Loaded extensions:
-- Build type: Debug
-- Not generating API documentation
fatal: No names found, cannot describe anything.
-- Detected git snapshot version: unknown
-- Not building libftdi1++
-- Not building python bindings
-- ftdi_eeprom build is disabled
-- libConfuse not found, won't build ftdi_eeprom
-- NOT building unit test
-- Configuring done
-- Generating done
-- Build files have been written to: ...

It successfully builds, however, when I try to run this code, it always say 0 devices found:

`std::vector<std::shared_ptricsneo::Device> devices = icsneo::FindAllDevices();

std::cout << devices.size() << " found!" << std::endl;

for (auto& device: devices) {
    std::cout << "Found " << device->describe() << std::endl;
}`

Is this due to the build file or is there something else that I need to do when connecting the device to my laptop?

Thanks.

@hollinsky-intrepid
Copy link
Contributor

What platform are you running this on? For Windows, you may need our device driver package. For Linux, you may need more permissions (try running with sudo to rule this out, and we can go from there).

@danieldiaz7
Copy link
Author

I'm currently running on a windows system. From the driver package, which file am I supposed to install?

@hollinsky-intrepid
Copy link
Contributor

Ah my bad, those are manually installable drivers. This package has an automated installer you can use.

@danieldiaz7
Copy link
Author

I downloaded the driver and the device is still not being detected.

Currently, I have neoVI explorer open and connected to my neoVI fire 2, however, when I try running my program, it's not detecting my device. When building, some files aren't fully built but the program still compiles at the end. Could this be the issue? Thanks.

@danieldiaz7
Copy link
Author

danieldiaz7 commented May 25, 2022

I think there might be something wrong with my build files. When I run cmake ..:

Include paths
Loaded extensions:
-- Build type: Debug
-- Not generating API documentation
fatal: No names found, cannot describe anything.
-- Detected git snapshot version: unknown
-- Not building libftdi1++
-- Not building python bindings
-- ftdi_eeprom build is disabled
-- libConfuse not found, won't build ftdi_eeprom
-- NOT building unit test
-- Configuring done
-- Generating done
-- Build files have been written to: ...

My current directory looks like:

+build
+sub_direc
|____ libicsneo
+CMakeLists.txt
+main.cpp

My main.cpp is where I include the code:

#include <iostream>
#include <icsneo/icsneocpp.h>
#include <vector>

using namespace icsneo;

int main() {

    std::vector<std::shared_ptr<icsneo::Device>> devices = icsneo::FindAllDevices();
    
    std::cout << devices.size() << " found!" << std::endl;

    for (auto& device: devices) {
        std::cout << "Found " << device->describe() << std::endl;
    }

    std::cout << "testing testing\n";
}

Outermost CMakeLists.txt contains:

cmake_minimum_required(VERSION 3.16.3)

# set the project name
project(CAN_Application)

# set the project version
# project(CAN_Application VERSION 1.0)

# add the executable
add_executable(${PROJECT_NAME} main.cpp)

add_subdirectory("sub_direc/libicsneo")

target_link_libraries(${PROJECT_NAME} icsneocpp)

I feel like when I build, there are some files/libraries that are not being included in the build process. Any tips or assistance will be greatly appreciated!

@vits71
Copy link

vits71 commented Dec 9, 2023

I had the same problem with Fire 3 and Win 11 x64. I needed to install Npcap and modify CMakeLists.txt to set LIBICSNEO_NPCAP_INCLUDE_DIR variable and rebuild the libicsneo again. Then there is alternate path in PCAPDLL::PCAPDLL used for opening wpcap.dll which was buggy (find details in another issue) but after I fix that bugs the device was finally found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants