I have printet the plade called "Wishbone_Plate.A.2.stl" and as you can see in my

I have printet the plade called “Wishbone_Plate.A.2.stl” and as you can see in my early posts they dont fit to the Reely dogbones :frowning:
Is see the downloaded files as a big confusion between a lot a versions and WHO know what parts fits to witch versions. In the file (mess) I find files called “Wishbone Test Front.A.2.stl” and “Wishbone Test Rear.A.2.stl”, they are 4mm shorter??
What file should I print to do this right?? Yes I need them to be shorter but is the “test wishbones” the right ones then??

I don’t have a 3D printer, yet. But it looks like others have printed the shorter one, so i would try to print the shorter test ones :).

I’m printing it right now :slight_smile:

It is confusing and would be better if there were more than one entry each with just one set of parts and the variants as remixes.

You probably want to print the ‘B.0’ variants, which are supposed to be sturdier. They are the same size as the ‘A.2’. The currently available CAD file (B.3) for the truggy uses the ‘A.2’ variants.

I’m trying to keep track of those details for my own build here : https://github.com/rdolbeau/OpenRC/, see under “Truggy/Components/Suspension”.

Ok. Thanks for your comment Romain. It looks like the “test” version i found fits perfect. So I am back on track :wink:

I realize I was unclear (and maybe even misleading) : the ‘A.2’ versions I’m talking about are the ‘Test’ you found, not the ‘Plate’ you originally printed. So printing the ‘Test’ is OK (… as I understand it :-).

The ‘Plate’ A.2 was uploaded to Thingiverse in January of 2013, whereas the ‘Test’ A.2 are in the zip file “STL_Files_For_OpenRC_Truggy_Rev_B.3.zip” uploaded in May of 2013 (there’s also an update from August, unrelated to the wishbones). I can’t find where Daniel originally posted the ‘B.0’ variants, but IIRC somewhere in this group.

Thanks for your effort Romain. It would be really nice if all early versions of files was removed. A zip files with all the latest files that fit together is really what I (and maybe others) need.

@Jan_Germann it´s on my todolist…

I’m founder of a new form of technological review, that is the review of Technology with responsibility of assimilation into the human life in mind.We are a non profit organization centered on public advocacy with the purpose of new policy development.http://www.ResponsibleAssimilation.org is in its infancy ,meaning right now is the best time for reviewers to jump on board this inevitably historical movement . One of the things you might help with if interested is, helping us in advocating for a “drone operators license” of some kind. Such things are better dictated by the users during development, responsibly. Rather than the public demand the government do it in a blinding state of hindsighted haste after lives are lost . I firmly believe that if the users and developers of the unmanned vehicle community come together they could self-govern what is rapidly becoming a potentially dangerous air traffic environment for passenger commuting flight . You MUST do this yourselves, responsibly before tragedy not after! Im interested in your thoughts. best regards, Jason Eyer

ResponsibleAssimilation@gmail.com

So am I correct in assuming that if I print the newest revision number of each part in the original Git repo they will all fit together properly?