-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem when running 110-waypoints example code #162
Comments
Hi @WHuangEI, It looks like the Regards, |
Thank you for your reply and answer. I downloaded the whole file and configured the robot around December 2022. The version is supposed to be > = 2.3.0. It confuses me and how can I check the API version I 'm using now and update it without damage to the other documents if my version < 2.3.0 |
And I thought After installing the whl file, I was able to run some example codes as instructed by readme.md, but there was nothing about installing SWU, and it seems that I did not download the install SWU file anymore. |
I entered the Kinova Web Application, and found that the Web App Version is 2.8.0-r.33, Web Client API Version is 2.2.0-r.27, Firmware Bundle is 2.2.0-r.51, and Armbase 2.2.0-r.58, all Actuators 2.2.0-15, and Vision is 2.2.0-r.22. Can i just press the 'upload' the 'Gen3-2.4.0.swu' file just downloaded today to upgrade my arm? is that a solution? |
I tried that and new errors occurred like this: |
So you did the right thing. Now, for the database error, this is probably because you have an older arm and the format of an "Action" changed. A Factory Reset will fix the issue, but you will lose all your protection zones and your saved Actions |
Sorry, I clicked the wrong button I can refer you to #100, which was the same issue Just be carefull when doing a actory reset. It will wipe all your configurations, your protection zones, your actions ... |
Thank you so much,I did it according to your guidance, and the problem was solved ! |
I would suggest to use the Low Level servoing mode instead of high level functions. This will allow you to control each actuator directly without interracting the with the base. You will have faster reponse time (low level works at 1000Hz compared to 40Hz) and will be able to send velocity/torque/position and/or current commands to each actuator individually. You will lose some high level data that the base computes, but I do not think you will need this data anyway. Low level also requires you to send a command each ms to the arm, so C++ is (almost) mandatory Here are two examples that might be usefull to get you going : Hope this helps |
Thank you very much, I will try your advice later and I will close this issue then. |
I will be closing this issue due to the original question being answered and the rest of the thread being inactive. |
Description
when running 110-waypoints example code, some errors occurred,how can I solve this ?
~/gen3_ws/src/kortex/api_python/examples/110-Waypoints$ python3 02-send_cartesian_waypoint_trajectory.py
Logging as admin on device 192.168.1.10
Moving the arm to a safe position
EVENT : ACTION_START
EVENT : ACTION_END
Safe position reached
Traceback (most recent call last):
File "02-send_cartesian_waypoint_trajectory.py", line 209, in
exit(main())
File "02-send_cartesian_waypoint_trajectory.py", line 204, in main
success &= example_trajectory(base, base_cyclic)
File "02-send_cartesian_waypoint_trajectory.py", line 140, in example_trajectory
result = base.ValidateWaypointList(waypoints)
File "/home/hwww/.local/lib/python3.6/site-packages/kortex_api/autogen/client_stubs/BaseClientRpc.py", line 2156, in ValidateWaypointList
result = future.result(options.getTimeoutInSecond())
File "/usr/lib/python3.6/concurrent/futures/_base.py", line 432, in result
return self.__get_result()
File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
raise self._exception
kortex_api.Exceptions.KServerException.KServerException: Server error name=ERROR_PROTOCOL_SERVER, sub name=UNSUPPORTED_METHOD => Error details were not received from server.
Version
At a minimum, provide the Kortex API and Kortex-enabled device versions.
KortexAPI :
Kortex Device :
Steps to reproduce
Code example
Expected behavior
Describe the expected behavior (in regard to the bug described above).
Any other information
Any other information you believe the developers need to know.
The text was updated successfully, but these errors were encountered: