Test Jigs, Test Sets and Prototyping

General Robotics Forum - All aspects of robots and their applications. 

Page 1 of 2       1 2 > last >> Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Test Jigs, Test Sets and Prototyping Too_Many_Tools 03-21-2007
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Too_Many_Tools on March 21, 2007, 5:37 pm
I would be interested in hearing what test jigs and test sets that you
have built and used in prototyping your robots.

Both electronic and mechanical efforts are of interest.

Pictures would be great.

Thanks for any contributions.

TMT


Posted by BobH on March 21, 2007, 8:25 pm
Too_Many_Tools wrote:
> I would be interested in hearing what test jigs and test sets that you
> have built and used in prototyping your robots.
>
> Both electronic and mechanical efforts are of interest.
>
> Pictures would be great.
>
> Thanks for any contributions.

I am building a motor controller for a large differential drive outdoor
rover type bot. In the interest of not breaking things in case of
firmware issues, I built a small vehicle with encoders on the motors
that weighs a few pounds. The cpu board is an eval board from the cpu
manufacturer. The drive board is another eval board for a dual H bridge.
When I get the firmware finished and solid, I will do the layout for the
motor controller with the CPU and full size power section. This approach
spreads out expenses and time requirements pretty well.

In addition to electronic and mechanical jigging, there is a script
driven tool to issue commands to the motor controller and capture
responses for debugging. This jig substitutes for the main host computer
that has not been developed yet.

I don't really have a good place to post pictures, sorry.

Bob



Posted by Too_Many_Tools on March 22, 2007, 12:24 am
wrote:
> Too_Many_Tools wrote:
> > I would be interested in hearing what test jigs and test sets that you
> > have built and used in prototyping your robots.
> > Both electronic and mechanical efforts are of interest.
> > Pictures would be great.
> > Thanks for any contributions.
> I am building a motor controller for a large differential drive outdoor
> rover type bot. In the interest of not breaking things in case of
> firmware issues, I built a small vehicle with encoders on the motors
> that weighs a few pounds. The cpu board is an eval board from the cpu
> manufacturer. The drive board is another eval board for a dual H bridge.
> When I get the firmware finished and solid, I will do the layout for the
> motor controller with the CPU and full size power section. This approach
> spreads out expenses and time requirements pretty well.
> In addition to electronic and mechanical jigging, there is a script
> driven tool to issue commands to the motor controller and capture
> responses for debugging. This jig substitutes for the main host computer
> that has not been developed yet.
> I don't really have a good place to post pictures, sorry.
> Bob

Thanks for the response Bob....it is what I am looking for.

Your approach sounds like a smart way to approach the prototyping
phase.

Is there anything you would redo if the opportunity allowed it?

TMT


Posted by BobH on March 22, 2007, 12:01 pm
Too_Many_Tools wrote:
> wrote:
>> Too_Many_Tools wrote:
>>> I would be interested in hearing what test jigs and test sets that you
>>> have built and used in prototyping your robots.
>>> Both electronic and mechanical efforts are of interest.
>>> Pictures would be great.
>>> Thanks for any contributions.
>> I am building a motor controller for a large differential drive outdoor
>> rover type bot. In the interest of not breaking things in case of
>> firmware issues, I built a small vehicle with encoders on the motors
>> that weighs a few pounds. The cpu board is an eval board from the cpu
>> manufacturer. The drive board is another eval board for a dual H bridge.
>> When I get the firmware finished and solid, I will do the layout for the
>> motor controller with the CPU and full size power section. This approach
>> spreads out expenses and time requirements pretty well.
>> In addition to electronic and mechanical jigging, there is a script
>> driven tool to issue commands to the motor controller and capture
>> responses for debugging. This jig substitutes for the main host computer
>> that has not been developed yet.
>> I don't really have a good place to post pictures, sorry.
>> Bob
>
> Thanks for the response Bob....it is what I am looking for.
>
> Your approach sounds like a smart way to approach the prototyping
> phase.
>
> Is there anything you would redo if the opportunity allowed it?

About the only thing I would do differently at this point is that I
would have bought an RF serial data link instead of building one.
Time is in pretty short supply for me and instead of just buying the
link for transferring command and telemetry, I opted to build one. To
borrow a line from an old song, a week went by and now it's July... and
I have not gotten back to the motor controller for too long.

Bob


Posted by Too_Many_Tools on March 24, 2007, 12:40 am
wrote:
> Too_Many_Tools wrote:
> > wrote:
> >> Too_Many_Tools wrote:
> >>> I would be interested in hearing what test jigs and test sets that you
> >>> have built and used in prototyping your robots.
> >>> Both electronic and mechanical efforts are of interest.
> >>> Pictures would be great.
> >>> Thanks for any contributions.
> >> I am building a motor controller for a large differential drive outdoor
> >> rover type bot. In the interest of not breaking things in case of
> >> firmware issues, I built a small vehicle with encoders on the motors
> >> that weighs a few pounds. The cpu board is an eval board from the cpu
> >> manufacturer. The drive board is another eval board for a dual H bridge.
> >> When I get the firmware finished and solid, I will do the layout for the
> >> motor controller with the CPU and full size power section. This approach
> >> spreads out expenses and time requirements pretty well.
> >> In addition to electronic and mechanical jigging, there is a script
> >> driven tool to issue commands to the motor controller and capture
> >> responses for debugging. This jig substitutes for the main host computer
> >> that has not been developed yet.
> >> I don't really have a good place to post pictures, sorry.
> >> Bob
> > Thanks for the response Bob....it is what I am looking for.
> > Your approach sounds like a smart way to approach the prototyping
> > phase.
> > Is there anything you would redo if the opportunity allowed it?
> About the only thing I would do differently at this point is that I
> would have bought an RF serial data link instead of building one.
> Time is in pretty short supply for me and instead of just buying the
> link for transferring command and telemetry, I opted to build one. To
> borrow a line from an old song, a week went by and now it's July... and
> I have not gotten back to the motor controller for too long.
> Bob- Hide quoted text -
> - Show quoted text -

Thanks Bob...I appreciate the advice.

Hmmm....no other posts.

Guess no one else is building robots. :<)

TMT


Page 1 of 2       1 2 > last >>

The site map in XML format XML site map
other useful resources:
Official Robosapien Website
Lego Mindstorms Website

Contact Us | Privacy Policy