I'm trying to build a release for a linear actuator to suddenly fire a weight in one direction. I have a motor attached to a long screw thread to move the weight slowly in one direction. The weight is attached to a spring and so builds up tension as it moves. Does anyone know of a sort of automated "half-nut" arrangement or similar that will spring apart allowing the weight to fly back without having to engage with the thread?
I was wondering what materials I should use to build the chassis of the arm. I don't have any metal or woodworking tools.
« Last post by ocservo on July 02, 2015, 09:47:24 PM »
ROBS-301 is a kind of robot servo, it can hold any position between 0 to 360 degree, bus connection. Compatible with 3 control modes（PWM, LSS, OCS）, it can also rotate continuously.
Want to learn more about our ROBS series servos just click the link here Http://www.oc-servo.com/.
« Last post by mklrobo on July 02, 2015, 02:38:39 PM »
I am sorry for your loss, time and money. If your production (of whatever you are making) was
lost, your clients will not be happy either. No happy ending here, at all.
In the factory I worked in, we had a parts department that kept 3 vendors on any part that we
used. This was quite a feat, logistics
wise, and was a big headache.
However, the factory
kept running smoothly, so hats off to our parts department. Just in time
manufacturing can be quite costly, in time and money. Trust
is a major factor, as presented by your experience. It may be to your advantage to keep more than one vendor on
a list, that would stop the experience from losing money that could damage the production.(client rep)
The endeavor would be a pain and time consuming; since this event you had, might be a singular
experience, it might not be a good investment in labor(?). Good Luck!!!
« Last post by unix_geek on June 30, 2015, 02:44:59 AM »
Kudos on an advertisement that is actually useful! I've been trying to come up with a linear motion solution using the reprap GT2 belt/pulley set but this solution is way better. Especially impressed by the power it has.
« Last post by Andrew D on June 29, 2015, 07:46:49 PM »
Thank you but didn't get the motors. In this case money was not an object anyway. The motors had to be on time to meet our deadline.
Robotshop replied today that they had a national holiday the day after the order was placed.
Poor excuse because prior placing an order I called them a was assured the parts would ship next day after ordering them.
What's more - they were shipping from their warehouse in Vermont. There was no national holiday in Vermont on June 24th... only in Quebec. Someone in Quebec did not pass the order to Vermont.
Anyhow... Robotshop retracted the shipment after I complained (without consulting with me he he he
. That just shows how professional they are. I'll get a refund but that's nothing - I lost thousands because of their negligence. Not to mention time and aggravation. Got motors on Saturday from Amazon.
That was my last order from that place.
« Last post by anvoice on June 29, 2015, 05:36:10 PM »
Hi, and thanks for the response.
I do hope that I'm in constant improvement mode, the downside being that I'm not yet knowledgeable enough to even know which resources are available. For instance, I learned of ROS (robot operating system) after I made this post, and clearly that's not running on an arduino. On the other hand, starting with the arduino board will let me start learning more right now, while I still don't have the programming/technical skills to utilize a more advanced system.
My guess at this point is that I'll start with the arduino board despite possible limitations, and push it as far as it will go. Fortunately, I have a 3d printer, so I can make prototypes rather quickly and inexpensively (e.g. I designed, printed and constructed the body of the robot within a couple of days), that's a big plus.
Since eventually I want autonomous operation of the robot, possibly running ROS, wireless transmission of sensor/video data, etc, there is no doubt that I'll be getting a more powerful system, probably starting with a raspberry pi 2, in the near future. I just wanted to hear some expert opinions on whether some of my simpler goals are feasible on the arduino board, since I will have to rebuild the robot partially if I'm to swap out platforms and I'd rather not do it from the start.
Hopefully I'll be able to get a head start with the current setup, and advance from there. I'm always open to suggestions and hearing new advice.
« Last post by mklrobo on June 29, 2015, 03:15:34 PM »
Based on where you are, and where you seem to be going, I would recommend shooting for
the best of both worlds. Cost a little more, but the trajectory
will sustain your endeavors.
You seem to be in constant improvement mode, advancing your techniques, which, in turn,
demand more techno-equipment. This is the same dilemma I have found myself in, and so,
I bought a Raspberry Pi 2 and an Axon II. (I also have a Parallax propeller) The Pi is the brains of
the outfit, while the Axon will handle the immediate concerns. Both have potential in starting out,
as well as using them as tools to learn ARM architecture, to advance to other projects. Since I
am not as rich as Bruce Wayne, (Batman), I will have to reuse what I have to combat my
ignorance. An advantage you might consider is a forum(this one
) in which someone else is working
on a similar goal, which may eliminate time wasted, and continue at a comfortable pace which
allows you to enjoy the building of your projects.
« Last post by mklrobo on June 29, 2015, 06:31:49 AM »
Hello!Your description and problem:
1>I have palletizing. I want that creator create my detail. Than conveyor move my detail to vertical sensor. Than sensor stopped conveyor. Robot take detail and put it on palette. Creator create my detail again...
I find some information about communication between robot and conveyor components.
2>How does vertical sensor work? I want to stop the conveyor. Why "Wait input" does not work?
#1 - You would like the software simulator to simulate a conveyor that stops/starts on programmed command, then your robot takes the work off of the conveyor and puts on palette, correct?
#2 a> vertical sensor of the robot? b> stop conveyor - wait input contributes to control of conveyor.
If this is correct, then I would recommend this, for your work;
Since I am not familiar with your KUKA software, I will confine my response to a logical PLC format;
If the conveyor is short, and used only for this purpose (section) you could integrate the actions together
in one PLC (Programmable Logic Controller) I will suggest using Hall effect sensors to sense the works
emplacement. When the work passes a determined point, the hall effect sensor sends a "1", or "hot"
signal to the PLC. The PLC then makes a decision to pick up the work, with the robot. A few motors are
needed, so a simple PLC will suffice. I would recommend using the Axon as your PLC. You have a lot of
features in the Axon. I have just learned how to make a Hex file; and it seems that, one of my first
programs should be, to use the Axon like a PLC. If you decide to pursue this, I have included
a lot of info on my post in the misc section of this forum; Analyzing the Axon : Coding, Construction, and
I will check out your software, because you got me curious of its potential. Good Luck!!
« Last post by Rushmoore on June 29, 2015, 01:48:47 AM »
Thanks so much man! This helped so much!