|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Axis Camera Issue
I think the DNS name needs to be
"axis-camera" as corrected Last edited by Mark McLeod : 12-02-2015 at 09:18. Reason: fixed error |
|
#2
|
|||
|
|||
|
Re: Axis Camera Issue
The documentation shows just "axis-camera". .local is a suffix used to indicate mDNS should be used for resolution.
|
|
#3
|
||||
|
||||
|
Re: Axis Camera Issue
Today, I just booted up the driver station and it just magically worked. I have no clue what we did, but it happened.
|
|
#4
|
||||
|
||||
|
Re: Axis Camera Issue
Same issues. By changing the axis-camera to a hard coded IP address and changing the camera itself to a static address, we got our 1013 to work. However, it will NOT work under IP camera mode. It will work under USB HW mode on the dashboard. The data usage is extremely high - at least 6Mb. Changing resolution settings on the dashboard has effect - sometimes. But the data usage is quite high even down at 10 fps.
We tried the Microsoft USB camera and it worked straight out of the box, at 30 fps, with a lower CPU utilization on the roborio. We're not happy with the resolution itself - it's blocky and poor, but cpu utilization and fps is more important to us so we're sticking with the USB camera. Mounting it is even worse than the axis camera though. |
|
#5
|
|||
|
|||
|
Re: Axis Camera Issue
We had similar issues and everything was set up correctly. We finally found out that the resolution selected on the dashboard was the problem. Hope this helps anyone else with the problem.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|