Robot Arm Element - Adds robot arm to storyboard.

[yepher]

Adds robot arm

[yepher]

I'm not exactly sure how to handle the frame since the robot arm has a fairly wide range of movement.

Is there a way to define the "marching ants" frame independent of the robot arm frame?

[urish]

Amazing!

Added some comments / questions.

Also, what is the valid range of angles for each joint? Can we clamp the input angles to make sure we never draw an invalid configuration? (We already have utils/clamp.ts with a simple clamp() function)

Regarding the bounding box - is it currently bit enough to contain the entire valid range of movement?

[urish]

why?

[yepher]

When I let VS code format the SVG it becomes un-readable and I hate the warnings. But if you really want it to wrap all those lines I can remove it.

[urish]

Yes, prettier SVG formatting isn't that great.

But when the choice is between not-so-pleasing but consistent SVG formatting or getting the indentation wrong by the next developer who works on this code, I prefer the former.

Also, prettier should automatically format the code whenever you commit anyway. Didn't it?

[urish]

We also need GND/VCC pins (they are not currently used in the simulation, but we do want the schematic to look as close as possible to reality)

[yepher]

ok, will add the two pins. I was cheating since I knew they had no function.

[urish]

extracting the different values from this will probably make the code a bit tidies. i.e. at the start of the function:

const {elbowAngle, wristAngle, ...} = this;

Then you can use the variables directly, without repeating this. every time

[yepher]

The more I modify SVG the harder it is to update the SVG if I want to add/remove stuff from it. When it become invalid SVG it is a lot harder to update

[urish]

How about wokwi-robotic-arm? Not being a native English speaker, I'm not sure if there's an actual difference, so I'd love to hear the thoughts of someone whose a native English speaker.

[yepher]

Works for me

[urish]

Also:

1. Let's use a slider for the angle controls and a color picker for the colors in storybook?
   See the wokwi-rgb-led story for an example for both

2. Is there a reason you went with yellow as the default color for the robotic arm?

[yepher]

I guess I accidently delete this somewhere along the way. I will add it back in:

argTypes: {
    sholderAngle: { control: { type: 'number', min: 260, max: 360, step: 1 } },
    elbowAngle: { control: { type: 'number', min: 0, max: 135, step: 1 } },
    wristAngle: { control: { type: 'number', min: 0, max: 120, step: 1 } },
    gripperAngle: { control: { type: 'number', min: 270, max: 360, step: 1 } },
    gripperColor: { control: { type: 'color' } },
    armColor: { control: { type: 'color' } },
    jointColor: { control: { type: 'color' } },
  },
  args: {
    sholderAngle: 270,
    elbowAngle: 82,
    wristAngle: 80,
    gripperAngle: 270,
  },

As for yellow, I figured a big heavy dangerous piece of equipment like this robotic arm should be yellow :) Actually I just randomly picked yellow.

[urish]

I guess I accidently delete this somewhere along the way. I will add it back in:

"range" type seems more convenient than "number" for the angles (at least for me)

As for yellow, I figured a big heavy dangerous piece of equipment like this robotic arm should be yellow :)

haha :) google images show that it's either metallic or black combined with either blue, yellow, light gray, or orange (or sometimes just plain black).

So I guess yellow isn't a bad choice. I thought either metallic or purple could be fun (it's the dominant color in Wokwi), though I've no strong opinion here. Yellow is good too.

[yepher]

I was not quite sure how to apply the clamp function since this is an output device.