Definition and access to an Hexapod ID

[PierreRoyer]

It would be handy that the HexapodProxys and HexapodSimulators are defined with the concept of an identifier, that can be set at instantiation, and queried at any moment. The identifier can be a simple integer 1, 2, ... or any other concept.
This would be an easy way to handle collections of reference frames transparently over multiple hexapods without hardcoding names of reference frames or duplicating code.
[I'm of course open to discussion on alternative concepts]

[rhuygen]

@PierreRoyer we will need to discuss this in more detail since the Hexapods have already an identifier which is used to start the Controller at the control server level. That identifier is used to make sure the intended hexapod is addressed in the commanding, when multiple hexapods co-exist. I guess you are talking about a completely different type of identifier.

[rhuygen]

Se also #377.

[PierreRoyer]

My goal is to compare coordinates in Hexapod HW object and RF Model object.
Therefore I need to query both, but the names of the RF differ for the 2 hexapods, therefore I need a way to differentiate them from the hexapod object (or hexapodSimulator object). The proposal is to provide .set_id() and .get_id() methods on the control servers and on the siumulators

def is_model_sync(model, hexhw, verbose=None, rounding=4, atol=0.0001, rtol=0.0001):
    coohex = hexhw.get_user_positions()
    hexid = hexhw.get_id()
    usr_string = f"hex{hexid}usr" # "hex1usr, hex2usr
    obj_string = f"hex{hexid}obj" # "hex1obj, hex2obj
    cootr, coorot = model.get_frame(usr_string).get_active_translation_rotation_vectors_to(model.get_frame('obj_string'))
    # previously : coomodtr, coomodrot = model.get_frame('hexusr').get_active_translation_rotation_vectors_to(model.get_frame('hexobj'))

[rhuygen]

This should be fixed in #379 and #380 (also in release v0.23.0).
Use the property device_id on the Proxy, hexhw in the above case.