Variable object Connected event is triggered, call variable.ReadValue() method to synchronise the PLC value; but Variable.Error event is triggered, throwing ErrorCode: 14 SYSTEM: Not enough system non-cyclic objects;
We need to understand: what does this alarm mean? Why is it thrown? What is the impact and how to solve this alarm;
I think you need to provide better description like what you are doing, what tool you used for that and what is source of this error output. Otherwise we can only guess.
it looks like @boyu.zhu is working with PviServices and gets an error event now.
But the error numbers are from the old PSOS os which was the base of SG3 targets.
So I suppose he is in the wrong documentation chapter.
@boyu.zhu :
Probably you get the error number from a callback like this ?
Hello, yes, I am using PviServices, but during the use Visual Studio reports an error, we call the variable.ReadValue() method to synchronize the PLC value after the Variable object Connected event is triggered; but then the Variable.Error event is triggered, the ErrorCode: 14 SYSTEM: Not enough system non-cyclic objects;
Thank you for your reply, what I mean is that when variable connected is performed and then I call the variables read function in the process to read the corresponding variable, an error is reported: ErrorCode: 14 SYSTEM: Not enough system non-cyclic objects;
We need to understand: what does this alarm mean? Why is it thrown? What are the implications and how to resolve it?
honestly, it looks like you are on the wrong track.
‘Not enough system non-cyclic objects’ is not a message from PVI services.
Instead it is a message that can only occur when you are working with old B&R PLC based on Motorola processors. But even with them I would not expect to get the message in PviServices program.
Thanks for your reply, this error does not affect the use of PVI services, I would like to know what is the effect of this alarm and how to get rid of this alarm.
I would like to know what is the effect of this alarm
I think you need to give us a little more information about where exactly this error text occurs in your program. Try catching the exception via a breakpoint and reading the exception text.
The error message you posted comes from very old documentation and makes no sense in this context.