Jump to content

John Doe II

Member
  • Content Count

    223
  • Joined

  • Last visited

  • Days Won

    1

John Doe II last won the day on November 25 2019

John Doe II had the most liked content!

Community Reputation

16 Good

About John Doe II

  • Rank
    Sting Ray

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Techs at the teleport always referred to them as class A/B/C. we just followed suit.
  2. it does seem to imply that if you lose vacuum for some reason then the WACP is no longer held in place. Never having used this setup I am not really sure - hence asking here. But then again, if I re-read this, it could also read as "there is no SAFTEY lock" - it must still attach into place somehow - just that there is no safety lock so you could possibly get the port off accidentally and that is where the vacuum comes into play. When vacuum is pulled the WACP is locked tight against whatever method is used to attach it to the housing. There was a post somewhere were Alex Mustard siad he uses the WACP with a Subal housing (D850 iirc). Dr Mustard never mentioned any issues so I have to assume it works well ?
  3. we use 10 and 172 ranges all the time.
  4. I have been in touch with Saga and Jose advises that the WACP on the Subal is held in place by vacuum only. I have to assume that this is OK and works well. "You also have to have a vacuum system, the ring that I manufacture does not have a safety lock, I have made many of these rings and they are all like that, when you assemble the set you have to put it in the correct position and make the vacuum, with this The set remains rigid and you cannot move it." Luckily I have had a vacuum system fitted and upgraded to a type 4 port mount on the housing - so all set to go for this. Has anybody actually used this type of setup? Any pointers/heads-up/gotcha's ?
  5. Do you think it would help at all to use a class A subnet IP instead of a class C ? Get right away from the 192.168.x.x ranges ?? something simple like 10.10.0.1 /29 ? So as you say, static IP's on each end with a small number of useable IP's like a /29. That might do away with all the hunting for the IP's that the camera seems to be doing. And if that is indeed useful then as you say a /30 is even better - be faster for the camera's IP tables to scan (it will most likely be a linux variant of OS onboard the camera ...possibly BSD .... and if that is the case it would be using some form of IP Tables). It does seem to be some IP address issue though.
  6. OK well that is good to know. There is of course a vacuum system fitted to the C200 housing by default so that all helps. I have been in touch with Saga re the WACP on a Subal but will take that over to the right forum section. Not going to bother with WACP on the Seacam housing since I have the Nikonos seacam conversion lens for that housing. It has taken a long time to get all this gear together but almost there now.
  7. Yep - understand all that. I was also in IT - not quite as heavy as network support but i was involved in installing WAN links and setting UP Public IP's and Private IP's on various subnet levels. I am not quite sure what the 169.x.x.x range is all about - generally when you get a 169.x.x.x the connection is not getting through. Overall it does seem as the ethernet link can be made to work with enough perseverance. Its surely a better way to go then the alternatives and gives up to 300ft of usable cable length.
  8. I have never fitted a bulkhead fitting to a housing so not sure what is involved or how precise it needs to be. So will let the dealer do it in his workshops to make sure it comes out to me right. I am going to go ahead and get the ethernet setup from Dive and See. Products / Connectors / DNC-2084 DNC-2084 US $395 Elbow style Underwater LAN Ethernet Cat6 bulkhead connector, 8 circular contacts * DNC-2084 Elbow style bulkhead connector is used for facilitating the transmission of LAN Ethernet data at speeds up to 1,000 Mbps (1 Gigabit per second) between underwater systems * The new design allows installing the bulkhead connector in available - desirable direction on your housing. Elbow shape (90 degrees) of the connector keeps the external cable horizontally, instead of the standard vertical style of the connections * Material: Marine Aluminum with Hard Anodizing coating * Bulkhead connector has a water block, which is allowing to keep vacuum inside of your underwater housing * HIGH SPEED CAT5E CABLE, Stranded T-568B Wiring * 8 Contacts (Brass - Gold plated) * Custom length and other connector types are available * Depth - 240 PSI (160 meters) * Compatible with LAN Ethernet Dive And See cables DNC-1101, DNC-1044, etc to go with this cable Products / Underwater Cables / DNC-1044 DNC-1044 US $650 300ft Underwater to Surface Cat6 Ethernet Network Cable, LAN * Depth Rating 90 meters * Connecting any CAT6 applications to the computer, router, hub, Network, distribute data or video* Z CAM E2 Gigabit Ethernet for data, control & live preview* Transmit UltraHD (3840x2160) at 25/29.97 fps 4K/HD Camera such a AJA RovoCam* Gigabit Ethernet* Power over Ethernet (PoE) compatible* Supports IP Cameras* Cable compatible with Dive And See bulkhead connectors DNC-2025, DNC-2031, DNC-2071, DNC-2084, DNC-2082* The bulkhead connector sold separately
  9. Agree - however you just dont know how Canon have coded the setup. It sounds like there is some sort of routine that the camera runs to hand out an IP - and it sounds convoluted at best. But this is why there is some sort of issue with the ethernet on this camera. Something odd about it for sure. And no, I dont have a camera to try it on. I have yet to purchase the camera. As has been said many times here, work backwards. First find a camera that works for your purpose then get the housing/ports/extras setup and then worry about the actual camera itself last as thats the easy bit.
  10. Came across this in my searching on the topic of how to resolve the known ethernet problem for the remote browser. Thought it might be useful to put it up here in case anyone comes along in the future looking to solve this same problem. ______________________________________________________________________________________________________________________________ "I have not set this up with any of the EOS cinema line but I dealt with the issue with my 1DX series bodies which I always connect via ethernet. The Canon instructions are NOT well written and if you are using Windows 10 it seems to create its own issues after updates but there is a work around to it. If possible, go with an ethernet cable directly into your workstation which avoids the additional complication of dealing with a router. That is what I do with my HP Z840 and Z820 workstations. Once you do this, try using the automatic network configuration in the camera and then launch the Canon utility software on your computer. The initial setup/configuration is very slow and will appear at times to be stuck but give it time (up to 5 minutes if I remember correctly). It will grab a dynamic address as part of the setup and once it completes write down this address and enter it as a fixed IP address in the camera network setup. This was 1/2 of the trick to getting it to work quickly and reliably with my Win 10 workstations because otherwise connection was very slow every time. The other half of the trick is to set the Canon software to NOT launch automatically but instead you should launch it manually after you start network connect for subsequent uses. After I went to this fixed IP setting and not launching software automatically, the problems that occurred after frequent Win 10 updates went away and the ethernet connection is a pleasure to use. I often use three DSLR bodies at events (1DX, 1DX 2, and 1DX 3) and I transfer everything via ethernet. Until I figured out the trick of setting a fixed IP address it was a pain every time but now it is a quick and sure connection. And from the time I spent "googling" looking for a solution I figured out that apparently not many people use a direct ethernet connection because I found a lot of people asking questions but not finding solutions. Good luck! Rodger EOS 1DX M3, 1DX M2, 1DX, 5DS R, 1D M2, EOS 650 (film), many lenses, XF400 video " ________________________________________________________________________________________________________________________________________________________ So while not exactly the same camera it is quite possible that the above workaround will solve the C200 ethernet problem as well. If it does work then it makes everything simple. Not cheap though. Nothing is ever cheap with underwater anything. $650 for 100m of ethernet, $395 for a bulk head. So $1050 plus fitting of bulkhead to get all this working. Still if it can work its the simplest way to do it all and I will be thankful we can get the ethernet connection working. So, I do need the camera now after all as I need to know whether this work around works on the C200 because I have to get the right cable and bulkhead and get it fitted before it comes out to me. But at least some progress.
  11. That is correct - I dont have the camera yet. In this crazy world of underwater photography the camera is the cheap bit. I am getting all the other bits together first as that's where the real money is. I will get the cam when I am ready to splash the setup. The camera keeps going down in price in the mean time. Seems around the 3K price for a good low hours used cam is where it is at right now. As ever, one has to wait for the right piece of equipment to come along. But they do eventually. The very last thing I will buy is the lights. Lighting tech is moving so fast. The ethernet on this cam is buggy. Many users have reported it. Its a 2017 cam (ancient now by a lot of standards - but its 4K 12 bit Raw - crazy times we live in to call that standard ancient). If by 2021 this ethernet problem is still a thing then I cant see it ever being sorted out. Probably only Canon can fix it with a firmware fix perhaps? But it looks like they have long since moved onto to bigger and better things, so it seems likely that the ethernet on this cam will never work the remote browser well. Shame really because if it did work well it is perfect for my application and simple enough to use a dive and see cable/bulkhead. My target depth is 55m - so 100m would allow sufficient slack so as not to pull on cables etc - provided I use ethernet. The HD-SDI cable solution while known to work only gives 45m. I am working in a vast inland lake. But gets as rough as the sea. No tides. Some places do seem to have a current but most places I work dont.
  12. Does make sense - no power requirement is a big one. Anything using power generates heat and there is enough heat being generated in a closed housing as it is without adding more. Which is what I want to do. The cam generates its own wi-fi signal and devices can lock onto it. So i need to to get that wi-fi signal and transmit it to the surface. The device I linked does this - it takes the wi-fi signal and sends the data out on ethernet. Advantage is I can get a 100m run to the surface. Disadvantage - and its a big one in this case - it most likely wont fit into the housing. Plus it needs power (could probably take power from the USB on the camera) and therefore must produce some heat. The online reviews for this device are not good anyway so not the way forward. I am not sure either hence posting here in case anyone here knows how to do this. Seems that the Nauticam wi-fi extender setup is the way to do this. I am sure a lot of clever guys have looked at this and that is what they came up with - has to be some good reasons why. Problem is the max cable length is only 45m - looks like that is going to have to do. This cam came out in 2017. As of 2020 there are YT videos out on setting up the remote browser feature and how it works well on wi-fi and is buggy on ethernet. I dont know how I would fix that. If it was going to be addressed by canon it would have been done by now. I am assuming that the ethernet connection is not going to be viable here. Wi-fi is a known good operator on this cam.
  13. ahhh isee - RF signal only. Hmmm seems an odd way to do it. Would something like this work ? https://www.amazon.com/IOGEAR-Ethernet-2-WiFi-Universal-Wireless-GWU637/dp/B018YPWORE the only issue i could see is space in the housing.
  14. opps - you're right - meant to say 300ft. I want to put the camera at 50m depth and to control the camera from topside. There is this : https://reefphoto.com/blogs/custom-projects/wi-fi-extender-configuration-guide not sure why they are using SDI cable ? maybe they are trying to record through that sdi cable ? I dont have the camera yet - getting all the expensive stuff squared away first - the cheapest bit of all this is the camera !
  15. Ha ! well there is this ... https://reefphoto.com/products/nauticam-wi-fi-extender-kit-wifi My Google foo sometimes fails me. Got there in the end. This might work with a dive and see 300m ether cat 6 cable. Going to check it out to see if we can make this work..
×
×
  • Create New...