NUbook Page on Mocap#339
Conversation
❌ Deploy Preview for nubook failed.
|
✅ Deploy Preview for nubook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@Tom0Brien can you confirm that the steps for recording the dataset are correct. I think they are but I just wnat to make sure they are clear |
| - **Calibration wand** | ||
| - **Calibration square** | ||
| - **Reflective markers** |
There was a problem hiding this comment.
| - **Calibration wand** | |
| - **Calibration square** | |
| - **Reflective markers** | |
| - **Calibration wand** | |
| - **Calibration square** | |
| - **Reflective markers** |
Can we add photos for these? Also the image for the usb dongle would be nice too. It's cause these are things that are easily moved and can be lost. If we need to find them, a picture should help
| 1. Connect the **motion capture modem/router** to the ethernet wall ports. | ||
| 2. Connect the **MSI laptop** to this modem via ethernet. | ||
| 3. At the **main lab modem**, disconnect the **black ethernet cable** leading from the wall port, and connect the **cream coloured cable** to the wall port. | ||
| 4. Next, unplug the **green cable** that connects the modem to the network hub, and connect the other end of the **cream coloured cable** in it's place. |
There was a problem hiding this comment.
We are cooked if the cable colours ever change. I think it is better to associate the cables with the devices they connect instead of just the colour
There was a problem hiding this comment.
I also was going to say that the terminology 'modem' and 'network hub' are not really correct. Instead, as @JohanneMontano said, this section should be more explicit than relying on physical descriptions of cables, etc. For example, "connect the outside network to the WAN port of epsilon-x router; disconnect the switch from the epsilon-x router's LAN port; connect the robocup-x router's LAN ports to a generic wall outlet", etc. rather than "disconnect green cable from router." (Which router? Which port? LAN or WAN?)
ysims
left a comment
There was a problem hiding this comment.
Looks good, getting someone to go through this (and update the PR) could be a good new recruit task.
| <summary>Network</summary> | ||
|
|
||
| - **Dedicated modem/router** for the motion capture system (isolated network) | ||
| - Ethernet cables for connecting cameras, modem, and laptop |
There was a problem hiding this comment.
| - Ethernet cables for connecting cameras, modem, and laptop | |
| - Ethernet cables for connecting cameras, modem, and computer |
|
|
||
| <summary>Hardware</summary> | ||
|
|
||
| - **Dedicated MSI Laptop** (Windows 10, Motive 2.3.1 pre-installed) |
There was a problem hiding this comment.
Maybe make this more generic but say that as of writing, the MSI laptop is set up with Motive in the lab.
eg
'Computer with Windows 10, Motive 2.3.1, [any port requirements, eg ethernet] - MSI laptop in the NUbots lab has these requirements'
| > _Note: This step may not need to be repeated every time. If the motion capture network is already configured, skip to the next section._ | ||
|
|
||
| 1. Connect the **motion capture modem/router** to the ethernet wall ports. | ||
| 2. Connect the **MSI laptop** to this modem via ethernet. |
There was a problem hiding this comment.
| 2. Connect the **MSI laptop** to this modem via ethernet. | |
| 2. Connect the **mocap computer** to this modem via ethernet. |
these are just to make it more generic, since I dont trust that MSI laptop to last forever.
| <Alert type="warning"> | ||
|
|
||
| Doing this temporarily removes ethernet access from the main lab network. Double-check that no one else is relying on the main network via ethernet before switching. | ||
|
|
||
| </Alert> |
There was a problem hiding this comment.
This might be good to put higher in the guide 😆
|
|
||
| ## Configuring Motive | ||
|
|
||
| 1. Open the **MSI laptop** and boot into **Windows 10**. |
There was a problem hiding this comment.
| 1. Open the **MSI laptop** and boot into **Windows 10**. | |
| 1. Turn on the **mocap computer** and boot into **Windows 10**. |
| 3. Change the network IP address to ensure that the three systems are on the same subnet. | ||
| 4. Change the network to `robocup-x` and configure the network. |
There was a problem hiding this comment.
This might need to be more specific. Something like
Change SSID to robocup-x
Input robocup-x password in the password field
Press c to configure and n to apply to network changes (if I'm remembering the process correctly off the top of my head)
Created a new NUbook page for our motion capture system.
Todo
Preview
https://deploy-preview-339--nubook.netlify.app/guides/tools/mocap-setup