User Manual/2. Setting up the system

From Chordata documentation
Jump to: navigation, search
This article is work in progress, you might find that part of the information contained here is incomplete.

Congratulations! If you got here it’s because you have already gathered together all the parts needed to build your motion capture suit. Now is the moment of truth.

Initializing and testing the system[edit]

In this chapter we will put everything in place and see if it's working correctly. We should check the following functionalities:

  • The SBC boots correctly.
  • The SBC acts as an access point, and we are able to connect to it from a separate PC.
  • The Utility software on the SBC is working correctly.
  • The Hub and K-Ceptors are wired correctly and the Notochord is able to talk to them.

Wiring the Hub and raspberry[edit]

The Chordata Hub has two possible configurations: with or without a separate power source. This chapter describes how to build and use the simpler one without separate power source. In this configuration the power comes from the SBC.

Start by wiring the hub and the raspberry using female jumper wires as described in the diagram. Then power the Raspberry. You should see a red led constantly on and a green led blinking, that means that the amount of power provided is enough to keep the Raspberry working, and also that the system is booting.

Raspberry pi 3 and Chordata Hub wiring

Checking the Hub color code to get the state of the system[edit]

When the power is plugged to the SBC you should see the blue led [R1] on the Hub turn on and stay that way. This means that power is also arriving to the Hub. After some time you should see the RBG led [U4] on the hub start to change state:

HUB RGB led color codes
0 ORANGE the system has boot, but the WIFI interface is still not ready
1 GREEN the SSID has been exposed, and the system is waiting for a node to connect, or that someone has already connected to the WIFI network, but hasn’t accessed the server.
2 BLUE the system has found an external WIFI access point with the correct name, and it has connected to it
3 RED there was an error
4 YELLOW at least 1 client is connected to the notochord server
5 WHITE the notochord is transmitting data
If on boot the SBC founds an external SSID named “Chordata-net” with the password “chordata” it will drop its Access point funcionalities and connect to that external network

If after some time the led turns green or blue, then we are good to go.

Accessing the remote console[edit]

Notochord remote console

The remote console is a web-interface program that allows you to control the state of the notochord from any computer or mobile device, without installing additional software. Your device should be connected to the same network than the notochord, most of the time this means accessing the WIFI network that the notochord has exposed with the name Chordata-net. Then from a web browser go to the address:


The notochord.local name is resolved because the notochord acts as a DNS server on the local network. If your browser just keeps waiting for a response, and eventually times out, it probably means that you device is using another DNS server. You can try checking if your browser has an static DNS on its configuration, otherwise perhaps an static DNS server was set system wide. If your are connected to another network apart from the Chordata-net your device might be using the other network's DNS. Try disconnecting from other networks apart from the notochord one.

You should see a page like the one in the picture, this is the remote console:

Click in the big Connect button. You should see a welcome message on the console, and the RGB led on the Hub should turn YELLOW.

Within the remote console the most common operations are displayed as buttons. But the console exposes a Command Line Interface which gives you a very flexible access to most of the notochord functionalities. You can type help to get a list of the remote commands available. The most important command is init which accepts arguments. Every argument passed as initialization argument to a call to notochord. For example, you can type init -h to get a list of all the possible notochord arguments

Connecting the K-Ceptors[edit]

Plug one of the ID Modules on top of one of the K-Ceptors, then plug it to one of the gates of the Hub.
Be sure to plug the cable on the IN --> connector of the K-Ceptor. Other K-Ceptors can be connected to the output of the previous one forming a chain, always going from OUT --> to IN -->.

On a working K-Ceptor the Blue led [D1] should turn on and stay that way.


If you built the hardware yourself and want to know how to test and troubleshoot a K-Ceptor take a look at: Troubleshooting a K-Ceptor