Thank you, the problem was solved by itself. I do not know what happened, but today, after the restarts, everything is fine. Both TCP Check and TCP Update are processed without problems. Mystic.
Posts by 0b1rg
-
-
Hello,
sys.cfg autoload data contains:
#
CAB_TASK_MODULES:-File "HOME:/user.sys" -ModName "user" -AllTask
-File "RELEASE:/options/gtpusdk/ScreenMaker.sys" -ModName "ScreenMaker"\
-AllTask -Hidden-File "HOME:/ApplSys/ROB1/BE_User.sys" -ModName "BE_User" -Task "T_ROB1"
-File "RELEASE:/Options/BullsEye/code/BE_Mnu.sys" -ModName "BE_Mnu"\
-Task "T_ROB1"-File "HOME:/ApplSys/GoSafeUsr.sys" -ModName "GoSafeUsr" -Task "T_ROB1"
-File "HOME:/ApplSys/GoSafeEEv.sys" -ModName "GoSafeEEv" -Task "T_ROB1"
-File "HOME:/ApplSys/GoSafeDataR1.sys" -ModName "GoSafeData"\
-Task "T_ROB1"-File "HOME:/ApplSys/GoSafeMnuR1.sys" -ModName "GoSafeMnu" -Task "T_ROB1"
-File "HOME:/ApplSys/gapMain.mod" -ModName "gapMain" -Task "T_ROB1"
-File "HOME:/ApplSys/PartP1.mod" -ModName "PartP1" -Task "T_ROB1"
-Task "T_ROB1"
===
BE_User.sys contains correct tool "tWeldGun"
-
New data: after passing through TCP Setup, TCP Check and TCP Update are executed. But after restarting the controller, TCP Check cannot be performed.
Something happens after restarting the controller. -
LEC2016
Thanks for your reply. The sensor is clean. The fact is that after the controller is restarted, the robot "loses" the tool. When you call TCP Check or TCP Update, the robot does not even move to BullsEye from the Home Position, but immediately displays the message:«BullsEye Status
BullsEye could not find information about the requested tool. Try re-initializing the tool. Returning to main program…»
-
Hello,
I have the same problem.
When i calling TCP Check or TCP Update routines, robot doesn't move to TSC.
FlexPendant message: BullsEye couldn't find information about the requested tool. Try re-initializing the tool...I already did TCP update. But it takes some time after full initialization, in the latter case - 1.5 hours and the tool again does not pass TCP Check and TCP Update and again writes a message.
Any ideas?