rebuild mini kceptor and hub

Dodo2207

I calibrated my first sensor. My next test is with Blender the next days.

I'll build couple more sensors and another hub the next week.

Dodo2207

Hi @valor how did you get the connection between the the pi and thr PC?

I need to recalibrate each time I start the raspi.
I tried with the. /notocoard -x IP4 adress but it only calibrates the Kc. If I need a different adress where can I find it

I opend a blendfile added the nodes abd click connect but nothing happend.

valor

Dodo2207 I have the raspi connected to my wifi, the DHCP server is configured to give the raspi a static IP address, this way i always know it's IP address and it does not change.
As long as I can ssh to the raspi from my PC i know the connection is working.

daylanKifky

Dodo2207 I tried @daylanKifky python script.

This is a problem of clear not existing in windows. But I remember creating another version of the script to take this into account, see here: https://forum.chordata.cc/d/63-calibration-issues/71

Dodo2207 I need to recalibrate each time I start the raspi.

You are supposed to re do the pose calibration each time you capture, what you do with notochord -x is the sensor calibration which is stored in the EEPROM

Dodo2207 I opend a blendfile added the nodes abd click connect but nothing happend.

In order to troubleshoot this connect a Dump node to the Notochord node. Do you get any incoming messages printed on the blender console?
If you don't there's probably a firewall blocking them, see here: https://forum.chordata.cc/d/93-progress-experience-using-chordata/8

Dodo2207

Ok Ill do it later as well. Hopefully it will work.

Dodo2207

Hi @valor, I set a stratic Ip to the Raspi and conect via ssh to it.
I tried @daylanKifky python script.
I get following repeatible lines:

I cant see the roations of my sensor in Blender

I used for the calibration process the ip of my windows 10 machine.
For scanning I use the same ip adress.

Another prob is that port 1 and port 6 are not working on my hub. Ill create a second hub and hope they will work then.

valor

Dodo2207 I don't think I know that script.
It's a good idea to have a spare hub. I used my backup-hub for troubleshooting as well.

Dodo2207

Thanks for your answer @daylanKifky , @valor 🙂

After trying it with 2 windows Ill see the the sensor output in the second window.

But if Im replaceing the pi adress to my computer adress with Blender, I wont get any output in the second pi window.

I turnd off the firewall as well.

Its possible that I broke notchcord with changeing my pi adress to something similar like 192.168.XXX.XX ?
I changed the notchcord adress in Blender to my new pi adress too.

I connected the pi via ethernet cable to my network

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.
🙂

« Previous Page Next Page »