Ok, the HEBI C++ API v3.3.0 should now be available in NuGet. Note there are a couple backwards-incompatible changes from v1.0.0 (the last NuGet version) and v3.x. These are: - timestamps, and sender ID moved from hebi::Feedback.actuator() to hebi::Feedback - the robot model parsing and API has chan...

I just got the NuGet package build working. I'm doing some final tests here, but I should be pushing this in the next hour.

Thanks again for your patience! I'll go ahead and update our release scripts so this is built and updated for future releases as well.

Apologies for the delay. Yes, CMake can be used to generate Visual Studio projects. I updated the instructions at https://github.com/HebiRobotics/hebi-cpp-examples; please let me know if this makes sense and you are able to build these at least. However, I know that doesn't fully solve the NuGet iss...

Thanks for pointing this out. Currently, this is only viewable via the MATLAB API; however, we will update the C API with this feedback this week, and should have C++ API support next week.

Sorry for the issue!

Best,
Matt

Sorry for the issues here. You are correct, the NuGet packages are quite outdated; we had been primarily focused on the CMake workflow and let these slip because of a complication with a library reference. I'll try to get this sorted out and get new versions out this week. I'll keep you posted on th...

Thanks for writing, and for the initial diagnosis. If I understand correctly, Scope successfully fins the modules when run on the same computer as the script fails on, correct? Here are a couple questions/ideas to hopefully get this tracked down: System: - In Scope, are you sure all 18 modules are p...

Whoops -- missed your last question there. You can combine the actuators into one group, but still index into the commands to send individual values for commands. However, when you call "send command", messages are sent to all actuators in the group with their respective commands; you cannot just se...

Rasmus, Sorry for the late reply. Thanks for sharing the code snippets -- I can point out a few things here that should help and may address the problem. I don't see any velocity commands, though. If you are able to share a full file, I can provide more complete feedback; alternatively, I would be h...

Rasmus, Thanks for reaching out. My guess here is that you are using a CommandStruct/GroupCommand which still has position commands in it. The solution here is either to clear the position command from the CommandStruct/GroupCommand, or to use a new CommandStruct/GroupCommand object. If you let me k...

Rasmus, When commanding a position, this is telling the actuator to try to move to this position instantaneously. While you can use velocity limits to try to address the issue, this isn't really what they are designed for. Instead, we recommend you plan a smooth trajectory to the destination positio...