April 24, 2019, 10:23:29 PM
Robotforum | Industrial Robots Community

 Bulls Eye - BEToolNotFound after BESetupToolJ

Author Topic:  Bulls Eye - BEToolNotFound after BESetupToolJ  (Read 323 times)

0 Members and 1 Guest are viewing this topic.

January 30, 2019, 08:54:43 PM
Read 323 times
Offline

Deniska


Hi,

The Bulls Eye is completed in manual mode.
If i try BECheckTCP or BEUpdateTCP, it doesn't work. The tool is the same.
I have BEToolNotFound 6. Tool is not in collection.
But if i look BE_Data_T_ROB1.sys file, there is my tool added.

Do you have any ideas ?
Thank you

Today at 10:23:29 PM
Reply #1

Advertisement

Guest

February 05, 2019, 01:20:02 PM
Reply #1
Offline

LEC2016


Do you have be_device and be_scan setup?

February 05, 2019, 01:22:40 PM
Reply #2
Offline

Lemster68


Is the tooldata declaration global?

February 07, 2019, 05:30:50 PM
Reply #3
Offline

Deniska



February 07, 2019, 06:12:12 PM
Reply #4
Offline

Deniska


If I've found good thing...
I have the BE_Data_T_ROB1 file and inside I have two lines like this :

LOCAL CONST be_device DeviceList{5}:=...;
LOCAL CONST be_setup SetupList{5}:=...;

last of this lines contains the name of my tool after BESetupToolJ.
I still need to resolve this problem

Thank you

February 08, 2019, 11:26:05 AM
Reply #5
Offline

LEC2016


I've never seen bulls eye set up this way. Post your File....

February 09, 2019, 04:19:24 PM
Reply #6
Offline

chivikoko



Today at 10:23:29 PM
Reply #7

Advertisement

Guest

February 10, 2019, 03:34:38 PM
Reply #7
Offline

SAABoholic


Make sure your tooldata is declared as Task persistent.

i.e.    TASK PERS tooldata tWeldGun:=[TRUE,[[126.634,-1.06616,384.948],[0.895829,0.000883905,0.444388,0.00309824]],[1,[1,0,0],[1,0,0,0],0,0,0]];

@Chivikoko - BullsEye is an automatic TCP calibration tool mainly used in ArcWelding applications.


Share via facebook Share via linkedin Share via pinterest Share via reddit Share via twitter