rebuild mini kceptor and hub

daylanKifky

Dodo2207 Its possible that I broke notchcord with changeing my pi adress to something similar like 192.168.XXX.XX ?

not really, the only way to break it is to mess with the source and re-compile.

I'm pretty sure it's a firewall problem, sometimes the router also has one. But most of the times is just the windows one, which is apparently not easy to setup.
You could try to ping your computer from the RPi and viceversa, just write:

ping <IP ADDRESS>

on the RPi terminal or your PC's command line and see if you get an answer

Dodo2207

@daylanKifky, thanks for your help 🙂
I tried it and I get the ping both ways. Cmd showed me the pis and his own ping, same as the pi.

Ill create an second notochord image on a second sdcard and if thats not working ill switch to linux and try to connect to Blender there.

Ill keep you up to date 👍️

daylanKifky

Switching to linux feels always like a good idea to me 😉

But keep in mind that firewalls are typically permissive with the type of traffic ping generates. So this test only confirms that both devices are on the same network and no hardware problem is present.

Dodo2207

daylanKifky I tried again. I deactivated the firewall but nothing happend 🙁

Do you know which port need to bee allowed and whicht protocol it needs for proper working?

My router is a "FritzBox".

daylanKifky

Notochord uses UDP, by default at port 6565. You can confirm the port it's using by looking at initial banner

Dodo2207

Its not working again 🙁
I write down all the steps which I did. Maybe I forgot something important

notochord access port 6565 with the UDP protocol.
Let Blender through the private and public firewall
Open Blender
- delete the default cube, lamp and camara
- init Chordata
- switched to Mocap mode
started the pi
- is connected via wifi with my network
- switched to cd notochord/bin
Connected the Kc
calibrate the Kc with ./notochord -x
I scanned ./notochord --scan BlenderIP Host
Went in Blender
-chose Chordata testcube file
-chose subtarget kc-CH_2-2
-hit connect

Is the Notochord adress in the Notochord node the pis Ip?
If I check Show advanced Network do I need to enter my Blender host IP to the local Ip field?
Its possible to check if the Blenderserver from the plugin is working?

Dodo2207

Here is a screenshot with the nodes

daylanKifky

The steps seem right. You don't need to do the sensor calibration each time.

Take a look at this thread https://forum.chordata.cc/d/93-progress-experience-using-chordata/7

I gave @Chibiin some tests when he was experiencing similar problems. Perhaps you can try those.

But in the end it was just a misconfiguration of the firewall

Dodo2207

@daylanKifky and @valor thank you sooooo much for help. My first Sensor is working 🙂 🙂 🙂

I did some mistakes:
1. I forget to allow my computer to use port 6565
2. I thought my PC had a static IP. I tried the whole time with a wrong Ip to connect.

Ill create 14 more sensors the next days 🙂

Ill keep you up to date with my work 👍️

Flavia

Dodo2207 and @valor hi there! I'm Flavia, the Communications Lead of Chordata. Congratulations on the good work to both of you! In today's post on our social media, I talk about you:

Dodo2207

Hi @valor do you have any tips how to troubleshot the kceptor to identify which parts are not working?

valor

Dodo2207
Before doing any deep-checking, try to see if the cabling and the connector is working. Both 5V and 3V3 LEDs should light up. If the 3V3 is not lit then check your voltage regulator IC NCP114, and the output capacitor next to it (should be C6 if I remember it).
Then:

Check the polarities on applicable components and 1st-pin markings on ICs
Check the solder joints on neigboring pins for shorts
Check the solder joints for gaps
Get a working K-Ceptor and place it next to the non-working (aka device-under-test, DUT) and start measuring for the resistances across random points and expect the same on the DUT. If there's a difference then foloow the path and identify what can be causing the the difference.
If when connected this particular K-ceptor distrupts everything then unplug it and If you have a decent PSU, try powering this K-ceptor with current-limit set to 100mA. If the voltage drops below 4.0-4.5V then you have a hidden short somewhere on the board.
As a worst case, unsolder the IMU IC (save it in a market bag) and try another one. If it does not work, set the board aside and build a new board using the saved IMU IC.
🙂

Dodo2207

Thanks for your answer @valor.
Ill try building more kcs and test it.
The strange part is, that only one light is on on the working kc.

Ill try your steps after my exams in two weeks. Then I can concentrate me completly on this project 👍

valor

Dodo2207 Well, "Only one light is on" is a good hint for where to look at. Is it the 5V0 LED which is working, and 3V3 which is not working? if so check the output of the NCP114 regulator for 3.3v output.

Dodo2207

Thanks for your answer @valor. Ill check later in the month

Dodo2207

Hey everyone, sorry for beein inactive.
Ill continue with this projects the next weeks.

Dodo2207

Hi everyone, I paused the project.
My plan is to continueing 2021.

My goal is to use the sensors for props and/ or positioning for some eork with blender.

Ill keep the thread up to date

« Previous Page