FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
08-18-2023 07:42 AM
I'm trying to communicate with a basler camera through their pylon driver over ethernet.
To test if core can discover the camera, I simply just need it to print the device number of the camera,
but in the log I get the following problem
I am at a loss here and would appreciate some help.
Solved! Go to Solution.
08-18-2023 08:38 AM
Moved to corresponding sub forum SDK.
To sum things up: you pack your code into a snap install it on a ctrlX CORE and then you get the error on your picture in the logbook.
Could you add a system report of your ctrlX CORE so we get some more insights. (1.20 See in online documentation, 1.12 see documentation here)
Could you add some information about hardware topology and network settings in your application? Just to check if camera can even be reached via the network.
Does your snap have the necessary system plugs to access the network (See snapcraft.yaml)?
08-18-2023 09:12 AM
snap have the necessary system plugs to access the network
I'm embarrassed that my download failed.
I just set the ip address of the webcam to 192.168.1.11 on the same network segment as core (192.168.1.1)
08-18-2023 03:48 PM
So XF10 is connected to a switch and also camera is connected to the same?
It seems you are working with system version 1.12. Can you confirm?
Which version of the SDK is used?
08-22-2023 09:49 AM
After some modifications, I am having the problem as shown in the picture above
I can determine that the core and basler cameras can communicate with each other, for example to get the device model, but I can't put the image data into ptrGrabResult
“RetrieveResult(5000, ptrGrabResult,TimeoutHandling_ThrowException)”
ptrGrabResult is the variable used to store the image capture result, it is a pointer to the CGrabResultPtr class.
08-29-2023 04:33 PM
Hello @always did you solve this proble already right? expanding the MTU of the interface?