Closed robinbansal08 closed 4 years ago
Hey @robinbansal08 is it possible there's an IP address conflict on your network (perhaps DHCP Handed 192.168.0.55 to another device)? You could check by powering off the camera and seeing if ping works or fails.
Otherwise, the 1.6.2114 firmware release is several years old and it would be worth your time to upgrade and see if the issues persist.
@graugans any other thoughts from the embedded side?
@robinbansal08 please check the following:
If the error is still present please contact your local ifm sales responsible and initiate an RMA
Thank you for your replies.
@graugans You are correct regarding the MAC addresses issue (+/-1). This camera (192.168.0.51) with the issue was working fine before, but this issue came up when I updated the firmware (to version 1.23.x) of few of the other cameras in the same network. Based on your suggestion, I have compared their MAC addresses and found one of the cameras (of which I updated the firmware) has consecutive sequence of the MAC address to the camera (192.168.0.51).
I have already replaced the camera(192.168.0.51) and now all the cameras in the network are working fine now.
I have also checked the MAC addresses of all the cameras in the same network and found around half of the cameras having MAC addresses +/-1 with other cameras.
Currently all cameras are working fine but I want to update their firmware as we have to run our applications over the camera. So if we update the firmware with the latest version 1.30.x, will this issue (ping packets loss) can still occur with the cameras with consecutive sequence MAC addresses ?
This issue is resolved, as per your suggestion I have updated the firmware of the cameras to 1.30.5309 and the cameras with sequence of +/-1 MAC addresses are working fine.
I am glad to hear the issue is solved. I'll close this, please reopen in case of any issues related to this topic.
I'm running Ubuntu 16.04 together with the O3D303 camera.
A ping to the camera IP 192.168.0.51 shows 90% packet loss:
When trying to use libo3d3xx command line utilities commands, most of the times, it fails with XMRPC call timed out error.
I have already tried with rebooting, resetting the camera, but problem still persists.
There are several other O3D303 cameras connected in the same network, but they are working fine.
pactrispro@CLOUDLink:~/xpsSea$ o3d3xx-dump --ip 192.168.0.51 > camera_51_dump.json
Here is the result of it: