Hello,
I am trying to use a D-link DCS-933L ip camera with Roborealm for my team’s vision code, but I can not get Roboealm to find the camera.
The camera is set up via its app and you can view its video feed through the phone.
Using the read HTTP command I used these settings,
Camera Type: D-link DCS-2102 (only d-link option)
Url: http://192.168.2.58/video/mjpg.cgi?profieid=1
Username and Password are put in
No HTTP Headers
Refresh Frequency:ASAP
Timeout: 1000ms
this does not work.
For the D-Link internet camera command:
ip Adress:192.168.2.58
Port: 80
Username and Password are put in
Refresh Frequency:ASAP
camera Type:DCS 900/920
This does not work either.
I tried this on the KOP router and a Belkin router but neither of these worked
If you know what I am doing wrong please reply
Thanks,
Ben
Is the IP on the computer that RoboRealm is running on compatible with the default camera IP address you are using (e.g., 192.168…)?
Our standard FRC IP addresses are either 169.254… in the pit or 10.TE.AM… on the playing field.
Giving the camera a static IP compatible with your RoboRealm PC or setting it to use DHCP is preferable.
The laptop’s ip is 192.168.2.56
should i change both ip’s to 10.54.04.2, 10.54.04.5 (or some other #)?
As long as they are compatible then I wouldn’t worry too much about the IPs for now, just get things to work. Eventually you’ll need to change them for competition.
You should be able to use a web browser to view the camera stream with the camera directly connected to the PC.
I haven’t played enough with RoboRealm to be much help debugging that interface, but I’d suggest getting the standard one’s to work first.
Using settings in the browser got it to work!
Thanks.
Ben,
If you get the browser to view the video on the same machine then you know that the network connection is good, so that’s a first test to check.
Then have a look at the Axis configuration. In more recent years the camera supports more formats. You need to specify MJPEG as the streaming format.
Finally, the authentication also changed. Try switching authentication off (i.e. don’t require a username/password) or switch it to a basic authentication scheme (I think the newer models support more sophisticated authentication.)
Once you have made these two changes to the camera, check that the browser connection still works and then try the Axis module set to 900/920. This is an issue one team had last year and with the above changes seemed to fix the issue. Please post here if that doesn’t fix the problem.
Thanks,
STeven.