Thread: Two Camera's
View Single Post
  #2   Spotlight this post!  
Unread 26-01-2011, 19:59
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Two Camera's

You are onto something ... , but then you are off.

It is possible to plug the camera(s) into the dlink and give them IP addresses in the 10.te.am.11+ range. I'd suggest making them static rather than dynamic IP assignment.

This is super useful from the programming laptop since you can now use vision assistant or a web browser to connect to the camera, make changes, capture images, monitor, etc.

This is also useful from a dashboard. Rather than ask the cRIO to forward all of the traffic from one port to the other, the camera can do this with no cRIO effort.

In the shop, when your dlink is in access point mode, the dlink publishes a network with an SSID name. If another laptop, iphone, etc knows the name of the network, any security settings, and the IP of the camera, they can log into the camera.

At a competition, the dlink is reconfigured to be a bridge -- basically the same as the black bridge from last year. Since it is a bridge, it doesn't publish a network, it extends one. Additionally, the network SSID that FIRST creates for each team is encrypted, and it would be that network a laptop would need to join in order to be able to communicate with the camera.

So, this is a really cool new option, but it doesn't lead to computers in the stands doing what you theorize.

Greg McKaskle