Debugging custom analysis tools in visual basic – Rockwell Automation FactoryTalk Historian Classic User Guide User Manual
Page 142

Chapter 7 Creating RSBizWare Custom Analysis Tools
Your report object should look like this:
If the name of your custom analysis tool in the Configuration
Console is not what you expected (MyDemo.NegativeCalculator),
then you may not have renamed the default project or class name in
the Visual Basic project. If you did not rename these, then your
analysis tool may be named Project1.Class1. You can go back to
Visual Basic, change the names, and recompile your project. Then
when you unregister and register the custom analysis tool in the
Configuration Console, the name should show up correctly.
You may find that a custom analysis tool that you develop does not
calculate as expected on the first try. When custom analysis tools are
producing incorrect values, the easiest way to find the problem is to
debug them with the Visual Basic debugger.
To set the debugger up, do the following:
1. Access the Visual Basic project settings for your custom
analysis tool under Visual Basic's Project menu item and select
the Debugging tab.
2. Select the Start program option, select the Configuration
Console executable (\Program Files\Rockwell
Software\RSBizWare\RSBizWare Production Client.exe)
as the program to run when the debugger starts, and click OK.
Debugging Custom Analysis
Tools in Visual Basic
142
Rockwell Automation Publication HIST-UM001K-EN-E-June 2014