You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone,
I am trying to use onshape-to-robot api to generate urdf file. I have my own onshape workspace and exported the access_key and secret_key in the environment.
Create a folder named abc_assembly and it have the config.json file.
But when I try to create the urdf using the following command onshape-to-robot abc_assembly
After adding some parts in the tree,the following Resource not found error comes up every time for a particular part.
! ERROR (403) while using OnShape API
! {
"moreInfoUrl":"",
"message":"Resource does not exist, or you do not have permission to access it.",
"status": 403,
"code": 0
}
I consider all the possibilities of failure.
Sync the system time with universal time
Access key and Secret key is successful imported in the environment
Have my own copy of the onshape workspace
Don't know what's going wrong.Because it is successfully generating urdf for the other onshape document.
Something I noticed that on Resource does not exist the documentId is different from the what actually in the config.json file. So, My guess is that it is causing the failure of the urdf generation. But didn't know why it's showing this behaviour.
The text was updated successfully, but these errors were encountered:
Hi everyone,
I am trying to use onshape-to-robot api to generate urdf file. I have my own onshape workspace and exported the access_key and secret_key in the environment.
Create a folder named
abc_assembly
and it have the config.json file.But when I try to create the urdf using the following command
onshape-to-robot abc_assembly
After adding some parts in the tree,the following Resource not found error comes up every time for a particular part.
I consider all the possibilities of failure.
Don't know what's going wrong.Because it is successfully generating urdf for the other onshape document.
The text was updated successfully, but these errors were encountered: