Quantcast
Channel: querying device connected through ethernet - Super User
Viewing all articles
Browse latest Browse all 3

querying device connected through ethernet

$
0
0

I have a device (high-speed camera) which communicates through an ethernet port. When I connect it to my computer (Scientific Linux 6.4 x64) I see indicator lights blink on both the computer's port and the camera, suggesting that there is some kind of data transmission going on, at least initially.

The problem is that the device isn't visible to any of the tools designed to work with it. So I would like to interact with this device at a lower level, partly for debugging, partly for education, and partly as a sanity-check.

I'm very new to networking and so am likely confused on some basic concepts, but I was wondering if there was some way to send a broadcast or a packet or some other way to investigate/communicate with the camera directly?

I have tried using nmap (to ping IP ranges) and this did not get me anywhere (I don't know if a camera directly connected to ethernet should necessarily have an IP).I have also tried using arp-scan, this also failed for similar reasons (no IP for eth0).

EDIT - More Information:

Camera Make: AOS

Camera Model: X-PRI

Software: AOS CaPIICam SDK(As an aside, this is intended to run on Windows, and I have tried to run it through both a native Windows environment and Wine, with identical results.)

I am not sure what type of cable I am using. The wire pattern on both ends is identical (orange-blue-green-brown) and so I am guessing that it is not crossed over. I am connecting directly from Camera -> Cable -> Computer.

As for the source code, here it is:

int main() {    CCaPIICam   MyCam;    CAM_RC      rc;    int         ndev;    char*       sNames[50];    for (int i = 0; i < 50; i++)        sNames[i] = new char[40];    rc = MyCam.GetCamNames(ndev, sNames);    camerror(rc);    getchar();    return EXIT_SUCCESS;}

where camerror(int) is just a switch-case print-to-console routine for reporting the error codes in accordance with the API documentation. It compiles and links fine under native Windows and on a VM, but camerror() reports "invalid node" on GetCamNames() which is not defined in the documentation.


Viewing all articles
Browse latest Browse all 3

Latest Images

Trending Articles





Latest Images