I have done my first FP GUI for the real production robot. It was pretty simple for a newbie like me. Thanks for the new features of 5.08 release !
It was easy to access RAPID and create NumPad for user inputs. It was fast and simple to read/write robot variables with data binding, but…
The most simple thing on the GUI - add PictureBox does not work on on my solution :worried: Is there something I did not catch on the manual that should aware of ??
If I just create an empty view and test it on FP it works, but when I add just one simple picture ( using System.Windows.Forms.PictureBox) it does not start on FP anymore.
Is it on the Virtual FlexPendant that you have this problem? There is a remaining problem in 5.08 on the Virtual FlexPendant that causes the problem that you describe. On the real FlexPendant I have not heard of any problems of this kind. (Please let me know if it is a real FP)
For the Virtual FlexPendant the easiest workaround is to remove the last parameter of the TpsView attribute. The default is Manual, so it won’t make any difference if it is an application meant to be started from the ABB menu.
The problem is documented in an RSI like this: "There is a remaining problem on the Virtual FlexPendant resulting in a CustomAttributeFormatException exception.The problem occurs when the SDK application is built towards a different revision compared to the one running. The problem is related to embedded images.
There are a number of work-arounds:
Recompile the SDK application towards a Robot Application Builder with the same revision number as the running system.
Remove the StartupType assembly attribute assignment in the SDK TpsView header, i.e., for the TpsView remove StartupType = TpsViewStartupTypes…)"
Everything you said was correct I tested the example on real controller and it started up with picture - without errors.
I used the workaround #2. I removed the parameter of the TpsView attribute. And now it is running on RS also. For debugging I am using RS 5.08 BETA, with RW 5.08.1005.1, but lets wait the official release of RS and try the workaround #1 later…
Sorry, that I have not read the RSI carefully enoght, but as a punishment that caused me two days struggling with the stupid errors