SmartArmMaster Window v23.09.07_144551

This is the last version that can be attributed to my role at UTokyo.

Manual comments:

Re-added delay to Protocol v3.

v23.06.06_120600

Latest automated release.

Manual comments:

Updated submodules.

• dqrobotics@77acf9a42
• cpp-interface-vrep@bd2f2cc9fd

v22.12.22_145109

Latest automated release.

Manual comments:

• Updated dqrobotics and cpp-vrep-interface.

v22.08.04_160257

Latest automated release.

Manual comments:

• Fixed VREP support when a single interface is used.
• Improved error reporting when the VREP mode is on. It should no longer crash when an object in the scene does not exist.
• Fixed motion scaling being allowed to be zero, which caused the program to crash.
• Added a configurable parameter coppelia_sim_automatic_simulation_control that can be true to automatically start/stop the VREP simulation. Set it to false to prevent this behavior.

v22.06.20_142231

Latest automated release.

Manual comments:

• Reintroduced force feedback support, now working in Protocol 3 and Protocol 2.
• Removed unused parameters from the configuration.json
• Made the configuration.json parameters all be unified and written in lowercase with _.
• (07/14) Added the WITH_CONTEC builds for those using CONTEC boards to read potentiometers.

v22.06.03_103633

Automated release on 22.06.03_103633.

Manual comments:

• Added Protocol 3, which allows for any number of additional keyboard key states to be tracked by the program. Those must be configured in the configuration.json in the installation folder.
• From Protocol 3, the version of the protocol is part of the message. The patient side program will be able to discern among versions more easily with that, but recent versions can already check if Protocol 2 or 3 are being sent automatically.
• The keys to be tracked must be specified using Virtual-Key Codes. Remember to convert the HEX values into decimals for the configuration.json.
• With these, any number of keyboard-emulation pedal keys can be tracked by the program.
• Protocols 2 and 1 are unchanged and should still work, as long as they are specified in the configuration.json.

v22.05.16-143215

Latest automated release.

v22.05.16-141303

Latest automated release.