05-10-2024, 04:18 PM
(This post was last modified: 05-10-2024, 04:39 PM by PythomSpace.)
(05-07-2024, 03:19 PM)Sergei Wrote: It is necessary to use names such as 'Tool 1' and 'Frame 1' considering the specifics of this postprocessor:
The result will be as follows:
Code:"action":800,"coordID":1,"coordName":"Frame 1","insertedIndex":1,"customName":""
"action":801,"toolID":1,"toolName":"Tool 1","insertedIndex":2,"customName":""
Also, I added the "customName":"" field
The .rdkp package with the updated postprocessor is attached
Testing out a bit more here is what i noticed.
For the variable "toolCoord" in the actions the borunte post processor sets it to the same as the "toolID" so it looks like this "toolCoord":1 in the output from roboDK if I use "Tool 1"
when I load the program on the teaching pendant it sets the tool and frame correctly for Tool 1 and Frame 1. it also works fine using Free Path actions to have "toolCoord":1 but for the Line3d-Pose actions it does not find the tool and I still have to edit them manually to set them to Tool 1. The Frame is working correctly I only have to manually set them to tool to Tool 1.
After I save and export the changes from the teaching pendant the toolCoord now shows as "toolCoord":65537 for the Line3d-Pose actions. I am not sure where it gets the 65537 number from but it seems to need to use that for the program to run correctly on the robot arm using Frame 1 and Tool 1
Hers is the RoboDK Station I used to create the program
toolCoordTest.rdk (Size: 1.43 MB / Downloads: 370)
Here is the output from RoboDk
toolCoord_RoboDK.zip (Size: 4.25 KB / Downloads: 315)
Here is the export back from the teaching pendant after the tool was selected and set manually
toolCoord_Pendant.zip (Size: 1.31 KB / Downloads: 307)
Thanks for all your help with the post processor.

