Chordata Unboxing and first impressions

Jump

Update the mocap system is very difficult to take off, as you end up in the middle of a tangled mess. I also have do not have a way to store the system other than as a wad of elastic straps and wires, and I can only imagine it will be a nightmare to put back on.

daylanKifky

Jump

Thanks for your valuable suggestions. We use the feedback that we get from this forum as our main source of ideas when developing our system, so we will for sure take yours into consideration when designing new versions.

The decision of using regular ethernet cables for this revision was explicitly conceived to allow users to get spare cables as easy as possible. So if you prefer other lengths of cables you can get them on any local store. But the set of cables that come with your kit should allow you to connect all the KCeptors while giving a good freedom of movements. We tested them in several body types. Are you following the cable distribution recomendations that can be found in this section of the documentation: https://chordata.gitlab.io/docs/mount-to-body/#different-cable-lenghts ?

Jump

Thank you for the kind words. Please understand I'm merely using this thread as a place to document my thoughts as I am getting used to the system, my goal was never to portray what was likely a very practical decision as invalid.

Jump

(Final?) Update
Unfortunate news, as my system appears to be busted.
To explain, the Pi can no longer detect any KCeptor along the '5' branch. I've narrowed it down to the Pi hat, as the problem persists when changing the cables and KCeptors attached to that port. I have no clue what has happened to it, as the system seemed to work fine when I put it away (all KCeptors were detected and no errors occurred). I can only assume I'll need a new pi hat, and I have no clue what that'll cost- assuming any extras exist to be purchased in the first place. I may try reinstalling the NotochordOS before I give up entirely. What a waste.

daylanKifky

Jump I have no clue what has happened to it, as the system seemed to work fine when I put it away (all KCeptors were detected and no errors occurred).

Oh, that's an extremely unlikely thing to happen. Moreover because of the way the Hub is build, if there's no sign of physical damage in the connector itself it is really hard to explain a unique gate failing.

Please get in touch with us through email or using our contact form and we will try to solve the issue

Jump

For reference, here is me testing a KCeptor on a working port.

Which gives this output:

But now here is me testing the same KCeptor and cable on the busted port.

Which gives this output:

I can see no damage to the port that isn't working. All the pins seem fine and the pcb seems to have no visible damage. If there are any debugging steps I can take I would very much like to know.

Jump

Reinstalling the OS didn't work. It look's like I'm gonna have a headless system.

Jump

Images of gate 5:

Jump

I have sent you an email about this issue, if you need more information form me please reach out.

daylanKifky

Hello Jordan,

could you do a test to diagnose the functionality of the bus that reads the KCeptors?

Please connect to the RPI through SSH, plug only one KCeptor on any gate and run this line:

i2cset -y 1 0x70 0xff; i2cdetect -y 1

Repeat the operation with the same KC in the gate 5. Do you have a positive reading in the range [0x40,0x42]?

Jump

sorry for the delay, things got a little busy in my personal life
I ran into an issue where I was complete unable to connect to the RPI through SSH, no matter what I tried the connection was refused when I attempted to connect to it using putty on my windows PC.
This problem continued even after a reinstall of notochord OS, so I eventually gave up and simply used a display and keyboard.
Enter the command you provided produced the follow results, (the first result was with the kcepter connected to gate 3, and the second result was with it connected to gate 5)

Jump

I have also found an issue with the Connection Manager, as I was unable to use the pi to connect to my wifi.
I was able to give the pi internet access via ethernet cord, but connecting this way would not give internet access to my PC when connecting to the pi, only the pi itself had that connection.
Below is the output of the shell after setting the wifi and attempting to update OS

Jump

daylanKifky

Hello Jump
The new wifi configuration will work only after a raspberry reboot. We should probably add that as a message to the user in the remote console.

From the capture of the console that you are sending me I assume that you hit the update button after setting the WIFI lan, right?

Jump

also to rule out any issues that could be from my end, I flashed a different micro sd card with notocord os, but there was no change

Jump

no good I'm afraid
after clicking the reboot button in the remote console the pi was stuck in a state where the Chordata network was visible but I was unable to connect to it

after powering off the pi it would no longer create the chordata network at all, the only solution I've found is to reinstall notocord os

daylanKifky

We are preparing a new version of the notochord with fixes to some small issues that we gathered in the last weeks. We will also review the external WIFI configuration.
It should be out in a few days

zaanen

daylanKifky
I had the same issue with the wifi settings Bruno.
@Jump on next try if fails the notochord is reachable by ethernet connection also.
Then there is a reset wifi button on the remote console where you set the wifi first time.
That fixed for me the AP.

« Previous Page Next Page »