Connecting to a Device
Network Setup
At boot the device requests an IP address from a DHCP server. If no server responds within 10 seconds, it falls back to a fixed address: 192.168.1.11 (subnet 255.255.255.0). The device screen shows WAIT IP while it is waiting, then its address.
Always read the IP from the device screen: it is the address you need.
Direct cable (no router)
Connect your PC directly to the device with an Ethernet cable. The device settles on 192.168.1.11 after 10 seconds. Set your PC's Ethernet adapter to a static address on the same subnet, for example 192.168.1.50 with mask 255.255.255.0.
Router or switch with DHCP
Connect both your PC and the device to the same router or switch. The device receives an address from the router; read it on the device screen. Your PC is already on the right subnet.
What the App Does For You
The connection is handled by the app: you do not send SETUP or set any address by hand.
- At launch, the app reconnects to the last board you used. If it has none (or it does not answer), it scans the network.
- One board found → the app connects to it. Several boards → the header shows Select a board and the Board window lists them. None → No board; the app keeps looking in the background.
- Once connected, the app takes the board (the board will stream its data to this computer) and, if the board needs it, configures it (Configuring…).
- When the header shows Ready, press START.
The Board Window
Click Board in the toolbar to open it. In the Scan tab:
- Click Scan. Boards of the local network appear in a list with their IP address.
- Click a board to connect to it. The window can then be closed with Select.
- If the scan finds nothing, type the IP address shown on the device screen in the field; the app connects when you press Enter or leave the field.
The Port field is the device's command port (55152 by default); the Channels counter shows the channel count reported by the connected board. The File tab opens a recording instead of a live board: see Recording and Replay.
Board Already in Use
A board streams to one computer at a time. If the board you connect to is already sending its data to another computer, the app asks:
| Choice | Effect |
|---|---|
| Take control | The stream is redirected to this computer. The other computer is notified. A running acquisition or Studio program on the board is not interrupted. |
| Observe only | The app stays connected without taking the board: you can read the board state but you do not receive its data. |
If another computer takes the board from you, a message The board is now used by … appears and the state becomes Board in use.
Status in the Header
The coloured dot and label next to the board show its state:
| Label | Meaning |
|---|---|
| No board | No board connected; the app keeps searching. |
| Searching… | A scan is in progress. |
| Select a board | Several boards were found: choose one in the Board window. |
| Connecting… | The app is talking to the board. |
| Board in use | Another computer owns the board (see above). |
| Observer | Connected without owning the board. |
| Waiting for headstage | No headstage is connected. START becomes available when one is detected. |
| Configuring… | The app is initialising the acquisition. |
| Ready | The acquisition can be started. |
| Starting… / Running | Acquisition starting or running. |
| Board busy | A measurement (for example an impedance scan) or a Studio program is running. |
| Problem | Something is wrong; the label tells what (for example Headstage detected but chip unreadable, No data received after start, Data stream interrupted). |
| Board lost | The board stopped answering (power or cable). The app reconnects when it comes back. |
The START and STOP buttons of the header are disabled when they cannot apply. Hover START to see why (for example Not ready: Waiting for headstage).
If the headstage is unplugged during an acquisition, the board stops it and the app shows Waiting for headstage; the app configures the board again when a headstage is back.
Connection Status in the Commands Panel
The connection target is shown at the top of the UDP Commands panel:
Target: 192.168.1.11:55152
If commands time out or the header shows Board lost, verify:
- The Ethernet cable is plugged in on both ends.
- Your PC is on the same subnet as the device.
- No firewall is blocking UDP ports 5000, 55151, 55152 and 55153.
Multiple Devices
On a network with a DHCP server, each device receives its own address, so several devices can coexist. Select the one you want in the Board window.
With direct cables (no DHCP), every device falls back to 192.168.1.11, which causes an address conflict if more than one is on the same network segment. Connect them one at a time, or put them on separate segments.
Older Firmware
A device with older firmware (no state report) is still supported with limited features: the app shows Older firmware (limited features) and leaves both START and STOP available.