Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Error retrieving position from Yaskawa Motoman robot with external axes

#1
Dear RoboDK,
I attempted to retrieve the robot's position while connected to an external axis, but encountered the attached error. Could you please help me identify the cause of this issue?

Error message: Data transmission failure (error code = -1)

Thank you for your support


Attached Files Thumbnail(s)
外部軸設定.png    外部軸同期後のポジション取得ログ.png   
#2
Did you synchronize your external axes with the robot arm?

Did you provide the correct pulses/degree ratio for the arm and also the external axis?

Can you share the RoboDK project file?
#3
Dear Albert,
Thank you for your support.
I'm sending the RoboDK file.
Please confirm.

Manami.


Attached Files
.rdk   KisarasuLab_20250926.rdk (Size: 5.76 MB / Downloads: 13)
#4
I understand you have a 6-axis robot arm synchronized with 1 axis rail. You may need to properly configure the motion group of your external axes.

When you start the driver you can find additional configuration parameters for your driver in an INI file located in your AppData folder:
C:/Users/username/AppData/Roaming/RoboDK-Drivers/MotomanHSE.exe.ini

More specifically, I recommend you to change these settings:
Code:
Debug_Print=false <- Set it to true for more debug information
AXIS_EX_CONTROL_GROUP=1 <- you may need to set it to 2
AXIS_EX_CONTROL_IS_BASE=false
ROBOT_CONTROL_GROUP=1
#5
Hi, Albert

Thank you for your response.

Please find attached the data summarizing the results of the instructions you provided.
If you notice anything unusual or have further suggestions based on the attached data, we would greatly appreciate your guidance.

Kind Regards,
Hiroe Ota


Attached Files
.xlsx   Results_configuration parameter setting.xlsx (Size: 450.02 KB / Downloads: 11)
#6
Hi, Albert

We have received confirmation that the error has been resolved.
Please proceed to close this thread.

I appreciate your support.

Hiroe Ota
#7
Dear Ota,
Excellent! Thank you for letting us know.
I'm happy to hear this issue has been resolved.
Albert
  




Users browsing this thread:
1 Guest(s)