This kind of suggests something about the nature of the problem, then, right? If you were here, I'd be only to happy to hook them up and sort out any issues for you - but as it is, I have to recommend working through it with CS.On two, I did. On the other two - I could not even get access to them via a direct connection to a computer.
The camera defaults to DHCP on. After a minute or two, if it does not get an address automatically from a DHCP server, it fails over to a static IP (192.168.100.168).- Connect an SDI cable to the port on the camera
- Connect the other end of the SDI cable to a monitor
- Connect the ethernet port on the cam to your network
(Look at the SDI-connected monitor for the following steps)
- Hit "menu" on the remote
- Navigate to the "Ethernet" setting
- Select DHCP
- Switch to "ON"
To be a bit fussy here (to avoid any confusion), Windows users would use NDI Studio Monitor (which is installed with the HX driver); Mac users have NDI Video Monitor (the older NDI Video Monitor for Windows wouldn't be of much help here).- Go back to the main menu and select "Status"
- Go to page 7, Ethernet, and make note of the IP
- Exit the menu
- Using NDI Video Monitor, locate your camera according to the IP listed above
- If you can see it, so can the TriCaster.
I appreciate your input, but that's not what I ran into yesterday. These cameras were set to "DHCP OFF" straight out of the box. (The other two were a-ok.) I had to go in and change them manually - they would not default over to the "on" setting no matter what I did or in what order they were connected.The camera defaults to DHCP on. After a minute or two, if it does not get an address automatically from a DHCP server, it fails over to a static IP (192.168.100.168).
If you power it up some time before connecting it to a network with a DHCP server, it may fail over to this static address. Something like this is almost certainly what happened to you.