Released in 2023 in order to re-imagined camera control hardware design, TeeHee has since ushered in an entirely new generation of hardware camera control options, including TeeHee HaLow.
The TeeHee project is now entirely open source. TeeHee and TeeHee HaLow run OpenWrt-based OS’s, have fully transparent BOM’s posted on their respective product pages and ship with comprehensive documentation. Both TeeHee and TeeHee HaLow enable both users and makers to take camera control further than ever before.
TeeHee acts as an Ethernet bridge that lives on the camera body. Put simply, TeeHee takes the Ethernet protocol from a camera body and allows the Ethernet data to be transferred wirelessly rather than through an RJ45 cable. In fact, that’s what any camera control hardware offering on the market currently does. How they do it differs (e.g. they may not use the Ethernet protocol to convey the control commands), but the overall conduit for passing along the control data is comparable.
TeeHee is compatible with all major cinema camera systems, provided you have the correct data cables for them. These include Arri, Red, Sony, Canon and Vision Research (Phantom). You can purchase data cables here.
Yes! TeeHee comes pre-imaged and only requires a few simple steps to configure. As long as you already have an on-set network set up, it’s as simple as connecting TeeHee to the SSID and setting the IP address of TeeHee.
Once you configure TeeHee to work with your network, its settings are stored and can even be transferred to additional TeeHee units, either at the same time or in the future. It’s a very “set-it-and-forget-it” setup process: You do it once and it doesn’t need to change, even from job to job, because your network is not changing.
At the same time, TeeHee is built around OpenWrt, which is infinitely customizable since it is open-source and constantly being developed by the networking community at large. There is nothing proprietary about TeeHee software that prevents you from using TeeHee as, for example, a pocket WiFi router with its very own DHCP server. TeeHee was designed for those who have never done camera control before—but at the OS level remains robust enough to be customized for those who wish to change settings or repurpose the hardware for something besides camera control.
All camera control hardware requires at least two devices: One that lives on the camera body, and one that lives with the person doing the controlling. If controlling multiple cameras, you will need one control box per camera (e.g. TeeHee). Multiple TeeHee units can connect to a single workstation through a wireless access point like the Ruckus R710. To enhance range and reliability, you can also deploy multiple access points (hardlined or wirelessly) as mesh points to blanket a larger physical space around your set.
Any external camera control device that lives on a cinema camera body will also require at least one cable, usually two. One cable is often required for power, while the other is for the “control” commands you’re sending. For TeeHee, you can find examples of power cables and data cables on their respective product pages.
You will need some sort of wireless access point at your “workstation” that operates at the same frequency as TeeHee. A popular option for 2.4/5Ghz is the Ruckus R710. For more information on what peripheral hardware is required for camera control, please see the preceding question (above).
Explicit numbers for range depend on a number of factors, including local interference, frequency congestion and the access point(s) you’re using to connect to TeeHee. In general, TeeHee running at the traditional WiFi frequency of either 2.4Ghz or 5Ghz will be reliable around a stage or on-location set as long as you have one or more access points in the area that will enable strong connectivity. Due to the prevalence of on-set 2.4Ghz and 5Ghz traffic, however, your experiences will be greatly affected by your exact locale.
TeeHee is a dual-band device, and therefore can work at either 2.4Ghz or 5Ghz. You cannot use both frequencies simultaneously, but you can easily set which frequency (and even which band within that frequency range) you’d like to use on-the-fly within the OpenWrt interface.
You can find a comparison grid of common camera bridges here.
TeeHee and Slate (by GL.iNet) are both network bridges that run OpenWrt. After that, the features on both the software and hardware features begin to bifurcate rather quickly since Slate was not designed with camera control in mind. It’s also worth noting that Slate is no longer an active product line.
On the OS side, TeeHee boots 80% faster than Slate and is clone-able, meaning you can save a settings profile and upload it to additional TeeHee units for expedited configuration.
On the hardware side, TeeHee is built to be more durable for set use (aluminum vs. plastic), offers reliable power input with a locking Lemo connection and was influenced by working AC’s who helped inform its design, including the anti-twist mounting holes, wide voltage range and overall form factor.
If the hardware for your camera control device accepts 2-Pin 0B Lemo for power (pin one being ground) and/or RJ45 cables as the connector for transferring control data, then yes, the same cables for TeeHee can be used interchangeably on other products. Please keep in mind appropriate voltage ranges and polarity schematics in any power application.
You can find both power cables and data cables on their respective product pages.
All wireless traffic in the US is allocated according to the FCC. WiFi, which is utilized by TeeHee, is a small portion of the long list of wireless frequency ranges allocated by the FCC. All hardware within all variants of TeeHee is FCC certified and compliant with domestic frequency regulations.
For international customers, the more common WiFi frequencies (e.g. 2.4Ghz, 5Ghz) are the same as those used in the US.
Let’s just say TeeHee is a talented little creature.
TeeHee runs OpenWrt, so any device that can connect to the wireless frequency employed by TeeHee is compatible with TeeHee. Any computer or device utilizing Ethernet protocol can hardline into a TeeHee. TeeHee was designed with camera control in mind, but it is very far from the only use case since OpenWrt grants an entire world of possibilities to the end user.
Because TeeHee and its OS, OpenWrt, work within the sandbox of WiFi Alliance standards, there’s really no limit to how many TeeHee units you can deploy on a single set. Well, sure, there is, but… you’re never gonna hit that upper threshold, in practice.
If you are thinking of TeeHee co-existing on the same network with a Slate unit, then yes, absolutely; A cam could have a TeeHee, and B cam could have a Slate unit. The two different units can play nicely on the exact same mesh network, as long as all devices are configured to operate within the same frequency range.