WHAT FRESH HELL IS THIS?
So now that my hardware is worked out, and now that I was able to calibrate all the Kceptors, I connected everything in the suit... with some unexpected results.
@daylanKifky , I call upon your expertise! Help a beta tester in trouble!
I started up Notochord,and got this error message:
info~[ 105] Timer started, 21 nodes on scheduler
error~[ 274] error switching branch right_leg. Retrying.. (0)
error~[ 463] error switching branch right_leg. Retrying.. (1)
error~[ 651] error switching branch right_leg. Retrying.. (2)
error~[ 840] error switching branch right_leg. Retrying.. (3)
error~[ 1028] error switching branch right_leg. Retrying.. (4)
error~[ 1048] Too many errors when switching branch right_leg.
error~[ 1049] An error ocurred: Can't write to mux
Seemed like a simple question of not having the leg connected to the Hub properly. But the connection seemed tight. Ran it again, same error. On a hunch, I tried
info~[ 437] Scan: No Hub found
error~[ 5817] Fatal error: No armature, aborting.
Shut it all down, checked the connections. Rebooted, this time I ran
i2cdetect -y 1 - it showed no Hub! Shut it down, reconnected the jumper wires. Tried it again, this time the familiar 73 showed up. Maybe just a bad wire? A loose connection? So I tried these things:
- Shut down. Connected Head/Dorsal and Base only (J2 and J5). Ran
i2cdetect -y 1, it saw "73." Ran --scan, it saw everything on CH_2 and CH_5.
- Shut down. Connected arms and legs. Ran
i2cdetect -y 1 and it saw "73." Ran the biped, it said the base was missing now. Then I ran --scan and it said "No Hub!" ran
i2cdetect -y 1 again and 73 was gone.
- Shut down. Disconnected Base. Started up, ran
i2cdetect -y 1 again, 73 was back. Shut down, connected base, ran
i2cdetect -y 1, 73 was OK with the base now! Ran the biped. It couldn't find right leg again, just like above. Ran --scan, and it said "No Hub."
I'm not sure what is going on. Could my Hub be disintegrating before my very eyes? Could somehow the "base" connector, so close to the leg connectors that keep disappearing, be broken or shorted? Could a bad wire be the cause?
The weird thing is that two days ago I used the exact same Hub to calibrate all my Kceptors out of the J1 connector on the Hub and everything was just fine.
Experience my frustration yourself! Full logs in this pastebin here: