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

Error when trying to use device discovery (O3R camera) #334

Closed
mehranq opened this issue Dec 3, 2021 · 6 comments
Closed

Error when trying to use device discovery (O3R camera) #334

mehranq opened this issue Dec 3, 2021 · 6 comments
Assignees

Comments

@mehranq
Copy link

mehranq commented Dec 3, 2021

Hi. A couple of things I want to raise/ask.

1) I am trying to using the DeviceDiscovery function from the camera base class to find the O3R cameras connected to my VPU. I am getting the following exception when trying to do so. When I check the console it has the line, "An invalid argument was supplied" printed. I have tried running it directly using the ifm3d command line tool using "ifm3d discover" command but I get the same "An invalid argument was supplied" error message:

devicediscoverty

I am able to run ifm3d dump and here is the result for that:
ifm3d dump.txt

2) I would also like to confirm whether the following (highlighted in red squares) are LEDs that are supposed to turn ON when a camera is connected in the corresponding port. In my case, they don't turn on when I have a camera connected:

ifm vpu camera light indicator

Hope I can get some help on these issues.

@graugans
Copy link
Member

graugans commented Dec 6, 2021

Hey @mehranq , the LEDs are supported in the next firmware release series 0.14.x which we currently do internal testing with.

@inbangsa
Copy link
Collaborator

inbangsa commented Dec 6, 2021

@mehranq on discovery: I have tried to reproduce the issue but was not able to reproduce it on windows nor on Linux. can you provide more information on which windows and Visual studio version you are using and would also want to know the build type of ifm3d (Release/Debug)

ifm3d discover uses udp communication for discovery of devices in subnet. Are udp packets allowed on your PC and not blocked by firewall on network. can you try creating a outbound and inbound rule on firewall for udp port 3321 ( this port is used by ifm3d for discovery).

@mehranq
Copy link
Author

mehranq commented Dec 6, 2021

Hey @mehranq , the LEDs are supported in the next firmware release series 0.14.x which we currently do internal testing with.

@graugans Thank you for the info.

@inbangsa Here is the info you requested:

Windows version:
windows version

Visual Stuido version:
vs version

I checked the firewall settings and the inbound rules were already setup like so:
inbound rules ifm3d

I added the outbound rule as per your suggestion like so:
outbound rule ifm3d

I restarted my pc and re-ran the ifm3d discover command. However, I still get the same error message "An invalid argument was supplied"

FYI, I built the library from source on windows in RELEASE config as instructed on your github page for building on windows. I built the library about a month ago. Could it be the case that this issue existed previously but does not occur in the latest version of the library?

@inbangsa
Copy link
Collaborator

@mehranq there is no change in this feature from last couple of months.

we are not able to reproduce this issue, and all tests are working fine on windows and linux machine. we are in developement of windows installer for ifm3d which will provide binary version and we would like you to test this feature with that.

@github-actions
Copy link

github-actions bot commented Oct 8, 2022

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Oct 8, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

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

No branches or pull requests

3 participants