SpammerHellDontDelete at 09:38, 19 July 2009

2009-07-19T09:38:02Z

← Older revision		Revision as of 02:38, 19 July 2009
Line 3:		Line 3:
	if the motor function is like this:		if the motor function is like this:

	</pre>		<pre>
	case 1:		case 1:
	shiftOut(serial_in, SRCK, LSBFIRST, B10000000);		shiftOut(serial_in, SRCK, LSBFIRST, B10000000);
Line 31:		Line 31:
	then the motors actually turn on in an order more like 2,1,4,3,6,5,8,7. So, here is how it should look:		then the motors actually turn on in an order more like 2,1,4,3,6,5,8,7. So, here is how it should look:

	</pre>		<pre>
	case 1:		case 1:
	shiftOut(serial_in, SRCK, LSBFIRST, B01000000);		shiftOut(serial_in, SRCK, LSBFIRST, B01000000);

SpammerHellDontDelete: New page: ==Code calibrated== if the motor function is like this: case 1: shiftOut(serial_in, SRCK, LSBFIRST, B10000000); break; case 2: shiftOut(serial_in, SRCK, ...

2009-07-19T09:37:37Z

New page: ==Code calibrated== if the motor function is like this: </pre> case 1: shiftOut(serial_in, SRCK, LSBFIRST, B10000000); break; case 2: shiftOut(serial_in, SRCK, ...

New page

==Code calibrated==

if the motor function is like this:

</pre>
case 1:
shiftOut(serial_in, SRCK, LSBFIRST, B10000000);
break;
case 2:
shiftOut(serial_in, SRCK, LSBFIRST, B01000000);
break;
case 3:
shiftOut(serial_in, SRCK, LSBFIRST, B00100000);
break;
case 4:
shiftOut(serial_in, SRCK, LSBFIRST, B00010000);
break;
case 5:
shiftOut(serial_in, SRCK, LSBFIRST, B00001000);
break;
case 6:
shiftOut(serial_in, SRCK, LSBFIRST, B00000100);
break;
case 7:
shiftOut(serial_in, SRCK, LSBFIRST, B00000010);
break;
case 8:
shiftOut(serial_in, SRCK, LSBFIRST, B00000001);
</pre>

then the motors actually turn on in an order more like 2,1,4,3,6,5,8,7. So, here is how it should look:

</pre>
case 1:
shiftOut(serial_in, SRCK, LSBFIRST, B01000000);
break;
case 2:
shiftOut(serial_in, SRCK, LSBFIRST, B10000000);
break;
case 3:
shiftOut(serial_in, SRCK, LSBFIRST, B00010000);
break;
case 4:
shiftOut(serial_in, SRCK, LSBFIRST, B00100000);
break;
case 5:
shiftOut(serial_in, SRCK, LSBFIRST, B00000100);
break;
case 6:
shiftOut(serial_in, SRCK, LSBFIRST, B00001000);
break;
case 7:
shiftOut(serial_in, SRCK, LSBFIRST, B00000001);
break;
case 8:
shiftOut(serial_in, SRCK, LSBFIRST, B00000010);
break;
</pre>

Goofy, but changing code is easier than designing PCBs so it'll have to do!

==Motors not quite calibrated for my big ankle==

Is the veltex insert in my test Northpaw stock length? I hope it's arbitrarily shorter than all the ones we already cut; when stuffed inside the armature and lined with pager motors, it's a good half inch at least _too short_ and even with the last two motors at the very very edges, the gap between motor 1 and motor 8 is just way too big! Ack!

==Some messing around with the belt==

*First off, my attempt to rewire the LED board tester is totally FUBAR. Gah.
*Next, much time was wasted playing with the code before realizing the belt's motor array wiring is also totally FUBAR.
**The two power rails seem to be connected. (I must have thought I did a basic electrical test after first building the array, when clearly I never did until tonight...).
**This is most likely happening on the half of the array were one power rail is being cut and soldered to while the other rail is underneath it. Either the trimming of the insulation, or the soldering, or both, is creating enough of a connection to mess things up.
**It's not a perfect connection, as motors on one side run stronger than the other.
**Extensive multimeter funtime and tedious wire surgery will be needed.
***This failure bodes poorly for our current motor array assembly procedure in general.

[[Category:Sensebridge]]

Hack Notes CVA 090718 - Revision history

SpammerHellDontDelete at 09:38, 19 July 2009

SpammerHellDontDelete: New page: ==Code calibrated== if the motor function is like this: case 1: shiftOut(serial_in, SRCK, LSBFIRST, B10000000); break; case 2: shiftOut(serial_in, SRCK, ...