HowlNET Overview
HowlNET is the proprietary networking technology designed specifically for multi-camera synchronization.
What is HowlNET?
HowlNET is an integrated solution that combines power distribution, effect data communication, and precise synchronization signals through a single Network cable between nodes.
Key Features
- Single Cable Solution - Power, data, and sync all in one RJ45 connection
- Daisy-Chain Architecture - Simple OUT → IN connections between nodes
- Automatic Discovery - WOLF nodes self-organize into Director/Listener hierarchy
- Real-Time Sync - Sub-millisecond timing across entire network
- Long Distance - Up to 100m (328 ft) between nodes
- Plug & Play - No manual configuration required
How HowlNET Works
Network Topology
HowlNET uses a daisy-chain topology where nodes connect in a linear sequence:
┌────────────┐
│ Computer │
└─────┬──────┘
│
│ USB Type-C
▼
┌────────────┐ ┌────────────┐ ┌────────────┐
│ WOLF 1 │────▶│ WOLF 2 │────▶│ WOLF 3 │────▶
└────────────┘ └────────────┘ └────────────┘
Director node:
- First node in the chain
- Connected to computer via USB (optional)
- Receives Bus power input (typ. 24V)
- Broadcasts commands to all Listeners
- Manages network timing and synchronization
- Stores configuration and effects using internal memory
Listener Nodes:
- All subsequent nodes in chain
- Receive power through HowlNET from previous node
- Execute commands and report status back through network
Power Distribution
HowlNET's features distributed power:
- Connect a Bus adapter to first node only (Director)
- Power flows through HowlNET cables to all nodes
- No need for individual power supplies
- Simplified cable management
Data Communication
HowlNET handles all inter-node communication:
- Command Distribution - Trigger, wake, and effect commands
- Status Reporting - Device connection status, calibration data
- Auto-Discovery - Automatic node enumeration
Network Latency:
- Typical: 260µs ±5µs message latency
- Synchronization: ±5µs trigger accuracy across all nodes
Daisy-Chain Direction
Always connect: HowlNET OUT → HowlNET IN
┌─────────────┐ HowlNET ┌─────────────┐ HowlNET ┌─────────────┐
│ WOLF 1 │───────────▶│ WOLF 2 │───────────▶│ WOLF 3 │───────────▶
│ (Director) │ OUT → IN │ (Listener) │ OUT → IN │ (Listener) │
└─────────────┘ └─────────────┘ └─────────────┘
Incorrect Connection
Connecting OUT → OUT or IN → IN will not work. HowlNET is directional.
Typ. Network Capabilities
Synchronization
| Feature | Performance |
|---|---|
| Trigger Accuracy | ±5µs across all nodes |
| Network Latency | 260µs ±5µs typical |
For event timing specifications, see Effect Overview.
Scalability
| Parameter | Limit |
|---|---|
| Maximum Nodes | 32 |
| Maximum Cameras | 6*Nodes = 192 |
| Maximum Mono Ports | 2*Nodes = 64 |
| Bus Length | 100m (328ft) |
Auto-Discovery
When nodes power on, they are added to the network. This happens automatically, no manual configuration needed.
Leash Integration
When connected to Leash via USB on the Director node:
- See all nodes - Full network visibility in Leash App
- Control any output - Trigger cameras and mono ports on any node
- Configure any output/input - Change node settings and port modes
- Monitor status - Real-time device connection status
- Design Effects - Configure effects and instructions for every port
Leash shows:
- Total WOLF nodes in network
- Total cameras ouputs across all nodes
- Total mono outputs across all nodes
- Total inputs across all nodes
Practical Examples
120 Camera Scanning System (20 Nodes)
┌───────────┐
│ Computer │
└────┬──────┘
│ USB
▼
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
│ WOLF 1 │─────▶│ WOLF 2 │─────▶│ WOLF 3 │ . . . . ▶│ WOLF 20 │
└───────────┘ └───────────┘ └───────────┘ └───────────┘
1 input 6 Cameras 6 Cameras 6 Cameras
6 Cameras
2 LED/Strobe
▲
│
┌───────────┐
| 24V Power |
└───────────┘
Total Possible: 120 cameras, 40 strobes, 20 inputs
Remote Cameras (Long Distance)
┌───────────┐
│ 24V Power │
└────┬──────┘
▼
┌───────────┐ 100m cable ┌───────────┐
│ WOLF 1 │──────────────────▶│ WOLF 2 │
└───────────┘ └───────────┘
1 input 1 input
6 Cameras
2 Strobes
Total Possible: 12 cameras, 4 strobes, 2 inputs (one local, one remote)
12 Cam PhotoBooth (2 Nodes)
┌─────────────────────────────┐
│ Dual Port USB Adapter │
└────┬──────────────────┬─────┘
▼ ▼
┌───────────┐ ┌───────────┐
│ WOLF 1 │────▶│ WOLF 2 │
└───────────┘ └───────────┘
1 input
6 Cameras 6 Cameras
2 Strobes 2 Strobes
Total Possible: 12 cameras, 4 strobes, 2 inputs
Troubleshooting HowlNET
Nodes Not Detected
Symptoms: Leash shows fewer nodes than expected
Solutions:
- Check cable connections (OUT → IN direction)
- Verify 24V power to first node
- Try different Bus Network cables
- Power cycle entire system
Power Issues
Symptoms: Distant nodes not powering on
Solutions:
- Check 24V adapter capacity (2.5A minimum)
- Reduce number of nodes or add power injection (contact@arceye.com)
- Use shorter network cable runs
- Ensure good cable connections
Timing Problems
Symptoms: Cameras not syncing properly across nodes
Solutions:
- Run camera calibration for all camera types
- Ensure firmware is up to date on all nodes
- Ensure cameras are waked (AF) before triggering
For more troubleshooting: Troubleshooting Guide
Best Practices
Cable Management
- Use quality cables - Cat5e or Cat6 recommended
- Label connections - Mark OUT and IN on each cable
- Avoid kinks - Don't bend cables sharply
- Secure routing - Use cable ties to prevent disconnection
Network Design
- Plan node order - Director first, Listeners in sequence
- Minimize distance - Shorter cables = more reliable
- Power planning - Calculate total node power consumption
- Test incrementally - Add modulesone at a time to verify
Maintenance
- Check connections - Verify RJ45 clips are secure
- Clean contacts - Remove dust from connectors
- Update firmware - Keep all moduleson same version
- Document setup - Note cable lengths and node positions
Having issues? See Troubleshooting