Drew 

I'm 98% sure that the bolt on the Nitto 32F is M6 x 1.0mm, which is 
standard for virtually all M6 threads on bicycles, including cantilever 
bosses, the larger rack bosses on some Rivs, seat bolts on Rivs, lots of 
other things...

Now, if you have a threaded M6 x 1.0mm hole in the front face of your fork 
crown, then in principle you could thread that rack bolt into that hole.  
At the moment you get it started, the rack will be out in front of the fork 
about 1-1/2" too far out in front.  As you thread it in the rack will get 
closer to the fork.  When the existing threads run out the rack will still 
be sitting about an inch too far forward.  Then what?  Will you just bend 
everything as much as you need to bend things to get the rack legs to reach 
the fork?  I think you would end up with something really badly bent and 
contorted, won't be anywhere close to level, will have the tombstone way 
farther away from the fork as ideal, and won't be 'tight' threaded in that 
hole.  You could handle the 'tightness' problem by backing out the rack a 
few turns and leaving room for a locknut.  That would solve one of three 
problems and make the other two worse.

Alternatively you could maybe get into the thread cutting game and try to 
thread the rack bolt much further down its length.  

Bill Lindsay
El Cerrito, CA

On Monday, May 3, 2021 at 2:11:01 PM UTC-7 Drw wrote:

> Can someone confirm the size/threading of the bolt that goes into the fork 
> crown on the nitto 32f? 
>
> I have a fork with a hole tapped for M6 on the front end, but no hole on 
> the back, so I'd need to thread it directly into that hole
>
> Thanks,
> Drew
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/4573987a-4cb0-448a-bc0d-55cc774de83an%40googlegroups.com.

Reply via email to