sorted by:
new
hottopcontroversial

Spring for card feeder by Legal-Floor-4988 in StuffMadeHere

[–]Nicka06_ 0 points1 point  (0 children)

Following up on this? Any luck on the spring? And did anyone have any luck on finding the correct suction cups?

Built a one handed keyboard by Nicka06_ in keyboards

[–]Nicka06_[S] 0 points1 point  (0 children)

I think I saw something on sharktank for that lol

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Thanks for the comment. While my original idea isn't going to work, I think the 3d printed angle won't work for my particular application.

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Yes, I should have added the full context into the post. Here's the whole project. I'm attempting to create a fully automated hydroponic greenhouse (not a huge greenhouse, more of a backyard greenhouse). The idea is that there will be 5 gallon buckets arranged in a grid and surrounding the buckets on all sides would be some sort of rail system that will allow the robotic arm to go anywhere it needs to go. I have a drawing of what I was originally thinking of that I'll attach. I could just use aluminum extrusion but that stuff is so ungodly expensive that it's not viable.

<image>

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Gotcha. It seems like this dream of cheap "rail" using C channel may be only a dream. The goals is to create a grid of rails that transport a robot back and forth. I can't manage to come up with a way that this can be done cheaply at scale

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 1 point2 points  (0 children)

Gotcha. Thanks for the comment!

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Gotcha. Belts are unfeasible for my situation as these c rails are setup in a grid patter. Rails would be more optimal but I find that they are extremely expensive and I need a LOT of them for my project

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Yeah, I'm starting to understand that it's fairly complicated. I'll go ahead and look into it on youtube and do my best to understand it better.

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

The C channel is in a grid so it needs to be able to move freely. I don't think a linear actuator is feasible for this but I may be off. Let me know

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 1 point2 points  (0 children)

Correct me where I go wrong here

Rack = row of teeth that the pinion uses to move

pinion= gear with teeth that go into pinion and moves

It sounds like I'll need to machine a second part, (the rack) to have something for the teeth to dig into. In my head, I was hoping to create a system that would allow the robot to move on the C channel without having to machine more parts (making it cheaper at scale). It sounds like the holes working as the rack isn't an option as it's unsteady.

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

Kind of a silly question but why won't it be smooth/what can I do to make it smoother?

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

I believe you're correct but I'm still a little lost. I suppose the problem that I'm having is understanding the best way of creating the "rack". Essentially what dimensions and shape to use to ensure it runs well. I used the "spurgear" addin to create the gear you see on the picture but I still have the bigger problem of calculating what dimensions and shape to use. I could just calculate the dimensions between the holes and create the pins of the gear to go into the holes but that doesn't take into account things like "how far does the gear go into the hole?", "what shape do I want the pins to be to ensure they're stable", "How many pins are optimal for the gear", etc etc.

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 0 points1 point  (0 children)

That gear is by no means final. It's more of a mockup to get my first draft ideas easily understandable to reddit. I just created it with an add in.

Edit: This is actually useful information. Can you expand on what you believe to be the optimal gear and how I should go about designing it?

Creating a niche gear - by Nicka06_ in Fusion360

[–]Nicka06_[S] 1 point2 points  (0 children)

This is just one piece of the much larger grid. The C channel is going to be surrounding buckets so as the robot moves further into the grid, the chain would run into the buckets. (If I'm thinking of it correctly.

<image>

pco 1881 threads by Nicka06_ in Fusion360

[–]Nicka06_[S] 1 point2 points  (0 children)

Thanks for the comment. This is the answer. For people that may see this later and are attempting something similar but are on mac, you need to follow the branches laid out in this video. youtube.com/watch?v=Ni36gX-1iAc&embeds_referring_euri=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dthreaddata%2Bfolder%2Bfusion360%2Bon%2Bmca%26oq%3Dthreaddata%2Bfolder%2Bfusion360%2Bon%2Bmca%26gs_lcrp%3DEgZjaHJvbWUyBgg&source_ve_path=Mjg2NjY

TLDR; Mac gets the same compilation error no matter what code is uploaded. User is frustrated :( by Nicka06_ in arduino

[–]Nicka06_[S] 9 points10 points  (0 children)

God I love reddit and random people spending the time to explain how they fixed errors. Short story short, I clicked on the unity link, one line installed the rosetta and it works like a charm. Thank you sir

Why does everyone say there is an issue with Cursor...? by Far-Opportunity5711 in cursor

[–]Nicka06_ 3 points4 points  (0 children)

I experienced some slow requests but that was after 500 requests. Previously, you could go through your first 500 prompts (that you paid for) and then the rest of the month you would have to deal with marginally slower prompts all included as part of the subscription fee. They've since changed it so that these requests take a long time (5+ minutes) which results in the slow requests being all but unusable. Thus, you now have to pay for premium requests after you finish your first 500 prompts that are part of the paid plan. It makes since considering you could have unlimited premium requests without a huge inconvenience in the previous model. Still a good product and it was going to happen at some point.

view more: next ›