Cannot access internal signals nor "panel" signals
sikilde
✭
Hello!
I tried to deploy a project that is working on a older robot(with a older SDK) into a new robot with RW 6.03(newer SDK) today, which didn't work completely..
I'm using the "Panel" signal "MAN1" to deactivate a button, and this is working on the older robot, but when I started the project on the TP it said that "MAN1" were not found.. Same goes for some other custom signals that were set to INTERNAL.
The old robot had SDK 6.1.1010.1, while the new one have 6.3.140.
Anyone have any idea on what that could have changed? Or is it a setting somewhere allowing the SM to access signals that are internal or ReadOnly?
I tried to deploy a project that is working on a older robot(with a older SDK) into a new robot with RW 6.03(newer SDK) today, which didn't work completely..
I'm using the "Panel" signal "MAN1" to deactivate a button, and this is working on the older robot, but when I started the project on the TP it said that "MAN1" were not found.. Same goes for some other custom signals that were set to INTERNAL.
The old robot had SDK 6.1.1010.1, while the new one have 6.3.140.
Anyone have any idea on what that could have changed? Or is it a setting somewhere allowing the SM to access signals that are internal or ReadOnly?
0
Categories
- 10.4K All Categories
- 5.3K RobotStudio
- 351 UpFeed
- 15 Tutorials
- 9 RobotApps
- 282 PowerPacs
- 404 RobotStudio S4
- 1.8K Developer Tools
- 239 ScreenMaker
- 2.6K Robot Controller
- 251 IRC5
- 36 OmniCore
- 6 RCS (Realistic Controller Simulation)
- 3 RobotStudio AR Viewer
- 702 RAPID Programming
- 14 Wizard Easy Programming
- 107 Collaborative Robots
- 3 Job listings