https://www.youtube.com/watch?v=-7xvqQeoA8c
these is the best (definitely better than HONDA Asimo) It's a shame
that google has sold boston dynamics hope for better robot project
(maybe a robot D-wave driven over QUIC or better wifi bus ???.. )
bkt
2017-06-15 23:34 GMT+02:00
good ... about axis number is for 2 arm robot ... not planning to
partecipate to darpa race (for these year ;)) ... the pose number is more
hight then world axis ... and actual axis number in g code, for 2 arm robot
(18 axis) I think is quite good, because most part of work is on pose flag
not in
You are right. It takes 12 numbers to specify the location the orientation
of two arms. But in a typical robot there will be more than 12 axis. If
you look at the stat of the art, there could be 100+ axis, see below.
With a typical robot the number of axis may not equal the number of degrees
On Thu, 2017-06-15 at 09:36 -0700, Chris Albertson wrote:
> On Thu, Jun 15, 2017 at 2:07 AM, andy pugh wrote:
> > On 15 June 2017 at 08:08, theman whosoldtheworld
> > wrote:
> >
> >> there are some possibility that the max joint/axis number become more
On 15 June 2017 at 17:36, Chris Albertson wrote:
> It depends on one's approach to a multi arm/leg robot.You can
> treat it as two 6 DOF arms or
> as one 12 DOF assembly.
>
I can certainly imagine a 2-arm robot using XYZ and UVW to position two
arms. Though then
On Thu, Jun 15, 2017 at 2:07 AM, andy pugh wrote:
> On 15 June 2017 at 08:08, theman whosoldtheworld
> wrote:
>
>> there are some possibility that the max joint/axis number become more than
>> 0-8 in future?
>>
>
> It might well increase in the release,
On 06/15/2017 03:41 PM, Bertho Stultiens wrote:
> On 06/15/2017 03:02 PM, andy pugh wrote:
>>> G00 1X1. 2X1.0200 3X14.950 4X10.9530...
>>> something in this fashion comes to mind first
>>> there may not be a YZABCIJK representation - just 1X through 15X
>> That doesn't work with a conventional
On 06/15/2017 03:02 PM, andy pugh wrote:
>> G00 1X1. 2X1.0200 3X14.950 4X10.9530...
>> something in this fashion comes to mind first
>> there may not be a YZABCIJK representation - just 1X through 15X
>
> That doesn't work with a conventional G-code interpreter because spaces are
> ignored.
>
On 15 June 2017 at 13:53, Stuart Stevenson wrote:
>
> G00 1X1. 2X1.0200 3X14.950 4X10.9530...
>
> something in this fashion comes to mind first
>
> there may not be a YZABCIJK representation - just 1X through 15X
That doesn't work with a conventional G-code interpreter
On 15 June 2017 at 13:46, Stuart Stevenson wrote:
> G Code is just a symbolic way to represent something in a human readable
> manner.
>
Indeed, and if we had a STEP_NC interpreter then perhaps we would need to
also consider adding to the number of axes.
--
atp
"A
one fifteen axis whatever(machine?)
G00 1X1. 2X1.0200 3X14.950 4X10.9530...
something in this fashion comes to mind first
there may not be a YZABCIJK representation - just 1X through 15X
For the human : big labels on each axis or 3D glasses to see the labels
projected. At some point the
G Code is just a symbolic way to represent something in a human readable
manner.
Another method could be used and would seem difficult for the humans to
comprehend.
On Thu, Jun 15, 2017 at 4:07 AM, andy pugh wrote:
> On 15 June 2017 at 08:08, theman whosoldtheworld
On 15 June 2017 at 08:08, theman whosoldtheworld
wrote:
> there are some possibility that the max joint/axis number become more than
> 0-8 in future?
>
It might well increase in the release, but I am not sure how many machines
need coordinated movement in more than 9
there are some possibility that the max joint/axis number become more than
0-8 in future?
(0-17 / 0-26 )
Actually if I well undertand is possible use makinekit fork with multiple
machinekit instance on same pc ... so same pc more than 0-8 joint ... but I
investigate other possbility.
bkt
14 matches
Mail list logo