Chordata Unboxing and first impressions

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.

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

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.

TackY

I had the same issue, chordata-net either not showing up or unable to connect to it.
What I did:
I connected a monitor and keyboard to the raspberry and set up the language code thingy manually according to the documentation - after that it still didn't work and there was a ssh error on booting the pi, this got solved by:

sudo ssh-keygen -A
sudo service ssh --full-restart

(regenerate all default ssh keys and restart the ssh service)

after this it launches the chordata-net correctly each reboot

daylanKifky

TackY sudo ssh-keygen -A

Yes, that should solve the SSH issue.

We are currently working on ways to avoid this "stuck with no wifi connection state", trying different approaches, it's tricky to find a robust way to implement it. Since the GUI itself is exposed thought that connection (we would like to avoid forcing users to plug an ethernet cable.
I'll open a new thread to discuss about it. I would love to know your opinions and suggestions

Jump

I appreciate the suggestions. I've had little time to tinker with the system lately, and I will likely just wait for the update before continuing

Jump

new and interesting issue, the 0x42 kcepter on branch 3 seems to blip in and out of existence

« Previous Page Next Page »