Forum Migration Notice
Update (2026-01-12): The user forums will be put into read-only mode on the 21st of January, 00:00 CET, to prepare for the data migration.

We're transitioning to a more modern community platform by beginning of next year. Learn about the upcoming changes and what to expect.

Cannot access internal signals nor "panel" signals

sikilde
sikilde ✭
edited June 2016 in ScreenMaker
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?

Categories