move-joints.py Hip yaw pitch

[foxcub99]

Currently only an option for LHipYawPitch and no option for RHipYawPitch meaning it cannot be changed. Needs to be changed to just HipYawPitch since they are linked and can only move together and should also move the right hipyawpitch at the same time.

[n33r4j]

should also move the right hipyawpitch at the same time.

You mean they're not moving together when you move the slider? Seems to be working for me. Are you having any lag/performance issues?

Needs to be changed to just HipYawPitch since they are linked and can only move together

Yep, you're right that they're linked but the name LHYP is maintained for convention, since that's how it is in the docs (both from Aldebaran and rUNSWift). HYP might be ambiguous, but I see where you're coming from. Also, I think it was the LHYP that was the dominant one (since it is powered while RHYP wasn't?).

[foxcub99]

Yeah getting quite a bit of lag, also not sure how to rotate the view

Screen.Recording.2024-03-22.at.12.29.37.pm.mov

[pzrq]

@n33r4j Could you please check your Aldebaran link? It doesn't seem to be working for me.

P.S. Absent other sources (perhaps it's hard-coded in C or otherwise at some low level?), I'd suggest going with Softbank's v2.8 HipYawPitch. Older Nao versions, e.g. for v2.0.6.8 surely aren't relevant to the Nao v6? If they are, it'd be good to know why, thanks.

[n33r4j]

Could you please check your Aldebaran link? It doesn't seem to be working for me.

Just updated, sorry.(I left a leading exclamation mark)

I've linked to the same source, just a different page. To quote them,

LHipYawPitch and RHipYawPitch are physically just one motor so they cannot be controlled independently. In case of conflicting orders, LHipYawPitch always takes the priority.

• source

It's pretty much LHYP everywhere else as well rUNSWift, qibullet, etc.