NeilP
1 GW
I have just finished ' writing/programming' a prog to punch in to my old casio FX7700 programable calculator.
You can enter either Spoke angle AND rim hole angular spacing, for those weird lacing patterns, or just enter whole number or decimal crosses.
By spoke angle I am referring to the angle between "big hand and small hand" from Rim end of spoke to centre of the hub to hub end of spoke, as in this picture stolen from the page also linked to
http://www.sheldonbrown.com/mismatch/

Also allows for dished wheels..calculates both side spoke lengths,
You can also enter a rim spoke hole offset for those rims where the spoke holes zigzag along the rim, left and right.
Has to be typed in by hand..I never had a data cable for mine,
but if any one has (or gets one of these) , then they are more than welcome to have this little 'program'
http://www.ebay.co.uk/sch/i.html?_kw=casio+calculator+fx+7700

"Spoke length"
"ERD"?→Z:Z>0⇒Z÷2→R
"RIM HOLE OFFSET"? →Q
"LH HUB DIA"? →Z:Z>0⇒Z÷2→D
"RH HUB DIA"? →Z:Z>0⇒Z÷2→G
"L FLNGE – CNT"? →Z:Z>0⇒Z-Q→I
"R FLNGE – CNT"? →Z:Z>0⇒Z-Q→J
"SPOKE HOLE DIA"? →Z:Z>0⇒Z÷2→O
"CROSS OR ANGLE"? →Z:Z>4⇒Goto1:Goto2
Lbl 1:Z→A:"RIM HOLE ANGULAR SPACING"? →Z:Z>0⇒Z→B:A÷2B→X:"CROSS=":X◄
Goto3
Lbl 2:Z→X:"NUMBER OF RIM HOLES"?→Z:Z>0⇒Z→H
(720÷H)X)→A:"SPOKEANGLE=":A◄
Lbl 3
((√(R2+D2+I2-(2RDcos A)))-O)→M
((√(R2+G2+J2-(2RGcos A)))-O)→N
"LEFT LENGTH=":M◄
"RIGHT LENGTH=":N◄
The formula lines, in Label 3 subsection, 4 lines.
from the end: R D I R, G Z & J. those are the "memory value Squared", not "memory value x 2"
For some reason the superscript "2" has not worked
When this program runs, after it displays the spoke lengths , it starts again at the beginning.
If you enter Zero for Any entry Except :
"RIM HOLE OFFSET"? →Q
"CROSS OR ANGLE"?
it remembers your last used entry. So if for instance you were calculating spoke lengths for the same motor, with different rims, you would enter the new ERD, then zero on each subsequent answer, except for the two above. need to think about changing that ..but since ou are the first person to try this in the year this post has been here, it is hardly a pressing issue.

You can enter either Spoke angle AND rim hole angular spacing, for those weird lacing patterns, or just enter whole number or decimal crosses.
By spoke angle I am referring to the angle between "big hand and small hand" from Rim end of spoke to centre of the hub to hub end of spoke, as in this picture stolen from the page also linked to
http://www.sheldonbrown.com/mismatch/

Also allows for dished wheels..calculates both side spoke lengths,
You can also enter a rim spoke hole offset for those rims where the spoke holes zigzag along the rim, left and right.
Has to be typed in by hand..I never had a data cable for mine,
but if any one has (or gets one of these) , then they are more than welcome to have this little 'program'
http://www.ebay.co.uk/sch/i.html?_kw=casio+calculator+fx+7700

"Spoke length"
"ERD"?→Z:Z>0⇒Z÷2→R
"RIM HOLE OFFSET"? →Q
"LH HUB DIA"? →Z:Z>0⇒Z÷2→D
"RH HUB DIA"? →Z:Z>0⇒Z÷2→G
"L FLNGE – CNT"? →Z:Z>0⇒Z-Q→I
"R FLNGE – CNT"? →Z:Z>0⇒Z-Q→J
"SPOKE HOLE DIA"? →Z:Z>0⇒Z÷2→O
"CROSS OR ANGLE"? →Z:Z>4⇒Goto1:Goto2
Lbl 1:Z→A:"RIM HOLE ANGULAR SPACING"? →Z:Z>0⇒Z→B:A÷2B→X:"CROSS=":X◄
Goto3
Lbl 2:Z→X:"NUMBER OF RIM HOLES"?→Z:Z>0⇒Z→H
Lbl 3
((√(R2+D2+I2-(2RDcos A)))-O)→M
((√(R2+G2+J2-(2RGcos A)))-O)→N
"LEFT LENGTH=":M◄
"RIGHT LENGTH=":N◄
The formula lines, in Label 3 subsection, 4 lines.
from the end: R D I R, G Z & J. those are the "memory value Squared", not "memory value x 2"
For some reason the superscript "2" has not worked
When this program runs, after it displays the spoke lengths , it starts again at the beginning.
If you enter Zero for Any entry Except :
"RIM HOLE OFFSET"? →Q
"CROSS OR ANGLE"?
it remembers your last used entry. So if for instance you were calculating spoke lengths for the same motor, with different rims, you would enter the new ERD, then zero on each subsequent answer, except for the two above. need to think about changing that ..but since ou are the first person to try this in the year this post has been here, it is hardly a pressing issue.
