Using the find_KCs program

sully

I was hoping for some clarification on the capabilities of find_KCs.sh

I'm still in the process of fully building my K Ceptors and am using the program to test each one after assembly without worrying about having the right XML configuration in notochord. Things are going well, I have 3 working K ceptors with values of [0], [1], and [2].

There are some quirks to my setup that I'm not sure if it's the nature of the program or an issue on my end. When I connect a single K ceptor to the hub and run ./find_KCs.sh it doesn't find it.

However it does find a K ceptor if I for example connect Hub ->in K Ceptor[0]out -> in KCeptor[1] in a chain configuration. Without fail, the program will detect the K Ceptor at the end of the chain and would in this instance return

MUX found at 0x73 == K-Ceptors in gate 1 ==> [1] == K-Ceptors in gate 2 ==> == K-Ceptors in gate 3 ==> == K-Ceptors in gate 4 ==> == K-Ceptors in gate 5 ==> == K-Ceptors in gate 6 ==>

Is this behaviour normal? I get a result like this across the board when I swap out cables, swap out K Ceptors and hub ports in every available configuration. It always returns the K Ceptor in the 2nd position of the chain. If I made a chain like this

Hub -> in Kceptor[0] out -> in Kceptor[1] out -> in Kceptor[2] is the program supposed to return this?

MUX found at 0x73 == K-Ceptors in gate 1 ==> [0], [1], [2] == K-Ceptors in gate 2 ==> == K-Ceptors in gate 3 ==> == K-Ceptors in gate 4 ==> == K-Ceptors in gate 5 ==> == K-Ceptors in gate 6 ==>

My setup would only return this for that example:

MUX found at 0x73 == K-Ceptors in gate 1 ==> [1] == K-Ceptors in gate 2 ==> == K-Ceptors in gate 3 ==> == K-Ceptors in gate 4 ==> == K-Ceptors in gate 5 ==> == K-Ceptors in gate 6 ==>

daylanKifky

sully
Well, yes it is supposed to print every K-Ceptor in the chain. It is a very simple script and it always worked well for me.

I haven't used it in a while though. Now the the notochord has a scan feature that gives you a similar output before starting to read the sensors it founds.

Try running

bin/notochord --scan

daylanKifky

🤔 maybe the wires are crimped in an incorrect order. The ordering on both ends should be mirrored.

I know this is a strange question coming from me, but.. where did you found the information to crimp them? I can't find it on the wiki 😅

sully

daylanKifky Ahh I was wondering about this but was led on because things were partially working. I had crimped them in parallel instead of mirrored. I didn't find any info about crimping I just made an assumption after watching some general tutorials. Made a new cable and it works as expected now, thanks!

daylanKifky

sully
Sorry about that, keeping the documentation complete and updated is not an easy task.

I added some more information on the Cables section of the wiki