Difference between revisions of "User Manual/2. Setting up the system"

From Chordata documentation
Jump to: navigation, search
(Power modes description)
(remove Color codes and Remote console)
Line 49: Line 49:
<gallery widths=400px heights=300px>
<gallery widths=400px heights=300px>
File:SBC power source supply.jpeg|Power lines on SBC power source mode  
File:SBC power source supply.jpeg|Power lines on SBC power source mode  
File:File:SBC power source selection.jpeg  | Selecting the SBC power source with a jumper  
File:SBC power source selection.jpeg  | Selecting the SBC power source with a jumper  
Line 60: Line 60:
[[File:Raspberry-hub-wiring.png|800px|Raspberry pi 3 and Chordata Hub wiring]]
[[File:Raspberry-hub-wiring.png|800px|Raspberry pi 3 and Chordata Hub wiring]]
===Checking the Hub color code to get the state of the system===
{{note | This feature is not implemented yet. Kits from the beta-testing program don't include the RGB led on the Hub board | error }}
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
! style="text-align:center;"| CODE
| style="background-color:orange;"|ORANGE
|the system has boot, but the WIFI interface is still not ready
| style="background-color:green;color:white"|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.
| style="background-color:blue;color:white"|BLUE
|the system has found an external WIFI access point with the correct name, and it has connected to it
| style="background-color:red;color:white"|RED
|there was an error
| style="background-color:yellow;"|YELLOW
|at least 1 client is connected to the notochord server
| style="background-color:white;"|WHITE
|the notochord is transmitting data
{{note | 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 | hint}}
If after some time the led turns green or blue, then we are good to go.
===Accessing the remote console===
[[File:Remote console.png|thumb|frame|Notochord remote console]]
The [[Remote console | 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 <code>Chordata-net</code>. Then from a web browser go to the address:
{{note | The <code>notochord.local</code> 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 <code>Chordata-net</code> your device might be using the other network's DNS. Try disconnecting from other networks apart from the notochord one.|warning}}
You should see a page like the one in the picture, this is the remote console:
Click in the big <code>Connect</code> button.
You should see a welcome message on the console, and the RGB led on the Hub should turn <span style="background-color:yellow;">YELLOW</span>.
{{note | 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 <code>help</code> to get a list of the remote commands available.
The most important command is <code>init</code> which accepts arguments. Every argument passed as initialization argument to a call to <code>notochord</code>. For example, you can type <code>init -h </code> to get a list of all the possible notochord arguments | hint}}
===Connecting the K-Ceptors===
===Connecting the K-Ceptors===

Revision as of 15:38, 8 April 2019

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

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

Some of this functionalities require some tweaking. They will be available soon..
  • 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.

Powering the system

10400mAh Power bank and Raspberry Pi

To power the system a 5V, 2A supply is needed. It can be connected to the SCB only, or also to the Hub. Both connections use a micro USB-B connector. By far the easiest way to achieve it is to use a common power bank. It should be rated for at least 2A.To have a durable supply a capacity of at least 10000mAh is desirable. Under normal capture conditions such a power bank was able to keep the system running for around 8 hours.

The Chordata Hub has two possible configurations: with or without a separate power source. A jumper on the Hub (JP1) allows you to select between these configurations.

  • In the former the power comes from a buck converter on the Hub, that takes a 5V input and delivers 3.3V to the rest of the system.
  • In the latter the power comes from 3v3 rail on the SBC.

The Chordata system uses only a 3.3V tension. Don't apply 5V or higher voltages directly to any pin! Otherwise it can result on unrepairable damage.

A 5 volt tension can be applied only via the micro USB connectors on the Hub or SBC

Using the dedicated power source

This is the recommended configuration. The power line from the Powerbank should go to the micro USB connector on the Hub (J12), and from the big USB connector (J11) to the SBC.

To use this configuration the jumper should be positioned connecting the pins #1 and #2 of JP1

Using the 3v3 rail from the SBC

This configuration is mostly used for testing purpouses. The power line from the Powerbank should only go to the micro USB connector on the SBC.

To use this configuration the jumper should be positioned connecting the pins #2 and #3 of JP1

Wiring the Hub and raspberry

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.

The blue led on the Hub should stay on as an indicator of a stable power supply.

Raspberry pi 3 and Chordata Hub wiring

Connecting the K-Ceptors

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