Is the ACE Scheduler running on the same machine as the PI Server? Assuming you have trust configured for the ACE Scheduler on the PI server, you probably want to verify which user is ACE Scheduler trusted as and if the user has the appropriate privilege for Point Security and Data Security.
Seems to me like it could be some unexpected error during runtime as well. Perhaps you can add debug messages into the ACE program, writing them into message log using LogPIACEMessage(MessageType, Message, FullACEContextPath). This function will write the message into message log on the ACE Scheduler.
You can use mlUserMessage for MessageType and modify Debug Level in ACE Manager to include User Message. This way you can have additional messages to monitor the program execution in runtime, and turn off when you are done troubleshooting.
I will look for the logging functions.
Meanwhile, I did s short test: I created a very simple job.
I created the point using the wizard for a new job.
There is the job:
Public Class TestAce
Private TESTFR As PIACEPoint
' Tag Name/VB Variable Name Correspondence Table
' Tag Name VB Variable Name
' TESTFR TESTFR
Public Overrides Sub ACECalculations()
TESTFR.Value = 3
Protected Overrides Sub InitializePIACEPoints()
TESTFR = GetPIACEPoint("TESTFR")
' User-written module dependent initialization code
Protected Overrides Sub ModuleDependentInitialization()
' User-written module dependent termination code
Protected Overrides Sub ModuleDependentTermination()
PI-ACE running on same machine as the PI Server 2010. PI-ACE 2010 Beta. The service is running under an admin user. This user is define in the security mapping as part of the piadmins group.
Might sound like a no-brainer, but are you sure you defined point TESTFR as an Output point? Also, can't you see anything related to security or archive errors in the PI Server Message Log?
As a last note, keep in mind PI ACE 2010 is in Beta form so I would recommend you contact email@example.com instead, such that they can determine whether it's a bug and fix it if it is. I'm sure you know that already, but that also means this should not be used in a Production environment...
The other simple issue is to made sure the ACEScheduler is running, if it is not no data is sent to PI.