Continuous Torque Measuring
Has anyone had success in creating RAPID code for RW 5.15.XX that continuously measures motor torque?
In this facility it has been requested to continuously monitor torque on multiple systems that are exclusively non-TCP (i.e. external axes only) for up to 14 axes simultaneously, or perhaps in serial fashion.
As a foreground task the procedures with the TestSignDefine instruction and TestSignRead function has worked on a single axis. However when converted to a background task it is inevitable that a Use TestSignDefine to define a signal to the channel. 40779 error will result. That unexpected undefined signal –which IS defined– error seems related to timing. And this happens with only a single axis monitored.
TuneMaster Log Signals and Test Signal Viewer are not options because they are manually activated and cataloging result history is problematic. Additionally logging overflow is a regularly occurring problem.
Any suggestions would be welcomed.
-=THANKS=-
In this facility it has been requested to continuously monitor torque on multiple systems that are exclusively non-TCP (i.e. external axes only) for up to 14 axes simultaneously, or perhaps in serial fashion.
As a foreground task the procedures with the TestSignDefine instruction and TestSignRead function has worked on a single axis. However when converted to a background task it is inevitable that a Use TestSignDefine to define a signal to the channel. 40779 error will result. That unexpected undefined signal –which IS defined– error seems related to timing. And this happens with only a single axis monitored.
TuneMaster Log Signals and Test Signal Viewer are not options because they are manually activated and cataloging result history is problematic. Additionally logging overflow is a regularly occurring problem.
Any suggestions would be welcomed.
-=THANKS=-
Tagged:
0
Comments
-
Hallo,do you have any messages in event-log under topic "internal" when this error occurs?Sometimes it gives some more clues.0
-
No those dreaded internal errors have not been found.
What has worked is a delay between defining the test signal and use of the function:TestSignReset;TestSignDefine 1,9,mech_unit,3,0.001;WaitTime nSigDelay;nTriggerVal:=TestSignRead(1);0
Categories
- All Categories
- 5.5K RobotStudio
- 394 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 249 ScreenMaker
- 2.7K Robot Controller
- 309 IRC5
- 59 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 785 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 4 Job listings